- Notes, cautions, and warnings
- Preface
- Getting Started
- Preparing for a Deployment
- Deployment
- Configuration
Providing the required information and deploying PowerProtect Data Manager takes approximately 15 minutes.
Parameters | Description |
---|---|
Deployment name | The name of the GCP deployment. |
Version | The combination of PowerProtect Data Manager and DDVE versions to deploy. |
Zone | The zone where both PowerProtect Data Manager and DDVE will be deployed. |
Network interfaces | The network interface to use. Accept the default or add a new interface. If adding a new interface, the name, subnetwork, and external IP must be provided. |
Data Manager name | The name of the PowerProtect Data Manager instance. |
Machine type | The resources assigned to the PowerProtect Data Manager instance. This cannot be changed from the default of Customer, which provides 8 CPU cores, 32 GB of RAM, 16,000 IOPS, and 1 premium NIC. |
SSH public key (Optional) | The SSH public key for the PowerProtect Data Manager instance. If entered, this is associated with the admin user. |
Use Custom DNS Server (Optional) | Select this to use one or more of your own DNS servers, which allows for reverse DNS lookups of IP addresses to hostnames. Otherwise, leave it unselected and leave the following three parameters empty. |
DNS Server IP Address | The IP addresses of up to 2 DNS servers, separated by a comma. |
Data Manager IP Address | The IP address of the PowerProtect Data Manager server. |
Data Manager FQDN | The fully qualified domain name of the PowerProtect Data Manager server. |
Deploy DDVE (Optional) | By default, a
DDVE instance is deployed with
PowerProtect Data Manager, and launched in the same subnet. You might choose to not deploy
DDVE if you already have an instance deployed, or if you are performing
PowerProtect Data Manager server disaster recovery.
If selected, also configure the following:
|