When you restore a backup, you are restoring the state of the NSX Intelligence configuration at the time the backup was made. You can restore an NSX Intelligence backup using a CLI command.
You must restore a backup on an installation of the NSX Intelligence appliance that is the same version as the backup you are restoring. By default, the backup file restored is the most recently generated backup. If you are restoring a backup to a newly installed NSX Intelligence appliance, set the archive name before restoring the backup.
- Verify that you have the admin login credentials and host info for the backup file server.
- Ensure that you have an admin access to the NSX Intelligence CLI.
- Log in with admin privileges to the new NSX Intelligence CLI server.
- Configure the remote server where the backups are located.
The command syntax is
set restore remote-host backup_server_IP_address remote-path remote_folder_path remote-host-username remote_host_username remote-host-password remote_host_password passphrase pass_phrasewhere the backup_server_IP_address is the remote host IP or FQDN address of the backup file server, remote_host_username account must have the necessary privileges to access the backup files in the remote_folder_path. For example,
set restore remote-host 10.11.22.33 remote-path /root remote-host-username root remote-host-password MyRemotePassword passphrase MyPassPhra$e
- Verify the restore configuration.
get configurationFrom the output, verify that the line with set restore looks correct. Using the example in the previous step, the output must include the following line.
set restore remote-host 10.11.22.33 remote-path /root remote-host-username root
- Restore the backup with the following command.
restore intelligence configurationIf the restoration is successful, you see a message similar to the following.
NSX Intelligence Restore Complete.
- You can view the progress of the backup restore using another CLI session.
- Log in to another NSX Intelligence CLI session.
- Enter the following command.
get log-file node-mgmt.log follow