Multiple Repositorys to same Storeonce Store

[rdrost]

Situation:
Existing repository on Storeonce Store created with Veeam GUI from Veeam backupserver 1, it contains backup copy job data.
Can one create a second repository on the same Storeonce Store with powershell and write to it from second/ new Veeam backup server 2 To be used for backup data.

The scenario is for migrating VM's with VMware SRM to another site and also migrate Veeam by creating new backup jobs on new Veeam backup server. But for deduplication write them to same storeonce store as it's original backup copy.

[HannesK]

Hello,
whether you configure Veeam via UI or PowerShell makes no difference in general.

Multiple catalyst stores on one StoreOnce system are no problem. As StoreOnce only has deduplication per catalyst store (no global deduplication), that probably does not help you. See https://helpcenter.veeam.com/docs/backu ... ml?ver=110 (bottom of the page)

Multiple repositories on one Catalyst store are possible: https://www.veeam.com/kb2987

Best regards,
Hannes

PS: I recommend looking at HPE Apollo servers in future. Much more performance at a lower price (yes, more disk usage, but overall better price / value ratio)

[rdrost]

I know muliple repositorys on same Storeonce Store are possible since Veeam version 10 and you need to create them with powershell to avoid data corruption. The Veeam GUI cannot handle a folders.
But can you write to one repo from 1 veeam backup server and to the second repo from another veeam backup server (By that i mean two different veeam B&R deployments). Given that both repo are on the same Storeonce Store.

What makes it even more difficult is that the current repository has not been created with powershell but with GUI. Before Veeam version 10 you could only create one repository per Storeonce store. (Back then we did it with Veeam GUI).

[foggy]

The PS workaround allowing to create 'subfolders' on the Catalyst Store allows to use the same store with different Veeam B&R servers, provided the 'folders' have different names. Also, keep in mind StoreOnce limits for the number of concurrent connections to the storage.

[Diego.wachholz]

Hi @foggy.

Regard the subfolders you mention, should I have to create it on StoreOnce (Catalyst Store) first or it will be done by VBR during the cmdlet execution? Example:

Repo 01
Add-VBRBackupRepository -Name Repo01 -Folder storeonce://vsa04:MultiBR@/SUBFOLDER1 HPStoreOnceIntegration -StoreOnceServerName vsa04.flab.local -UserName veeam -Password veeam

Repo 02
Add-VBRBackupRepository -Name Repo02 -Folder storeonce://vsa04:MultiBR@/SUBFOLDER2 HPStoreOnceIntegration -StoreOnceServerName vsa04.flab.local -UserName veeam -Password veeam

Thank you.

[foggy]

Hi Diego, there's no such thing as a folder on StoreOnce. This cmdlet allows Veeam B&R to tag names of Catalyst objects with the 'subfolder' name to distinguish them from others stored in the same Catalyst Store. So you do not need to pre-create anything on the storage itself, just create repos using the mentioned PS cmdlet.

[Diego.wachholz]

Thank you @foggy. I will test this configuration in a customer environment next week.

[zercho05]

Hello Hannes and all the others,

Can you shed some light on the following KB Artikle: https://www.veeam.com/kb2987
Is says: However, due to lack of folders concept on StoreOnce, such configuration may result in Veeam B&R metadata inconsistency causing backup data corruption.
What exactly is causing the metadata inconsistency.
We would like to use this configuration for 180+ Locations with Backup Copy Jobs. Here a picture with the config: https://www.dropbox.com/s/blryh94qr1v4a ... s.png?dl=0

I am happy to read from you guys.

BR
Stefan

[foggy]

Hi Stefan, concurrent access to a Catalyst Store by several Veeam B&R instances may cause metadata inconsistency, for example. However, with the workaround described in the mentioned article, you do not need to worry about it.

[zercho05]

Dear Foggy,
Thanks for your fast reply,

Can you also tell me what exactly counts as "Session" is in Veeam terms "Maximum concurrent backup sessions per node (2)"
Is a Session:
count per Veeam Backup File -> What I think it is!!!
or count per "Backup Copy Job" ?

Below is a part of your Documentation for Backup Copy Jobs (Store Once)

Is there any newer documents on this AND can you also put this information on:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
Cause this is really important, also for sizing the Infrastructure / HPE Store Once Product.



StoreOnce model Max restore points per single backcup chain (1)
Maximum concurrent backup sessions per node (2) -> this should also be on https://helpcenter.veeam.com/docs/backu ... ml?ver=110

(1) (2)
VSA 7 64
6200 14 192
2700 7 48
2900 14 96
4500 14 128
4700 14 192
4900 28 500
6500 28 512
3100 7 80
3500 14 192
5100 21 320
5500 35 1000
6600 42 1024

• This defines the maximum number of incremental backups associated with a full backup. If one backup per day is created
on a StoreOnce 2700, then there needs to be at least one synthetic full per week. Please note, this limit does not influence the
maximum number of restore points since it is possible to have multiple chains in retention.
• This number defines the limit for the StoreOnce node (server). Version 9.5 monitors the number of concurrent sessions and
can pause jobs on “wait for resource” state until enough resources are available.

[foggy]

The session here is a storage session used to open a single file. This is not a parameter the Veeam B&R user operates with so in documentation we convert it to the corresponding number of restore points in the chain, which is what the user deals with anyway.