Backup Copy interval start time

[y1008946]

In the past I've often had troubles with changing the interval start time.

Sometimes after changing the start time, the interval can still stop at the old time.

For example, yesterday at 4:30pm I had a disabled backup copy job which was due to expire at 3am.

I had just seeded the backup copy file and I was wanting to sync it for the first time.

Knowing that the first run after seeding takes a long time (it says calculating disk digests) I wanted to change the interval start time so it didn't expire during the middle of the backup copy job.

So I changed the interval start time to 4pm and enabled the job.

When it got to 3am the interval expired though and the job failed.

What should I have done to ensure the backup copy job started at the time I set?

Many Thanks

Case no. 00607608

[y1008946]

I've manually run the backup job to try to sync the backup copy job again.

The backup copy job has started to sync again but it is running terribly slowly, it has read 7GB in an hour and it is still on 0%. At that speed it is going to take days.

30/07/2014 07:16:57 :: Hard disk 2 (410.1 GB)
30/07/2014 07:17:14 :: Changed extents are not available.

This backup copy job normally only takes 2 hours, why is it going so slow and what can I do?

Many Thanks

[foggy]

Unless you click Sync Now, the current copy interval will finish according to the 'old' start time value, but the next interval will be stretched till the new start time value. Please review the description of the synchronization Interval start time change, given in the user guide.

Regarding your second question, digests calculation, which is required after re-mapping backup copy job to existing backup, can take considerable time, depending on the backup size.

[y1008946]

Thanks for explaining how it works.

When the backup copy job failed yesterday it had finished calculating digests and it was at the stage of loading them from the target. From past VMs usually it means it is only a few hours away.

29/07/2014 21:11:28 :: Calculating disk 2 digests (100% Done)
30/07/2014 01:05:00 :: Changed extents are not available.
30/07/2014 01:05:01 :: Digests are missing on source, loading them from target

After the backup copy job failed yesterday I ran the backup job. It made the backup copy job start again and it has been running for 8 hours, currently at 10% complete. This is all it has said for the last 8 hours.

30/07/2014 07:16:57 :: Hard disk 2 (410.1 GB)
30/07/2014 07:17:14 :: Changed extents are not available.

The changes from the seeded backup copy, to the two incremental backups, totals 16 GB. Its transferred 15.5 GB over the WAN so far, do you think this job is just going to keep going and going. Or is it likely that the last 90% will take no time at all?

What does 'Changed extents are not available' mean?

Thanks

[foggy]

This message means that source WAN accelerator does not have information about changed blocks and, since the job was mapped to the new backup file, the entire disk needs to be read.