Disaster recovery (DR) REST APIs
Suggest changes
PDFs
SnapCenter disaster recovery (DR) functionality uses REST APIs to backup SnapCenter Server. Perform the following steps before using the DR REST APIs.
Steps
-
Create a new Server DR backup, which restores a SnapCenter Server from a specified Server DR backup using DR Backup REST API:
/4.5/disasterrecovery/server/backup -
Bring up the secondary server machine, but before installing the SnapCenter Server on the secondary server you should complete the prerequisites.
-
The alternate server host name/Host FQDN should be same as the primary server host name, but the IP address can be different.
-
Secondary server version should be the same as the primary server.
-
Secondary SnapCenter should be installed on the same location and on same port as primary.
-
-
Before triggering the server DR restore operation, you should bring up the target path or the path where the DR backups are stored after the disaster.
-
Ensure that the DR backup files are copied to the new SnapCenter Server using the following command:
xcopy <Ssource_Path> \\<Destination_Server_IP>\<Folder_Path> /O /X /E /H /K {ex : xcopy C:\DRBackup \\10.225.81.114\c$\DRBackup /O /X /E /H /K}
-
-
Install SnapCenter Server on the secondary machine.
-
While performing the DR restore operation, you should ensure that no jobs are running related to the SnapCenter Server.
-
-
Install the secondary SnapCenter Server in the same location and on the same port as primary server.
-
Perform server DR restore operation using the DR restore API:
/4.5/disasterrecovery/server/restoreIf the plug-in is not able to resolve the server hostname, log in to each of the plug-in host and add the etc/host entry for the new IP in the <New IP> SC_Server_Name format. For example,
10.225.81.35 SCServer1The server etc/host entries will not be restored. You can restore it manually from the DR backup folder.
-
|
For an F5 setup, restore operation is performed as stand-alone, you should run a set of commands to create the F5 again. See, Link: How to migrate SnapCenter to another server |
|
|
After DR restore, the host will be added but you should install the plug-in manually. |
|
|
Repository backup schedule will be restored only if you install the SnapCenter Plug-in for Windows and attach NetApp LUN to the server machine. |
|
|
If the DLLs are corrupt, you can attempt to repair SnapCenter Server or correct the faulty installation. |
|
|
If NSM or config files are corrupt, you can uninstall and reinstall the SnapCenter Server with the same version. |
|
|
If the VM is corrupt, bring up another VM or a machine with the same name and install SnapCenter Server with the same version. |
REST API supported for disaster recovery of SnapCenter Server
Using REST APIs, you can perform the following operations on the REST APIs Swagger page. For information to access the Swagger page, see How to access REST APIs using the swagger API web page.
-
You should log in as the SnapCenter Admin user.
-
The SnapCenter Server should be up and running to run DR restore API.
-
If the DLLs are corrupt, repair the SnapCenter Server installation.
-
If NSM is corrupt or configuration files are corrupt, uninstall and reinstall the SnapCenter Server with the same version.
-
If the VM is corrupt, bring up another VM with same name and install SnapCenter Server with the same version.
SnapCenter Server DR supports all plug-ins.
| Description | REST API | HTTP method |
|---|---|---|
Fetch existing SnapCenter Server DR backups You should provide the target path where the DR backups are stored. |
|
GET |
Create a new Server DR backup. |
|
POST |
Restores a SnapCenter Server from a specified Server DR backup. |
|
POST |
Delete the Server DR backup based on backup name. |
|
DELETE |
Enable or disable the storage DR |
|
POST |
See the Disaster Recovery APIs video.