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
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- 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
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
NetApp configuration prerequisites
For the Infrastructure Management Server (IMS) to discover a NetApp enclosure, ensure that the storage network physical connections and NetApp server are properly configured.
The NetApp storage objects work on the Data ONTAP operating system, which provides various interfaces to administer the NetApp storage objects. The IMS communicates to the enclosures using the ONTAP SDK interface to get the NetApp enclosure information. This communication occurs through the HTTP protocol (using the port number 80) or through the HTTPS protocol (using the port number 443).
The IMS supports NetApp enclosures that have Data ONTAP 1.4 or later.
Resiliency Platform supports Netapp storage with volumes or qtrees mounted via NFS or with LUNs provisioned via Fibre Channel (FC).
The physical connection requirements for NetApp enclosure discovery are as follows:
Network connectivity between the discovery host and NetApp enclosure.
You should be able to connect from the discovery host to NetApp enclosure or server using HTTP and HTTPS connections. Use the following URLs to access the enclosure:
https://netapp_address/na_admin
Port 443 is used for HTTPS connection.
http://netapp_address/na_admin
Port 80 is used for HTTP connection.
netapp_address is the IP address or NetApp array name, registered with the Domain Name System (DNS).
Setting up the device includes NetApp server configuration and enabling support for MultiStore Virtual Systems on NetApp enclosure.
Configure the array with an IP address or name, and an administrator-level account with valid user name and password. These credentials are used by IMS to access the enclosure for discovery.
Ensure you turn on the following options in the NetApp enclosure. These are required for NetApp SnapMirror operations.
httpd.admin.enable
httpd.enable
Ensure that the following licenses are installed and enabled:
licensed_feature.multistore.enable (required for discovering IP addresses)
licensed_feature.flex_clone.enable (required for rehearsal operation)