Need help on Backup Copy Job Configuration between 2 StoreOnce

[weijiang]

Dear Admin,

We had purchased a new StoreOnce in our offsite location recently. And there is existing StoreOnce located in Primary site.
Now we would like to configure Backup Copy Job between 2 StoreOnce Repository which is "Primary Site" backup copy job to "Offsite".

In the New backup copy job configuration, we are able to detect the "Target backup repository" (OffSite) but it does not detect the "Source backup repository" (Primary Site).
I need help on how to allow VEEAM to detect the source backup repository.
***Our source backup repository(StoreOnce has been implemented long time ago) is used for offload data from our MSA Storage on the primary site.

[HannesK]

Hello,
I assume, that you want to use the V10 catalyst copy feature. To use it, make sure that both StoreOnce systems are connected as Catalyst repositories

https://helpcenter.veeam.com/docs/backu ... ver=100#hp
https://helpcenter.veeam.com/docs/backu ... ml?ver=100

Then you can use the catalyst copy
https://helpcenter.veeam.com/docs/backu ... ml?ver=100

but it does not detect the "Source backup repository" (Primary Site).

if you can write to it since long time ago, then it must be detected. Otherwise the software cannot write to it. I assume, that long time ago, someone configured it without catalyst. That's why it is not available in the catalyst copy backup copy job

Question: are you trying 1 or 2?
1) MSA -> StoreOnce primary -> StoreOnce secondary
2) StoreOnce primary -> StoreOnce secondary

Just to be 100% sure: are you trying a "classic" backup copy job or a "catalyst copy" backup copy job?

Best regards,
Hannes

[weijiang]

Hi Hannes,

Ok. I will read the article. Please do not achieve my case first. Because I'm currently with support for another issue "Invalid snapshot configuration".

I will come back continue after fix that issue.

[weijiang]

Hi Hannes,

Yes. Both StoreOnce is connected as Catalyst repository.
We are trying StoreOnce primary --> StoreOnce secondary. And we would like to perform a "catalyst copy" backup copy job.

Our classic backup copy job is running fine which is from MSA --> StoreOnce primary.

We did a reboot on StoreOnce primary but the "catalyst copy" backup copy job still not able to detect the StoreOnce primary repository. Please help.

Best regards,
Wei Jiang

[foggy]

Hi Tan, by "not able to detect" - do you mean you are not able to select it as the source repository in the Catalyst Copy job (it is not displayed in the drop-down list of repositories)? Please also note that in the current version, Catalyst Copy jobs do not support backup copy jobs as a source, just the regular backup jobs. Support for backup copy jobs is added in the upcoming v11 though.

[weijiang]

Hi Foggy,

Yes. It is not able to select it as the source repository in the Catalyst Copy Job. It is not displayed in the drop-down list of the repository.
What we cannot see is the source repository, not the backup copy jobs.

We want to select the Source StoreOnce but it did not display in the drop-down list. But we can select the target StoreOnce in the drop-down list.

[foggy]

Please make sure the source array is added as the Catalyst repository in the same Veeam B&R instance and meets the outlined requirements. If everything seems fine and you still do not see it, feel free to ask our support engineers for a closer look.

As for the backups created by backup copy jobs, they just will be skipped by the Catalyst Copy job in the current version.

[weijiang]

Hi Foggy,

I just check the source repository is version 3.16.5. Is this the reason why it is not displayed in the drop-down list?

[foggy]

Yes, the minimum version is 3.18.7.

[weijiang]

Hi Foggy,

I upgraded the StoreOnce version to 3.18.7 but it is still not displayed in the drop-down list.

[foggy]

Have you rescanned the repository after the upgrade?

[weijiang]

Hi Foggy,

Yes. Manage to detect the source repository in the drop-down list. But how come there is only run when there are restore points appear?
There are a lot of restore points in the source repository.

[weijiang]

Hi Foggy,

When I review the help center, It mentioned that "When the backup copy job for HPE StoreOnce runs for the first time, it copies all existing backup files.". Job has created but never run.

[foggy]

What kind of backups are stored on the source repository? As I've mentioned earlier, only backups created by regular backup jobs are currently supported. Support for backups created by backup copy jobs is coming in v11.

[weijiang]

Hi Foggy,

To make you more clear a bit. I do not understand what you mean.

1. We have a normal backup job that backup all our VMs to an MSA Storage.
2. Then we have a backup copy job which use to copy the file from the MSA Storage to StoreOnce(Source Repository).
3. Now what we want is to configure the Catalyst backup copy job from the StoreOnce(Source Repository) to a new StoreOne(Target Repository). We thought the job should copy all the files from the Source repository to the Target repository. But it never runs and shows "As new restore points appear".

[weijiang]

Hi Foggy,

One more thing we found in the Catalyst replication job is show 0 objects.

[foggy]

3. Now what we want is to configure the Catalyst backup copy job from the StoreOnce(Source Repository) to a new StoreOne(Target Repository).

This is coming in v11. Currently, Catalyst Copy job is able to copy backups created by the backup jobs only, not backup copy jobs (so like if you had copied directly to StoreOnce in p.1).

[weijiang]

Hi Foggy,

Any idea when v11 launch?
Do you have a better idea of how we can use the Target StoreOnce to have a copy of our Primary StoreOnce before v11 launch?

[foggy]

v11 is Q1. Currently, you can use backup copy jobs for that, however, they will not utilize Catalyst Copy.

[CraigL2112]

Did this feature never end up coming to fruition? We're trying to do exactly what @weijiang was trying -- have StoreOnce perform a Catalyst Copy Backup Copy Job to a second StoreOnce device, with the source for the backups being a standard Backup Copy Job.

To be clear: Backup is performed to primary repository. BCJ runs and copies to a StoreOnce Catalyst repository. Catalyst Copy BCJ does not appear to see the new recovery points in the Catalyst repository that were put there by the standard BCJ.

[Regnor]

So far I didn't try to implement this myself, but this has been listed in the v11 Whats New document:

Backup Copy jobs as source — Backup Copy jobs can now also be used as the source for Catalyst Copy jobs.
Previously, only primary backup jobs were supported as the source.

https://www.veeam.com/veeam_backup_11_0 ... new_wn.pdf

[CraigL2112]

Interesting. We tried it yesterday and when the source of the new points into the Catalyst repository was a standard Backup Copy Job, the CATALYST Backup Copy Job did not replicate them.

Will dig in deeper and see if we missed something. Thank you!