NCM Configuration Backup retention - how long is too long?

martian_monster

Greetings -

We currently backup all of our networking infrastructure using NCM.  We currently hold all of the configurations for 30 days.  We have had some issues pop up that it would have been good to have some older configurations to compare.  We would like to keep the configurations around for 1 year. 

Will this have an affect on the database?

Or are these files just saved locally and it will not affect the database?

If keeping these files for this long will create some kind of issue can we archive the configurations off someplace to reference later?

Just looking to check with others to see what they do.

Thanks,

Dave

bobmarley

We left the database settings default for storing the configs in the DB, however you can also store older copies in a config archive which is outlined below.

This archive only requires space on a disk drive. We had an additional drive added and write the files there. 

It would be a good practice to copy those over to your disaster recovery repository, so they are available to the Network Teams.

Specify config transfer, comparison, and archive settings (solarwinds.com)