Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- About Elastic Networking Adapter (ENA) support in Resiliency Platform
- Recovery to cloud data center
- Recovering virtual machines to AWS
- Recovering virtual machines to Azure
- Recovering virtual machines to Google Cloud Platform
- Recovering virtual machines to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- Recovery to on-premises data center
- Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of virtual machines to Azure
- Checklist for recovery of virtual machines to Orange Recovery Engine
- Checklist for recovery of virtual machines to Google Cloud Platform
- Checklist for recovery of virtual machines to vCloud Director
- Checklist for recovery to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of virtual machines using NetBackup
- Checklist for recovery of virtual machines using third-party replication technology
- Checklist for recovery of application using third-party replication technology
- Checklist for recovery of virtual machines to AWS
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploy and download the Resiliency Platform virtual appliances
- About deploying the Resiliency Platform virtual appliances
- Downloading the Veritas Resiliency Platform virtual appliances
- Deploying virtual appliances in AWS
- Deploying virtual appliances in Azure
- Deploying virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Prerequisites for deploying the virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Deploying virtual appliances in vCloud Director
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Deploy and download the Resiliency Platform virtual appliances
- Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Prerequisites for deploying the virtual appliances in AWS
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Apply Updates
- About applying updates to Resiliency Platform
- Step 1: Prepare for upgrade
- Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
- About applying updates to Resiliency Platform
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Recovering virtual machines to premises target data center
- Recovering virtual machines to cloud target data center
- Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Integrating with InfoScale clusters
- Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
- Configuring InfoScale clusters in Resiliency Platform
- Managing the custom application or replication type in Resiliency Platform
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage NetBackup primary pairing
- Manage Recovery Readiness Bundle
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- Managing network objects in Resiliency Platform
- Network objects in Resiliency Platform
- DNS server configuration settings
- Managing network pairs
- Mapping network objects (Production and Rehearsal mapping)
- Manage networks
- Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Managing user authentication and permissions
- Configuring authentication domains
- Managing settings for alerts and notifications and miscellaneous product settings
- Manage settings
- Section VII. Working with resiliency groups
- Organize assets
- Editing a resiliency group
- Deleting a resiliency group
- Viewing resiliency group details
- Manage virtual business services
- About virtual business services
- Organize applications
- Managing service objectives
- Organize assets
- Section VIII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) from AWS region to AWS region
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) from Azure to Azure
- 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) to Google Cloud Platform
- 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
- Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section IX. Managing disaster recovery
- Perform DR operations for virtual machines
- About Rehearse operation
- Performing the rehearsal operation for virtual machines
- Performing the recover operation for resiliency group
- Recovering virtual machines with multiple recovery points
- About Rehearse operation
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section X. Managing certificates
- Section XI. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Section XII. Using Resiliency Platform APIs
- Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting: NetBackup issues
- Resolving the Admin Wait state
- Troubleshooting: IP customization
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
Managing VMware virtual machines for remote recovery using NetBackup images
When you want to protect your assets that are being backed up using NetBackup, you need to organize them into a resiliency group and apply the service objective where the data availability mode is Copy.
To manage virtual machines for remote recovery using NetBackup images
- Prerequisites
Ensure that you have completed the NetBackup configuration tasks and the Local and remote service objective, with data availability as Copy, is activated.
See Prerequisites for integrating NetBackup with Resiliency Platform.
Ensure that the virtual machine configuration prerequisites are met.
See Prerequisites for configuring VMware virtual machines for recovery using NetBackup images.
- Navigate
Assets (navigation pane) > Resiliency Group(s) tab > Manage & Monitor Assets
You can also launch the wizard from the Unmanaged or Overview tabs.
- Select the virtual machines:
Select Host as the asset type, select the data center, and select other filters as needed to display a list of virtual machines.
Select the virtual machines that are backed up using NetBackup. You can identify the assets based on the NetBackup policy name and the technology that is displayed in the Data availability column.
Drag and drop the required virtual machines to Selected Assets.
- The next page displays the environment for the selected assets on both the data centers.
- The next page lists the service objectives that are available for the selected assets. You can expand the service objective to view details. Select the appropriate service objective.
- Select the target (recovery) data center.
- Do the following in the NetBackup Configuration panel and click Next.
Review the information about common policies across the selected virtual machines and the primary server on which the data is to be recovered. Review the target primary servers selection, the schedule, and policy details.
Select either the Cluster or the ESXi option.
If you select the Cluster option, select the target cluster from the dropdown. You can select multiple datastores which are the shared datastores.
If you select the ESXi option, you can choose the ESX server which is part of the cluster or standalone ESX server and select datastore on which the virtual machine is to be recovered remotely. The datastore could be the shared or local datastores.
Select the appropriate datastores for each disk and the configuration file.
Select either of the option Apply to all the virtual machines or Select target for each virtual machine. If you select the option Select target for each virtual machine, then each of the virtual machines are moved into different target datastores.
Resiliency Platform provides an option to use the NetBackup Instant Access feature to recover/rehearse the virtual machine instantaneously. Using Instant Access the virtual machine is mounted directly to the ESXi host to allow the backup storage device to treat the snapshot as a normal virtual machine. During the restore operation, the virtual machines will be moved to the target datastore using VMware Storage vMotion in the background.
If Resiliency Platform detects that the backup storage has Instant Access capability, you can select it as the preferred recovery method for the discovered data centers.
For the discovered data centers, click Select Instant Access for Recover operation or Select Instant Access to for Rehearsal operation, as the case may be.
Resiliency Platform automatically uses the full restore option if the backup image is not located on an Instant Access capable storage or additional NFS data stores can not be mounted.
On the Select Recovery Method page, you can also choose the recovery host from a list to be used for recovering the virtual machines according to the appropriate transport mode. Resiliency Platform lets NetBackup decide the transport mode for recovery. The default mode chosen by NetBackup is the same mode that was used while creating the backup as specified in the backup policy. You need to select the appropriate recovery host according to the transport mode used in the backup policy.
Note:
During rehearsal operation, using Instant Access to boot the virtual machine does not consume additional space on the target EXSi host.
See Support for NetBackup Instant Access to recover a resiliency group.
Review the summary.
Note:
If you change the name of the datastore in future, you need to edit the resiliency group and update the datastore name in the datastore selection section. This is because the current recovery configuration may use the datastore name you selected while creating the resiliency group.
- Complete the network customization steps for the virtualization technology.
- Verify the summarized information and enter a name for the resiliency group.
When you finish the wizard steps, Resiliency Platform invokes a workflow which initializes the virtual machines for the DR configuration. You can view the progress or ensure that this operation is successfully completed on the Activities page.
See Viewing activities.
Verify that the new resiliency group is added to the Resiliency Groups tab.
See Viewing resiliency group details. to view the target selection details for the resiliency group in the NetBackup tab.
Note that after configuring the resiliency group, it might take some time for the backup images to reflect in the Recover Wizard. Also note that all the available images from NetBackup primary server are not discovered. The discovery of images is on the selected RPO which is defined in the service objective. If the RPO is "X", at the time of creation of resiliency group, then 2X or past one month backup images, whichever is the maximum duration are discovered. Example if the RPO is 2 months, then the images for last 4 months since the time of creation of resiliency group are discovered. If the RPO is 4 hours then images for last one month are discovered.