Create Synthetic full backup periodically ?

[Soze]

Hello everyone,

I contacts you by what I have a little trouble understanding the synthetic full backup ... I obviously read your knowledge base that speaks, but I confess not to understand everything (my English is very basic) ...
Can you tell me a little more clearly and simply, please?

In truth, I do not really understand the difference with the full backup.

When I read the documentation on your site, you have the synthetic full backup as better, having only advantages compared to full backup.
But what are the drawbacks? For if this is the best synthetic, so always use it right?

Thank you in advance !

[foggy]

Active and synthetic fulls each have their own advantages and drawbacks. Active full reads data from production datastore thus affecting running VMs, while synthetic one uses existing backups to "synthetically" make a new full from them. However, active full is a sequential write to the target repository while synthetic one requires random I/O and puts higher load on the target disks. You select what is more acceptable in your case.

[Soze]

So the synthetic backup uses more I / O and therefore can slow down the restore?

[foggy]

It uses more I/O during creating full backup, not during restore. Both types of fulls are equal in terms of recovery.