Restoring a backup restores the state of the network at the time of the backup. In addition, the configurations maintained by Global Manager appliances are also restored.
- Verify that you have the login credentials for the backup file server.
- Verify that you have the SSH fingerprint of the backup file server. Only SHA256 hashed ECDSA (256 bit) host key is accepted as a fingerprint.
- Verify that you have the passphrase of the backup file.
- If any nodes in the appliance cluster that you are restoring are online, power them off.
- Install one new appliance node on which to restore the backup.
- If the backup listing for the backup you are restoring contains an IP address, you must deploy the new Global Manager node with the same IP address. Do not configure the node to publish its FQDN.
- If the backup listing for the backup you are restoring contains an FQDN, you must configure the new appliance node with this FQDN and publish the FQDN. Only lowercase FQDN is supported for backup and restore.
- In a web browser, log in to Global Manager at https://gm_vip_fqdn/.
- Make the Global Manager active. You can restore a backup only on an active Global Manager.
- On the main navigation bar, click System.
- In the navigation pane, select Location Manager.
- On the Location Manager page, click Make Active, enter a name for the Global Manager, and click Save.
- On the main navigation bar, click Edit. and then click
- Enter the IP address or FQDN of the backup file server.
- Change the default port if necessary. The default port is 22.
- To log in to the server, enter the user name and password.
- In the Destination Directory text box, enter the absolute directory path where the backups are stored.
- Enter the passphrase that was used to encrypt the backup data.
- Leave the SSH Fingerprint blank and accept the fingerprint provided by the server after you click Save in a later step.
- Select a backup and click Restore.
- The restore process prompts you to take action, if necessary, as it progresses.
- After the restored manager node is up and functional, deploy additional nodes to form a NSX Global Manager cluster.