Back up copy job timing.

[larry]

I have a backup job that kicks of a 6:30pm.
Then a backupcopy job at 12am.
Worked as expected until one time one VM missed the 12am window.
Now everyday the backupcopy of that VM occurs shortly after 6:30pm then the others start at 12am.
Can you force a backup copy job to redo all VM copies at the start time (12am) ? There would be no change to that one vm but I want the offsite copy to occur at 12am.
The last 7 times the one VM occurs shortly after 6:30pm ( when the vm backup is done)

This is how I would want it to work once after an issue but on the next run it should go back to 12am, Veeam knows becuase a warning that no changes occured.

Code: Select all

BackupSync job: Syn-2008-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 8:06:45 AM.
 Success
2 of 2 VMs processed 
 

Tuesday, September 10, 2013 12:00:27 AM 
Success 2 Start time 12:00:27 AM Total size 1000.0 GB Backup size 939.6 MB  
Warning 0 End time 12:00:01 AM (+1) Data read 2.4 GB Dedupe 1.0x 
Error 0 Duration 23:59:33  Transferred 923.0 MB Compression 2.7x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
Ser-2008 Success 12:01:51 AM 12:03:21 AM 380.0 GB 1.2 GB 564.7 MB 0:01:29   
SQL-2008 Success 6:37:50 PM 6:39:04 PM 620.0 GB 1.2 GB 358.3 MB 0:01:14   
 
 
  

BackupSync job: Syn-2008-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 8:06:45 AM.
 Warning
2 of 2 VMs processed 
 

Wednesday, September 11, 2013 12:00:05 AM 
Success 1 Start time 12:00:05 AM Total size 760.0 GB Backup size 0.0 KB Job has failed unexpectedly
 
Warning 1 End time 5:25:00 PM Data read 1.2 GB Dedupe 1.0x 
Error 0 Duration 17:24:54  Transferred 982.7 MB Compression 1.0x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
Ser-2008 Success 12:02:37 AM 12:03:53 AM 380.0 GB 1.2 GB 491.3 MB 0:01:15   
SQL-2008 Warning 12:01:40 AM 5:25:00 PM 0.0 KB 0.0 KB 0.0 KB 17:23:19  Latest restore point is already copied             ****this is where the vm needs to be flagged to wait until next cycle.
Task has been cancelled
 
 
 
  

BackupSync job: Syn-2008-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 8:06:45 AM.
 Success
1 of 1 VMs processed 
 

Wednesday, September 11, 2013 5:25:19 PM 
Success 1 Start time 5:25:19 PM Total size 620.0 GB Backup size 1.9 GB  
Warning 0 End time 12:00:06 AM (+1) Data read 3.9 GB Dedupe 1.0x 
Error 0 Duration 6:34:46  Transferred 1.4 GB Compression 2.7x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
SQL-2008 Success 6:38:30 PM 6:41:43 PM 620.0 GB 3.9 GB 1.4 GB 0:03:12   
 
 
  

BackupSync job: Syn-2008-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 8:06:45 AM.
 Success
2 of 2 VMs processed 
 

Thursday, September 12, 2013 12:00:15 AM 
Success 2 Start time 12:00:15 AM Total size 1000.0 GB Backup size 1.1 GB  
Warning 0 End time 12:00:00 AM (+1) Data read 2.5 GB Dedupe 1.0x 
Error 0 Duration 23:59:44  Transferred 1.1 GB Compression 2.3x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
Ser-2008 Success 12:02:51 AM 12:04:30 AM 380.0 GB 1.3 GB 741.3 MB 0:01:38   
SQL-2008 Success 6:37:52 PM 6:39:04 PM

[veremin]

You can specify the starting time in the settings of backup copy job: settings -> Copy every -> Starting at. Otherwise, you can wait till the 12 o’clock and click “Sync Now”, this action will create a new synchronization interval that starts at 12. Thanks.

[larry]

I have it set to copy at 12am everyday the issue is one VM is not sync then but it starts afer the backup job. The job is continous. I don't want to be here at 12am to click sync now.

Looking at other jobs it looks like if I do an extra backup then it will sysc at the one vm and after it will stnc at the right time. I just don't normally let backups go over the WAN during the day. The way it is now, after one failure backupcopy will never start all vms at the right time untill all VMs in a job have one failure or the backup job fails or has an extra run.

the two work arounds that I use to fix is to do the extra backup and allow so backups over WAN during the day or to change the start time of the copy job after a failure.

