Best Practice: Image based backup to Dedup-Server
what is the best practice for image based backups to Dedup-Server?
Should we preform fulls by every shedule or only one full and then forever differentals?
Any benefits for one of this options and what about recovery time?
In the current version of Dedup Server there´s no possibility to set up Retention Policy and control versioning (unlike standard backup without using Dedup Server where you can remove older versions) so all the versions you´re uploading via Dedup are staying in the cloud. In this case there´s no need to schedule Full Backup and run it from time to time, you can just run full backup one time and then run just differentials.
Recovery time is longer than with standard backup without Dedup Server because the process is using Postgres Repository to prepare data for the restore and assemble it from lots of deduplicated pieces and it may take some time depending on the size and type of the data you have. It´s hard to evaluate it so the easiest way to check it for your particular case is to test it in your environment.
Check this guide for more info on Dedup Server:
Please let us know if you have any questions!
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 - CloudBerry Dedup Server
FAQ - Managed Backup - Customization
FAQ - Managed Backup - Licensing
FAQ - Managed Backup - Storage
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2022 MSP360 Forum