Veritas Resiliency Platform 3.0

Veritas Resiliency Platform is deployed as a virtual appliance. A virtual appliance is a virtual machine image consisting of a pre-configured operating system environment with a software application installed on it. This virtual machine image can be deployed on a hypervisor.

There are Four virtual appliances available for Resiliency Platform to deploy the Resiliency Manager, Infrastructure Management Server (IMS), Replication Gateway, and YUM virtual appliance. You need to deploy the Replication Gateway only if you choose to use Resiliency Platform Data Mover for replicating your data. If you choose to use any third-party array-based or hypervisor-based replication, you only need to deploy the Resiliency Manager and IMS in your environment. YUM virtual appliance is deployed for the purpose of upgrade. You need to deploy YUM virtual appliance only if you do not want to use a repository server.

Following is the list of considerations for deploying the virtual appliances:

  • For recovery to premises data center, you typically deploy and configure at least one Resiliency Manager and one Infrastructure Management Server (IMS) in the production data center and at least one Resiliency Manager and one Infrastructure Management Server (IMS) in the recovery data center.

  • In case you plan to use Resiliency Platform Data Mover for recovery of your assets to premises data center, you need to deploy at least one Replication Gateway in the production data center and one Replication Gateway in the recovery data center.

  • For recovery to cloud data center, you typically deploy and configure at least one Infrastructure Management Server (IMS) and one Replication Gateway in the production data center and one Resiliency Manager, one IMS, and one Replication Gateway in the recovery data center.

  • The Replication Gateway on the production data center must have access to the ESX servers for the production virtual machines to be replicated. The Replication Gateway on the recovery data center must have access to the ESX servers where the recovery virtual machines will be provisioned.

On -premises, you can deploy these components using any one of the following methods:

In cloud, you can deploy these components using any one of the following methods:

Once the Resiliency Platform virtual appliances are deployed, you are required to configure the Resiliency Platform component through the product bootstrap.

Deploy Resiliency Platform
How to deploy and configure the virtual appliances
Getting Started
Learn concepts and basic console features
Manage Infrastructure
How to manage Resiliency Managers and Infrastructure Management Servers
Add Asset Infrastructure
How to add hosts, virtualization servers, and storage arrays to the IMS
Manage Settings
How to set up user access, email notifications, and other product settings
Organize Assets
How to organize and manage assets as resiliency groups and virtual business services
Manage Disaster Recovery
How to manage disaster recovery and evacuation plan
Monitor, Automate, and Troubleshoot
How to view activities, reports and logs, use customized resiliency plans, and troubleshoot.
Command Line Utilities
How to use Application SDK and klish menu
Update and Licenses
How to update and manage licenses
Veritas Resiliency Platform 3.0

Veritas Resiliency Platform is deployed as a virtual appliance. A virtual appliance is a virtual machine image consisting of a pre-configured operating system environment with a software application installed on it. This virtual machine image can be deployed on a hypervisor.

There are Four virtual appliances available for Resiliency Platform to deploy the Resiliency Manager, Infrastructure Management Server (IMS), Replication Gateway, and YUM virtual appliance. You need to deploy the Replication Gateway only if you choose to use Resiliency Platform Data Mover for replicating your data. If you choose to use any third-party array-based or hypervisor-based replication, you only need to deploy the Resiliency Manager and IMS in your environment. YUM virtual appliance is deployed for the purpose of upgrade. You need to deploy YUM virtual appliance only if you do not want to use a repository server.

Following is the list of considerations for deploying the virtual appliances:

  • For recovery to premises data center, you typically deploy and configure at least one Resiliency Manager and one Infrastructure Management Server (IMS) in the production data center and at least one Resiliency Manager and one Infrastructure Management Server (IMS) in the recovery data center.

  • In case you plan to use Resiliency Platform Data Mover for recovery of your assets to premises data center, you need to deploy at least one Replication Gateway in the production data center and one Replication Gateway in the recovery data center.

  • For recovery to cloud data center, you typically deploy and configure at least one Infrastructure Management Server (IMS) and one Replication Gateway in the production data center and one Resiliency Manager, one IMS, and one Replication Gateway in the recovery data center.

  • The Replication Gateway on the production data center must have access to the ESX servers for the production virtual machines to be replicated. The Replication Gateway on the recovery data center must have access to the ESX servers where the recovery virtual machines will be provisioned.

On -premises, you can deploy these components using any one of the following methods:

In cloud, you can deploy these components using any one of the following methods:

Once the Resiliency Platform virtual appliances are deployed, you are required to configure the Resiliency Platform component through the product bootstrap.