I am not sure I would use SOBR in this case.  You can do standard repo for local/remote (Storeonce) and then also for Scality.

Then when setting up jobs you can use the Backup Copy Job for the remote copy to Storeonce and use a GFS Backup Copy to Scality to meet the retention requirement there.

This to me would be the simplest way as using SOBR where you put Scality in Capacity/Archive Tier might prove more challenging and at least with a BCJ you can control the GFS and retention you need.

thanks Chris. Will experiment but we do need the storeonce to be storage level copy, not image.

If that is the case could you not do storage level copy on the Storeonce devices from local to remote versus using Veeam then?  The BCJ with GFS can still be used for Scality.

Hi ​@MavMikeVBR 

Here is the proposed solution:

Weekly Backup

• Schedule your backup jobs to run weekly as per your requirements.

Local Copy (14 Days) – StoreOnce

• You can create a local SOBR that uses your StoreOnce storage. Set the retention policy for this SOBR to 14 days to ensure that the backups are kept locally for this period.
• Configure backup copy jobs to transfer backups to StoreOnce.
• Set retention for the StoreOnce tier to 14 days.

Remote Copy (14 Days) – StoreOnce

• For the remote copy that also uses StoreOnce, create another SOBR that includes remote storage.
• You can use a remote StoreOnce device (e.g., in a secondary data center or cloud storage) as a remote target.
• Set the retention for this SOBR to 14 days as well.

Move to Scality for 6 Months

• Create a third tier in the SOBR for Scality (assuming it’s cloud or object storage). You can add Scality as a performance tier or capacity tier, depending on your Veeam version.
• The backup jobs will initially be stored in the local and remote StoreOnce repositories.
• Once the data ages beyond 14 days, it can be moved automatically to Scality.
• Set the retention for Scality to 6 months.

Monthly Backups Kept in Scality for 5 Years

• For your monthly backup requirement that must be kept for 5 years, this is a bit tricky but achievable with a combination of backup copy jobs and retention settings.
• You could configure monthly backup copy jobs to only copy monthly backups to Scality.
• Once in Scality, configure the retention for these specific backups to 5 years.

Final Structure:

Tier 1: Local (StoreOnce) - Retention 14 Days

Tier 2: Remote (StoreOnce) - Retention 14 Days

Tier 3: Scality (Capacity Tier) - Retention 6 Months (with Monthly Backups retained for 5 Years)

I think I’ve read this correct from your suggestion….so

SOBR1 - local with just performance tier. Storeonce local repo

SOBR2 - remote storeonce repo in performance tier plus scality (set scality repo to 6 months retention) in capacity tier, move after 14 days but it keeps for 6 months yes? as per repo definition

daily backups - 14 days local (SOBR1) with copy job to SOBR2

monthly copy job with 5 years, this will need to be image-level backups but the problem here is where is the source copied from? Problem I’ve seen is that as storage level copy (storeonce to storeonce), veeam doesnt get the copy from the remote copy which it has to be. It gets it from the local which is more data over the link.

LOCAL is site1 with storeonce

REMOTE is site2 with storeonce and scality. Copies to scality need to be local to that site.

this is definitely more complex that I thought….

If you use standard repos instead of SOBR you can make it easier.  But if SOBR is required it does make things a little bit harder to configure.