Search <book_title>...

Product Documentation

Last Published: 2024-08-30

Product(s): Resiliency Platform (10.3)

Prerequisites for adding hosts

Before you add hosts to Veritas Resiliency Platform for discovery and monitoring by an Infrastructure Management Server (IMS), ensure that the following prerequisites are fulfilled.

General prerequisites for adding host assets:

Ensure that the IMS can communicate with the host.
See Network and firewall requirements.
Ensure that the time difference between the system clocks on the IMS and on the host is not more than 90 minutes. It is recommended to configure NTP on the virtual machine that needs to be secured. NTP should be configured in such a way that when the virtual machine is on the source data center, it remains in sync with the IMS on source data center. After migration, the virtual machine should be in sync with the IMS on the target data center.
If a text file with comma separated values is used to add hosts, ensure that it uses the correct syntax.
Ensure that the vCenter server and the hosts which are being prepared for in-guest protection need to be added to the same IMS and that they cannot be part of two different IMS.

Additional prerequisites for Linux systems

To add a Linux host with the configuration mode option, Configure using VRP Console, use a user account that is a part of the root group or a user account that has password-less sudo privileges.
See Configuring password-less sudo privileges for user account on Linux host.
Ensure that openssh-clients package is present in the system. Typically it is installed in the operating system by default.
For Resiliency Platform Data Mover host, it is recommended to install and configure ntpdate. It ensures that the system's time remains in sync even after migration to the other site.
For Resiliency Platform Data Mover host, ensure that dmidecode package is available in the system. Typically it is installed in the operating system by default. However, it may be not present in minimal OS installations.
In order to install the host package while adding the Linux host, ensure that the PasswordAuthentication field is set to yes in the /etc/ssh/sshd_config file on the host.
You need to remove all the stale network files from the below directory before adding the host.
- RHEL and Centos path: /etc/sysconfig/network-scripts
- SUSE: /etc/sysconfig/network
If a host is being added or prepared using a sudo user (in case of linux workloads), it requires the sudo package version to be minimum 1.7.8.
For Suse 15, ensure that insserv package is installed in the system. Typically, it is installed in the operating system by default.
In order to persist the iptable rules, ensure that the iptables service is running and the IPTABLES_SAVE_ON_STOP, IPTABLES_SAVE_ON_RESTART and IPTABLES_SAVE_COUNTER directives are set to yes in the iptables config file.
While preparing host for replication, an incorrect package detected. Hence the prepare host for replication failed while installing IOTap package. You need to install libnsl package for RHEL 9 to complete the workflow.

Additional prerequisites for Windows systems

To add a Windows host, it is recommended to use a domain user account with local administrator privileges.
If you cannot use a domain user account with local administrator privileges, you have an option to use an Administrator user or a user in local administrator group with required prerequisites.
See User account required for adding a Windows host.
Ensure that you have appropriate User Access Control (UAC) settings for the user that is used for adding the Windows host.
See UAC settings required for adding a Windows host.
The Windows Management Instrumentation (WMI) service must be running.
Ensure that the password for the host does not contain a double quotes character.
After you add a new data disk to a Windows host and attach it to IDE controller, you need to initialize the disk. This needs to be done before adding the host.
If you have McAfee antivirus already installed on the virtual machines, you need to disable the other encryption options before adding the host.

Additional prerequisites for Oracle Discovery Hosts

VRP supports Redhat Enterprise Linux hosts as Oracle Discovery Hosts.
You have to install Oracle Client (Net) on the host. Oracle Net on the host must be configured by "oracle" user such that the tnsnames.ora points to all the Oracle instances to be discovered and managed. You can use the Oracle Net Configuration Assistance (netca) to configure the tnsnames.ora file.
If you are configuring Oracle RAC, ensure that all RAC nodes are configured in the tnsnames.ora file. Make sure that sqlplus command on the discovery host is able to reach all the Oracle database instances individually.
If the Oracle Database is replicated using Oracle DataGuard, make sure that you add only the database that is local to the Datacenter in the tnsnames.ora. You should use a different Discovery Host in the remote Datacenter for managing the remote Database.
You may use the same discovery host to manage the multiple Oracle databases in the same datacenter. The Oracle Net has to be configured to be able to communicate with all the instances of all these databases.

See About adding host assets.

See Managing host assets.

See Removing Windows Install Hosts.