Weekly backup to object storage

[InFrance]

Hi,
We currently perform all our Veeam backups to a local hardened repository.
All servers, including non critical servers, are currently backed up every weekday evening.(forward incremetals with synthetic full)
We would like to add an additional copy to an external immutable object storage
We are limited by time and bandwidth so would like to just backup some non critical servers just on the weekend.

The objective is to perform a backup (or copy) every weekend for 4 weeks (4 restore points) for non critical servers.
A new repository with a maximum immutability period of 27 days to cover the 4 weekly copies would be created as the target repository.
The idea is to have a second "direct to object storage" backup job for the servers that runs just on weekends.

However, immutable backups require a weekly synthetic full or active full backup.

Would this mean that we would essentially perform a full backup every weekend?

Is there a better way of performing a weekly backup (or copy) for some servers or would I need to perform non immutable backups to achieve this?

I would appreciate any comments

Regards

[Mildur]

Hello InFrance,

However, immutable backups require a weekly synthetic full or active full backup. Would this mean that we would essentially perform a full backup every weekend?

No, regular full backups are not necessary on immutable object storage. You are good to go with forever incremental chain for your "direct to object storage" copy job
It's also important to note that synthetic full backups cannot be set up for direct-to-object storage jobs. Active fulls can be implemented, but they will require the storage space of a full backup.

For transferring one copy per week to object storage, you can use a periodic Backup Copy job set to run on a specific weekday.
However, it's worthwhile to consider having daily backup copies outside of your primary data center for recovery purposes. I often ask my customers: "Can your business survive if only a backup is available from 7 days ago?"
The loss of 7 days of production data can be catastrophic for some organizations.

Best,
Fabian

[InFrance]

Fabian,
Thank you for your reply

I will try a weekly direct to object storage copy

regards

[lucaliga]

Hello,
we are in a similar situation. Simple question: We want to have an offsite backup cloud. Which is the better approach ? Use the object storage repository cloud (offsite) as target for a Backup Job or a Backup Copy Job ?
The doubts comes from two different statement by Veeam experts. In Veeam R&D forum FAQ Object Storage by HannesK there is:

Q: Are regular full backups required with object storage?
A: Default setting for backup and backup copy Jobs to object storage based repositories is forever incremental.

Q: How does GFS work if there is no regular full?
A: Restore Points will be marked as GFS (weekly, monthly, yearly). A regular full backup is not needed.

Gostev in a few year ago comment (I don't have original link but I copied and saved the entire statement) wrote:
Typically, Veeam users who implement our reference architecture with primary and secondary repositories only offload GFS full backups which are created by Backup Copy jobs in the secondary repository. While those regular incremental chains are typically within operational restore windows, so they should not be offloaded to start with. And beyond operation restore windows, it usually makes no sense to keep daily incrementals - either locally, or offloaded.

Seems to me these are opposite sentence. HannesK suggest to NOT use full backup instead Gostev suggest to use full backup.
My question is: Off-site backup on object storage service (S3 or not, object lock immutability or not, in my case is Wasabi no object lock) should be setup in which mode ?
A) Forever incremental (beside first execution run active full) of either one between a backup job or a backup copy job like HannesK suggest
B) "Forever" copy the latest existing GFS Full backup available created by Backup Copy job like Gostev suggest

Thanks for suggestions.
Luca