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
Sample script output
Below are outputs of some sample scripts with different use cases.
Args input file contains:
{"ARGS":{"AES_ARGS":{"OP_TYPE":"DISCOVERY","OP":"Probe"}}}
JSON output after script execution:
{ "APPLICATION" : { "APP_NAME" : "SampleApp", "OPERATION_TYPES" : { "START" : { "Name" : "START" }, "STOP" : { "Name" : "STOP" } }, "DISCOVERY_TYPES" : { "DEEP" : { "Name" : "DEEP" }, "PROBE" : { "Name" : "PROBE" } }, "AES_VERSION" : "1.0.0.0" }, "APPLICATION_INSTANCE" : { "SampleApp" : { "APP_ID" : "SampleApp", "NAME" : "SampleApp", "DISCOVERY_TYPE" : "discovered", "INFO_REQUIRED" : "no", "STATE" : "Online", "APP_TYPE" : "SampleApp" } }, "OPERATIONS" : { "PROBE" : { "OPERATION_NAME" : "PROBE", "APP_NAME" : "SampleApp", "OPERATION_ARGS" : { "INSTANCE_NAME" : "SampleApp" }, "OPERATION_EXECUTED" : 1, "RET_CODE" : 0, "AES_VERSION" : "1.0.0.0", "OPERATION_TYPE" : "DISCOVERY", "ERR_CODE" : 0, "RET_MSG" : "probe is successful" } } }
Args input file contains:
{"ARGS":{"AES_ARGS":{"OP_TYPE":"DISCOVERY","OP":"DEEP"}}}
JSON output after script execution:
{ "APPLICATION" : { "APP_NAME" : "SampleApp", "OPERATION_TYPES" : { "START" : { "Name" : "START" }, "STOP" : { "Name" : "STOP" } }, "DISCOVERY_TYPES" : { "DEEP" : { "Name" : "DEEP" }, "PROBE" : { "Name" : "PROBE" } }, "AES_VERSION" : "1.0.0.0" }, "APPLICATION_INSTANCE" : { "app_inst" : { "APP_ID" : "app_inst", "NAME" : "app_inst", "HOMEDIR" : "inst_homedir", "APPLICATION_INSTANCEProps" : { "SERVICEGROUPNAME" : { "PROP_TYPE" : "", "PROP_VALUE" : "sample_sg", "PROP_NAME" : "ServiceGroupName" }, "CLUSTERTYPE" : { "PROP_TYPE" : "", "PROP_VALUE" : "MSCS", "PROP_NAME" : "ClusterType" }, "ISCLUSTERED" : { "PROP_TYPE" : "", "PROP_VALUE" : "true", "PROP_NAME" : "IsClustered" }, "APP_DISP_NAME" : { "PROP_TYPE" : "", "PROP_VALUE" : "sample_instance", "PROP_NAME" : "app_disp_name" } }, "TOTAL_SIZE" : 100, "DISCOVERY_TYPE" : "discovered", "APP_INPUTS" : { "QID1" : { "QID" : 1, "QDescription" : "Specify the administrator user name to discover its data files.", "Mandatory" : "yes", "QText" : "Administrator user name", "Encrypted" : "no" }, "QID2" : { "QID" : 2, "QDescription" : "Specify the administrator user password to discover its data files.", "Mandatory" : "yes", "QText" : "Administrator password", "Encrypted" : "yes" } }, "APP_CATEGORY" : "database", "INFO_REQUIRED" : "yes", "APP_TYPE" : "SampleApp", "STATE" : "online", "VERSION" : 1, "USED_SIZE" : 90, "OWNER" : "Administrator" } }, "APPLICATION_FILE" : { "app_inst;app_file" : { "SIZE" : 10, "APP_ID" : "app_inst", "NAME" : "app_file", "APPLICATION_FILEProps" : { "FILE_DESC" : { "PROP_TYPE" : "", "PROP_VALUE" : "Database file", "PROP_NAME" : "file_desc" } }, "TYPE" : "data", "PERMISSION" : "all", "FILE_PATH" : "c:\\app_inst\\app_file.data", "FILE_ID" : "app_inst;app_file", "STATE" : "online", "VERSION" : 1, "OWNER" : "administrator" } }, "APPLICATION_UNIT" : { "app_inst;app_unit" : { "APP_ID" : "app_inst", "APPLICATION_UNITProps" : { "UNIT_DISP_NAME" : { "PROP_TYPE" : "", "PROP_VALUE" : "sample_unit", "PROP_NAME" : "unit_disp_name" } }, "NAME" : "app_unit", "HOMEDIR" : "unit_homedir", "TYPE" : "database", "APP_UNIT_ID" : "app_inst;app_unit", "TOTAL_SIZE" : 100, "STATE" : "online", "VERSION" : 1, "USED_SIZE" : 50, "OWNER" : "unit_owner" } }, "OPERATIONS" : { "DEEP" : { "OPERATION_NAME" : "DEEP", "APP_NAME" : "SampleApp", "OPERATION_EXECUTED" : 1, "RET_CODE" : 0, "AES_VERSION" : "1.0.0.0", "OPERATION_TYPE" : "DISCOVERY", "ERR_CODE" : 0, "RET_MSG" : "deep discovery is successful" } } }
Args input file contains:
{"ARGS":{"AES_ARGS":{"OP_TYPE":"OPERATION","OP":"START","APP_INST_ID" :"SampleApp"}}}
JSON output after script execution:
{ "APPLICATION" : { "APP_NAME" : "SampleApp", "OPERATION_TYPES" : { "START" : { "Name" : "START" }, "STOP" : { "Name" : "STOP" } }, "DISCOVERY_TYPES" : { "DEEP" : { "Name" : "DEEP" }, "PROBE" : { "Name" : "PROBE" } }, "AES_VERSION" : "1.0.0.0" }, "OPERATIONS" : { "START" : { "OPERATION_NAME" : "START", "APP_NAME" : "SampleApp", "OPERATION_ARGS" : { "INSTANCE_NAME" : "SampleApp" }, "OPERATION_EXECUTED" : 1, "RET_CODE" : 0, "AES_VERSION" : "1.0.0.0", "OPERATION_TYPE" : "OPERATION", "ERR_CODE" : 0, "RET_MSG" : "Start is successful" } } }
Args input file contains:
{"ARGS":{"AES_ARGS":{"OP_TYPE":"OPERATION","OP":"STOP","APP_INST_ID" :"SampleApp"}}}
JSON output after script execution:
{ "APPLICATION" : { "APP_NAME" : "SampleApp", "OPERATION_TYPES" : { "START" : { "Name" : "START" }, "STOP" : { "Name" : "STOP" } }, "DISCOVERY_TYPES" : { "DEEP" : { "Name" : "DEEP" }, "PROBE" : { "Name" : "PROBE" } }, "AES_VERSION" : "1.0.0.0" }, "OPERATIONS" : { "STOP" : { "OPERATION_NAME" : "STOP", "APP_NAME" : "SampleApp", "OPERATION_ARGS" : { "INSTANCE_NAME" : "SampleApp" }, "OPERATION_EXECUTED" : 1, "RET_CODE" : 0, "AES_VERSION" : "1.0.0.0", "OPERATION_TYPE" : "OPERATION", "ERR_CODE" : 0, "RET_MSG" : "Stop is successful" } } }
Check the following properties in the OPERATIONS tag in the JSON output after executing a script.
OPERATION_EXECUTED denotes whether the operation is executed. 1 indicates executed, 0 for not executed.
RET_CODE denotes whether the operation is successfully executed. 0 indicates success and any positive number for failure. This return code is set by the callback function for the respective operations.
ERR_CODE displays the error code when the operation fails. 0 indicates no error.
RET_MSG displays the return message for the respective operation. This return message is set by the callback function for the respective operations.