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
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- 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 appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- 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
- Integrating with InfoScale Operations Manager
- 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 Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. 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) 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
- 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 VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- 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 IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
Restoring virtual machines to cloud (AWS) using NetBackup Automated DR
Using Resiliency Platform console, you can recover VMware virtual machines that are protected by NetBackup automated DR to AWS S3 object store and managed using a service objective where the data availability mode is Copy.
You can choose from the most recent successful backup image or another available backup image.
A virtual machine is restored using the selected backup image at selected cloud data center. Before that, the virtual machine whose data is being restored is stopped and unregistered. When the local restore is executed in the cloud data center, the virtual machines are removed and re-created using the selected backup image.
To restore a virtual machine on cloud, you can choose the backup images for on-premises virtual machines that are only available in the S3 bucket for either local or remote restore operation.
When restoring virtual machines on premises, you can choose for the backup images that are available either locally on premises or in the S3 bucket for that on premises virtual machine for either local or remote restore operation.
The network settings of the virtual machine are configured as per the subnet mapping, as specified during the configure for remote recovery operation. Finally, the virtual machine is brought up and running at the selected cloud data center.
If a virtual machine is deleted, you can choose the latest backup copy or any previous backup to restore the virtual machine on the cloud data center.
During the restore operation, first the AMI is created on the cloud recovery data center with the selected backup image which is backed up to S3 bucket using NetBackup Automated DR, and using that AMI the cloud instance is provisioned.
Resiliency platform attempts to delete the AMIs that are created as part of the DR operations once the cloud instances are provisioned using the AMIs. Any undeleted AMI that has a tag VRP-AMI-LifeCycle-State whose value is set to Removable can be safely removed manually.
Consider the following before running the restore operation on cloud:
The region of the cloud data center configured in Resiliency Platform and the region of the S3 bucket should be the same.
Appropriate network mapping should be present between premises and cloud network .
Resiliency manager should be connected to the NetBackup Cloud Recovery Server to perform the restore operation.
A successfully restored image is tagged. Hover the mouse on the tag to view additional information such as the NetBackup master server name, the image type (full or incremental), and the last test date and time.
To restore virtual machine data to the cloud data center
- Review the following prerequisites:
The resiliency group that contains the on-premises virtual machines must be protected using the service objective activated for copy based recovery.
- Navigate to Assets (navigation pane) > Resiliency Group(s) tab
- Go to the details page for the resiliency group with the virtual machines that you want to recover, and select Restore.
- In the Restore Resiliency Group panel do the following, and click Next.
Review the target data center.
Select Confirm outage of assets for resiliency group to confirm that there is an outage on the on-premises data center. This is not applicable if the restore is of the type local.
Choose the backup image to be used. You can choose from the latest image or any other available backup from the specified time range.
To choose from a specific time range, select the date and the time range. Then select the hours or minutes since the start time. Click Search.
- Click Finish.
Use Details to view the details of this operation in a graphical representation.
(bottom pane) >On successful completion of the restore operation, verify that the selected virtual machines are online in the cloud.
While performing the restore operation if an outage was declared on the production data center, you must clear the outage. Only after you have cleared the outage, you can restore the backup images from the cloud data center to the on-premises data center.
See Clearing outage.