Deploying Backup Appliance
Important |
|
To deploy a new backup appliance from the Veeam Backup & Replication console, do the following:
- Launch the New Veeam Backup for Google Cloud Appliance wizard.
- Choose a deployment mode.
- Specify a Veeam Backup for Google Cloud account in which the appliance will be deployed.
- Specify a name and description for the appliance.
- Specify connection type for the appliance.
- Specify network settings for the appliance.
- Specify credentials for the default user account.
- Wait for the appliance to be added to the backup infrastructure.
- Finish working with the wizard.
How Deployment Works
When deploying Veeam Backup for Google Cloud, Veeam Backup & Replication performs the following steps:
- Creates a Google Cloud storage bucket with the name deployfiles-{InstanceName}-{TimeStamp} and uploads a preconfigured VM deployment package to this bucket.
- Deploys a VM instance from the Ubuntu 22.04 LTS image.
- Creates a temporary Google Cloud storage bucket for installation packages.
- Uploads Veeam Backup for Google Cloud installation packages and their software dependencies to the temporary storage bucket.
- Initiates the creation of a Google Cloud storage bucket with the name {ProjectNumber}-{Location}-blueprint-config to store the installation state files, logs and variables.
- Installs the required software components on the VM instance.
- Configures the default service account on the backup appliance. The default service account will then be used to perform data protection and recovery operations within the Google Cloud project to which the backup appliance belongs. Out of the box, this account is already assigned all the required permissions listed in section Service Account Permissions.
You will be able to add other service accounts later, after Veeam Backup for Google Cloud installation. For more information, see Managing Service Accounts.
- Removes the temporary storage bucket.
Note that the deployfiles-{InstanceName}-{TimeStamp} and {ProjectNumber}-{Location}-blueprint-config buckets will remain in Google Cloud infrastructure after the deployment procedure and must not be removed manually. Otherwise, backup appliance removal operation may fail or cause unexpected errors.
Related Topics