Continuous Replication Delete First Problem
-
@olivierlambert So, Continuous Replication works but I have a problem with the "Delete First" option.
When replication runs the first time it transfers a full copy. Subsequent runs do a delta update. Each delta update is merged into the destination copy to keep it up to date. With this there is a single ready to run backup copy. I have it run every hour to keep the backup rather current.
After a week of delta update runs I want it to start over with a new full copy just to make sure that over time errors
have not been merged into the replicated copy. I set the full backup interval to 168 (number of hours/runs in a 7 days) so XO will do a full backup.Normally the full backup will run to the destination storage before the old full copy is removed. The problem I have is there is not enough storage space on the destination machine (I know, buy more storage) so I selected "Delete First" for the job. It seems like a good option as the old full backup will be removed before the new full one starts and it frees the disk space and works as needed. ...BUT... it does it for delta updates too. This means the full backup destination copy is removed before the delta starts and then there is nothing to apply the delta to. So the delta update fails. The next run will do a full backup because there is copy.
I think that "Delete First" should be smarter and only delete the FULL copy (and extra deltas) when a NEW FULL copy is being done. It should NOT delete the only full copy when just a delta is running and backup expects a full copy to still be on the destination storage.
Or should there be a new option for "Smart Delete First" that checks for available space on the destination and estimates if there is enough room for a duplicate copy before the backup starts. If there's not enough space then delete the old backup and start the new one, or fail if deleting would still not allow for enough free space on the destination.
-
That's a question for @julien-f
