The backup datastore stores all the data that is required to recover services according to a Recovery Point Objective (RPO). Determine the target location and make sure that it meets performance requirements.

vSphere Data Protection uses deduplication technology to back up virtual environments at data block level, which enables efficient disk utilization. To optimize backups and leverage the VMware vSphere Storage APIs, all ESXi hosts must have access to the production storage.

Table 1. 
Options for Backup Storage Location

Option

Benefits

Drawbacks

Store production and backup data on the same storage platform.

  • You do not have to request a new storage configuration from the storage team.

  • You can take full advantage of vSphere capabilities.

You cannot recover your data if the destination datastore or the production storage is unrecoverable.

Store backup data on dedicated storage.

  • If production storage becomes unavailable, you can recover your data because your backup data is not located on the same shared storage.

  • You separate production and backup virtual machines.

  • The backup schedule does not impact production storage performance because the backup storage is completely separate.

You might be required to install and configure a dedicated storage volume for backups.

Table 2. VMware Backup Store Target Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-OPS-BKP-002

Allocate a secondary storage datastore for the vSphere Data Protection appliance and the backup data.

  • vSphere Data Protection emergency restore operations are possible even when the primary VMware vSAN datastore is not available because the vSphere Data Protection storage volume is separate from the primary vSAN datastore.

  • The amount of storage required for backups is greater than the amount of storage available in the vSAN datastore.

You must provide secondary storage.