"Copy Backup Job" not working

[marcel.mertens]

Hello,

i backup all my VMs every night starting at 8 PM to a local repository.
I also created a "copy backup" job set to "copy every 1 day, starting at 8 am" with all my backup jobs linked.
The target repository is a SMB dedup device (Dell DR4100). DataTransfer window is set to 8AM - 8PM.
But the job is in "idle" status and all VMs are in "Pending" state with "waiting for new restore points".

For example for last night:
I have restore points between 11th december 8PM and 12th december 5am. But the Copy job still says "waiting for new restore points"

Is there something wrong? Or how long does new restore point detection take?

Greetings from Germany,

Marcel Mertens

[foggy]

Marcel, backup job copies restore points created within the specified copy interval. Can you confirm that there are restore points created within the specified interval? If there are restore points to copy, you might want to open a ticket with our support team and let them take a look at this behavior. Thanks.

[marcel.mertens]

i created to new jobs:

Copy Backup Job - Run at 11:00 every 1 day
Backup Job. Run today at 10:50 and at 11:10. No action on the copy backup job.
restared service, restarted backup server...nothing

[foggy]

What if you click "Sync Now" to force the job to start new synchronization interval? Have you contacted support with that?

[marcel.mertens]

Sync Now doesn't help.
Support is contacted.

[ccitrano]

Marcel,

Did you get to the bottom of this. I'm having the same issue. The backup copy was working fine until I upgrade to the latest patch this past week.

I have 3 jobs that are all doing this and there are restore points from Reverse Incremental jobs available.

Chuck.

[Vitaliy S.]

Chuck, while we are all waiting for the results of Marcel's case investigation, it might be worth opening another case to receive quicker assistance on this issue.

[valre_]

Hello,
Do you have any news for this issue ?
I've the same problem with my Backup Copy Job. since v7R2.
Thanks

[foggy]

Valère, I do not see a case ID in this thread that I could track for resolution, so please contact technical support directly for details.

[larry]

I had this after a patch Wednesday the hell day after patch Tuesday

What I found worked for me was to run the backup job a second time which right after the backup finishes then the copy job kicks off and then all is well. Support posted a script that you can put in the task scheduler to restart a backup job. I just started early and right click the job to run now, the job completes quick because little change at night.

[valre_]

Hello,
I solved my problem. I was running a Backup Copy Job with same source and target repository. It automatically excludes the source.
So, I create a new repository on the same server and now it rocks !

[veremin]

Yes, you're right. There is inbuilt mechanism that prevents backup copy job from looking restore points in the repository that is specified as backup copy job target.

However, if you're willing to store both backup and backup copy files in one location, you can simply create additional folder there and specify it as a target repository for backup copy job.

Thanks.

[Janv]

I do have the same problem and frustration. What I did is to clone the exact job and it then run 100%. this is not the ideal solution but it do work 100%. Do not know why copy jobs is such a issue.

[foggy]

Hi Jan, this thread contains several cases with similar symptoms likely caused by different reasons and there's no clear evidence of an issue on the Veeam B&R side. I'd recommend contacting support for a quick review of your setup - there's a chance the behavior is caused by some misconfiguration of the copy job. Thanks!