Overview

Introduction

Data protection strategy can be realized in a Service Provider cloud subscription or the one owned by the customer.
During the initial architecture phase of Public Cloud protection as a service, Service provider should consider:

• Source data location / account owner - if it’s in Service Provider subscription or customer’s subscription
• Veeam Backup for Public cloud appliance placement - will it be in Service Provider or customer’s subscription
• Repository and retention - where backups should be stored: customer’s Object Storage in the Cloud, Service Provider storage in the Cloud or offloaded on-premises
• Desired self-service capabilities for tenants (exptected or not)

Components

To cover these scenarios, you will need the following components of the solution:

• Veeam Backup and Replication with plugins for Public Cloud
  This is where you keep protected data under one hood, manage the data from Cloud appliances and initiate recoveries to another location, region, subscription, to another hyperscaler or to on-premises.

• Veeam Backup Appliance in Public Cloud
  It acts as a control plane for protection by keeping settings of Cloud accounts and permissions, initiates backup and restore functioning.

• Veeam Service Provider Console and Cloud Connect (optional but highly recommended)
  Veeam Service Provider Console provides monitoring and management capabilities for Veeam Backup & Replication, and simplifies licenses and usage reporting.
  It is specifically crucial and recommended to use it with pod design deployments (taking in consideration number of individual VBR installations).

Backup Process

Within Veeam Backup for Public Cloud, data will be processed from snapshots by worker instances which are automatically provisioned based on your Public Cloud account settings. Protected data will be placed in Repository – object storage assigned to a backup policy. Once data is protected with Veeam Backup for Public Cloud, this data is manageable in Veeam Backup and Replication that enables:

• full or partial recoveries from Cloud Storage (S3 bucket, Azure Blob, Google Cloud Storage)
• Backup Copy Job to secondary location
• cross-cloud recovery
• recoveries to on-premises

Note for small-scale infrastructures

If your tenants have just few VMs to protect, bills for native snapshots and other backup operations might be huge comparing to on-premises backups. To optimize total costs you may utilize Veeam Agents to protect those workloads, using same Veeam Backup and Replication with licenses for Agents instead of Public Cloud.

Layouts:

Pod Architecture
Shared Architecture

---