Backup Copy - wrong starting time?

[redhorse]

Hello,

yesterday I've changed the starting time of two backup copy jobs to 1 am, the backup copy job has automatically restarted after the configuration change. Now, I wonder why both jobs started today at 6 am, that's also the time where the no copy windows starts. I expected the jobs to start at 1 am, did I understand the configuration wrong?

[DGrinev]

Hello,

The backup copy jobs are working in continuous mode, looking for the restore point during the predefined interval which starts at 1 AM in your case.
Can you share the source backup jobs schedule, it should help to understand the reason for the said behavior. Thanks!

[redhorse]

The three source jobs started at 6, 7 and 9 pm, the corresponding backup copy job was finished at 10.19 pm and all three restore points were transferred.

The backup copy job log says:
27.06.2019 06:00:11 :: Job finished at 26.06.2019 22:19:54

But as I configured the backup copy job to restart daily at 1 am I don't understand why the job restarted at 6 am.

[wishr]

Hi RH,

Could you please post the whole log or at least ~30 lines before the aforementioned line and ~10 lines after?

Thanks

[redhorse]

Code: Select all

26.06.2019 16:41:20 :: Job started at 26.06.2019 16:41:19  
26.06.2019 16:41:21 :: Continuing current copy interval  
26.06.2019 16:41:23 :: Building list of machines to process  
26.06.2019 16:41:26 :: Waiting for permitted network usage period  
26.06.2019 20:00:08 :: Total size: 53,6 GB  
26.06.2019 20:00:08 :: Processing server1
26.06.2019 20:00:08 :: Processing server2
26.06.2019 20:22:08 :: Waiting for new restore points  
26.06.2019 21:49:09 :: Total size: 149,4 GB  
26.06.2019 21:49:09 :: Processing server3
26.06.2019 22:14:11 :: Starting full backup file merge  
26.06.2019 22:14:11 :: Required backup infrastructure resources have been assigned  
26.06.2019 22:14:17 :: Restore point 28.05.2019 06:00:00 created successfully  
26.06.2019 22:19:52 :: Full backup file merge completed successfully  
26.06.2019 22:19:54 :: Waiting for the new copy interval  
27.06.2019 06:00:08 :: Copy interval has expired  
27.06.2019 06:00:11 :: Load: Source 0% > Proxy 0% > Network 99% > Target 0%  
27.06.2019 06:00:11 :: Primary bottleneck: Network  
27.06.2019 06:00:11 :: Job finished at 26.06.2019 22:19:54

[wishr]

Your job started at 26.06.2019 16:41:19 and then finished at 26.06.2019 22:19:54, not at 6AM as you mentioned. Could you post your copy job and interval configuration screenshots?

[redhorse]

Yes, the job started at 16:41 I reconfigured it at this time. The job finished the last restore point at 6 am but the copy interval has also expired at 6 am but that should be 1 am in my oppinion. That's important because tape job uses this backup copy source and therefor the interval has to be finished to transfer the latest restore point to tape.

Screenshot is not possible now, but here is the configuration:

Job -> Copy ervery 1 day starting at 01:00
Schedule -> 00:00 to 05:59 (Enable), 06:00 to 19:59 (Disable), 20:00 to 23:59 (Enable)

Anything else?

[DGrinev]

Wait a minute, I see in the log that the restore point name is 28.05.2019 = May 28th (not June).
Is there any chance you have GFS Retention enabled and that was GFS restore point creation time? Thanks!

[redhorse]

No GFS retention is not enabled, I was also wondering about that restore point mentioned in the log. This is the full file (vib) in the chain which is the oldest restore point, I also see this in other backup copy jobs where this behavior with the wrong starting time not occurs (copy interval expires on starting date of the cycle).

[wishr]

Hi,

Here you go:

The below line states that the job was waiting for the permitted interval.

Code: Select all

26.06.2019 16:41:26 :: Waiting for permitted network usage period   

Then it started at:

Code: Select all

26.06.2019 20:00:08 :: Total size: 53,6 GB 

...successfully processed some backups...

Then the copy interval expired:

Code: Select all

27.06.2019 06:00:08 :: Copy interval has expired 

And you got the data transfer completion timestamp:

Code: Select all

27.06.2019 06:00:11 :: Job finished at 26.06.2019 22:19:54

That matches your configuration.

Thanks

[redhorse]

But what effect has my configuration that the job starts every day at 1 am?

Because the job copy interval expires at 6 am and not at 1 am (as my other jobs) the restore points are not affected for the tape backup.

[veremin]

I think the observed behaviour is covered in User Guide; check change of the backup copy interval start time section. Thanks!

[redhorse]

Yes, now everything is clear.

Thanks all for your help!