Product Documentation
- 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
- 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 Google Cloud Platform
- 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 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 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 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
- 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
- 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
- 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 Google Cloud Platform (GCP)
- 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
- 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 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
Adding an IMS
Veritas Resiliency Platform includes an Infrastructure Management Server (IMS) to discover and monitor assets. When you first configure Resiliency Platform in the web console, you set up the Resiliency Manager and resiliency domain with the Getting Started wizard. Optionally, you can also add one or more IMSs. You can also add IMSs later, after you exit the Getting Started wizard. This procedure describes how to add IMSs later.
To add an IMS
- Prerequisites
A Resiliency Manager and resiliency domain must be set up using the Getting Started wizard.
See Getting started with a new Resiliency Platform configuration.
The virtual appliance for the IMS must be deployed and configured.
If the IMS is in AWS or Google Cloud Platform (GCP) cloud data center, ensure that the IMS has an IAM role with all the required permissions attached to it.
AWS: See Permissions required for IAM roles for Resiliency Manager, IMS, and Replication Gateway.
GCP:See API permissions required for Google Cloud Platform.
Note:
Resiliency Platform create rules in AWS cloud to perform the real-time discovery. Make sure to delete the rules at the time of removing IMS or deleting the Resiliency Platform infrastructure.
Information needed for adding the IMS:
Provide hostname.
The admin user credentials for the IMS virtual appliance. This information is optional and you need to enter only if the server is directly accessible.
If the server is not directly accessible, you can still initiate the process of adding an IMS by entering only the data center, friendly name, and FQDN/IP address. In this case, you get a registration URL which you have to use after logging in to the virtual appliance console of the IMS that you want to add and then the IMS is added to the data center.
Ensure that the IP address and hostname of the IMS gets resolved from the Resiliency Manager.
- Navigate to Settings (menu bar) > Infrastructure > Details View and then Select + Infrastructure Management Server.
You can also access this page from the Quick Actions menu > Manage Asset Infrastructure.
- In Add Infrastructure Management Server, enter the information for the IMS and submit.
Tips:
You can select from a list of existing data centers or add a new data center.
See How Infrastructure Management Servers relate to data centers.
To specify a new data center, select New in the Data Center field, then specify the location and name. When entering the location, enter a form of location identifier, such as city, and the location list will populate with potential matches for you to select.
Enter a friendly name for the IMS.
Enter the FQDN or IP address of the server.
Enter the user name and the password. These two are optional information that you need to enter only if the IMS is directly accessible. If you provide this information, the IMS is immediately added to the data center.
If you do not provide the username and password of the IMS, a registration URL is displayed on the screen. This URL is valid only for 30 minutes. if the URL expires, you need to regenerate the registration URL to complete the process.
See Regenerating registration URL for an IMS.
Copy the URL string and then log in to the virtual appliance console of the IMS. In the klish menu, run the following command:
manage > configure ims_register
See Klish menu options for IMS.
You are prompted to provide the IMS registration URL. Enter the URL that you had obtained after initiating the process from Resiliency Manager console.
- Verify that the IMS is successfully added.
Once the IMS is successfully added, you can add the asset infrastructure to the IMS.
See Adding the asset infrastructure.
Note:
When the IMS is connected to a RM in it's own datacenter, that IMS is displayed alongside the RM in the same row on the UI. However, when the IMS is connected to a RM in another datacenter, that IMS is displayed in a row below the RM.
- If you add an IMS to an existing data center after the DNS settings for the data center have been configured, go to the DNS settings for the data center, select the modify option for the DNS server, enter a test host name and IP address, and run a test. This ensures that this newly added IMS can be used to perform DNS updates.
More Information