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
System resource requirements for Resiliency Platform
The amount of virtual CPUs, memory, and disk space that Veritas Resiliency Platform requires are listed in this section.
The minimum configuration that is recommended for a virtual appliance for Resiliency Manager, Infrastructure Management Server (IMS), Replication Gateway, and YUM repository server:
Table: Recommended configurations
Component | Recommended configurations |
---|---|
Resiliency Manager | Disk space 60 GB RAM 32 GB Virtual CPU 8 |
Infrastructure Management Server (IMS) | Disk space 60 GB RAM 16 GB Virtual CPU 8 |
Gateway | Disk space 40 GB RAM 16 GB Virtual CPU 8 Additional external disk of 50 GB |
YUM repository server | Disk space 60 GB RAM 4 GB Virtual CPU 2 |
Note:
You need to reserve the resources for Resiliency Manager and IMS to ensure that these resources do not get swapped in case of hypervisor getting overloaded.
If the virtual appliance does not meet the minimum configuration, you get a warning during the bootstrap of the virtual appliance and you are required to confirm if you want to continue with the current configuration.
If you are not using the YUM virtual appliance, then you need to configure a Linux server with minimum 50GB disk space as a repository server. Provisioning for the repository server is optional, it is required to install the Veritas Resiliency Platform patches or updates in the future.
See Setting up the repository server .
If you want to enable dynamic memory on Hyper-V, make sure that the following prerequisites are met:
Startup memory and minimal memory should be equal to or greater than the amount of memory that the distribution vendor recommends.
If you are using dynamic memory on a Windows Server 2012 operating system, specify Startup memory, Minimum memory, and Maximum memory parameters in multiples of 128 megabytes (MB). Failure to do so can lead to dynamic memory failures, and you may not see any memory increase in a guest operating system.
Even if you are using dynamic memory, the above mentioned minimum configuration should be met.
More Information