jhines97 wrote:If that option was implemented as a scheduling option for Backup Copy Jobs, or if an option to start another job was implemented as a check box in the Backup Job scheduling box you would be able to chain a Backup Copy Job to start right after a Backup Job was completed.
Backup copy job is a bit different in terms of scheduling, it runs continuously and is based on the copy intervals. Basically, it is chained to the source backup job in the sense that it waits for it to create the restore point and immediately starts copying data. If it is unable to meed the required backup window in your case (12 hous), it means that it is not properly configured or environmental limitations don't allow it to do this (too slow connection, for example). Was the initial job run successful? If you seed the initial backup copy job run or used the longer interval to allow the full data to be transferred, I guess it would then be able to copy all the changes during subsequent intervals.