Backup Copy and Catalyst Copy Targeting same Storeonce -- Is this okay?

[soncscy]

Working with a newly onboarded client who asked us to clean up their shop a bit -- they're deeply invested in HPE solutions and have a few StoreOnce devices.

Once of their complaints pre-v10 has been lack of Catalyst Copy support, which we were more than happy to tell them about, but since it seems we cannot convert existing Backup Copy Jobs to Catalyst, the only option is "new Catalyst Copy Job".

That's fine

But, the client had a question I cannot answer, as our shop doesn't have any Storeonce devices to test with:

Can they run existing Backup Copies to the same Catalyst target that is the target for a Catalyst Copy.

I checked the documentation, and I found this:

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

You must not create identical pairs of source and target repositories, even in different backup copy jobs.

I'm not sure if that limitation is exclusive to Catalyst Copy jobs though...

Can someone clarify for me if Backup Copies and Catalyst Copies can co-mingle on the same share?


To simplify my Scenario:

Is this possible?

Two Storeonce Devices, A and B
Backup Copy job
Catalyst Copy Job

Backup copy 1 - > Source = Irrelevant, Target = Storeonce-B
Catalyst copy 1 - > Source = StoreOnce-A, Target = Storeonce-B

Is the above Scenario valid? Both regular Backup Copies and Catalyst Copy Jobs can target the same StoreOnce Catalyst Share?

[HannesK]

Hello,
yes, you can do that.

Best regards,
Hannes

PS: HPE has free StoreOnce VSAs (1TB I believe) which work fine in my lab since a long time

[foggy]

I'm not sure if that limitation is exclusive to Catalyst Copy jobs though...

Yes, this refers to adding the same source and target repositories to different Catalyst Copy jobs, which you're not going to do (your jobs have different types and the sources are different).

[soncscy]

Crystal clear, thank you both!

(And I suppose we should get the Storeonce VSA...just, I'd say at least 10% of our meetings is talking clients out of dedup black boxes But that's a personal thing)