This is an archive version of the document. To get the most up-to-date information, see the current version.

Limitations for HPE StoreOnce

In this article

    If you plan to use HPE StoreOnce as a backup repository, mind the following limitations. Limitations apply only if you use HPE StoreOnce in the integration mode, not the shared folder mode.

    • Backup files on HPE StoreOnce are locked exclusively by a job or task. If you start several tasks at a time, Veeam Backup & Replication will perform a task with a higher priority and will skip or terminate a task with a lower priority.

    In Veeam Backup & Replication, tasks have the following priority levels (starting with the top priority): backup job > backup copy > restore. For example, if the backup and backup copy jobs start simultaneously, Veeam Backup & Replication will terminate the backup copy task. If a file is locked with the backup job, you will not be able to restore VM data from this file.

    • When you create a backup job targeted at HPE StoreOnce, Veeam Backup & Replication will offer you to switch to optimized job settings and use the 4 MB size of data block for VM data processing. It is recommended that you use optimized job settings. Large data blocks produce a smaller metadata table that requires less memory and CPU resources to process.
    • The HPE StoreOnce backup repository always works in the Use per-VM backup files mode. For more information, see Per-VM Backup Files.
    • The length of backup chains (chains that contain one full backup and a set of subsequent incremental backups) on HPE StoreOnce cannot be greater than 7 restore points. The recommended backup job schedule is the following: not more than 1 incremental backup once a day, not fewer than one full backup (active or synthetic) once a week.
    • HPE StoreOnce does not support the reverse incremental backup method.
    • The HPE StoreOnce backup repository does not support the Defragment and compact full backup file option (for backup and backup copy jobs).
    • You cannot use the HP StoreOnce backup repository as a target for Veeam Endpoint backup jobs. Backup copy jobs, however, can be targeted at the HP StoreOnce backup repository.
    • You cannot use the HPE StoreOnce backup repository as a source or target for file copy jobs.
    • You cannot use the HPE StoreOnce backup repository as a cloud repository.

    Several Backup Repositories on HPE StoreOnce

    You can configure several backup repositories on one HPE StoreOnce appliance and associate them with different gateway servers.

    Mind the following:

    • If you configure several backup repositories on HPE StoreOnce and add them as extents to a scale-out backup repository, make sure that all backup files from one backup chain are stored on one extent. If backup files from one backup chain are stored to different extents, the transform operations performance will be lower. For more information about transform operations performance, see https://www.veeam.com/blog/hp-storeonce-catalyst-integration-coming-in-v9.html.
    • HPE StoreOnce has a limit on the number of opened files that applies to the whole appliance. Tasks targeted at different backup repositories on HPE StoreOnce and run in parallel will equally share this limit.
    • For HPE StoreOnce working over Fibre Channel, there is a limitation on the number of connections from one host. If you connect several backup repositories to one gateway, backup repositories will compete for connections.
    • Deduplication on HPE StoreOnce works within the limits of one object store.