Support Statement — Restoring Backups Replicated by HPE StoreOnce cyber vault
| KB ID: | 4972 |
| Product: | Veeam Backup & Replication |
| Published: | 2026-11-13 |
| Last Modified: | 2026-11-13 |
Oops! Something went wrong.
Please, try again later.
Details
Veeam Backup & Replication supports restoring backups from an HPE StoreOnce Catalyst store that was replicated by HPE StoreOnce cyber vault. The vault's Catalyst store is added to a separate Veeam Backup Server as an HPE StoreOnce repository, and its backups are imported and restored in the same way as backups on any other Catalyst store.
This scenario was validated with Veeam Backup & Replication 13.1 and HPE StoreOnce 5.3.0, covering restore from the vault's Catalyst store. The HPE replication mechanism was outside the scope of this validation.
Scope of Support
- Veeam: Creating backups on the production Catalyst store, and importing and restoring backups from the vault's Catalyst store.
- HPE: The vault, copy mappings, replication schedule, and the integrity and consistency of the replicated data. Replication runs independently of Veeam and is neither managed nor monitored by Veeam Backup & Replication. Vault configuration and operation are documented by HPE. See the HPE StoreOnce cyber vault user guide at hpe.com/support/storeoncedocs.
Replication in this scenario is performed entirely by HPE StoreOnce. No Veeam backup copy job (StoreOnce Catalyst Copy) is involved. Because the vault's Catalyst store is a distinct store from the production store, adding it to a separate Veeam Backup Server is consistent with the requirement that each Catalyst store be added to only one backup server.
In the validated configuration, backup data deleted from the production store was also removed from the vault during later synchronization. The vault should not be treated as an independent backup history, and importing a restore point does not prevent its backup data from being deleted. Retention and protection behavior is documented by HPE.
Recommended Action
No changes are required on the production Veeam Backup Server. In the recovery environment:
- Repository: Add the vault's Catalyst store as an HPE StoreOnce repository using the standard procedure.
- Rescan: Adding the repository does not create a rescan schedule. After each HPE synchronization completes, rescan the repository manually or with
Sync-VBRBackupRepositoryso that new restore points are imported. - Backup metadata: The vault copy mapping replicates all objects in the Catalyst store, including the backup metadata files (
.vbm). Automatic import during rescan uses these files. If they are unavailable, backups can still be imported manually from the full backup files (.vbk). - Encrypted backups: Keep the encryption passwords, or a key-recovery mechanism, available in the recovery environment.
- Recovery time objectives: Restores from deduplicating storage can be slower. For details, see KB2660.
- Isolated environments: Windows-based recovery servers with restricted internet access may be affected by the issue described in KB4819.
More Information
- Veeam Backup & Replication User Guide: HPE StoreOnce
- Veeam Backup & Replication User Guide: HPE StoreOnce Supported Features
- Veeam Backup & Replication User Guide: Rescanning Backup Repositories
- Veeam Backup & Replication User Guide: Importing Encrypted Backups
- Veeam PowerShell Reference: Sync-VBRBackupRepository
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
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.
