HOW TO USE MACRIUM REFLECT WITH LOW DISK SPACE FULLSo if you only ever have one Full backup at your destination, then the ONLY time that disk space option will be relevant to you is when you're creating another Full. However, if you're making an Incremental at the time the low disk space threshold is reached, then that Incremental's parent Full will NOT be considered for purging, because deleting that Full would render the Incremental that Reflect is currently creating useless. But sometimes people would rather keep older backups since in general if a new backup fails, there's an opportunity to run them again later unless your system just happens to die right after that failed backup. It is a last resort if you would truly prefer to lose old backups early instead of allowing new ones to fail. As you suggested, that can mean you'll lose quite a few backups, which is why that setting is NOT intended to be used as a replacement for a retention policy that is achievable based on the size of your backups and your destination capacity. A set is defined as a Full and all of its child backups. However, notice that the option says "Purge the oldest backup set(s)". So if you drop below 5 GB partway through a backup, Reflect will pause the backup, perform the purge, and then keep going. The free disk space threshold purge option can be triggered in the middle of a backup job. It's a good thing you asked, because you're going to need to rethink your strategy a bit, and it would probably be a good idea anyway.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |