Using NetIM 2.x’s SAVE_RESTORE Utility
SAVE_RESTORE allows you to perform an on-line backup of most primary settings, as well as, the NetIM Core model from a NetIM 2.0.2 or later version installation. You can use the SAVE_RESTORE utility as part of your Core configuration and model disaster recovery backup process. However, VM backup or snapshots are preferred as a complete backup solution for your entire NetIM 2.x deployment.
You can also use the SAVE_RESTORE utility to keep two NetIM installations in-sync in terms of primary settings, configuration, and some model data. However, VM snapshots may be a preferred solution in your setting.
Riverbed support may also request the output of “SAVE_RESTORE export” as part of a technical support case.
Usage: app.sh SAVE_RESTORE export <path to directory for exporting zip file>
Usage: app.sh SAVE_RESTORE import <path and file name of zip file to import>
Note: The SAVE_RESTORE utility supports partial back up and restore to the same version of NetIM 2.x, that has been upgraded in an identical manner. Using SAVE_RESTORE to backup one version of NetIM and restore to another version of NetIM is not fully supported.
SAVE_RESTORE allows you to backup and restore your NetIM Core model and primary configuration settings including:
· Device and Platform Information
· Global Discovery Settings
· Trap Receiver Credentials
· Groups and Sites
· Auto Grouping Rules
· Device Drivers
· IP Detection Service Settings
· Polling Profiles
· Interface filters
· Business Hours Settings
· Alerts and Notification Settings
· User-Defined Metrics Settings
· Synthetic Tests
· NetProfiler Settings
· Custom Attributes
“SAVE_RESTORE export” does not require stopping NetIM Core services and, hence, requires no downtime to the NetIM system you are backing up. However, we recommend that you perform the export after the completion of any network discovery process or network model refresh process. Additionally, you should refrain from making configuration and settings changes to the NetIM while you are executing a “SAVE_RESTORE export” operation. “SAVE_RESTORE export” creates a zip file in the directory you specify when you execute the command (by default, SAVE_RESTORE will write the backup file to /opt/riverbed/NetIM/op_admin/tmp/vne/configExport). The backup file is named with the date and time of the export, i.e. Jan-31-2020@09-45-29.zip.
Using “SAVE_RESTORE import” to restore from backup
“SAVE_RESTORE import” requires an existing NetIM 2.0.2 or later version deployment in order to import the settings and database you previously exported. “SAVE_RESTORE import” takes, as input, a zip file created by the “SAVE_RESTORE export” command.
IMPORTANT: NetIM Core services are stopped during the “SAVE_RESTORE import” process.
IMPORTANT: Any existing NetIM Core network model database will be erased and replaced with the network model database contained in the zip file you are importing.
IMPORTANT: SAVE_RESTORE should be used only for saving and restoring to the identical release version of NetIM 2.x. i.e., save from a NetIM 2.1.0 installation and restore to a NetIM 2.1.0 installation that has been identical installed and upgraded
Using “SAVE_RESTORE import” to create a near-replica of your primary NetIM
You can use “SAVE_RESTORE” to create a near-replica operating backup from your primary NetIM. First, deploy and configure your primary NetIM and then execute the “SAVE_RESTORE export” command on your primary NetIM. Next, deploy your backup NetIM deployment and setup and start your swarm and core services. Before performing any WebUI-based settings or configuration on the backup NetIM, use the “SAVE_RESTORE import” to import all the settings from your primary NetIM. Finally, use the NetIM wizards and configuration pages to configure remaining settings that are not migrated (this final step only needs to be performed the first time you perform the migration).
You can then use “SAVE_RESTORE export” on your primary NetIM and “SAVE_RESTORE import” on your backup NetIM to keep the primary and backup in sync on a continuing basis.
Note:
· “SAVE_RESTORE import” requires that you plan for some minimal downtime of the NetIM while the import process takes place. NetIM Core services are stopped during the “SAVE_RESTORE import” process.
· During the down time, the NetIM WebUI will be inaccessible as will all Core services, including REST APIs. Additionally, all NetIM product integrations (i.e., Portal) will also be impacted.
· Polling and all swarm services will continue uninterrupted during the import process.
· Alerting and notification will also continue during the “SAVE_RESTORE import” process but will be affected when the Core model resyncs with the swarm.
· Any existing NetIM Core database will be erased and replaced with the database provided in the zip file you are importing.
· After the import is complete, the SAVE_RESTORE import” script will restart all NetIM Core services and resync with the swarm services.
“SAVE_RESTORE” Known Limitations
“SAVE_RESTORE” backs up and restores most of your primary NetIM configuration settings and model data. “SAVE_RESTORE” does not currently backup and restore the following:
· Archived configuration files
· Identity Provider (SAML and SCAS) settings and local users
· User Management - Local users
· Roll-up settings
· SNMP Default Port
· SSH Default Port
· Delay between SSH Session Retries (sec)
· Source Data Difference Detection setting
· Number of Consecutive Failures Required to Indicate a Device is Down
· IP Detection Service’s Resolve IP address using DNS setting
· Scheduled Jobs
· IP Forwarding Tables collection settings
· Report Export Settings
· Test Engines must be re-configured to integrate with the restored NetIM if the NetIM’s IP address or hostname is changed
· Notification sender will be the sender configured in the primary NetIM
o For example, sender name: hostname-primary@riverbed.com would remain the same when settings are restored on a different host system such as hostname-backup
· Any external Links configured on the primary system may stop working if the links pointed to the original system and the system is down
©2021 Riverbed Technology. All rights reserved. Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein may not be used without the prior written consent of Riverbed Technology or their respective owners.