Synthetic Full to Wasabi Retention
Here's the scenario I'm envisioning:
October: Perform our initial full > incremental's for the rest of the month
November: Synthetic full on the first Sunday of the month > incrementals the rest of the month
December: Synthetic full on the first Sunday of the month > incrementals the rest of the month
I'm using Wasabi as only a DR strategy so trying to keep the amount of data we have in Wasabi as low as possible.
What retention settings would accomplish this? Would a bi-weekly synth full perhaps be more appropriate?
Thanks for your question!
Can you please let me know what's the role of the server, what is the set of partitions, what applications located where and what's in your scope for the backup that you're describing?
Do you have any legal requirements to store data longer?
Role of the servers are typically just Domain Controllers/File Servers. A couple are running SQL. We always do two volumes, one being system only and the other for data. Applications would be located on the data volume. No legal requirements must be met. For the synth full we would be doing image-based and all partitions.
1. Back up the system with image-based backup and files/data with file-level or a specific application backup
2. For DC I assume daily block-levels and weekly fulls, for file-servers, for the system partition, I'd say weekly block-level and monthly full.
For data partition, frequency should be based on the nature of the data and the daily incremental part.
Speaking of retention,
For system partitions, it should be at least 30 days,
For data partitions, it depends on your internal requirements/policies.
I hope, this would help.
Unfortunately, I think this is over complicating what I'm trying to accomplish.
My goal really is just to set up each client the same:
-Backup all partitions
-Synthetic full backup
-Full backup: occurs every 1 month on first Sunday at 01:00
-Block-level Incremental backup: occurs every 1 day at 18:00
I'm so used to GFS and I'm struggling to understand what my retention policy should be when utilizing Synthetic Fulls. Say I want to keep 1 month. Do I do this for instance?:
-Specify custom retention policy for plan
-Keep number of versions: 1
or do I do:
-Delete versions older than 1 month
And do I or do I not check 'Always keep the last version'?
What would be the best method for a one month retention?
Think about 93 day retention by wasabi and their early delete fee
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
Warning 'cannot be purged' on retention policies MSP 360 backup in combination with Wasabi retention
Local backup possible issues if Block Level, Retention policy, and Full Backup Schedule?
Synthetic Full Backup on Wasabi
Synthetic Full & Wasabi
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2024 MSP360 Forum