Preparing host for replication
To enable the replication in Resiliency Platform using Resiliency Platform Data Mover, you need to add the asset and prepare it for replication. Asset can be a physical machine or a virtual machine.
To prepare a host for replication
- Ensure that you understand the use cases and prerequisites for adding hosts to an IMS.
Note:
After you add a new data disk to a Windows host and attach it to an IDE controller, you need to initialize the disk. This needs to be done before performing the Prepare Host for Replication task.
- Navigate to Settings (menu bar) > Infrastructure > Details View.
You can also access this page from the Quick Actions menu.
- Go to the on-premises data center and click Data Mover.
- Under Resiliency Platform Data Mover, click Prepare host for replication.
- In the wizard, select the type of host to be added.
Discovered Virtual Machines: Choose this option to select one or more virtual machines that are already discovered from your virtualization environment.
Non-discovered hosts (no-hypervisor configured or physical hosts): Choose this option to add virtual machines which are not yet discovered or which are physical hosts. You can import multiple hosts from a simple comma separated text file using this option.
- Choose the desired configuration mode from the following options:
Using VRP Console: You can configure a host using the username and password of the host. Resiliency Platform automatically installs the appropriate host agent packages on the host.
Using pre-deployed VRP Host Agent Packages: Choose this option if you do not have the username and password of the host or if you require full control for deploying the host agent packages using your tools and then configure the host without providing the username and password from the Resiliency Platform console. The VRP host agent packages can be downloaded from the IMS.
See Downloading Resiliency Platform host agent packages from IMS.
See Configuring Resiliency Platform host agent packages manually.
Note:
Ensure that you choose the same IMS to add this host from which you chose to download the VRP host agent package bundle to install and configure on that host.
- Select the IMS to which you want to add a host and click Next
- Based on the selected Host Type and Configuration Mode specify the following inputs:
Host Type
Configuration mode
Required Inputs
Discovered Virtual Machines
Using VRP console
Select one or more Virtual Machines and click Next. You can filter the virtual machines based on environment or on the virtualization server they are running on, or search them using their virtual machine name, family type, or host name.
Review the discovered Hostname for the virtual machine and modify it, if necessary.
Enter the username and password for each virtual machine in the table.
See Prerequisites for adding host for information about using non- root user accounts to add Linux hosts.
Click
to delete a row.
See Prerequisites for adding hosts . for information about using non- root user accounts to add Linux hosts.
Discovered Virtual Machines
Using a pre-deployed VRP Host Agent
Select one or more Virtual Machines and click Next. You can filter the virtual machines based on environment or on the virtualization server they are running on, or search them using their virtual machine name, family type, or host name.
Review the discovered Hostname for the virtual machine and modify it, if necessary.
Non-discovered hosts Physical hosts
Using VRP console
Type the host name and user credentials information in the table row. Use the following options to add information for multiple hosts.
Use the Add new rowoption to add a blank table row.
Use the Import from a text file option to import information from a text file with comma separated values. To do this, select the desired text file and click Load host details.
Use the
icon to copy the details of the elected table row. You can edit the details of the newly added row.
Use the
icon to delete the desired row.
See Prerequisites for adding hosts . for information about using non- root user accounts to add Linux hosts.
Non-discovered hosts or Physical hosts
Using a pre-deployed VRP Host Agent
Type the host name in the table row. Use the following options to add information for multiple hosts.
Use the Add new rowoption to add a blank table row.
Use the Import from a text file option to import information from a text file with comma separated values. To do this, select the desired text file and click Load host details.
Use the
icon to copy the details of the selected table row. You can edit the details of the newly added row.
Use the
icon to delete the desired row.
- Once you are done with entering the data for all the hosts, click Submit to initiate the Prepare Host for Replication activity for each host.
- Click the Status column value to navigate to the respective activity details view for a host to check if the activity is in progress or has failed.
The host is listed in the table for Replication Hosts on the Resiliency Platform Data Mover tab with Status column as Connected when the activity completes successfully.
When the recovery environment is AWS Cloud, the cloud storage and network drivers must be installed on the host in following conditions:
Windows Paravirtual (PV) drivers to recover Windows hosts
Xen block storage and networking drivers to recover SUSE Linux 11.4 hosts
If the compatible drivers are not installed already, the bundled versions of the required drivers are installed automatically when the hosts are added to resiliency group.
The bundled versions of the driver are located at:
For SUSE Linux platform:
/var/opt/VRTSsfmh/spool/addons/store/<VRTSitrptapversion_of_the_release>/AWSPVDriver
Refer to the Readme.txt file in this directory for version information of the bundled drivers.
If a VMWare virtual machine is already protected with Veritas Standalone Replication and has in-guest component then you cannot provision another virtual machine with the same BIOS ID as that of the protected virtual machine unless the protected virtual machine is upgraded to version 3.5.
See Troubleshooting: Cleaning up of stale Resiliency Platform configurations.
More Information