Below is a job that after a failure half the VMs would get backed up at 11:30 pm ( backup job just finished) the other ones the were successful the preivios time are backup copied at 5am which is wat they were suppose to do. I then switch the start time of the backupcopy to 2am, they all process at 2am now. Both quick fixes work I just need to keep an eye on when the copy jobs are taking place to use our WAN bandwidth the way we need to. The good part is I fixed my issue why the vm's were not getting backed up so this should just go away for me. To recreate this, lock a vm with a snap shot ( old veeam server backing up at same time will do ) then let sync at night, second day forward the failed VM will sync at wrong time.

Code: Select all

Tuesday, September 10, 2013 5:00:19 AM 
Success 9 Start time 5:00:19 AM Total size 2.4 TB Backup size 13.6 GB Job has failed unexpectedly
 
Warning 0 End time 5:25:01 PM (+1) Data read 29.2 GB Dedupe 100.0x 
Error 0 Duration 36:24:42  Transferred 27.1 GB Compression 2.2x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
Larry4270 Success 5:01:31 AM 5:07:56 AM 298.1 GB 3.3 GB 2.2 GB 0:06:24   
Lefhand-SAN-Live Success 11:23:44 PM 11:25:33 PM 32.0 GB 1.2 GB 723.8 MB 0:01:48   
LeftHand-Failover Success 11:25:39 PM 11:25:51 PM 0.0 KB 0.0 KB 0.0 KB 0:00:11   
LOAN-WS1 Success 11:25:57 PM 11:27:17 PM 280.0 GB 1.2 GB 356.3 MB 0:01:19   
Diebold-New Success 11:27:23 PM 11:28:22 PM 80.0 GB 873.0 MB 310.0 MB 0:00:58   
Fiscal Success 5:08:03 AM 5:10:55 AM 53.2 GB 1.8 GB 943.1 MB 0:02:51   
FormsPC Success 5:11:01 AM 5:17:30 AM 80.0 GB 4.3 GB 2.4 GB 0:06:28   
Groton-Shares Success 5:17:36 AM 5:32:21 AM 277.4 GB 16.2 GB 6.6 GB 0:14:45   
Insight-GR Success 5:32:27 AM 5:33:10 AM 120.0 GB 301.0 MB 98.9 MB 0:00:42   
 
 
  

BackupSync job: GrotonVMs-D-L-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 11:05:50 AM.
 Success
0 of 0 VMs processed 
 

Wednesday, September 11, 2013 5:25:19 PM 
Success 0 Start time 5:25:19 PM Total size 0.0 KB Backup size 13.6 GB  
Warning 0 End time 2:00:05 AM (+1) Data read 0.0 KB Dedupe 1.0x 
Error 0 Duration 8:34:46  Transferred 0.0 KB Compression 2.2x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
 
 
  

BackupSync job: GrotonVMs-D-L-BC_DR 
Created by VEEAM247\vmadmin at 8/27/2013 11:05:50 AM.
 Success
9 of 9 VMs processed 
 

Thursday, September 12, 2013 2:00:08 AM 
Success 9 Start time 2:00:08 AM Total size 1.2 TB Backup size 11.0 GB  
Warning 0 End time 2:00:00 AM (+1) Data read 21.3 GB Dedupe 100.0x 
Error 0 Duration 23:59:51  Transferred 11.0 GB Compression 2.0x 
Details  
Name Status Start time End time Size Read Transferred Duration Details 
Larry4270 Success 2:01:17 AM 2:08:11 AM 298.1 GB 4.6 GB 3.1 GB 0:06:54   
Lefhand-SAN-Live Success 2:08:19 AM 2:10:20 AM 32.0 GB 1.5 GB 842.8 MB 0:02:01   
LeftHand-Failover Success 2:10:27 AM 2:10:41 AM 0.0 KB 0.0 KB 0.0 KB 0:00:14   
LOAN-WS1 Success 2:10:48 AM 2:12:19 AM 280.0 GB 1.3 GB 350.4 MB 0:01:30   
Diebold-New Success 2:12:24 AM 2:13:22 AM 80.0 GB 967.0 MB 332.2 MB 0:00:58   
Fiscal Success 2:13:29 AM 2:15:55 AM 53.2 GB 2.0 GB 1.0 GB 0:02:25   
FormsPC Success 2:16:01 AM 2:24:04 AM 80.0 GB 6.6 GB 3.6 GB 0:08:03   
Groton-Shares Success 2:24:09 AM 2:27:56 AM 277.4 GB 3.9 GB 1.5 GB 0:03:46   
Insight-GR Success 2:28:02 AM 2:28:49 AM

[veremin]

I have it set to copy at 12am everyday the issue is one VM is not sync then but it starts afer the backup job. The job is continous. I don't want to be here at 12am to click sync now.

