Skip to main content
  • EN

Hi,

 

We have several backup copy jobs. 

Some do copy to tapes, some to NAS and some to object repository.

 

All of them are in a continuous running state; if a backup file is available, it will be copied.

 

The issue we're facing is that the backup job using the object repository works well during incremental backups, but it waits for two days before starting the copy when it's a full backup. This is a significant delay that we need to address.

 

Let’s say the full backup is finished on Saturday at 3 am, and I can see the .vbk file exists. All other backup copy jobs finish copying that file before Sunday noon, but the one with the object storage repository doesn’t even start before Monday afternoon.

 

Does anyone have any idea why it could be happening?

 

Thank you

Do any of your jobs overlap with the same VMs being backed up going to different repositories and also the timing of the jobs?  When things overlap the job trying to use the Object Repository could be waiting on locks that other jobs, etc. might be having on it.

Also if you have Continuous mode set for the Backup Copies it should pick up new files right away but again overlap and scheduling can cause issues.

Interestingly enough, there is a gap for about 4 to 5 hours when nothing is running. And when backup copy starts for object repository it starts with other jobs running at the same time

Well then the job should run as expected so unsure what else right now to suggest.  Are there any warnings or errors noted in the console?  Maybe check the job log to see if that points out anything - C:\ProgramData\Veeam\Backup\Jobname

Not sure what else to suggest other than a support ticket now to have them check as to why it is not running when it should.

I will check the logs. Thank you

Not a problem. Let us know if you find a solution so we can mark a best answer to your question.

Typically for continuous backup copy jobs I like to set the run time at the beginning to a span of a couple days.

I will check the logs. Thank you

I didn’t find anything or I’m not so good with those logs.

I will check the logs. Thank you

I didn’t find anything or I’m not so good with those logs.

Ok.  At this point I might suggest opening a support ticket to get further assistance or try searching the Veeam Forums to see if there is anything there that can help - https://forums.veeam.com

Unless anyone else can chime in here but again we are not technical support just a community of passionate users. 😁

yeah. i did open a ticket, but nothing helpful so far :(

Have you tried to set the copy job to “immediate mode”? To me, using “continuous” sounds like you selected this option in the scheduling page of the copy job’s properties, correct?

When using “immediate copy (mirroring)” instead of “periodic copy (pruning)” mode on the first page of the copy job properties, the job should start as soon as new restore points have been created by the primary job.

yeah. i did open a ticket, but nothing helpful so far :(

Ok well keep on with them as you should get to the bottom of the issue.

 
 
 

Have you tried to set the copy job to “immediate mode”? To me, using “continuous” sounds like you selected this option in the scheduling page of the copy job’s properties, correct?

When using “immediate copy (mirroring)” instead of “periodic copy (pruning)” mode on the first page of the copy job properties, the job should start as soon as new restore points have been created by the primary job.

No. Continuous copy is immediate (Mirroring)

Okay, so you’re using immediate mode….do you have any times excluded in the schedule?  As long as you’re using Immediate copy (mirroring) and you have it set for Any Time (continuously), it shouldn’t be delaying unless it’s waiting for some sort of lock on the restore points for some reason.  I can’t think of anything else that would cause an issue.  No health checks or anything like that on the restore points that it’s waiting for?

 

Comment


Terms & Conditions