Hi!

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:
https://www.cloudberrylab.com/download/CloudBerry_Dedup_Getting_Started.pdf

Please let us know if you have any questions!

Best Regards!