- Veeam Support Knowledge Base
- How to Use Multiple Backup Repositories Pointing to a Single Catalyst Store
How to Use Multiple Backup Repositories Pointing to a Single Catalyst Store
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
To minimize backup job duration and reduce disk space used for backups, you can configure multiple Veeam Backup & Replication repositories on a single HPE StoreOnce Catalyst Store. However, due to the lack of folders concept on StoreOnce, such configuration may result in Veeam B&R metadata inconsistency, causing backup data corruption.
Solution
Limitations and Considerations
The following are known limitations and considerations of this subfolder-based configuration:
- Repositories created using the method documented in this KB article cannot be edited or rescanned via the GUI. PowerShell cmdlets can be used to edit or rescan the created repositories.
This limitation will be resolved in a future Veeam Backup & Replication release. - After creating StoreOnce Repositories based on subfolders of a Catalyst Store, a StoreOnce Repository using the parent Catalyst Store itself without a subfolder must not be created and should be removed if it exists.
- Only subfolders of a Catalyst Store itself can be created; subfolders at a deeper nesting level are not supported.
To create multiple StoreOnce Repositories using a single HPE StoreOnce Catalyst Store, and avoid backup data corruption, do the following:
- Create a new HPE StoreOnce Catalyst Store.
- Open an Administrative PowerShell on the Veeam Backup Server, and use the following cmdlet to create repositories:
- Modify the parameters shown in <> to the correct values without the <>. (See syntax notes below)
- Remember to change <repository_name> and <subfolder_name> values when attempting to create multiple repositories.
Add-VBRBackupRepository -Name <repository_name> -Folder storeonce://<storeonce_fqdn>:<objectstore_name>@/<subfolder_name> -Type HPStoreOnceIntegration -StoreOnceServerName <storeonce_fqdn> -UserName <user> -Password <password>PowerShell Syntax Notes
- The format used in the example above is for stores over IP (Catalyst over Ethernet).
- For FC-connected stores (Catalyst over Fiber Channel), replace the StoreOnce name with the "COFC" identifier for FC.
- When using FC, you may also need to add "-Server <gateway>" before the user switch, where <gateway> is the Gateway server that has FC access to the storage.
- Script Values that must be adjust prior to excution:
- <repository_name> — the desired name of the backup repository
- <storeonce>://<storeonce_fqdn> — the short name and FQDN of the StoreOnce appliance
- <objectstore_name> — the StoreOnce Catalyst store name
- <subfolder_name> — desired subfolder name.
- Each subfolder name must be unique.
- Subfolder nesting is not supported.
- <storeonce_fqdn> — the FQDN of the StoreOnce appliance
- <user> — Admin
- <password> — Admin user password
- After creating the desired repositories, they may be used as the target for Veeam backup jobs.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.