Synthetic Full backup with S3/Glacier?
I'm trying to figure out whether Synthetic Full will be reasonable with Glacier storage class. Does anyone have a sense of what is going on behind the scenes?
Is it just marking the old base version and increments as deleted and then uploading a complete new base version of that particular file? If so, this should not trigger any Glacier requests, right?
Or is there something more complicated going on?
I was thinking of doing incrementals daily, and then Synthetic Full every two weeks. I don't mind having a 4 hour Glacier request delay once every two weeks, if that is what is needed. But I'd rather not be paying for tons of requests.
Synthetic full backup is incompatible with glacier tier AWS S3 storage. the software will not be able to combine the files stored in glacier storage. If previous uploads are in the glacier tier, the synthetic full backup will be ignored, and the software will upload the image from scratch.
AWS S3 Glacier does not support object aggregation
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
Connect (Remote Desktop)
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
FAQ - Managed Backup - Customization
FAQ - Managed Backup - Licensing
FAQ - Managed Backup - Storage
FAQ - Managed Backup - Backup Client
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2022 MSP360 Forum