Restoring Configuration Data

If UltraVR encounters anomalies after an upgrade or key data adjustment, you can import the backed up system configuration data to UltraVR 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 has been obtained.

The version of the backed up configuration data must be consistent with the current software version. Otherwise, protection or restoration services may become abnormal.
UltraVR has been stopped before backup data is imported. After UltraVR is stopped, you cannot use UltraVR to perform DR management. Stop UltraVR only for fault diagnosis.

Context

If the original management server is configured with a remote management server, modify the information about the remote management server on the current management server after the backup data of the original management server is imported into the current management server. Otherwise, exceptions may occur during service operation. For example, A and B are the original management servers and are the local and remote management servers of each other. C and D are the current management servers and are the local and remote management servers of each other. After the backup data of A and B is imported into C and D respectively, you must change the remote management servers on C and D to D and C respectively.

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

Procedure

Use WinSCP to copy the exported backup file ConfigData.zip to any directory on the UltraVR, for example, /home/configdata.
Use PuTTY to log in to the UltraVR management server as user root.
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.
Run cd /opt/UltraVR/Runtime/bin to enter the path.

In Linux, the installation path of UltraVR is /opt/UltraVR. The path is fixed.
Run the sh shutdownSystem.sh command to stop UltraVR.
UltraVR is stopped successfully if the following command output is displayed:
```
System is shut down successfully.
```
Before proceeding to the next step, ensure that UltraVR is stopped.
Run the sh import.sh command to import backup data.
After ensuring that UltraVR is stopped, type y in the prompt message and press Enter.
The following command output is displayed:
```
Please input the restore file:
```
Enter the save path of the backup data to be imported as prompted and press Enter. For example, the save path can be /home/configdata/ConfigData.zip.
The following command output is displayed:
```
Please input old encrypt password:
```
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.
```
Run the sh startSystem.sh command to start the UltraVR.
UltraVR is started successfully if the following command output is displayed:
```
System started completely.
```