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
Network and firewall requirements
The following are the network requirements for Veritas Resiliency Platform:
Before you use the hostname and the IP address in the Network settings, you need to register them with the DNS server.
The hostname or the IP address which is used for product configuration, should not have multiple entries in the DNS server. For example, the IP address should not be associated with multiple hostnames, or the hostname should not be associated with multiple IP addresses.
Ensure that ports 88 and 750 on DNS server are open for communication with IMS.
In case of recovery to cloud, ensure that port 53 on DNS server is open for bi-directional communication with the cloud data center.
The hostname that you use for a virtual appliance must not start with a digit and must not contain the underscore ( _ ) character.
Veritas Resiliency Platform supports only Internet protocol version (IPV) 4.
If you plan to use the DHCP server, the DHCP server should be in the same subnet where you plan to deploy the product.
The following ports are used for Veritas Resiliency Platform:
Table: Ports used for Resiliency Manager
Ports used | Purpose | For communication between | Direction | Protocol |
|---|---|---|---|---|
443 | Used for SSL communication | Resiliency Manager and web browser | Browser to Resiliency Manager | HTTPS, TLS v1.1+ |
14176 | Used for communication between the Resiliency Manager and Infrastructure Management Server (IMS) | Resiliency Manager and IMS | Bi-directional | HTTPS, TLS v1.1+ |
7001 | Used for database replication | Resiliency Manager and IMS | Bi-directional | TCP with SSL/TLS1.1+ |
389 | Used for communication with LDAP/AD server | Resiliency Manager and LDAP/AD server | Bi-directional | TCP, user provided |
636 | Used for communication with LDAP/AD server | Resiliency Manager and LDAP/AD server | Bi-directional | TCP with SSL/TLS, user provided |
22 | Used for communication between remote host to the appliance klish access | Appliance and the hosts | Bi-directional | TCP |
123 | Used for NTP synchronization | Appliance and the NTP server | Bi-directional | TCP |
14180 | Used for accessing API service | Resiliency Manager and the API service | Bi-directional | HTTS, TLSv1.1+ |
Table: Ports used for on-premises IMS and in-cloud IMS
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
14176 | Used for communication between the Resiliency Manager and Infrastructure Management Server (IMS) | Resiliency Manager and IMS | Bi-directional | HTTPS, TLSv1.1+ |
5634 | Used for IMS configuration | IMS and the hosts | Bi-directional | HTTPS, TLSv1.1+ |
14161 | Used for running the IMS console | Resiliency Manager and IMS | Resiliency Manager to IMS | HTTPS, TLSv1.1+ |
22 | Used for communication between remote host to the appliance klish access Used for remote deployment of the packages on remote UNIX host from IMS | IMS and the hosts | Bi-directional | TCP |
135 | Used for remote deployment on client computer (inbound) | Host and remote Windows hosts | Bi-directional | TCP |
123 | Used for NTP synchronization | Appliance and the NTP server | Bi-directional | TCP |
Table: Ports used for on-premises Replication Gateway and in-cloud Replication Gateway
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
33056 | Used for replication | On-premises virtual machine and Replication Gateway/Storage Proxy | Bi-directional | TCP |
5634 | Used for communication with IMS | IMS and Replication Gateway/Storage Proxy | Bi-directional | HTTPS, TLSv1.1+ |
8089 | Used for replication | in-cloud component and on-premises component | Bi-directional | TCP |
443 | Used for communication between paired Gateways | Paired Gateways | Bi-directional | HTTPS, TLS v1.1+ |
Table: Ports used for target Gateway in resync operation
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
67 | BOOTP server | Target Gateway enabled with DHCP role and physical host | Uni-directional | UDP |
68 | BOOTP client | Target Gateway enabled with DHCP role and physical host | Uni-directional | UDP |
69 | TFTP protocol | Target Gateway enabled with PXE role and physical host | Uni-directional | TCP/UDP |
Table: Ports used for virtual machines
Ports used | Description | For communication between | Direction | Protocol |
|---|---|---|---|---|
22 | Used for communication between remote host to the appliance klish access Used for remote deployment of the packages on remote UNIX host from IMS | IMS and the hosts | Bi-directional | TCP |
5634 | Used for communication with IMS | IMS and the hosts | Bi-directional | HTTPS, TLSv1.1+ |
33056 | Used for replication | On-premises virtual machine and Replication Gateway | Bi-directional | TCP |
More Information