Reading in back copy job from SOBR for restore

[jcofin13]

If you have back copy jobs sending backups to offsite storage in another physical location and the the backup copy job(s) are on a SOBR with 4 extents and you have a data locality policy on that SOBR how would you read from this SOBR if its the only data remaining. Pretend the source site goes away.

Seems like a simple question but if you lost the main site and needed to get data off this remote SOBR is it as simple as spinning up a veeam instance and scanning the 4 extents for items to restore? Technically i can see the VBK and VIB files on the extents while browsing the filesystem. The storage device is a windows box.

Or would you need to load up veeam and restore the backup config in order to read the whole SOBR in order to restore items? I imagine the SOBR config and items are stored in that config backup.

Does it matter?

Also...is there a simple way to test your backup job encryption password to ensure that you will be able to restore? Id like to make sure what is documented is actually working just to be sure. There is no enterprise manager in this instance. Its purely VBR backing up locally and backup copy jobs going offsite.

[vnikiforov]

Hello,

A Scale-Out Backup Repository extent is just another simple repository underneath, so the files on it stay readable after the backup server and the Scale-Out Backup Repository objects are gone. On a fresh backup server, add each of the four extent folders as a backup repository and tick the import of existing backups at the Review step. You can also rescan the repositories later. Imported backups show up under Backups > Disk (Imported). Encrypted ones sit under Disk (Encrypted) until you specify the password.

Data locality keeps a chain and its metadata (.vbm files) on one extent, so there is nothing to consolidate. If a chain was split anyway, gather its files into one staging folder as described in Importing Backup Files from Scale-Out Backup Repositories, or rebuild the Scale-Out Backup Repository from the same four extents on the new server and rescan it. Rebuilding is safe only when the original server is gone.

Configuration restore is the shorter path. It brings back the repositories, the Scale-Out Backup Repository, the jobs, the credentials and the encryption passwords, so encrypted backups open without retyping anything. Because you have passwords in Password Manager, your configuration backup must be encrypted, and an encrypted configuration backup carries those keys. Configuration backup cannot target a Scale-Out Backup Repository, so keep it somewhere the DR site can reach.

Veeam Backup & Replication V13 has a Verify button under Credentials & Passwords > Encryption Passwords, see Verifying Passwords.