Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Veritas Resiliency Platform
- About Resiliency Platform features and components
- About Resiliency Platform capabilities
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- About managing VMware Storage vMotion in Resiliency Platform
- About managing VMware snapshots in Resiliency Platform
- About IPv6 network support in Resiliency Platform
- Planning a resiliency domain for efficiency and fault tolerance
- On-boarding with Resiliency Platform
- About Resiliency Platform APIs
- Recovery options using Resiliency Platform
- Recovering physical machines to AWS using Resiliency Platform Data Mover
- Recovering VMware virtual machines to Orange Recovery Engine
- Recovering VMware virtual machines to AWS
- Recovering Hyper-V virtual machines to AWS
- Migrating VMware virtual machines to AWS
- Recovering VMware virtual machines to Azure
- Recovering Hyper-V virtual machines to Azure
- Recovering VMware virtual machines to HUAWEI CLOUD
- Recovering VMware virtual machines to OpenStack
- Recovering Hyper-V virtual machines to OpenStack
- Recovering physical machines to vCloud Director using Resiliency Platform Data Mover
- Recovering VMware virtual machines to vCloud Director
- Recovering Hyper-V virtual machines to vCloud Director
- Recovering VMware virtual machines to vCloud Director without adding vCenter server
- Recovering Hyper-V virtual machines to vCloud Director without adding Hyper-V server
- Recovering virtual machines from vCloud Director to vCloud Director
- Recovering physical machines to Orange Recovery Engine using Resiliency Platform Data Mover
- Recovering physical machines to VMware virtual machines on an on-premises data center using Resiliency Platform Data Mover
- Recovering VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
- Recovering VMware virtual machines from VMware to VMware using NetBackup
- Recovering virtual machines from VMware to AWS using NetBackup Automated disaster recovery
- Recovering VMware virtual machines using third-party replication technology
- Recovering Hyper-V virtual machines using third-party replication technology
- Recovering Applications using third-party replication technology
- Recovering InfoScale applications
- Deployment checklist
- Checklist for recovery of VMware virtual machines to AWS
- Checklist for recovery of physical machines to AWS using Resiliency Platform Data Mover
- Checklist for recovery of Hyper-V virtual machines to AWS
- Checklist for recovery of VMware virtual machines to Azure
- Checklist for recovery of Hyper-V virtual machines to Azure
- Checklist for recovery of VMware virtual machines to HUAWEI CLOUD
- Checklist for recovery of VMware virtual machines to Orange Recovery Engine
- Checklist for recovery of physical machines to Orange Recovery Engine using Resiliency Platform Data Mover
- Checklist for recovery of VMware virtual machines to OpenStack
- Checklist for recovery of Hyper-V virtual machines to OpenStack
- Checklist for recovery of VMware virtual machines from on-premises data center to vCloud Director
- Checklist for recovery of Hyper-V virtual machines from on-premises data center to vCloud Director
- Checklist for recovery of virtual machines from vCloud Director to vCloud Director
- Checklist for recovery of physical machines to vCloud Director using Resiliency Platform Data Mover
- Checklist for recovery of physical machines to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of VMware virtual machines using NetBackup
- Checklist for recovery of VMware virtual machines to AWS cloud using NetBackup
- Checklist for recovery of VMware virtual machines to on-premises data center using third-party replication technology
- Checklist for recovery of Hyper-V virtual machines to on-premises data center using third-party replication technology
- Checklist for recovery of applications to on-premises data center using third-party replication technology
- Checklist for recovery of InfoScale applications
- Prerequisites for vCenter server
- Prerequisites for ESXi cluster nodes
- Support matrix for RDM disk support
- System requirements
- System resource requirements for Resiliency Platform
- Network and firewall requirements
- Ports required for Resiliency Manager
- Ports required for IMS
- Ports required for recovery of assets using NetBackup
- Ports required for hosts
- Ports required for recovery of assets to AWS
- Ports required for recovery of assets to Azure
- Ports required for recovery of assets to Orange Recovery Engine
- Ports required for recovery of assets to HUAWEI CLOUD
- Ports required for recovery of assets to OpenStack
- Ports required for recovery of assets to vCloud Director
- Ports required for recovery of physical machines to on-premises data center
- Ports required for recovery of assets to on-premises data center using Resiliency Platform Data Mover
- Ports required for Replication Gateway used for recovery to cloud data center
- Ports required for Replication Gateway for recovery to vCloud Director without adding the vCenter or Hyper-V server
- Ports required for Replication Gateway used for recovery of physical machines
- Ports required for Replication Gateway used for recovery of VMware virtual machines to on-premises data center
- Ports required for recovery of assets to on-premises data center using third-party replication technology
- Ports required for recovery of InfoScale applications
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- About deploying the Resiliency Platform virtual appliances
- Downloading the Veritas Resiliency Platform virtual appliances
- Downloading the Resiliency Platform virtual appliances for recovery to vCloud
- Deploying the virtual appliance through VMware vSphere Client
- Deploying the virtual appliance through Hyper-V Manager
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliance in OpenStack through OpenStack dashboard
- Deploying the virtual appliance in OpenStack using volumes
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Uninstalling Resiliency Platform components when deployed through AWS Marketplace
- Virtual appliance security features
- About hotfixes
- References
- Apply Updates
- About applying updates to Resiliency Platform
- Adding disks with duplicate UUID for a Replication Gateway Appliance
- Upgrading AWS infrastructure when deployed through AWS Marketplace
- Upgrading AWS infrastructure when deployed using OVA files
- Prerequisites for a repository server
- Setting up the repository server
- Adding a repository server in Resiliency Platform
- Assigning a repository server in Resiliency Platform
- Applying updates to virtual appliances using the console
- Applying updates to virtual appliance using klish menu
- Refreshing the information about applicable updates
- Removing an update from the repository server
- Removing a repository server
- Downloading the Resiliency Platform update
- Setting up the YUM server
- Applying update for InfoScale environment
- Applying updates to the hosts
- Applying update on Resiliency Managers
- Applying updates to the Veritas Data Gateway
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Setting up the resiliency domain
- Connecting to the Resiliency Platform web console
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Adding OpenStack private cloud instance
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Integrating with InfoScale Operations Manager
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Adding the asset infrastructure
- Managing host assets
- About adding host assets
- Prerequisites for adding hosts
- Adding application hosts
- Refreshing host discovery information
- Removing hosts
- Uninstalling the host package from a Linux host
- Uninstalling the host package from a Windows host
- Reasons for add host operation failure
- Preparing host for replication
- Refreshing the replication host
- Moving the replication host to another IMS
- Removing the replication host
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- VMware vCenter Server privileges: configuring ESX servers
- VMware vCenter Server privileges: basic monitoring of assets
- VMware vCenter Server privileges: using third party replication
- VMware vCenter Server privileges: replication to on-premises data center
- VMware vCenter Server privileges: replication to cloud data center
- VMware vCenter Server privileges: using NetBackup
- Prerequisites for adding VMware virtualization servers
- About near real-time discovery of VMware events
- Setting up near real-time discovery of VMware events
- Configuring the VMware vCenter Server to generate SNMP traps
- Adding VMware virtualization servers
- Editing a VMware virtualization discovery configuration
- Viewing the details of a VMware virtualization discovery configuration
- Removing a VMware vCenter Server discovery configuration
- Refreshing VMware vCenter Server discovery information
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- Managing Replication Gateways
- Adding a Replication Gateway
- Refreshing a Replication Gateway
- Removing a Replication Gateway
- Moving a Replication Gateway to another IMS
- Viewing Replication Gateways
- About Replication Gateway pair
- Creating a Replication Gateway pair
- Modifying encryption for a Replication Gateway pair
- Replacing a Replication Gateway from a gateway pair
- Removing a Replication Gateway pair
- Viewing Replication Gateway pairs
- Configuring PXE on Replication Gateway
- Configuring the Replication Gateway as a DHCP Server
- Unconfiguring PXE boot server from a Replication Gateway
- Unconfiguring DHCP server from a Replication Gateway
- Managing Data Gateway
- Manage enclosure assets
- About the discovery host for enclosures
- Adding a discovery host
- Refreshing a discovery host
- Removing a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Editing the discovery configuration for an enclosure
- Removing the discovery configuration for an enclosure
- Refreshing enclosure discovery information
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- Managing network objects
- About network objects
- Adding a subnet
- Adding a Hyper-V VLAN
- Adding a network group
- Editing network objects
- Removing network objects
- Creating network pairs between source and target data centers
- Deleting a network pair
- Configuring DNS server settings for a data center
- Example of command for Windows keytab file
- Network pairs for recovering virtual machines to AWS
- Network pairs for recovering virtual machines to Azure
- Network pairs for recovering virtual machines to HUAWEI CLOUD
- Network pairs for recovering virtual machines to Orange Recovery Engine
- Network pairs for recovering virtual machines to OpenStack
- Network pairs for recovering virtual machines to vCloud Director
- Network pairs for recovering virtual machines to vCloud Director without adding hypervisor server
- Network pairs for recovering virtual machines from vCloud Director to vCloud Director
- Network pairs for recovering machines to on-premises data center
- Network pairs for recovering physical machines to VMware
- Network pairs for recovering physical machines to AWS
- Network pairs for recovering physical machines to Azure
- Network pairs for recovering physical machines to vCloud Director
- Manage settings
- Managing user authentication and permissions
- About user authentication in the web console
- About user permissions in the web console
- Predefined personas
- Configuring authentication domains
- Unconfiguring authentication domains
- Editing authentication domains
- Configuring user groups and users
- Assigning permissions to user groups and users
- Adding custom personas
- Predefined jobs that can be used for custom personas
- About limiting object scope for personas
- Configuring Windows global user
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing your assets
- Managing resiliency groups
- About resiliency groups with assets
- Configuring a resiliency group for basic monitoring
- Editing a resiliency group
- Deleting a resiliency group
- Starting a resiliency group
- Stopping a resiliency group
- Placing a resiliency group in maintenance mode
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing applications using Resiliency Platform
- About resiliency groups with applications
- Managing custom applications
- Providing inputs for partially discovered applications
- About application bundles
- Adding an application bundle to the Resiliency Manager
- Installing an application bundle on selected application hosts
- Enabling and disabling application bundle on selected application hosts
- Managing auto-deploy for an application bundle
- Uninstalling an application bundle from selected hosts
- Removing an application bundle
- Editing the discovery schedule for an application type
- Viewing the details of application types
- Viewing the applicable host details
- About resiliency groups with InfoScale applications
- Viewing InfoScale applications details
- Managing applications for basic monitoring
- Managing service objectives
- Organize assets
- Section VII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Understanding the role of resiliency groups in disaster recovery operations
- About ensuring the disaster recovery readiness of your assets
- How Resiliency Platform configures disaster recovery protection for virtual machines
- How Resiliency Platform Data Mover handles DR operations
- About manual intervention
- Limitations for virtual machine disaster recovery
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- Prerequisites for configuring Hyper-V virtual machines for recovery to AWS
- Replication Gateway pair selection options
- Volume type selection options
- Enable reverse replication option
- AWS Customization options panel
- Network customization options
- Prerequisites for network customization
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Prerequisites for configuring VMware virtual machines for recovery using NetBackup images
- Support for NetBackup Instant Access to recover a resiliency group
- Managing VMware virtual machines for remote recovery using NetBackup images
- Managing VMware virtual machines for remote recovery to AWS cloud using NetBackup images
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Configuring VMware virtual machines for disaster recovery using EMC SRDF replication
- Configuring VMware virtual machines for disaster recovery using EMC RecoverPoint replication
- Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
- Configuring VMware virtual machines for disaster recovery using Hitachi True Copy replication
- Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
- Configuring VMware virtual machines for disaster recovery using IBM SVC Global Mirror replication
- Configuring VMware virtual machines for disaster recovery using IBM XIV Remote Mirror replication
- Preparing Hyper-V virtual machines for using array-based replication
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
- Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
- Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
- Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
- Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
- Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
- Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Prerequisites for configuring applications for disaster recovery
- Prerequisites for configuring InfoScale applications for disaster recovery
- Configuring applications for disaster recovery using EMC SRDF replication
- Configuring applications for disaster recovery using EMC RecoverPoint replication
- Configuring applications for disaster recovery using NetApp SnapMirror replication
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- About Rehearse operation
- Rehearse operations for VMware virtual machines - array-based replication
- Rehearse operations for Hyper-V virtual machines - array-based replication
- Performing the rehearsal operation for virtual machines
- Performing cleanup rehearsal for virtual machines
- Migrating a resiliency group
- Taking over a resiliency group of virtual machines
- Performing the resync operation for virtual machines
- Performing the rehearsal operation using NetBackup images
- Performing the rehearsal operation on virtual machines from VMware to AWS using NetBackup Automated DR
- Restoring data using NetBackup to on-premises data center
- Restoring virtual machines to cloud (AWS) using NetBackup Automated DR
- Clearing outage
- Perform DR operations on a VBS
- Perform DR operations for applications
- Rehearse operations for applications - array-based replication
- Performing the rehearsal operation for applications
- Performing cleanup rehearsal for applications
- Migrating a resiliency group of applications
- Taking over a resiliency group of applications
- Performing the resync operation for applications
- Evacuate assets
- Manage Resiliency Plans
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- About manual task
- Using manual tasks in resiliency plans
- About custom script
- Perform DR operations for virtual machines
- Section IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Adding, modifying, or deleting email settings
- Adding, modifying, or deleting SNMP settings
- Downloading the MIB file
- Setting up rules for event notifications
- Adding, modifying, or removing Syslog server
- Modifying the purge setting for logs and SNMP traps
- Modifying the purge setting for reports
- Modifying the purge setting for activities
- Enabling or disabling telemetry collection
- Showing domains on login screen
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting: NetBackup issues
- Troubleshooting: Removing a Resiliency Manager from a resiliency domain
- Resolving the Admin Wait state
- Troubleshooting: Delete resiliency group operation
- Troubleshooting: Deployment of virtual appliances in Azure
- Troubleshooting: Copy file into the virtual appliance
- Troubleshooting: Copy file from the virtual appliance
- Manually cleaning up virtual machines
- Troubleshooting: IP customization
- Configure DR operation fails with an integration services error
- Resiliency Platform fails to attach storage policy to virtual machines
- Resiliency Platform fails to create storage policy
- Troubleshooting: Discovery of assets
- Troubleshooting: Hosts not added to IMS after migration to cloud data center
- Troubleshooting: Connection between Resiliency Managers in a resiliency domain
- Troubleshooting: DR operation failure with error message cannot change host configuration at VMware detach disk(s) subtask
- Troubleshooting: If datastores are renamed
- Troubleshooting: Migrate operation
- Troubleshooting: Takeover operation
- Troubleshooting: Failure to add IMS
- Troubleshooting: Replace Replication Gateway operation
- Troubleshooting: klish commands for Resiliency Manager, IMS, or Replication Gateway
- Troubleshooting: In Hyper-V guest environment writeable disk is shown as Read-only
- Troubleshooting: Steps to manually remove addon from hosts managed under Resiliency Platform
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
- Glossary
Prerequisites for configuring Hyper-V virtual machines for recovery to vCloud Director
Before you run the wizard to configure disaster recovery protection for a resiliency group of Hyper-V virtual machines, ensure that you have met the following prerequisites for virtual machine configuration:
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that the Hyper-V integrations services are installed and running inside the virtual machines.
If you want to do IP customization, ensure that the virtual machines are updated with the latest Hyper-V integration services.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
When protecting Hyper-V virtual machines that use Dynamic Memory, ensure that the Maximum RAM value is set to a reasonable value. This value is used to assign the memory size to the virtual machines on the target (recovery) site. If Maximum RAM is set to a very high value then while configuring the resiliency group for remote recovery, the operation may fail.
Both the source and recovery (target) gateway must have external storage equivalent to 12GB for each virtual machine protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the source and recovery (target) gateway must each have 120GB of external storage.
A maximum of 58 volumes or disks can be attached to the Replication Gateway on on-premises where as up to 45 disks can be attached to the Replication Gateway on vCloud Director. The total number of disks from the virtual machines in the resiliency group and the number of disks that are already attached to the gateway should not exceed this number. This is a VMware limitation.
If the status of the virtual machine on the recovery data center is not correctly displayed, then you need to refresh the cloud discovery or the virtualization server discovery.
Ensure that correct values are defined for all the following settings in the Network Specification tab on the vCloud Director Web console for the vCloud network to which the virtual machines will connect to.
Gateway address
Network mask
Primary and Secondary DNS
DNS suffix
If one or more of these values are not defined, then after performing the migrate or takeover operation, the virtual machines may not get attached to the Infrastructure Management Server (IMS) in vCloud Director. Subsequently you cannot migrate back to production data center.
A Windows host is already added to resiliency domain using 'Prepare Host for Replication' operation. If you now add a non-initialized data disk to the host on IDE controller, you need to initialize the disk, reboot the host and refresh Hyper-V server before you can protect the host for DR.
If you want to migrate the virtual machines on some specific datastores in vCloud, then you need to create a storage policy. If you do not create a storage policy, the virtual machines are migrated to any of the available datastores.
Provision a SCSI disk of size 1 GB to be used for Replication block tracking. IDE disk is not supported.
The virtual machine needs to have its boot order changed, so that Network boot comes before Boot from disk. This is done by accessing BIOS settings from the virtual machine console when the virtual machine is booting up. This needs to be done only once; after preparing the host for replication or before creating a resiliency group. Ensure that it is done before running the Migrate operation.
Ensure that legacy network adapter is added and is first in the boot order. Ensure that it is done before running the Migrate operation.
Additional legacy network adapter must be attached to each virtual machine that is to be protected. The legacy network adapter must have a static IP whose subnet mapping is done.