Using the NetIM SAVE_RESTORE utility

The SAVE_RESTORE utility 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 normal disaster recovery backup process; however, VM snapshots may be preferred in your setting as a more complete solution.

SAVE_RESTORE should be used only for saving and restoring to the identical release version of NetIM 2.x. for example, save from a NetIM 2.1.0 installation and restore to a NetIM 2.1.0 installation. Using SAVE_RESTORE to back up one version of NetIM and restore to another version of NetIM is not supported.

SAVE_RESTORE allows you to backup and restore the following:

For a list of SAVE_RESTORE limitations, including data and configurations that are not backed up and restored, see SAVE_RESTORE limitations.

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. For more information, see Using SAVE_RESTORE import to create a near-replica of your primary NetIM.

Usage: app.sh SAVE_RESTORE export <path to directory for exporting zip file>

SAVE_RESTORE export does not require stopping NetIM core services and, therefore, 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 writes 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: for example, [email protected].

Usage: app.sh SAVE_RESTORE import <path and filename of zip file to import>

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.

Note the following before executing this command:

• After the import is complete, the SAVE_RESTORE import script restarts all NetIM core services. SAVE_RESTORE does not start/restart swarm services. NetIM swarm services are assumed to be up.

• Any existing NetIM core network model database is erased and replaced with the network model database contained in the zip file you are importing.

You can use SAVE_RESTORE to create a near-replica of your primary NetIM. Once this procedure is completed the first time, 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.

Before you begin, note the following:

• 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 is inaccessible as are all core services, including REST APIs. Additionally, all NetIM product integrations (like the Portal) are also impacted.

• Alerting and notification also continue during the SAVE_RESTORE import process, but are affected when the core model resyncs with the swarm.

2. Execute the SAVE_RESTORE export command on your primary NetIM, as explained in Using SAVE_RESTORE export.

3. Deploy your backup NetIM deployment and setup and start your swarm and core services.

4. Before performing any WebUI-based settings or configuration on the backup NetIM, import all the settings from your primary NetIM, as explained in Using SAVE_RESTORE import to restore from backup.

5. After the import is complete, 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). For more information, see the next section, SAVE_RESTORE limitations.

The following are known limitations of SAVE_RESTORE:

• SAVE_RESTORE backs up and restores most of your primary NetIM configuration settings and model data. However, SAVE_RESTORE does not backup and restore the following:

• Test Engines must be reconfigured to integrate with the restored NetIM if the NetIM’s IP address or hostname is changed.

For example, sender name: [email protected] 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.