There will be an option to add custom configurations that we want to back up, like show cdp neig, show ip route, show log, or any other we want to backup?
actually the tool only backup running config and show vlan brief
thanks
[Fixed in 2.5.0] custom configurations
Hi,
We are definitely planning to add this.
You will be able to specify additional commands to run during backup.
We are also planning to add possibility to backup additional files on top of config.
Some vendors for example store certificates separately, and only reference them in the configuration.
All of this would also be configurable.
As to when this will be implemented - I would guess Q3-Q4 2018.
We are definitely planning to add this.
You will be able to specify additional commands to run during backup.
We are also planning to add possibility to backup additional files on top of config.
Some vendors for example store certificates separately, and only reference them in the configuration.
All of this would also be configurable.
As to when this will be implemented - I would guess Q3-Q4 2018.
-
Vik@Unimus
- Posts: 198
- Joined: Thu Aug 05, 2021 6:35 pm
Unfortunately, this development has been postponed due to technical complexity of the solution. This is one of developments we want to prioritize (not for our next major release 2.4.0, though) as there were some recent cases of customers who would prefer different backup command(s) altogether fitting better for their sometimes specific needs and this development is the right way to handle all of this (and more)
I am adding this thread to our internal ticket and once we have some updates, we will add it here, too.
I am adding this thread to our internal ticket and once we have some updates, we will add it here, too.
Hi everyone, just wanted to update this topic that this is now possible with the addition of Custom Backup Flows in the 2.5.0 release.
Full info on Custom Backups Flows specifically is here: https://blog.unimus.net/custom-backup-f ... nimus-2-5/
More info on the full 2.5.0 release here: viewtopic.php?f=3&t=1819
Hi,
Just tested this feature, and I have to say that it is more than welcome. Good work!
I have a few questions regarding the setup. I think I am doing it correctly, and if so it is a bit cumbersome to work with in the use case we have. Our use case is to backup multiple VDOMs (>200) from a Fortigate firewall.
Before this feature the entire config (> 800000 lines) is stored in a single backup object. This caused the Diff for example more or less useless. It was very hard to find out in which VDOM changes had been made.
We started to look at splitting this up with an external script and then import the individual VDOM configs into separate objects in Unimus, but then this feature came along
My understanding is that we need to create a zone and a tag for each VDOM in order to use this. Manageable, but cumbersome. Also only feasible with embedded zones.
Here´s how I configured it:
I already have a device backing up the entire config. That is kept as is. Lets say this has IP 10.10.10.10.
In order to create another device with the same IP, I need to place it in a different zone. I created a couple of zones, example names VDOM1, VDOM2, VDOM3. I also created tags with the same names, and associated them with the corresponding zone. In addition, I created a tag named "shared fortigate" used to minimize the risk of the flows I will create later being used on incorrect devices.
I created device 10.10.10.10 in each of the three new zones.
I created three flows, tagged with one of the VDOM names and with tag "shared fortigate". The flows are configured with "config vdom", "edit <corresponding VDOM>", "show full-configuration".
Then I ran backup on the three new devices and verified the outcome. Works great!
Provided I understood this correctly I am sure you can see that there is quite a lot work work involved here It can be automated, haven't yet looked if there are API methods for flows but even if they are not there yet it can be done with direct db access.
But once again, a lot of work
Then there is the amount of zones required, and the fact that it is not feasible to use remote cores for more than one zone, forcing us to use embedded core. Not a big issue for us, but could be for others.
I am thinking if a future enhancement could be to have a way to allow duplicate devices inside a zone? Maybe a flow can be assigned during creation and when a device has a flow it is allowed to have duplicates?
Also (just thinking out loud) maybe a way to use variables in a flow so that we can define all the VDOM names somewhere and utilize the same flow on all of them. I understand the complications, like I said just thinking out loud
Thanks again for this feature!
Kind Regards,
//Dan
Just tested this feature, and I have to say that it is more than welcome. Good work!
I have a few questions regarding the setup. I think I am doing it correctly, and if so it is a bit cumbersome to work with in the use case we have. Our use case is to backup multiple VDOMs (>200) from a Fortigate firewall.
Before this feature the entire config (> 800000 lines) is stored in a single backup object. This caused the Diff for example more or less useless. It was very hard to find out in which VDOM changes had been made.
We started to look at splitting this up with an external script and then import the individual VDOM configs into separate objects in Unimus, but then this feature came along
My understanding is that we need to create a zone and a tag for each VDOM in order to use this. Manageable, but cumbersome. Also only feasible with embedded zones.
Here´s how I configured it:
I already have a device backing up the entire config. That is kept as is. Lets say this has IP 10.10.10.10.
In order to create another device with the same IP, I need to place it in a different zone. I created a couple of zones, example names VDOM1, VDOM2, VDOM3. I also created tags with the same names, and associated them with the corresponding zone. In addition, I created a tag named "shared fortigate" used to minimize the risk of the flows I will create later being used on incorrect devices.
I created device 10.10.10.10 in each of the three new zones.
I created three flows, tagged with one of the VDOM names and with tag "shared fortigate". The flows are configured with "config vdom", "edit <corresponding VDOM>", "show full-configuration".
Then I ran backup on the three new devices and verified the outcome. Works great!
Provided I understood this correctly I am sure you can see that there is quite a lot work work involved here It can be automated, haven't yet looked if there are API methods for flows but even if they are not there yet it can be done with direct db access.
But once again, a lot of work
Then there is the amount of zones required, and the fact that it is not feasible to use remote cores for more than one zone, forcing us to use embedded core. Not a big issue for us, but could be for others.
I am thinking if a future enhancement could be to have a way to allow duplicate devices inside a zone? Maybe a flow can be assigned during creation and when a device has a flow it is allowed to have duplicates?
Also (just thinking out loud) maybe a way to use variables in a flow so that we can define all the VDOM names somewhere and utilize the same flow on all of them. I understand the complications, like I said just thinking out loud
Thanks again for this feature!
Kind Regards,
//Dan