So in this scenario, the SOBR make no sense and would only increase complexity. Customer don’t have an object storage, has currently an primary target for the whole jobs and the new target site with immutability (on two tiers) could be a good solution. so in total, i think we have to go with two BackupCopy Jobs to achieve this goal. Please refer to the Veeam Help Center for these kinds of documents. It is not meant as a full documentation or detailed explanation of the features. This guide is intended to provide best practices for Veeam Backup & Replication. Maybe some suggestions about this subject :). Veeam Backup & Replication Best Practices Welcome to the Veeam Backup & Replication Best Practices. Specially with the release of new Hybrid HPe Apollo (ssd/hdd).

I am thinking about this subject for a while and don’t know how to do it. Backup Infrastructure To communicate with HPE StoreOnce, Veeam Backup & Replication uses two Data Movers that are responsible for data processing and transfer: Veeam Data Mover on the VMware backup proxy Veeam Data Mover on the gateway server The HPE StoreOnce storage cannot host Veeam Data Mover. Unfortunately i think Veeam don’t have mecanism to detect to write on the closest host (the same). Then the backup copy jobs schedule are continuous, with primary Backup Copy jobs to copy at 2AM (usually finishes in 1 hour), and DR jobs to copy at 3AM. You will need two SOBR if you have many repos and you will need to use backup copy jobs. ago I just set the start time for the primary backup job (100VMs) to 10PM (incrementals usually finishes by 2AM).

You will need to use object storage if you want to achieve it.Ĭapacity Tier - User Guide for VMware vSphere () Mentionned SOBR but keep in mind, capacity tier is not supported for hardened repo.

Veeam best practice backup job