What I’ve said above for Synthetic full is mostly negated when using Synthetic Full with fast clone, for example a synthetic full that used to take about 20-22 hours for me when I migrated to fast clone went to an average of 19 minutes, that was on Windows Server 2016! 2019 & 2022 have been even better performing. This starts to play an important factor in how your repository is configured from a performance perspective, is it spinny (if so what RPM), is it flash and then what RAID configuration is being used. Synthetic Full is 2 IO (1 read, 1 write) from and to the destination repository. So it is better from a performance standpoint. There is another story to be told from an IO perspective here however as well, especially when we consider JUST synthetic full vs synthetic full with fast clone.Īctive Full is 1 IO (read) from the source datastore, 1 IO (write) to the destination repository. Hi in the same camp as I’ll only use Active full if I’ve got failed backup verification which is extremely rare.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |