Please enter search query.
Search <book_title>...
Product Documentation
Last Published:
2024-08-30
Product(s):
Resiliency Platform (10.3)
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Veritas Resiliency Platform
- About Resiliency Platform features and components
- About Resiliency Platform capabilities
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- About managing VMware Storage vMotion in Resiliency Platform
- About managing VMware snapshots in Resiliency Platform
- About IPv6 network support in Resiliency Platform
- About Continuous Data Protection (CDP)
- About Elastic Networking Adapter (ENA) support in Resiliency Platform
- Planning a resiliency domain for efficiency and fault tolerance
- On-boarding with Resiliency Platform
- About Resiliency Platform APIs
- 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 VMware virtual machines to vCloud Director
- Recovering Hyper-V virtual machines to vCloud Director
- Recovering VMware virtual machines to vCloud Director without adding vCenter server
- Recovering Hyper-V virtual machines to vCloud Director without adding Hyper-V server
- Recovering virtual machines from vCloud Director to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- Recovering physical machines to AWS using Resiliency Platform Data Mover
- Recovering physical machines to Azure using Resiliency Platform Data Mover
- Recovering physical machines to vCloud Director using Resiliency Platform Data Mover
- Recovering physical machines to Orange Recovery Engine using Resiliency Platform Data Mover
- Recovery to on-premises data center
- Recovering InfoScale applications
- Recovering Applications using third-party replication technology
- Recovering Hyper-V virtual machines using third-party replication technology
- Recovering VMware virtual machines using third-party replication technology
- Recovering VMware virtual machines from VMware to VMware using NetBackup
- Recovering VMware virtual machines to on-premises data center using Resiliency Platform Data Mover
- Recovering physical machines to VMware virtual machines on an on-premises data center using Resiliency Platform Data Mover
- Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of VMware virtual machines to AWS
- Checklist for recovery of physical machines to AWS using Resiliency Platform Data Mover
- Checklist for recovery of Hyper-V virtual machines to AWS
- Checklist of virtual machines for recovery from AWS to AWS
- Checklist for recovery of VMware virtual machines to AWS cloud using NetBackup
- 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 of VMware virtual machines from on-premises data center to vCloud Director
- Checklist for recovery of Hyper-V virtual machines from on-premises data center to vCloud Director
- Checklist for recovery of virtual machines from vCloud Director to vCloud Director
- Checklist for recovery of physical machines to vCloud Director using Resiliency Platform Data Mover
- 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
- Prerequisites for vCenter server
- Prerequisites for ESXi cluster nodes
- Support matrix for RDM disk support (VMware)
- Support matrix for Pass-through disk and shared disks in Hyper-V
- Checklist for recovery of virtual machines to AWS
- System requirements
- System resource requirements for Resiliency Platform
- Network and firewall requirements
- Ports required for Resiliency Manager
- Ports required for IMS
- Ports required for recovery of assets using NetBackup
- Ports required for hosts
- Ports required for recovery of assets to AWS or VMware in Cloud (VMC)
- Ports required for recovery of assets to Azure or Azure VMware Solution (AVS)
- Ports required for recovery of assets where both (source- target) data centers are cloud
- Ports required for recovery of assets to Orange Recovery Engine
- Ports required for recovery of assets to vCloud Director
- Ports required for recovery of assets to Google Cloud Platform
- Ports required for recovery of physical machines to on-premises data center
- Ports required for recovery of assets to on-premises data center using Resiliency Platform Data Mover
- Ports required for Replication Gateway used for recovery to cloud data center
- Ports required for Replication Gateway for recovery to vCloud Director without adding the vCenter or Hyper-V server
- Ports required for Replication Gateway used for recovery of physical machines
- Ports required for Replication Gateway used for recovery of VMware virtual machines to on-premises data center
- Ports required for recovery of assets to on-premises data center using third-party replication technology
- Ports required for recovery of InfoScale applications
- 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
- Downloading the virtual appliances for AWS
- Downloading the virtual appliances for Azure
- Downloading the virtual appliances for vCloud Director
- Downloading the virtual appliances for Orange Recovery Engine
- Downloading the virtual appliances for Google Cloud Platform
- Downloading the virtual appliances for recovery using NetBackup
- Downloading virtual appliances for recovery using InfoScale applications
- Downloading virtual appliances using Resiliency Platform Data Mover
- Downloading the virtual appliances using third - party replications
- Downloading virtual appliances for recovery of physical machines to VMware virtual machines
- Downloading the Resiliency Platform virtual appliances for recovery to vCloud
- Deploying the virtual appliance through VMware vSphere Client
- Deploying the virtual appliance through Hyper-V Manager
- 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
- API permissions required for Google Cloud Platform
- Uploading the OVA file using web-based method
- Uploading the OVA file using command-line method
- Creating Image using web-based method
- Creating Image using command-based method
- Launching the instances of virtual appliances
- 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
- References
- Deploy and download the Resiliency Platform virtual appliances
- Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Permissions required in AWS Marketplace for IAM roles RM, IMS and Replication Gateway
- Prerequisites for deploying the virtual appliances in AWS
- Configuring Amazon VPC for deployment using CloudFormation Templates
- Providing inputs for Resiliency Platform CloudFormation Templates
- Uninstalling Resiliency Platform components when deployed through AWS Marketplace
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploy virtual appliances in Azure Stack using Azure Stack Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Apply Updates
- About applying updates to Resiliency Platform
- Pre-upgrade tasks
- Step 1: Prepare for upgrade
- Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
- Step 3: Start the automatic bootstrap process
- Steps to replace the Replication Gateway appliance
- Rollback steps in AWS environment
- Rollback steps in Azure environment
- Rollback steps in VMware environment
- Rollback steps in Hyper-V environment
- Applying upgrade to Resiliency Platform for managing InfoScale clusters
- Applying updates to the hosts
- Applying update on Resiliency Managers
- Applying updates to the Veritas Data Gateway
- About applying updates to Resiliency Platform
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Setting up the resiliency domain
- Connecting to the Resiliency Platform web console
- Getting started with a new Resiliency Platform configuration
- Options for authentication domain configuration
- Getting started wizard - adding AWS data center
- Getting started wizard - adding Azure data center
- Getting started wizard - adding vCloud Director data center
- Getting started wizard - adding Orange Recovery Engine data center
- Getting started wizard - adding Google Cloud Platform data center
- Managing Resiliency Managers
- Adding a Resiliency Manager to an existing resiliency domain
- Viewing the status of a Resiliency Manager in a data center
- Performing data resync on a Resiliency Manager
- Renaming a Resiliency Manager
- Removing a Resiliency Manager from a resiliency domain
- Resiliency Manager outage impact on configuration and operations
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Adding Azure Stack private cloud configuration
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- About NetBackup and NetBackup Appliances
- About protecting assets with NetBackup using Resiliency Platform
- Prerequisites for integrating NetBackup with Resiliency Platform
- Recovering virtual machines to premises target data center
- Recovering virtual machines to cloud target data center
- Fetch Resiliency Platform certificates
- Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Configuring NetBackup Cloud Recovery Server (CRS) with Veritas Alta Recovery Vault storage account in Resiliency Platform
- Editing the NetBackup Cloud Recovery Server (CRS) configured with Veritas Alta Recovery Vault storage account
- Removing the NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault storage account
- Refreshing the NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault storage account
- Integrating with InfoScale clusters
- Support matrix for InfoScale applications
- Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
- Configuring InfoScale clusters in Resiliency Platform
- Reconfiguring InfoScale clusters in Resiliency Platform
- Removing the InfoScale clusters in Resiliency Platform
- Refreshing 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
- Adding the asset infrastructure
- Managing host assets
- About adding host assets
- Prerequisites for adding hosts
- Adding application hosts
- Refreshing host discovery information
- Removing hosts
- Uninstalling the host package from a Linux host
- Uninstalling the host package from a Windows host
- Reasons for add host operation failure
- Preparing host for replication
- Refreshing the replication host
- Moving the replication host to another IMS
- Removing the replication host
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- VMware vCenter Server privileges: configuring ESX servers
- VMware vCenter Server privileges: basic monitoring of assets
- VMware vCenter Server privileges: using third party replication
- VMware vCenter Server privileges: replication using Resiliency Platform Data Mover in Hypervisor mode
- VMware vCenter Server privileges: replication to cloud data center
- VMware vCenter Server privileges: replication using in-guest mode of Resiliency Platform Data Mover
- VMware vCenter Server privileges: using NetBackup
- VMware vCenter Server privileges: for recovery of physical machines to VMware
- Prerequisites for adding VMware virtualization servers
- Adding VMware virtualization servers
- Editing a VMware virtualization discovery configuration
- Viewing the details of a VMware virtualization discovery configuration
- Removing a VMware vCenter Server discovery configuration
- Refreshing VMware vCenter Server discovery information
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- Managing Replication Gateways
- Adding a Replication Gateway
- Refreshing a Replication Gateway
- Removing a Replication Gateway
- Moving a Replication Gateway to another IMS
- Viewing Replication Gateways
- About Replication Gateway pair
- Creating a Replication Gateway pair
- Modifying encryption for a Replication Gateway pair
- Replacing a Replication Gateway from a gateway pair
- Removing a Replication Gateway pair
- Viewing Replication Gateway pairs
- Configuring PXE on Replication Gateway
- Configuring the Replication Gateway as a DHCP Server
- Unconfiguring PXE boot server from a Replication Gateway
- Unconfiguring DHCP server from a Replication Gateway
- Managing Data Gateway
- Manage enclosure assets
- About the discovery host for enclosures
- Adding a discovery host
- Refreshing a discovery host
- Removing a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Editing the discovery configuration for an enclosure
- Removing the discovery configuration for an enclosure
- Refreshing enclosure discovery information
- Manage SSH host keys panel
- 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
- Creating network pairs between source and target data centers
- Mapping network objects (Production and Rehearsal mapping)
- Network pairs for recovering virtual machines to AWS
- Network pairs for recovering virtual machines from AWS region to AWS region
- Network pairs for recovering virtual machines to Azure
- Network pairs for recovering virtual machines from Azure to Azure
- Network pairs for recovering virtual machines to Orange Recovery Engine
- Network pairs for recovering virtual machines to Google Cloud Platform (GCP)
- Network pairs for recovering virtual machines to vCloud Director
- Network pairs for recovering virtual machines to vCloud Director without adding hypervisor server
- Network pairs for recovering virtual machines from vCloud Director to vCloud Director
- Network pairs for recovering machines to on-premises data center (For NetBackup, third-party replication or Resiliency Platform Data Mover)
- Network pairs for recovering physical machines to VMware
- Network pairs for recovering physical machines to AWS
- Network pairs for recovering physical machines to Azure
- Network pairs for recovering physical machines to vCloud Director
- Deleting a network pair
- Support for NIC teaming / bonding for physical machines
- Example of command for Windows keytab file
- Manage networks
- Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Adding, modifying, or deleting email settings
- Adding, modifying, or deleting SNMP settings
- Throttling the notifications
- Downloading the MIB file
- Setting up rules for event notifications
- Adding, modifying, or removing Syslog server
- Modifying the purge setting for logs and SNMP traps
- Enabling or disabling telemetry collection
- Showing domains on login screen
- Downloading log files
- Managing user authentication and permissions
- About user authentication in the web console
- About user permissions in the web console
- Predefined personas
- Configuring authentication domains
- Unconfiguring authentication domains
- Editing authentication domains
- Configuring user groups and users
- Assigning permissions to user groups and users
- Adding custom personas
- Predefined jobs that can be used for custom personas
- About limiting object scope for personas
- Configuring Windows global user
- Managing settings for alerts and notifications and miscellaneous product settings
- Manage settings
- Section VII. Working with resiliency groups
- Organize assets
- Viewing your assets
- Managing resiliency groups
- About resiliency groups with assets
- Configuring a resiliency group for basic monitoring
- Editing a resiliency group
- Deleting a resiliency group
- Starting a resiliency group
- Stopping a resiliency group
- Placing a resiliency group in maintenance mode
- Editing a resiliency group in maintenance mode
- Viewing resiliency group details
- Manage virtual business services
- Managing virtual business services
- About virtual business services
- Creating a virtual business service
- Editing a virtual business service
- Deleting a virtual business service
- Refreshing a virtual business service
- Displaying virtual business service details
- Starting and stopping a virtual business service
- Organize applications
- Managing applications using Resiliency Platform
- About resiliency groups with applications
- Providing inputs for partially discovered applications
- About application bundles
- Installing an application bundle on selected application hosts
- Enabling and disabling application bundle on selected application hosts
- Managing auto-deploy for an application bundle
- Uninstalling an application bundle from selected hosts
- Removing an application bundle
- Editing the discovery schedule for an application type
- Viewing the details of application types
- Viewing the applicable host details
- About resiliency groups with InfoScale applications
- Viewing InfoScale applications details
- Managing applications for basic monitoring
- Managing service objectives
- Organize assets
- Section VIII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Understanding the role of resiliency groups in disaster recovery operations
- About ensuring the disaster recovery readiness of your assets
- How Resiliency Platform configures disaster recovery protection for virtual machines
- How Resiliency Platform Data Mover handles DR operations
- Support for 128 SCSI disks for Replication Gateway of hardware version 14
- About manual intervention
- Limitations for virtual machine disaster recovery
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- Prerequisites for configuring Hyper-V virtual machines for recovery to AWS
- Replication Gateway pair selection options
- Volume type selection options
- Enable reverse replication option
- AWS Customization options panel
- Network customization options
- Prerequisites for network customization
- 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
- Prerequisites for recovering VMware virtual machines using Resiliency Platform Data Mover in Hypervisor mode
- Prerequisites for recovering VMware virtual machines using Resiliency Platform Data Mover in In-guest mode
- Replication Gateway pair selection options for on-premises data center
- Target Infrastructure Selection options
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Prerequisites for configuring VMware virtual machines for recovery using NetBackup images
- Support for NetBackup Classic AIR configurations
- Support for NetBackup Instant Access to recover a resiliency group
- Managing VMware virtual machines for remote recovery using NetBackup images
- Managing VMware virtual machines for remote recovery to AWS cloud using NetBackup images
- Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
- Support for NetBackup MSDP-C and Resiliency Platform Data Mover for configuring resiliency group
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Configuring VMware virtual machines for disaster recovery using EMC SRDF replication
- Configuring VMware virtual machines for disaster recovery using EMC RecoverPoint replication
- Configuring VMware virtual machines for disaster recovery using NetApp SnapMirror
- Configuring VMware virtual machines for disaster recovery using Hitachi True Copy replication
- Configuring VMware virtual machines for disaster recovery using HPE 3PAR Remote Copy replication
- Configuring VMware virtual machines for disaster recovery using IBM SVC Global Mirror replication
- Configuring VMware virtual machines for disaster recovery using IBM XIV Remote Mirror replication
- Preparing Hyper-V virtual machines for using array-based replication
- Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
- Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
- Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
- Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
- Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
- Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
- Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
- Configuring Hyper-V virtual machines for disaster recovery using Infinidat replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Prerequisites for configuring applications for disaster recovery
- Prerequisites for configuring InfoScale applications for disaster recovery
- Prerequisites for creating a remote recovery resiliency group for Oracle database replicated by Data Guard
- Configuring applications for disaster recovery using EMC RecoverPoint replication
- Configuring applications for disaster recovery using NetApp SnapMirror replication
- 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
- Rehearse operations for VMware virtual machines - array-based replication
- Rehearse operations for Hyper-V virtual machines - array-based replication
- Performing the rehearsal operation for virtual machines
- Performing the rehearsal operation using NetBackup images
- Performing the rehearsal operation on virtual machines from VMware to AWS using NetBackup Image Sharing
- Performing rehearsal operation on resiliency groups configured with multiple recovery points
- Performing cleanup rehearsal for virtual machines
- Migrating a resiliency group
- Performing the resync operation for virtual machines
- Performing the recover operation for resiliency group
- Recovering a resiliency group using replication-based recovery
- Recovering data using NetBackup to on-premises data center
- Recovering virtual machines with multiple recovery points
- Recovering virtual machines to cloud (AWS) using NetBackup Image Sharing
- Recovering virtual machines to cloud (Azure) using NetBackup MSDP-C
- Clearing outage
- About Rehearse operation
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- Managing resiliency plans
- About resiliency plans
- Creating a new resiliency plan template
- Editing a resiliency plan template
- Deleting a resiliency plan template
- Viewing a resiliency plan template
- Creating a new resiliency plan
- Editing a resiliency plan
- Deleting a resiliency plan
- Executing a resiliency plan
- Viewing a resiliency plan
- Instances to invalidate the R-Plan
- Creating a schedule for a resiliency plan
- Editing a schedule for a resiliency plan
- Deleting a schedule for a resiliency plan
- Viewing a schedule for a resiliency plan
- About manual task
- Using manual tasks in 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
- Adding, modifying, or deleting email settings
- Adding, modifying, or deleting SNMP settings
- Throttling the notifications
- Downloading the MIB file
- Setting up rules for event notifications
- Adding, modifying, or removing Syslog server
- Modifying the purge setting for logs and SNMP traps
- Modifying the purge setting for reports
- Modifying the purge setting for activities
- Enabling or disabling telemetry collection
- Showing domains on login screen
- Section XII. Using Resiliency Platform APIs
- Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Troubleshooting: Google Cloud Platform issues
- Troubleshooting: Disaster recovery from AWS region to AWS region
- Troubleshooting: Automated disaster recovery to Azure using NetBackup MSDP-C
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting : Issues occurred while prepare host for replication or while configuring resiliency group.
- Troubleshooting: Resync/repair replication issues for resiliency group configured using Multi-RPO recovery of hosts service objective
- Troubleshooting: NetBackup issues
- Troubleshooting: Removing a Resiliency Manager from a resiliency domain
- Resolving the Admin Wait state
- Troubleshooting: Delete resiliency group operation
- Troubleshooting: Deployment of virtual appliances in Azure
- Troubleshooting: Copy file into the virtual appliance
- Troubleshooting: Copy file from the virtual appliance
- Manually cleaning up virtual machines
- Troubleshooting: IP customization
- Configure DR operation fails with an integration services error
- Resiliency Platform fails to attach storage policy to virtual machines
- Resiliency Platform fails to create storage policy
- Troubleshooting: Discovery of assets
- Troubleshooting: Hosts not added to IMS after migration to cloud data center
- Troubleshooting: Connection between Resiliency Managers in a resiliency domain
- Troubleshooting: DR operation failure with error message cannot change host configuration at VMware detach disk(s) subtask
- Troubleshooting: If datastores are renamed
- Troubleshooting: Migrate operation
- Troubleshooting: Recover operation
- Troubleshooting: Recover operation in case of add/remove disks
- Troubleshooting: Failure to add IMS
- Troubleshooting: Replace Replication Gateway operation
- Troubleshooting: klish commands for Resiliency Manager, IMS, or Replication Gateway
- Troubleshooting: In Hyper-V guest environment writeable disk is shown as Read-only
- Troubleshooting: Steps to manually remove addon from hosts managed under Resiliency Platform
- Troubleshooting: Aborting the on-going activities / tasks
- Troubleshooting: AWS marketplace deployment with Data Gateway
- Troubleshooting: Cleaning up of stale Resiliency Platform configurations
- Troubleshooting: Preparing appliance for upgrade
- Troubleshooting : Issues while detaching and attaching data disk
- Troubleshooting: Issue while uploading the correct root certificate in vCloud Director
- Troubleshooting: Replication Gateway appliance
- Troubleshooting: Evacuation plan failed with exceptions raised by ERS.
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
- Glossary
Sample script
Find below a template script that you can use for developing your application module script. A sample script is also provided with hard coded data that can be modified to develop your script.
Sample script
use strict;
use warnings;
use VRTS::AppSDK::AppEnablementSDK::Application;
use VRTS::AppSDK::AppEnablementSDK::Constants qw(:LOG_LEVELS :
APP_INST_ATTRS :APP_UNIT_ATTRS :APP_FILE_ATTRS :
APP_CUSTOM_ATTRS :APP_INPUT_KEYS);
# Define an application here
my $appObj = new VRTS::AppSDK::AppEnablementSDK::Application("SampleApp");
if(defined $appObj)
{
# Set and register various operations that this application script
# supports.
$appObj->set_discovery_types("DEEP, PROBE");
$appObj->set_operation_types("START, STOP");
$appObj->register_operation_callback("START",\&start);
$appObj->register_operation_callback("STOP",\&stop);
$appObj->register_discovery_callback("PROBE",\&probe);
$appObj->register_discovery_callback("DEEP",\&deep);
print ($appObj->commit());
}
#################################
#Function: start
#
#Starts an application instance
#
#Parameters:
#arg - hash containing the application instance name
#
#Returns:
# 0 if successful else 1
# you can also return success or failure message which is optional.
#################################
sub start
{
my ($arg) = @_;
my $FuncName = ( caller 0 )[3];
$appObj->log(LOGLEVEL_DEBUG,"Inside $FuncName");
my $inst_name = $arg->{INSTANCE_NAME};
$appObj->log(LOGLEVEL_DEBUG,"Application instance name: [$inst_name]");
#Write the code here to start an application instance
#and return an appropriate status code and message.
#Return 0 for success and 1 for failure.
return 0, "Start is successful";
}
#################################
#Function: stop
#
#Stops an application instance
#
#Parameters:
#arg - hash containing the application instance name
#
#Returns:
# 0 if successful else 1
# you can also return success or failure message which is optional.
#################################
sub stop
{
my ($arg) = @_;
my $FuncName = ( caller 0 )[3];
$appObj->log(LOGLEVEL_DEBUG,"Inside $FuncName");
my $inst_name = $arg->{INSTANCE_NAME};
$appObj->log(LOGLEVEL_DEBUG,"Application instance name: [$inst_name]");
#Write the code here to stop an application instance
#and return an appropriate status code and message.
#Return 0 for success and 1 for failure.
return 0, "Stop is successful";
}
#################################
#Function: probe
#
#Discovers and reports the application instance state
#
#Parameters:
#arg - hash containing the application instance name
#
#Returns:
# 0 if successful else 1
# you can also return success or failure message which is optional.
#################################
sub probe
{
my ($arg) = @_;
my $FuncName = ( caller 0 )[3];
$appObj->log(LOGLEVEL_DEBUG,"Inside $FuncName");
#Write the code here to discover and report the application instance name.
#Report the state of the discovered application instance
# on the Resiliency Platform.
my $inst_name = $appObj->add_application_inst("app_inst");
if (defined $inst)
{
# The state must be reported either 'online' or 'offline'
$inst_name->set_property(APP_INST_STATE,"Online");
}
#return 0 if successful else 1
return 0, "Probe is successful";
}
#################################
#Function: deep
#
#Discovers and reports the sub-components and data file information of
#an application instance.
#
#Parameters:
#arg - hash containing the application instance name
#
#Returns:
# 0 if successful else 1
# you can also return success or failure message which is optional.
#################################
sub deep
{
my ($arg) = @_;
my $FuncName = ( caller 0 )[3];
$appObj->log(LOGLEVEL_DEBUG,"Inside $FuncName");
#Write the code here to discover and report the sub-components
# and the data file information of an application instance.
my $inst_name = $appObj->add_application_inst("app_inst");
if (defined $inst)
{
# Set application instance properties
# Ensure that the following property is set, else the application
# state is not displayed on the Resiliency Platform web console.
# You cannot perform operations if the state is not displayed
# on the console.
# Accepted values are 'online' and 'offline'
$inst_name->set_property(APP_INST_STATE,"Online");
# Following properties are optional
$inst->set_property(APP_INST_VERSION,"1.0");
$inst->set_property(APP_INST_OWNER,"Administrator");
$inst->set_property(APP_INST_ISPARALLEL,"false");
$inst->set_property(APP_INST_HOMEDIR,"inst_homedir");
$inst->set_property(APP_INST_APP_TYPE,"emp_database");
$inst->set_property(APP_INST_APP_CATEGORY,"database");
$inst->set_property(APP_INST_TOTAL_SIZE,"100");
$inst->set_property(APP_INST_USED_SIZE,"90");
# Set application instance custom properties
# Setting custom properties is optional.
$inst->set_custom_property("app_disp_name", "sample_instance");
#################################
# If your application is clustered using any high availability
# technology, then you need to set the following custom properties.
# $inst->set_custom_property("ClusterType", "MSCS");
# $inst->set_custom_property("ServiceGroupName", "sample_sg");
# $inst->set_custom_property("IsClustered", "true");
#-------------------------------
# Check if your application module script requires additional
# information such as user name and password from the user
# who is accessing the Resiliency Platform web console.
# If information is required, then check if the information
# is already asked and do we have its responses available here
# using the following API. Use those responses to complete
# your task.
# Use following API with QID as input
my $response1 = $inst->get_qresponse('1');
my $response2 = $inst->get_qresponse('2');
#-------------------------------
# If response is not available then ask for information
# again using the following API:
# Define questions to be asked in a hash
my $qid1 = {
'QID' => '1',
'QText' => 'Administrator user name',
'Mandatory' => 'yes',
'QDescription' => 'Specify the administrator user name
to discover its data files.',
'Encrypted' => 'no'};
my $qid2 = {
'QID' => '2',
'QText' => 'Administrator password',
'Mandatory' => 'yes',
'QDescription' => 'Specify the administrator user password
to discover its data files.',
'Encrypted' => 'yes'};
# Add the hash using the following API:
$inst->add_question($qid1);
$inst->add_question($qid2);
#-------------------------------
# Write the code here to discover an application unit (application
# sub-components) and application files information.
# Note: Discovering application unit is not mandatory
# but discovering application files is mandatory.
# Add application sub-component here
my $unit = $inst->add_application_unit("app_unit");
# Add properties for application unit
# Following properties are optional:
$unit->set_property(APP_UNIT_OWNER, "unit_owner");
$unit->set_property(APP_UNIT_VERSION, "1.0");
$unit->set_property(APP_UNIT_STATE, "online");
$unit->set_property(APP_UNIT_ISPARALLEL, "false");
$unit->set_property(APP_UNIT_HOMEDIR, "unit_homedir");
$unit->set_property(APP_UNIT_TYPE, "database");
$unit->set_property(APP_UNIT_TOTAL_SIZE, "100");
$unit->set_property(APP_UNIT_USED_SIZE, "50");
# Setting custom properties is optional.
$unit->set_custom_property("unit_disp_name", "sample_unit");
#-------------------------------
# Write the code here to discover information of application data files.
my $file = $inst->add_application_file("app_file");
# Following property is important and mandatory if you want to
# configure your application for disaster recovery.
# Value of this property could be data, log, etc. but the
# Resiliency Platform considers only those DR configuration files
# which are marked as 'data'.
$file->set_property(APP_FILE_TYPE, "data");
# Following property is important and mandatory if you want to
# configure your application for disaster recovery.
# Value of the property must be full file path
# e.g. '/root/app_inst/app_file.data' or
# 'c:\\app_inst\\app_file.data'
$file->set_property(APP_FILE_PATH, "c:\\app_inst\\app_file.data");
# Following properties are optional:
$file->set_property(APP_FILE_NAME, "app_file.data");
$file->set_property(APP_FILE_VERSION, "1.0");
$file->set_property(APP_FILE_OWNER, "administrator");
$file->set_property(APP_FILE_STATE, "online");
$file->set_property(APP_FILE_SIZE, "10");
$file->set_property(APP_FILE_PERMISSION, "all");
# Setting custom properties is optional.
$file->set_custom_property("file_desc", "Database file");
}
#return 0 if successful else 1
return 0, "deep discovery is successful";
}
More Information