Disaster recovery in SnapCenter
The SnapCenter disaster recovery (DR) feature lets you recover from disasters like resource corruption or server crashes. It helps to restore the SnapCenter repository, server schedules, configuration components, and the SnapCenter Plug-in for SQL Server and its storage.
This section explains the two types of DR in SnapCenter:
SnapCenter Server DR
-
SnapCenter Server data is backed up and can be recovered without any plug-in added to or managed by the SnapCenter Server.
-
Secondary SnapCenter Server should be installed on the same installation directory and on the same port as the primary SnapCenter Server.
-
For Multi-factor authentication (MFA), during SnapCenter Server DR, close all the browser tabs and reopen a browser to log in again. This will clear the existing or active session cookies and update that the correct configuration data.
-
SnapCenter disaster recovery functionality uses REST APIs to backup the SnapCenter Server. See REST API workflows for disaster recovery of SnapCenter Server.
-
Audit settings-related configuration file is not backed up in DR backup and neither on the DR server after the restore operation. You should manually repeat the Audit log settings.
SnapCenter Plug-in and Storage DR
DR is available only for SnapCenter Plug-in for SQL Server. If the plug-in is down, switch to another SQL host and recover the data by following a few steps. See Disaster recovery of SnapCenter Plug-in for SQL Server.
SnapCenter uses ONTAP SnapMirror to replicate data, which can be used for DR by keeping data synchronized at to a secondary site. To initiate failover, break the SnapMirror replication. During fallback, reverse the synchronization to replicate data from the DR site back to the primary location.