tsightler wrote:I don't think he's trying to chain the backup job off of the replication, he specifically states that he chains the replication job to run right after a backup job to immediately update the replica with the new data. The problem is, he's likely running the backup job fairly often, and if it's schedule happens to start before the chained replica job finishes, it kills the replica job and leaves things in an inconsistent state. He needs a way to make the backup job not try to run again on the schedule until the replica job finishes.
Your understanding is spot on. The backup and offsite replication happens 4 times a day. Most of the time it's fine. Once a month when the dedupe does the thorough garbage collection, it churns enough bits to make the next backup / replication take much longer than normal. Replication isn't killed until the backup job completes and it starts the merge process on the very backup that the replication job is trying to use.
tsightler wrote:I have an alternative approach that I would suggest, what about simply disabling the Backup job in the pre-script of the replica job, and re-enabling the backup job with a post-script in the replica job. That would seem to achieve the goal fairly elegantly and reduce the code to the following:
WOW! What an awesome idea! I'll give that a shot. I won't be able to fully see if it works until almost another month later. We just recently had the monthly huge backup / replication occur a few days ago.
Thanks for the suggestion!
PS: Sorry, we do not have Veeam One