Restore Scenarios

This section explains possible restore scenarios from the capacity tier.

Unavailability of Backup Files

If one of the offloaded backup files becomes unavailable on any of the extents in a scale-out backup repository, you can restore it by doing the following:

  1. Rescan a scale-out backup repository.

For more information on how to rescan a scale-out backup repository, see Rescanning Scale-Out Repositories.

  1. Copy data from the capacity tier to the performance tier.

For more information on how to copy data, see Downloading Data from Capacity Tier.

Note

The performance or capacity extents must not be in the Maintenance mode.

Unavailability of Extents

A performance extent in a scale-out backup repository may become unavailable or be in the Maintenance mode. To restore data in such case, you can use any method described in section Data Recovery.

For example, you are restoring a virtual machine consisting of three data blocks, of which two blocks reside on the Extent 1 and another required block is stored on the Extent 2 which is unavailable. In such scenario, Veeam Backup & Replication gets two blocks from the Extent 1 and another required block from the capacity tier.

Restore Scenarios 

Unavailability of Scale-Out Backup Repository

To restore data if the entire scale-out backup repository is unavailable, you can use any method described in section Data Recovery.

If the entire scale-out backup repository becomes unavailable, Veeam Backup & Replication restores data from the capacity tier only.

For example, both performance extents that store required backup files to restore a virtual machine are not available. In such a scenario, Veeam Backup & Replication restores data from the capacity tier only.

Restore Scenarios 

Unavailability of Backup Server

To get access to backups in the capacity tier in case the entire configuration of the backup server becomes corrupted and your scale-out backup repositories are no longer available, you can:

Related Topics

Page updated 8/2/2024

Page content applies to build 12.2.0.334