You can use HPE StoreOnce storage appliances as backup repositories.
To work with HPE StoreOnce, Veeam Backup & Replication leverages the HPE StoreOnce Catalyst technology and two HPE StoreOnce components:
- HPE StoreOnce Catalyst agent. The HPE StoreOnce Catalyst agent is a component of the HPE StoreOnce Catalyst software. The HPE StoreOnce Catalyst agent is embedded into the Veeam Data Mover setup. When you add a Microsoft Windows server to the backup infrastructure, the HPE StoreOnce Catalyst agent is automatically installed on the added server together with Veeam Data Mover.
- HPE StoreOnce appliance. The HPE StoreOnce appliance is an HPE StoreOnce storage system on which Catalyst stores are created.
To communicate with HPE StoreOnce, Veeam Backup & Replication uses two Data Movers that are responsible for data processing and transfer:
- Veeam Data Mover on the VMware backup proxy
- Veeam Data Mover on the gateway server
The HPE StoreOnce storage cannot host Veeam Data Mover. For this reason, to communicate with the HPE StoreOnce storage, you need to deploy a gateway server. Veeam Backup & Replication will automatically deploy Veeam Data Mover on this gateway server. For more information, see Gateway Server. For communicating with the HPE StoreOnce storage appliances, the gateway server must run a 64-bit Microsoft Windows version.
When any job addresses the backup repository, Veeam Data Mover on the gateway server establishes a connection with Veeam Data Mover on the VMware backup proxy, enabling efficient data transfer over LAN or WAN.
The gateway server is selected when you assign a backup repository role to the HPE StoreOnce appliance. You can define the gateway server explicitly or instruct Veeam Backup & Replication to select it automatically.
For work with HPE StoreOnce, Veeam Backup & Replication uses the Catalyst agent installed on the gateway server. If you want to reduce the load on the network between the source and target side, assign the gateway server role to a machine on the source side, closer to the VMware backup proxy.
Veeam Backup & Replication supports HPE StoreOnce storage systems working over the following protocols:
- TCP/IP protocol: Veeam Backup & Replication communicates with the HPE StoreOnce appliance by sending commands over the LAN.
- Fibre Channel protocol: Veeam Backup & Replication communicates with the HPE StoreOnce appliance by sending SCSI commands over Fibre Channel.
Data processing over Fibre Channel (FC) connectivity enables local area network-free backup to HP StoreOnce, eliminates the load from backup activities and increases availability of LAN resources to production workloads.
Considerations and Limitations for HPE StoreOnce
If you plan to use HPE StoreOnce as a backup repository for jobs other than file backup jobs, object storage backup jobs and Veeam Plug-in for Enterprise Application jobs, consider the following recommendations and limitations. These requirements and limitations apply only if you use HPE StoreOnce in the integration mode, not the shared folder mode.
- Check that HPE StoreOnce that you plan to use is supported. For more information, see Backup Target.
- A Catalyst Store cannot be added to multiple backup servers.
Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection. You can disable the TLS connection with a registry value for the deduplicating storage appliances that do not support the TLS connection. For more information, see this Veeam KB article.
- When you create a 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 usually works in the Use per-machine backup files mode. For more information, see Backup Chain Formats. Note that there are cases when the HPE StoreOnce backup repository can store per-machine backups and non per-machine backups. For example, when backups are evacuated to this repository from other extents in a SOBR. For more information, see Evacuating Backups from Performance Extents. Note that restore from such backups can last longer than from per-machine backups.
- We recommend against enabling encryption for the jobs targeted at the deduplication storage appliance. Encryption has a negative effect on the deduplication ratio. For more information, see Data Encryption.
- HPE StoreOnce does not support the reverse incremental backup method.
- For backup jobs, HPE StoreOnce does not support the forever forward incremental backup method. When creating a backup job, you must enable synthetic or active full backups. For more information on how to enable such backups, see Backup Settings.
- The HPE StoreOnce backup repository does not support the Defragment and compact full backup file option.
- You cannot use HPE StoreOnce backup repositories as sources or targets for file copy jobs.
- You cannot copy backup files (VBK, VIB and VRB) manually to the HPE StoreOnce backup repository. To copy such files, use backup copy jobs or evacuate backups if you use a scale-out backup repository.
- You cannot use the HPE StoreOnce backup repository as a cloud repository hosted behind a Cloud Connect Gateway server.
- To optimize data transfer between two HPE StoreOnce repositories, use backup copy jobs for HPE StoreOnce repositories. For more information on how to create jobs and recommendations for them, see Creating Backup Copy Jobs for HPE StoreOnce Repositories.
- You can use HPE Cloud Bank Storage only as a target for backup copy jobs for HPE StoreOnce repositories. Veeam Backup & Replication supports HPE Cloud Bank Storage for HPE StoreOnce software version 4.3.2 or later.
- Veeam Backup & Replication supports fixed block chunking functionality for HPE StoreOnce software version 4.3.2 or later. To be able to use this functionality in Veeam Backup & Replication, check that the Align backup file data blocks option is enabled in the repository settings.
- HPE StoreOnce has a limit on the number of concurrently opened files. Due to this limit, the maximum length of backup chains (chains that contain one full backup and a set of subsequent incremental backups) on HPE StoreOnce is also limited and depends on the particular storage model. For more information, see the following table.
Table — Storage models and number of restore points
For more information and recommendations on working with HPE StoreOnce, see this Veeam KB article.
HPE StoreOnce and Unstructured Data Backup
If you plan to use HPE StoreOnce storage appliances for unstructured data backup, consider the following recommendations for optimal performance:
- A StoreOnce system can have multiple Catalyst stores, and large backup loads (exceeding 1PB) should be spread across more than one Catalyst store on the same StoreOnce system.
- Do not include Catalyst stores in a SOBR intended for unstructured data backups. This will reduce the global deduplication of the StoreOnce system.
HPE StoreOnce and Veeam Plug-ins for Enterprise Applications
If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in for Oracle RMAN or Veeam Plug-in for SAP HANA, the total number of stored files (data and metadata) must not exceed 3,000,000 per Catalyst store. If necessary, multiple Catalyst stores may be created on the same StoreOnce system.
If you plan to enable immutability for the HPE StoreOnce deduplicating storage appliance, consider the following recommendations and limitations:
- HPE StoreOnce software version must be 4.3.2 or later.
- Dual Authorization must be enabled on HPE StoreOnce. For more information on Dual Authorization, see HPE Support Center.
- [For Veeam Backup & Replication versions prior to 12.1 (build 18.104.22.1681)] The Maximum ISV Controlled Data Retention setting must be set to 365000 on HPE StoreOnce. For more information, see HPE Support Center.
- [For Veeam Backup & Replication version 12.1 (build 22.214.171.1241) and later] Check that the Maximum ISV Controlled Data Retention setting in HPE StoreOnce is greater than each of the following settings configured in Veeam Backup & Replication:
- The immutability period (the Make recent backups immutable for setting).
- The long-term retention period (the Keep certain backups longer for archival purposes setting).
If a period configured in Veeam Backup & Replication is greater than the Maximum ISV Controlled Data Retention setting, Veeam Backup & Replication keeps backups immutable for the period configured in the Veeam Backup & Replication settings but resets the expiration of the backup immutability flag during each job run. While the actual number of days that the backup must be kept immutable is greater than Maximum ISV Controlled Data Retention, Veeam Backup & Replication sets the expiration period equal to Maximum ISV Controlled Data Retention.
- [For Veeam Backup & Replication versions prior to 12.1 (build 126.96.36.1991)] HPE StoreOnce immutability cannot be used for backup copy jobs for HPE StoreOnce repositories. Even if the target HPE StoreOnce supports immutability, the copied backups are not immutable.
- To use the immutability feature for regular backup copy jobs (without HPE Catalyst Copy), enable the GFS retention policy. For more information, see Long-Term Retention Policy (GFS) for Backup Copy Jobs.
- Immutability applies only if you use HPE StoreOnce in the integration mode, not the shared folder mode.
- Immutability is supported only for forward incremental backup chains. Once a backup file becomes immutable, it can be merged or deleted only when the immutability time period expires.
HPE StoreOnce Immutability and Veeam Agents
For more information on how immutability works with Veeam Agents, see the Backup to Deduplicating Storage Appliances section in the Veeam Agent Management Guide.
Several Backup Repositories on HPE StoreOnce
You can configure several backup repositories on one HPE StoreOnce appliance and associate them with different gateway servers.
Consider 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 performance of transformation processes will be lower. For more information about transformation performance, see this Veeam blog post.
- 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.
- If your VMs contain similar data, it is recommended to create backup repositories on a single HPE StoreOnce Catalyst Store. This minimizes backup job duration and reduces disk space used for backups. For details, see this Veeam KB article.