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
- Setting up the resiliency domain
- About the web console
- Connecting to the Resiliency Platform web console
- Getting started with a new Resiliency Platform configuration
- Adding a Resiliency Manager to an existing resiliency domain
- Removing a Resiliency Manager from a resiliency domain
- Viewing the status of a Resiliency Manager in a data center
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- About NetBackup and NetBackup Appliances
- About protecting assets with NetBackup using Resiliency Platform
- Using NetBackup - an overview
- Prerequisites for integrating NetBackup with Resiliency Platform
- Adding NetBackup master server
- Adding IMS to NetBackup master server as an additional server
- Editing the NetBackup master server
- Removing the NetBackup master server
- Removing IMS from NetBackup master server
- Refreshing the NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- About Veritas InfoScale Operations Manager
- Resiliency Platform support for InfoScale applications
- Managing InfoScale applications using Resiliency Platform
- Support matrix for InfoScale applications
- Prerequisites for managing Veritas InfoScale Operations Manager server using Resiliency Platform
- Adding a Veritas InfoScale Operations Manager server
- Regenerating registration URL for a Veritas InfoScale Operations Manager server
- Deleting a Veritas InfoScale Operations Manager server
- Editing the details of a Veritas InfoScale Operations Manager server
- Reconnecting the Veritas InfoScale Operations Manager to a Resiliency Manager
- Managing Resiliency Platform Data Mover gateway pairing
- Viewing Veritas Replication Gateways
- About Veritas Replication Gateway pairs
- How Resiliency Platform Data Mover supports encryption for data replication
- Creating a Veritas Replication Gateway pair
- Removing a Veritas Replication Gateway pair
- Viewing Veritas Replication Gateway pairs
- Modifying encryption for a Veritas Replication Gateway pair
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Asset infrastructure use cases
- Adding asset infrastructure for Hyper-V virtual machines
- Adding asset infrastructure for VMware virtual machines
- Adding asset infrastructure for application discovery on Hyper-V virtual machines
- Adding asset infrastructure for application discovery on VMware virtual machines
- Adding asset infrastructure for application discovery on physical systems
- Adding the asset infrastructure
- Managing host assets
- Managing Hyper-V assets
- Managing VMware virtualization servers
- Managing enclosure assets
- Preparing and maintaining host assets
- About adding host assets
- Prerequisites for adding hosts
- Adding a Windows Install host
- Installing the host package on a Windows host
- Adding application hosts
- Preparing host for replication
- Removing hosts
- Refreshing host discovery information
- Uninstalling the host package from a Linux host
- Uninstalling the host package from a Windows host
- Managing Hyper-V virtualization server assets
- About Microsoft Hyper-V virtualization discovery
- Prerequisites for Microsoft Hyper-V virtualization discovery
- Adding Hyper-V virtualization servers
- Removing Hyper-V virtualization servers
- Refreshing Hyper-V virtualization servers
- Configuring asset infrastructure for replication for Hyper-V virtual machines
- Managing VMware virtualization server assets
- Prerequisites for adding VMware virtualization servers
- VMware vCenter Server privileges required for implementing Resiliency Platform Data Mover
- About near real-time discovery of VMware events
- Setting up near real-time discovery of VMware events
- Configuring the VMware vCenter Server to generate SNMP traps
- About adding a host for discovery of VMware 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 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
- Editing the discovery configuration for an enclosure
- Removing the discovery configuration for an enclosure
- Refreshing enclosure discovery information
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Managing user authentication and permissions
- About user authentication in the web console
- About user permissions in the web console
- Predefined personas
- About limiting object scope for personas
- Configuring authentication domains
- Editing authentication domains
- Unconfiguring authentication domains
- Showing domains on login screen
- Configuring user groups and users
- Assigning permissions to user groups and users
- Adding custom personas
- Predefined jobs that can be used for custom personas
- Configuring Windows global user
- Managing service objectives
- Managing reports
- Managing settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Adding, modifying, or deleting email settings
- Adding, modifying, or deleting SNMP settings
- 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
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- About updating Resiliency Platform
- About applying updates to Resiliency Platform
- Prerequisites for a repository server
- Downloading the Resiliency Platform update
- Using YUM virtual appliance as YUM server
- Setting up the repository server
- Adding a repository server in Resiliency Platform
- Assigning a repository server in Resiliency Platform
- Applying updates to virtual appliances using the console
- Applying updates to virtual appliance using klish menu
- Applying update on Resiliency Managers
- Applying update for InfoScale environment
- Applying updates to Resiliency Platform Data Mover bundle
- Applying updates to the hosts
- Removing an update from the repository server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Viewing events and logs in the console
- Accessing Resiliency Platform log files
- Displaying risk information
- About the Resiliency Manager services
- Components of Resiliency Platform virtual appliance
- Troubleshooting discovery of assets
- About the frequency of asset information discovery
- Troubleshooting the connection between Resiliency Managers in a resiliency domain
- Troubleshooting removing a Resiliency Manager from a resiliency domain
- Manually recovering the replication gateway
- Using Veritas Services and Operations Readiness Tools to find a Unique Message Identifier description and solution
- Troubleshooting and maintenance
- Section VIII. Reference
- 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. You can add an IMS after you exit the Getting Started wizard.
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.
Information needed for adding the IMS:
The fully qualified domain name (FQDN) or IP address.
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.
Settings (menu bar) > Infrastructure > Details View
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, use that URL string as a parameter to the following command:
manage > configure ims_register registration URL
Where, registration URL is the URL obtained after initiating the process form Resiliency Manager console.
See Using klish.
- Verify that the IMS is successfully added.
Once the IMS is successfully added, you can add the asset infrastructure to the IMS.
- 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.