Sharing same Backup Repository

Manuel Monteiro · Oct 01, 2019 4:57 pm

Hello everyone.

Please help me evaluating this scenario:
Production:
Three hosts direct attached to storage (FC)
A physical Veeam backup proxy direct attached to storage and a HPE StoreOnce (FC)
Veeam Backup Essentials Enterprise

Now considering a new infrastructure (new hosts, new storage) sharing the same rack.
Is it possible to use/share the same backup target (StoreOnce)? If it’s possible, is it recommended as a no issue configuration?
I believe it’s possible to license this new infrastructure with Essentials editions for the same customer, but the Veeam console must be independent from the first one. Am I right?

Post by **foggy** » Oct 01, 2019 6:15 pm this post

Is it a migration project or do you plan these infrastructures to coexist?

Manuel Monteiro · Oct 01, 2019 6:31 pm

Planning both infrastructures to coexist.

Post by **foggy** » Oct 02, 2019 10:52 am this post

Is there a reason for having a separate Veeam B&R server for the second infrastructure?

Basically, yes, you can share StoreOnce between them provided you're pointing jobs to different Catalyst Stores (note that in this case there will be no deduplication between backups of different backup servers). If you point them to a single Catalyst Store, then the workaround allowing to create 'subfolders' on the storage need to be used to avoid issues, since natively StoreOnce doesn't have folders. 'Folders' for different backup servers should have different names. In both cases keep in mind StoreOnce limits for the number of concurrent connections to the storage.

As for the licensing, then both Veeam B&R instances should be covered by licenses having similar editions (Enterprise in your case).

Post by **jmmarton** » Oct 02, 2019 12:51 pm this post

You should be able to use the same Catalyst share even since you'll have a separate gateway within each Veeam environment, and each gateway can leverage the same share. Just keep in mind that the connection handling within VBR won't work effectively because a single gateway needs to handle the connections to the SO, and in this case you'd have two gateways with neither gateway knowing about the other.

Joe