Deployment Environment Requirements

This section describes hardware and software environments required for deploying the maintenance terminal, to ensure that UltraVR can work correctly.

To ensure the stability of DR and backup, you are advised to deploy the UltraVR on an independent server. Note that the UltraVR and the service host cannot be deployed on the same server.
The time zones of the servers where the UltraVR is deployed at the production and DR sites must be the same. In addition, the same time source has been configured, and the time has been synchronized.
To prevent time deviation caused by different time zones, ensure that the time zone of the maintenance accessing UltraVR is the same as that of the server where the UltraVR is deployed.
To deploy the UltraVR on a VM, ensure that the UltraVR exclusively occupies the VM resources.

Maintenance Terminal Requirements

Table 1 describes maintenance terminal requirements.

**Table 1** Maintenance terminal requirements
Item	Requirement
Operating system	Both Chinese and English operating systems are supported.
Browser	Internet Explorer 11 Firefox 95 Chrome 96

UltraVR Deployment Environment Requirements

Table 2 describes their deployment environment requirements.

**Table 2** UltraVR environment specifications
Specifications	Requirement
Operating system	EulerOS release 2.0(SP10)x86_64 EulerOS release 2.0(SP10)aarch64
CPU	Minimum configuration: 2-core 1.6 GHz CPU Standard configuration: 4-core 1.6 GHz CPU or higher
Memory	Minimum configuration: 4 GB DDR Standard configuration: 8 GB DDR or higher NOTE: If the physical memory capacity is 4 GB, the available physical memory capacity must be 2 GB at least. If the physical memory capacity is 8 GB, the available physical memory capacity must be 4 GB at least. If the installation environment is a VM, the VM cannot use dynamic memory allocation. The requirements on swap are as follows: If the memory capacity ranges from 4 GB to 16 GB, the swap value must be the same as the memory capacity. If the memory capacity is greater than 16 GB, the swap value must be 16 GB.
Free disk space	If the Linux operating system is installed, the requirements for disk partitions are as follows: /: ≥50GB swap: ≥8GB /opt: ≥10GB
Bandwidth of the management network	2 Mbit/s or higher In the Disaster Recovery Data Center Solutions (Active-Passive Mode) and (Geo-Redundant Mode), if two UltraVRs are deployed. The bandwidth of the management network between the UltraVR is 2 Mbit/s or higher.
Deployment mode	Centralized deployment: Only one UltraVR management server can be deployed, and the server must be interconnected to the management network of data centers. Distributed deployment: In the Disaster Recovery Data Center Solutions (Active-Passive Mode) and (Geo-Redundant Mode), at most two UltraVR management servers can be deployed and management networks between the servers must be interconnected.

Requirements for Configuring Permission on Installation Packages and Directories

To decompress an installation package, note the following:

The name of the directory where the installation package resides can contain only letters, digits, underscores (_), hyphens (-), and one space.
The package cannot be decompressed to the installation directory of UltraVR. In Linux, the installation path of the UltraVR is fixed to /opt/UltraVR.

Before installing the UltraVR, ensure that permission of directories at each level (755 by default) listed in Table 3 and that of the / root directory are properly assigned. Otherwise, users ICUser, Tomcat, and GaussDB have no operation permission on installation directories of the UltraVR Server, interrupting services. In this manner, you are advised to set permission of these directories to 755.

**Table 3** Description of directory permission
Directory	Description	Impact
/usr/local	GaussDB database installation directory	If the permission is improper, the database cannot be normally started.
/usr/lib	Directory for saving file lib of the GaussDB database	If the permission is improper, the database may fail to be normally started.
/usr/lib64	Directory for saving file lib of the GaussDB database	If the permission is improper, the database may fail to be normally started.
/opt	Directory under which the UltraVR Server is installed and data of the GaussDB data is saved	If the permission is improper, UltraVR may unable to run properly.
/usr/sbin	Save directory of logs collected by running the DataCollect command.	If the permission is improper, UltraVR may fail to collect logs.

Run the ls -ld directory name command to check the permission information about a directory.
Run the ll command to check owners and permission information about the files.

Set users' operation permission on installation directories of UltraVR. The following details the process using directory /opt as an example:

Log in as user root to the server where UltraVR is to be installed.
Run the cd /opt command to go to directory /opt.
Run the chmod 755 /opt command to set permission on the directory to 755.

Requirements for Configuring the Host File

Before UltraVR installation, the permission on the host file must meet the following configuration requirements:

Ensure host file hosts contains information about the mapping between the management IP address of the UltraVR Server and the host name.

If the mapping is not configured, the UltraVR service cannot be started after UltraVR installation.
If the mapping is improperly configured, the UltraVR cannot be logged in after it has been installed and started.

To configure the mapping between the management IP address of the UltraVR and the host name, perform the following steps:

Log in to the UltraVR Server server as user root.
Run the cd /etc command to go to the directory where file hosts resides.
Run the vi hosts command to open file hosts.
Press i to enter the editing mode and edit file hosts.
Add the following content (management IP address 192.168.10.10 and host name host01 are used as examples) into file hosts:
```
192.168.10.10 host01
```
Run the hostname command to check the host name.
Press Esc, and run the :wq! command to save the change and exit.

Requirements for Configuring the Encryption Algorithm

To enhance operating system security, you are advised to set sha256 as the password encryption algorithm for operating systems of physical servers and VMs on which the UltraVR are to be installed. Otherwise, passwords of the ICUser, DRManager created during the software installation may be encrypted using MD5 by default. MD5 is a less secure encryption algorithm that may be cracked. To change the encryption algorithm for operating systems, perform the following steps:

Log in as user root to the server where the UltraVR is to be installed.
Run the vi /etc/default/passwd command and press Insert to edit the passwd file, and check the current encryption algorithm of the operating system (the value of CRYPT).
- If the current encryption algorithm is sha256 or sha512, go to 4.
- If the current encryption algorithm is not sha256 or sha512, go to 3.
Change the value of CRYPT to sha256.
Add the explanatory note # in the CRYPT_FILES=blowfish field and make the parameter is invalid.
Press Esc, and run the :wq! command to save the change and exit.

If the current encryption algorithm of the operating system is not modified before installing the UltraVR software, you need to modify the password of the ICUser and DRManager user and make the parameter is invalid. For details, refer to See the default password of the account for the target node on the Type A (Background) sheet in the UltraVR V100R003C10SPC900 Account List.