Wasabi target best practice

[costasppc]

Hello,

We are testing Wasabi as backup destination.
I have a question regarding the job configuration. Is it better to create jobs for local disks along with copy jobs to wasabi or different jobs for local storage and wasabi?

Best regards

K

[Mildur]

Hi Kostas

I recommend 1 backup and 1 copy job. If you use two backup jobs, you will put load on your production environment twice.

There are also other considerations regarding application aware processing and database server. Having two backup jobs do application aware backups for a MSSQL server may break transaction log backups (if you use them).

Best,
Fabian

[costasppc]

Thank you very much for your answer, so I will create the jobs as you suggested.

Best regards

K

[mtv]

I have followed this best practice and make backup copy job to Wasabi.

After retention (30 days) has expired, I've noticed, that in Wasabi console storage utilization is still rising and nothing is deleted. Wrote to their's support and they answered that they don't see any demands from Veeam side for deleting and that is because backup copy is doing only incrementals and i must run at least once monthly full backup to purge data and make changes with the retention periods.

But in backup copy there is no option to schedule full backup - only right click and Active full button.

What can i do because i cannot imagine manually doing this?

[mtv]

Of course doing (as wasabi) suggested additional full (beside existing synthetic once per week) on main job is not (best) options since it will reflect also to NAS and ocupied storage there...

Would GFS on copy job to Wasabi help solve this problem?

[Andreas Neufert]

To optimize IO, the blocks that we store in object are kept up to 10 days longer. So you will see that deletion will start after retention end date + 10 days.

[mtv]

thank you! So no need for full backups (in connection with the deletion from wasabi as they tell me)?

[Andreas Neufert]

No, this is even not possible. We write incremental forever data blocks in separate objects and just link restore points together from these blocks. The delete of blocks/objects that do not belong to any restore point will start when the immutability period is over, which is retention + 10 days.

[mtv]

By those +10 days you don't mean block generation? Because imutable period is set much lower than retention and it (immutability) is already expired including block generation time.

My settings are from 1st day:

- Immutability 20 days
- Retention 30 days

Today we are on 38th day day since first backup copy and no delete calls from Veeam to Wasabi as their helpdesk established

[Mildur]

Hello MTV

For immutable backups on object storage, please use this formula:

- immutability period + retention + block generation = actual object storage retention

For your specific scenario, actual object storage retention for a single object is 60 days:
- 20 days + 30 days + 10 days = 60 days

Best,
Fabian

[mtv]

Thank you!

Huh I didn't expect this because the backup whose retention (30 days in my case) expired had already been deleted from the local VBR. Does this mean that i will still paying for them (60 days to Wasabi) but I can't use them (anything older than 30 days is no longer available in VBR)?

Isn't it better then to set retention to 1 and immutable to 30 and have all immutable for 30 days (now 20 days) and billing for 41 days by provided formula (now 60 days)?

Regards,

M

[Mildur]

Hi MTV,

We are currently working on optimizing storage usage for immutable backups.

In the meantime, you should configure your settings according to your needs.
If you want to be able to restore from the last 30 days, then set a retention policy of 30 days.

You can use our calculator to estimate the required size for Object Storage: Veeam Backup & Replication Calculator..

Best,
Fabian

[mtv]

Thank you Fabian! I'm glad we've cleared that up. Will do as suggested (30 days retention).

PS: is there any ETA for new version with mentioned optimization?

Regards

[Mildur]

Hi mtv

No ETA or information to share about potential enhancements for now.

Best,
Fabian

[mtv]

one more question - what about GFS (like couple of monthly GFS's) if it is outside retention (for retention we established that actual retention in terms of deleting / billing = immutability period + retention + block generation)?

Regards

[Mildur]

Hi mtv

GFS backups in "direct copy to object storage" scenarios are immutable for the entire retention time.
Please use our calculator as shared in my previous comment to get an estimation about the storage usage.

Best,
Fabian

[Drew Schlussel]

Make sure you are only required to support 30-day retention - as a Veeam customer, that is something you can request via an email to support@wasabi.com