SANnav Backup and Restore
SANnav allows you to take backups of the SANnav server data and restore it as required, such as in scenarios where the data is deleted or corrupted. Also, you can use the backup when you want to bring up a new SANnav server. Creating a backup helps to protect the server’s data and configuration in the event of a disaster, such as server failure. You have options to exclude large data sets, which can save restoration time in some situations. You can perform a scheduled daily or weekly backup or an on-demand backup.
Note: The backup option is not supported with the trial license.
Below is the list of core and optional backups in SANnav:
Core Backup (Default)
The default backup file includes core schema in PostgreSQL, Elasticsearch indexes except for events and configuration files.
• Fabric information
• Inventory data
• Server configuration
• Switch asset information
• Zone configuration
Optional Backup
Optional backup files include historical statistics, events from Elasticsearch, and reports.
• Faults event data and reports
• Performance Data
SANnav does not purge older backups. Make sure you check the disk space periodically for successful scheduled backups.
Prerequisites
Ensure that the PostgreSQL and Elasticsearch services are working for a successful backup. For Linux OS the external location should be mounted in the SANnav server to validate the location.
Recommendations for Backup
The recommendations for backup are given below:
• It is recommended to do a full backup on a weekly or monthly basis as the daily backup may slow down the server.
• Make sure your backup location has enough disk space before you backup your data.
• Make sure your backup location is different from the location where the SANnav Management Portal is installed.
• For scheduled backups, it is recommended to check occasionally if the backup data size is having any abnormal pattern like some files are too large or too small.
Parent topic