Device backup for the 1st time - Suggestion

Question

We currently have a nightly job that backs up our devices.  What I'm seeing (and have been since day one with Cirrus) is Cirrus doesn't understand that a configuration is missing (from the db) and needs to back it up.  So when you add a device the 1st night when this backup job is running Cirrus should see no backup is present and therefore make a backup of the config.  So what we have to do is when we had a device we run the download device config manually to get the initial config in the db and then Cirrus takes it from there.  It would be nice that Cirrus recognized this and backed it up the 1st time.

On a related note.  Be default all nodes in the node list are shown with a '+" so you'd expect there are nested configs there.  But in the above case a new device will show the '+' but nothing is under it.  Now when you click the '+' on that node it goes away.  Another suggestion is to not display that '+' sign if nothing is present underneath the node.

BB

BryanBecker · Answer

We have a nightly job that's set up for the following :

* All nodes in the database
* Only save configs that have changed is checked

It works fine for devices that already have 1 backup in the database.  But for a brand new device that is added the backup job will not back the config up until I manually get the 1st backup in there.  I'm running 3.5.1 also.

BB

Haley · Answer

We are unable to duplicate the 1st scenario described above.  The tested scenarios on Cirrus 3.5.1 are as follows: 1. Add device to existing Cirrus database. (telnet/telnet or snmp/tftp) 
2. Add device to new or default Cirrus Backup job
3. Specify to backup the running config within the Backup job.
4. Do not compare, compare to baseline, and compare to last config.
5. “Only Save configs that have changed” was checked and unchecked.
6. Start the job.
7. Remove the device and try another combination of the settings specified above.
Each time the jobs ran as expected.  The running config was downloaded and saved as the only config under the device.   
Please describe your Backup job settings so we can continue to test the issue.  
For scenario 2, we are able to duplicate that a plus sign is listed before a device when the node list is displayed regardless of whether a configuration has been downloaded.  I have posted this issue and it will be resolved in an upcoming release.