Backup Copy not respecting the Reg Key BackupCopyMirrorAll

[Wayneywoo]

Hi all,

According to Veeam documentation and for ref, this post where I initially found the answer - post519764.html#p519764

The reg key to make a backup copy job copy all restore points doesn't appear to be respected when creating and running a new copy job. Seems only the last full RP is being copied. The original chain has full's going back 3 months and for some reason these are not being processed.

I tried creating a new copy job, made sure the job name is in the reg key and then ran it and I only have the last full with a number of incrementals following.

Anyone have any experience with this, able to point me in the right direction?

Is there a log file that would show this reg key being acknowledged?

Is this a feature not included in Community Edition?

Thanks all!

[david.domask]

Hi Wayne,

I'm not aware of the registry value requiring any specific license to enable, so would be a bit difficult to tell what's happening without a review of the logs. I understand you're using Community Edition, but NFR and Community edition can receive support on a "best-effort" basis, so it's best to start with a Support case.

I'm actually not quite following on this part:

> I tried creating a new copy job, made sure the job name is in the reg key and then ran it and I only have the last full with a number of incrementals following.

So do I get it right that one of the chains was copied in full (VBK + VIBs) on the new test backup copy? Or the Full with a number of incremental backups was after the backup copy had run for awhile?

The Job log for the Backup Copy Job ought give a hint if you want to try to research it yourself, but it will be best for a support case if possible.

[Wayneywoo]

Hi David,

Thanks for replying!

The line you question, after running the new copy job, instead of parsing all RPs (the first being a monthly full around 3 months ago, then going through the following 2 monthly's and maybe a couple of incrementals) the job parsed the last full, a couple of incrementals and has since been copying new RP's so hasn't parsed the entire chain from the start, the original monthly and working forwards. I've logged a support ticket, weird issue!

Hope that makes sense.