Restoring Configuration Data

If eReplication encounters anomalies after an upgrade or key data adjustment, you can import the backed up system configuration data to eReplication to implement restoration.

Prerequisites

The data encryption password configured during configuration data backup has been obtained.
A cross-platform file transfer tool, such as WinSCP, has been installed.
A cross-platform remote access tool, such as PuTTY, has been obtained.
The login password of user root or DRManager in Linux.

The version of the backed up configuration data must be consistent with the current software version. Otherwise, protection or restoration services may become abnormal.
eReplication has been stopped before backup data is imported. After eReplication is stopped, you cannot use eReplication to perform DR management. Stop eReplication only for fault diagnosis.
In active/standby mode, perform the import operation on both the active and standby ends.

Context

After restoration, data generated between the backup point in time to the restoration point in time is lost.
After restoration, data on eReplication may become inconsistent with that on storage devices, hosts, vCenter servers, FusionCompute. The system automatically checks data consistency. Alarms are reported if data inconsistency is detected. You can troubleshoot the problem based on reported alarms.

Procedure

Import backup data in Linux.
1. Use WinSCP to copy the exported backup file ConfigData.zip or DataBackUp.zip to /home/DRManager directory on the eReplication Server.
  
  The following describes the procedure of exporting the ConfigData.zip file. In actual scenarios, export the file of the desired name.
  
  Run the chmod 750 /home/DRManager;chown :LEGO /home/DRManager/ConfigData.zip;chmod 640 /home/DRManager/ConfigData.zip command to modify the permission.
2. Use PuTTY to log in to the eReplication management server.
  In software package-based installation mode: Log in as user root.
3. Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.
  
  After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run exit to exit the system after completing your operations.
4. Run cd /opt/BCManager/Runtime/bin to enter the path.
  
  In Linux, the installation path of eReplication is /opt/BCManager. The path is fixed.
5. Run the sh shutdownSystem.sh command, enter y and press Enter to stop eReplication.
  eReplication is stopped successfully if the following command output is displayed:
```
The DR system is shut down successfully.
```
  Before proceeding to the next step, ensure that eReplication is stopped.
6. Run the sh import.sh command to import backup data.
7. After ensuring that eReplication is stopped, type y in the prompt message and press Enter.
  The following command output is displayed:
```
Please input the restore file:
```
8. Enter the save path of the backup data to be imported as prompted and press Enter. For example, the save path can be /home/DRManager/ConfigData.zip.
  The following command output is displayed:
```
Please input old encrypt password:
```
9. Enter the data encryption password that is configured during the backup data export and press Enter.
  Backup data is imported successfully if the following command output is displayed:
```
restore successfully. Please restart the Server.
```
10. Run the sh startSystem.sh command to start the eReplication.
  eReplication is started successfully if the following command output is displayed:
```
System started completely.
```