1-800-691-1991 | 9am - 8pm ET

Veeam Backup & Replication support for HPE Cloud Volumes Backup


Veeam support statement for HPE Cloud Volumes Backup.


Veeam Backup & Replication v10 provides now official support for HPE Cloud Volumes Backup under the Veeam Experimental Support. For details on Experimental Support, see KB2976.

HPE Cloud Volumes Backup is a cloud-based backup service from HPE that emulates on-premises StoreOnce Catalyst Stores and can be used by Veeam Backup & Replication as a backup target that will automatically replicate to the HPE cloud. The HPE Cloud Volumes Backup Gateway Server can be added to Veeam Backup & Replication as a regular HPE StoreOnce Catalyst backup deduplication repository like any other Catalyst Store.

Considering possible bandwidth and latency constraints, Veeam recommends inline with the HPE guidelines the usage of HPE Cloud Volumes Backups as a secondary target repository, meaning that it is ideally used as a target for Backup Copy jobs with enabled HPE Catalyst Copy.

NOTE: Due to the limit on the number of concurrently opened files on HPE Cloud Volumes Backup, the maximum length of backup chains (chains that contain one full backup and a set of subsequent incremental backups) on HPE Cloud Volumes Backup repositories is limited by 32.
Veeam Backup & Replication
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later