Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
Manually recovering the replication gateway
Perform the following tasks to manually recovery the replication gateways.
The first backup should be taken after all the consistency groups are configured with the replication gateway. All subsequent backups should be taken after performing every disaster recovery operation such as migration and takeover.
To take a backup of the replication gateway
- Run the following command to create a backup file:
# /opt/VRTSitrpgw/utils/vxgw_recover backup
The extension of the backup file is .gz. Keep a copy of the backup file
VXGW_BKUP_<date>.tar.gz
on another system. This file is required to recover the gateway. Every time you run a disaster recovery operation such as Migrate, Takeover, you need to take a backup.
To recovery the replication gateway
- Stop the replication for all the hosts having the vxtap kernel module that are associated with the gateway. Use the following commands to stop replication:
For Linux host:
/opt/VRTSitrptap/bin/vxtapaction stop -cg <cgid>
For Windows host:
"C:\Program Files\Veritas\VRTSitrptap\vxtapaction" stop -cg <cgid>
where <cgid> is the ID of the consistency group.
- Use the following command to stop replication for all the consistency groups on peer gateway:
curl -X POST -l http://localhost:8080/ConsistencyGroup/<cgid>/abort
- Go to Settings, click Infrastructure, click Manage Asset Infrastructure and then click Hosts to view the host details. Note the name and the IP address of the host which is designated as the gateway.
- Delete the gateway virtual appliance.
- Use klish menu to remove the host and the gateway from Infrastructure Management Server (IMS).
Klish menu: manage > infra-appliance remove <fully qualified name of the gateway>
- Provision a new virtual appliance for the gateway. The IP address of the new virtual appliance must be the same as the old appliance.
- Stop all the services on the gateway using the following command:
/opt/VRTSitrp/bin/itrpadm service --stop ALL
- Copy the backup file to the new gateway and run the following command:
# /opt/VRTSitrpgw/utils/vxgw_recover recover <path to the backup file> /VXGW_BKUP_<date>.tar.gz
The recovery of configuration files is now complete.
- Start all the services on the gateway using the following command:
/opt/VRTSitrp/bin/itrpadm service --start ALL
- Use the following command to stop replication for all the consistency groups recovered by the gateway.
curl -X POST -l http://localhost:8080/ConsistencyGroup/<cgid>/abort
- Use the following command to start replication for all the consistency groups associated with the recovered gateway.
curl -X POST -l http://localhost:8080/ConsistencyGroup/<cgid>/start
- Use the following command to start the replication on each host having the vxtap kernel module associated with the recovered gateway.
For Linux:
/opt/VRTSitrptap/bin/vxtapaction start -cg <cgid>
For Windows:
"C:\Program Files\Veritas\VRTSitrptap\vxtapaction" start -cg <cgid>