moodjbow wrote:No, we didn't seed since we used the Hyper-V manual that is missing such information. Why didn't you guys update it? The topic "Creating Seed for Backup Copy Job" is only under vSphere manual.
moodjbow wrote: But what will happen if it takes longer than 24 hours to copy the latest restore point, say because of large data changes on the file server?
moodjbow wrote:And one more improvement step would be if you make clear to us IT admins that the interval on the initial copy job should cover the whole chain of backups in the past that we want to copy.
I also made a mistake with smaller interval and now only hope that we don't have to restore from secondary repository too early information!
moodjbow wrote:The copy job shouldn't stop until finished when the copy process takes longer than 24 hrs.
The copy job shouldn't error out when the parent backup job takes longer than 24 hrs. to complete.
Users browsing this forum: Bing [Bot] and 61 guests