![]() It will create a new full file and replace the original one, saving you space overall, but still requiring ~2,5x (same as conventional fulls) free space for the duration of the new full creation. It only works if no synthetic or active fulls are selected, so reverse incremental or forever forward incremental backup methods. You also have to be mindful of the size on the repository - both active and synthetic fulls will occupy additional space on your repository that is roughly equal to the initial full file and stay there until retention clears off oldest chains. ![]() For example, first three weeks a synthetic will be created on Saturday, but on the last Saturday of the month an active full will be run instead. ![]() Furthermore, synthetic runs on a weekly basis only whereas active full can be selected to run on the same day as synthetic, but both weekly and once a month. If they're scheduled to run in the same day, then active full will have the priority and will be run instead of synthetic. To answer your question about the ability to select both Synthetic and Active fulls, that is true. ![]() I think Falldog covered the majority of your questions, those animations are really good for understanding how retention works and what role Fulls plays in it, depending on the backup method. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |