Providing inputs for Resiliency Platform CloudFormation Templates
You need to provide inputs for creating instances using CloudFormation templates (CFT). Some of the fields get auto populated with the default value, you can change the values if required. For rest of the parameters, you need to enter a valid value.
Table: EC2 Instance Configuration
Field | Description |
|---|---|
Resiliency Manager Instance Name | Enter the name of the Resiliency Manager instance. |
IMS Instance Name | Enter the name of the IMS instance. |
Replication Gateway Instance Name | Enter the name of the Replication Gateway instance. |
EC2 Instance Type | This field is auto-populated with the best fit instance type. You can change the default value, if required. |
Key Pair for SSH access | Select the appropriate SSH key pair. While selecting the SSH key pair, ensure that you already have access to the pair. This is critical because SSH key pair is the only way to log in to the system and you cannot change the SSH key pair after the EC2 instance gets created. |
Create 'ImportSnapshotRole' AWS IAM Role for VRP? | Resiliency Platform requires ImportSnapshotRole for recovery of assets to AWS. Select Yes to create the role. Make sure that you have permission. Select No if you already have ImportSnapshotRole role. |
Staging Disk size for the Replication Gateway | Enter the size of the staging disk for Replication Gateway in the unit of GB. The minimum supported disk size of 50GB lets you protect up to 8 virtual machines and to protect more virtual machines an additional staging storage of 6 GB per virtual machine is required. |
Data Volume Type | Select the appropriate Volume Type for the data volume. This field has default value selected as 'gp2' volume type. You can change and select another as per your requirement. |
Resiliency Manager Data volume IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected Volume Type is IO1 only .IOPS value must be between 100 to 64000. |
Infrastructure Management Server Data volume IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected Volume Type is IO1 only. IOPS value must be between 100 to 64000. |
Replication Gateway Staging Disk IOPS (Required only when selected Volume Type is IO1 from IO1 and IO2) | This value will be used when selected DataVolumeType is IO1. The maximum ratio of provisioned IOPS to requested volume size (in GiB) is 50:1. For example, a 100 GiB volume can be provisioned with up to 5,000 IOPS. If appropriate IOPS value is not selected , the deployment fails. This value will be used when selected DataVolumeType is IO2. The maximum ratio of provisioned IOPS to requested volume size (in GiB) is 500:1. For example, a 100 GiB volume can be provisioned with up to 50,000 IOPS. If appropriate IOPS value is not selected , the deployment fails. |
KMS Key ARN for Staging Disk encryption | If you want to encrypt staging disks attached to the gateways using the KMS key, then select ARN of the respective KMS from the KMS Key drop-down. Else keep the default value as 'Not Encrypted'. |
Table: Resiliency Manager Network Configuration
Field | Description |
|---|---|
Network Interface to be used for communication with other Resiliency Managers | Select the network interface that can be used to communicate with other Resiliency Managers in the resiliency domain. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with Infrastructure Management Servers | Select the network interface that can be used to communicate with Infrastructure Management Servers. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interfaces to be used for accessing the User Interface | Select the network interfaces that can be used to access the Resiliency Manager web user interface. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
Resiliency Manager eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
Resiliency Manager eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
Resiliency Manager eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
Resiliency Manager eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
Resiliency Manager eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
Resiliency Manager eth1 NAT IP (Optional) | Provide the NAT IP for eth1 if applicable |
Table: Infrastructure Management Server Network Configuration
Field | Description |
|---|---|
Network Interface to be used for communication with Resiliency Managers | Select the network interface that can be used to communicate with Resiliency Managers. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with Replication Gateways | Select the network interface that can be used to communicate with Replication Gateways. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
IMS eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
IMS eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
IMS eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
IMS eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
IMS eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
IMS eth1 NAT IP (Optional) | Provide the NAT IP for eth1 if applicable |
Table: Replication Gateway Network Configuration
Field | Description |
|---|---|
Network Interface to be used for communication with the Infrastructure Management Server | Select the network interface that can be used to communicate with the Infrastructure Management Server. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with peer gateways | Select the network interface that can be used to communicate with peer gateways. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used for communication with workload Virtual Machines | Select the network interfaces that can be used for communication with the workload Virtual Machines. NAT settings are applicable for this role. If you want to use this network interface in a NAT environment, provide NAT details in the form. |
Network Interface to be used as the default gateway | Select the network interface that can be used by default for outgoing communication. |
Replication Gateway eth0 Subnet | Select the subnet which can be connected to the eth0 network interface. |
Replication Gateway eth1 Subnet | Select the subnet which can be connected to the eth1 network interface. This input is only relevant if you have selected eth1 for one of the communication roles. You should provide a valid subnet always. |
Replication Gateway eth2 Subnet | Select the subnet which can be connected to the eth2 network interface. This input is only relevant if you have selected eth2 for one of the communication roles. You should provide a valid subnet always. |
Is the eth0 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth0 and if you wish to use NAT with eth0, select Yes. |
Replication Gateway eth0 NAT Hostname (Optional) | Provide the NAT hostname for eth0 if applicable |
Replication Gateway eth0 NAT IP (Optional) | Provide the NAT IP for eth0 if applicable |
Is the eth1 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth1 and if you wish to use NAT with eth1, select Yes. |
Replication Gateway eth1 NAT Hostname (Optional) | Provide the NAT hostname for eth1 if applicable |
Replication Gateway eth1 NAT IP (Optional) | Provide the NAT hostname for eth1 if applicable |
Is the eth2 Network Interface behind NAT? | If NAT settings are applicable for the communications you have selected for eth2 and if you wish to use NAT with eth2, select Yes. |
Replication Gateway eth2 NAT Hostname (Optional) | Provide the NAT hostname for eth2 if applicable |
Replication Gateway eth2 NAT IP (Optional) | Provide the NAT IP for eth2 if applicable |
Table: Common Network Configuration
Field | Description |
|---|---|
VPC ID | Ensure the following while selecting the VPC:
|
CIDR block to allow inbound access | Provide CIDR block to allow inbound access to the appliances which will be set as source in Security Group. Provide a valid value considering your VPC and subnets configuration. If required, you can modify security group later according to your requirement. |
Table: Resiliency Platform Installation Parameters
Field | Description |
|---|---|
NTP Server | FQDN or IP address of the NTP server to be used for the instances. In case of multiple values, enter the space-separated values. |
TimeZone | Select the timezone for the instances. |
Table: Data Gateway Deployment Information
Field | Description |
|---|---|
Data Gateway deployment bucket name | Make sure that the deployment bucket pre-exists and is created in the local region where the CFT is being deployed. |
Deploy Veritas Data Gateway? | Optional parameter You need to deploy Data Gateway only if you want to use Object Storage for replication. See About Data Gateway. |
Does the Data Gateway bucket already exist? | Select Yes if the Data Gateway already exists. If you want to re-use an existing Data Gateway Bucket, that bucket should also be local to the region in which the CFT is being deployed. |
SNS Topic Protocol | Select a protocol from the list. |
SNS Topic Endpoint | Provide an endpoint that is appropriate for the selected SNS topic protocol. |
More Information
Deploying the virtual appliances in AWS through AWS Marketplace