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
Troubleshooting: NetBackup issues
The following table lists some of the issues that you may come across while restoring backup images using NetBackup.
Table: Troubleshooting NetBackup
Description | Solution |
---|---|
Restore operation fails at the Restore virtual machine image step. | In the Recent Activities panel, check the details of the failed step. Details such as Job ID and NetBackup master server name are displayed. These can be used to retrieve the failure reason using bperror command on the NetBackup master server. |
After completion of the Restore operation, the NICs attached to the virtual machines are not displayed. | Ensure that port group or VLAN mapping is complete at the production data center. If multiple network interface cards (NICs) are assigned to a virtual machine, then you need to apply IP customization to all the NICs. |
Restore operation fails | Check the log file on the Infrastructure Management Server (IMS) for errors. Log file location: /var/opt/VRTSsfmh/logs/mhrun.log |
Restore operation fails. The activities monitor on NetBackup master server shows the following error. NetBackup VMware policy restore error (2820) | When you add a VMware access host or a recovery host to the NetBackup master server, ensure that you add only the NetBackup client. Else the restore operation performed using the Resiliency Platform console may fail. |
Restore operation is paused for a prolonged period at the Restore subtask | Do the following:
|
After adding the NetBackup master server, if you immediately perform the 'Configuring the assets for remote recovery using the Copy service objective' operation, then the operation may fail. | Discovery of NetBackup master server by Resiliency Platform takes some time. If there are no configuration issues, then you may perform the 'Configuring the assets for remote recovery using the Copy service objective' operation after some time. |
Deleted NetBackup policies | Resiliency Platform does not validate deactivated NetBackup policies but displays RPO risks if the assets are protected. |
Reissuing NetBackup certificate | Consider the following scenario: You have integrated Veritas Resiliency Platform with NetBackup 8.1. For some reason if you have had to redeploy the IMS and you have replicated the previous asset configuration, then you need to reissue the certificate on the IMS that is associated with NetBackup master server. To reissue the certificate, do the following: Run the following Klish commands on the IMS on which NetBackup master server was added:
On the NetBackup master server console, under Security Management > Certificate Management, click to obtain the token. |
The NetBackup master server goes into disconnected state after upgrading the Resiliency Manager - IMS server to 3.4. | If NetBackup master server was added in previous version of Resiliency Platform using the registration URL and Resiliency Platform is upgraded to3.4, the master server state displays as Reconfiguration required. You must edit the NetBackup master server to bring it back to the connected state. |
If NetBackup master servers lower than version 8.1.2 are added in Resiliency Platform, and if these master servers are upgraded to version 8.1.2, the master servers are displayed as Disconnected in Resiliency Platform. | Remove the master server from the Resiliency Platform configuration and re-add it to resolve the issue. |
Table: Troubleshooting NetBackup restore to cloud
Description | Solution |
---|---|
Cloud Recovery Server is disconnected | In such a situation, a risk is raised on the Resiliency Group if one is configured. Also, the Cloud Recovery Server (CRS) will show as disconnected on the Copy Manager page of the cloud data center. Ensure that the CRS running and you can connect to it from the Resiliency Manager. |
Rehearsal or restore operation fails at the Restore virtual machine image step | The issue can be caused due to the following reasons:
|
Rehearsal or restore operation fails after the Restore virtual machine image step on the cloud data center. | The issue occurs because of transient failures to provision network interfaces or to register and start the provisioned cloud instances. To attempt recovery again, invoke the Start resiliency group operation and ensure that you select the option to . If the issue persists, retry the restore operation to delete any registered cloud instances on the target data center and recreate them. |