If you don’t want to click “Sync NOW” manually, you can schedule the following simple PS script to be run at 12 am:

Code: Select all

$Job = Get-VBRJob -name "Name of backup copy job"
Sync-VBRBackupCopyJob -Job $Job 

This is supposed to create a new synchronization interval that starts at 12. Thanks.

[larry]

ok thanks.
I think veeam should flag the next sync time of a vm to be the jobs start at time when it see's ":: Latest restore point is already copied" and not pending waiting on change which fires off the copy job at the worng time.

[mc625569]

Agree with above.
The timing/syncing/coordination of copy jobs with backup jobs needs some further polish.

[veremin]

Can you provide a little bit more information regarding what sides of backup copy job timing/syncing need further improvement or what issues you’ve recently faced with the current implementation? Thanks.

[VladV]

For one I would like to be able to set the day of the week on which a backup copy job starts if it was set to Copy every 7 days or to be able to shift the day of the week in some way.

[veremin]

Ok, thanks for the heads-up.

For now you can either start the job manually on a certain day, using VM “Sync now” option or execute (via Windows Scheduler) on a given day the above mentioned script that will set weekly synchronization interval for you.

Thanks.

[Woffle99]

Sorry to open a slightly old thread, but I'd like to echo the request for the ability to set which day of the week a backup copy job starts. I have a weekly job that I want to start at 3am on Saturday morning, once other backups and tasks are finished and the lines are free of other traffic, but obviously waiting up til that time to press the 'Sync Now' button is hardly terribly practical!

I'll look to use the script above and schedule a task, but it does seem like rather a glaring omission that we can't set the exact start time for a backup copy job to run from within the program. Please can you look to add it in a future update.

Thanks.

[foggy]

Thanks for the feedback, Mark.

[veremin]

once other backups and tasks are finished and the lines are free of other traffic

Also, If you want to run the backup copy jobs right after backup activity, then, you can specify the script as a post job activity (instead of scheduling it via Windows Scheduler) and select it to run on certain days only, using corresponding button.

Thanks.

[VladV]

Also, If you want to run the backup copy jobs right after backup activity, then, you can specify the script as a post job activity (instead of scheduling it via Windows Scheduler) and select it to run on certain days only, using corresponding button.

Thanks.

I am sorry for ressing an old thread but I have to bring to attention the following behavior when using "Sync Now" or a script for starting a new sync. In my case, where I have most of the jobs set to Copy every 7 days at 12:00am, if I hit "Sync Now", the job restarts, begins copying a new restore point if available BUT, at 12:00am, it stops and only then it starts a 7 day cycle. Some of my jobs have a very long backup copy window which exceeds 24 hours, so if I want to move the day when the cycle starts I have to go through an error that the job could not finish in the copy interval and I have to press Sync Now or schedule a script, the day before I actually want it to sync.

Ex:
If I have a Backup Copy Job that is set to copy every 7 days at 12:00am, that runs on a Sunday, and I want it moved to Tuesday, I have to press or schedule a Sync Now anytime on Monday. When the Sync Now occurs, the job starts copying a new restore point if available and at 12:00am - Monday morning it restarts and only then it begins the 7 day cycle.

VBR 7.0.0.871

[veremin]

Yep, this is expected behavior described in the corresponding section of our User Guide. Thanks.

[foggy]

To avoid errors, just do not use the Sync Now command. The current synchronization interval will be finished according to the 'old' start time value and the next one will be stretched until the new start time comes.

[VladV]

To avoid errors, just do not use the Sync Now command. The current synchronization interval will be finished according to the 'old' start time value and the next one will be stretched until the new start time comes.

And how do you define a new start day if not by using Sync Now? The job edit window only permits the time of day and not the day itself even if the Copy interval is longer than a day.

Yep, this is expected behavior described in the corresponding section of our User Guide. Thanks.

The whole example in the manual revolves around the time of day and not the day itself. If I would have been able to copy a backup to our DR site in under 24 hours I would have gone with an interval of 1 day, but this is not the case.

An example of how this should work is the backup copy job creation mechanic. If I create a new job from scratch, say it was created at 4:00PM on Tuesday, and set it to 7 day sync and 12:00, the job will start and only restart the next Tuesday morning at 12:00am. The key is to check Enable the job when I click finish.

PS: I found the note in the manual confirming the behavior as reported: http://helpcenter.veeam.com/backup/70/v ... _sync.html

[foggy]

Yep, correct. If you need to change the day the interval starts, you have to use Sync Now and cope with the behavior you're observing.