Feature Request: VB365 GFS option

[Char_GP]

I had this topic discussed in the ticket 07526219.
We would wish to have a GFS option like we have in VBR.

Currently for VB365 it's possible to set any number for the retention period, so we thought about makeing an additional job for weekly/monthly/yearly backups.

The problem here is, that for the job schedule, there are too limited options. So the maximum schedule would be 7 days.
If there would be at least the option to set each X weeks or each X months, that would be a good workaround, if an implementation of the GFS option like it's in VBR would not be possible.

Currently for us this could become a disqualifying factor for a license extension.

[Mildur]

Hello Char

Welcome to the forum.
I would like to understand, why do you need GFS restore points? Can you please elaborate?

Microsoft 365 workloads are different from machine backups in Veeam Backup & Replication. VB365 also use different repositories types. Also running regular full backups (GFS) wouldn't not work very well because of the throttling policies applied to SharePoint and Exchange Online APIs.

Best,
Fabian

[Char_GP]

Hi Fabian,

We often receive tickets to recover SharePoint sites from older dates. Most of the files are very important, and if they are not recoverable, it can result in significant damage. Since we have encountered more of these cases, the business no longer wants to accept this situation and is requesting a solution.

Setting the retention to a year, for example, would take up too much space, so this is not currently an option for us. I understand your point regarding the throttling policies, but if we had the option to keep a two-month or one-year backup, similar to GFS, then it wouldn’t really matter to us if it takes a few days to create.

It is still better than not having this option available at all in our case.

Best regards,
Char

[mjr.epicfail]

Hi Char,

Snapshot backup model will backup everything you have in the tenant and only the changes like:
- editing (adds a new version of the file)
- deleting

Will be rotated out after retention is hit.
for example:
Retention of 1 year.
version 1 of a file is getting changed and now you have a new version: 2.
Your backup contains both versions.
After a year the version 1 of the file will be rotated out of the backup, but version 2 will remain.

Deleting of a file works the same way.
You delete a file and only after the retention period is hit, this fill will be deleted.

If you want to create a full and make for the sake of argument 12 month backups.
You will have roughly 12x the current data storage volume of storage.
This will be vastly more than just adding some years to the retention.

As for a solution for now.
Don't enable retention on the repository
Create a new repository
Create a new job or point the existing job to the new repository.

This will make sure you will keep a year worth of backups (kind of how GFS would work)