Source:HPE StoreOnce Configuration

Overview

This article describes SEP sesam integration with Hewlett Packard Enterprise (HPE) StoreOnce Catalyst storage system. It explains StoreOnce configuration, which is not part of SEP sesam. For detailed information on HPE StoreOnce, refer to HPE documentation.
The Hewlett Packard Enterprise (HPE) StoreOnce backup appliance allows to configure multiple Catalyst stores which can be used as a backup storage. HPE StoreOnce fully controls the backup data and enables efficient encryption, recovery, deduplication and replication. SEP sesam uses HPE StoreOnce Catalyst Library which implements the StoreOnce Catalyst client API. This API provides the remote procedure call (RPC-based interface) that allows SEP sesam to interact with StoreOnce appliance.

StoreOnce Catalyst concept and terminology

HPE StoreOnce enables bandwidth efficient backup and restore over LAN, WAN and Fibre Channel. The data transfer during backup can be minimized by using HPE source-side deduplication. Encryption is defined on the Catalyst store side for each individual Catalyst store; once the encryption is enabled, it cannot be disabled again.

HPE uses the following terminology related to StoreOnce Catalyst:

• StoreOnce Catalyst: StoreOnce interface name.
• StoreOnce Catalyst store: Device type where the backups are stored on the StoreOnce appliance.
• StoreOnce Catalyst clients: The applications which connect by using the StoreOnce Catalyst interface.
• StoreOnce Catalyst items: The backup items stored in the Catalyst stores on the StoreOnce appliances.
• Data job: Any backup or restore.
• Copy job: Actual copy of the data, not mirror image. The backup application specifies outbound copy job as source store and inbound copy job as destination store. Once copied, the outbound and inbound copy jobs are independent of each other. This means that each copy job can be deleted, moved, or added to/from the backup application.
• Physical data size quota: Maximum amount of data that can be written to the store after deduplication.
• Logical data size quota: Maximum amount of data that can be written to the store before deduplication.
• Data immutability period: Also named StoreOnce retention period. During the specified period, the data on store remains protected for the amount of time defined by immutability period even if the SEP sesam EOL (retention time) has already expired.

Requirements

To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

• Every Catalyst store requires a separate license.
• The Catalyst library is required to access the HPE StoreOnce Catalyst store.
• SEP sesam Server v. 4.4.3 Beefalo or higher. Check Hardware requirements for SEP sesam Server or RDS.
• If you want to perform HPE source-side deduplication (on Linux or Windows), you have to configure RDS on the client. For details, see How to create a Remote Device Server (RDS).

Configuring HPE StoreOnce

Make sure that the requirements are met and then configure your HPE StoreOnce from the HPE StoreOnce Management Console StoreOnce Catalyst menu. You can also monitor the overall status, such as the network throughput and bandwidth for backup.

1. From the StoreOnce menu -> Settings tab -> enable Client Access Permission Checking to be able to define client permissions. If you do not enable this option, all clients have full access to all active stores!
2. Switch to the Clients tab and specify backup clients names and their permissions.

	Note
	Access to StoreOnce Catalyst stores is controlled through client identifiers with optional passwords, so you should also specify a client ID for the backup client.

3. Use the Blackout Windows tab if you want to prevent the backups from running during specific time. This can be used to save resources and set up your custom backup schedule.
4. Use the Bandwidth Limiting Windows tab to set up the bandwidth limit. If you want to replicate the data to HPE StoreOnce distant appliances, it is also required to set the threshold and the bandwidth limit for the WAN speed.

Creating HPE StoreOnce Catalyst store

After you have configured your HPE StoreOnce, you can create multiple Catalyst stores for different purposes, e.g., to clone, copy or replicate the savesets.

1. In the StoreOnce menu, click Create button at the top right corner. The Catalyst Store Details tab opens.
2. Enter the name of your Catalyst store and a description.
3. Optionally, set the immutability (retention) period for your data jobs and inbound/outbound copy jobs. This option may serve as additional protection for your data as you will set up the retention policy when configuring SEP sesam. If defined, the data will be protected for the defined period of time even if the SEP sesam EOL has expired. If the SEP sesam EOL is longer than the defined immutability period, the data will be protected as defined by SEP sesam.
4. You can set the primary (default) and secondary transfer policy; the latter can be used for reaching a secondary StoreOnce appliance with the replication. Depending on your environment, you can select low or high bandwidth for each transfer policy. Low-bandwidth backup is using Catalyst source-side deduplication (fixed block chunking), while high-bandwidth backup is using Catalyst target-side deduplication (variable block chunking). Typically, if the StoreOnce is not being used for other backups and the network is not a bottleneck, high-bandwidth performance will be similar to low-bandwidth performance. However, if the StoreOnce is being used as a shared backup infrastructure, low-bandwidth backups should deliver better performance.
5. You can also define the physical and logical data size quota for every Catalyst store. The physical data size quota sets the maximum amount of data that can be written to the store after deduplication. When the threshold level is reached, the backup jobs can no longer write new data.
   The logical data size quota sets the maximum amount of data that can be written to the store before deduplication occurs.
6. Optionally, you can enable StoreOnce encryption for each individual Catalyst store; once the encryption is enabled, it cannot be disabled again. Encryption is only supported if activated when creating a Catalyst store; SEP sesam encryption is not supported in this case.

	Note
	If you have enabled encryption, you have to save your key store information to a file that can be retrieved, if needed. For details, see Saving Encryption Key Store for HPE StoreOnce Catalyst.

7. In the HPE StoreOnce v. ≥ 3.18, you can also set up external object storage – HPE Cloud Bank Storage – where you can replicate your data. HPE Cloud Bank stores write deduplicated data to public or private cloud storage, as opposed to a regular HPE StoreOnce Catalyst stores where data is written to disk in the HPE StoreOnce system. Note that the HPE Cloud Bank storage is supported as a Catalyst copy target, not as a backup target, and should be used for long-term retention and archive of backups and offsite backup copies intended for disaster recovery. For details, refer to the HPE Cloud Bank Storage documentation.
8. Click Create to create your first Catalyst store. Then repeat the procedure with the relevant settings for all the Catalyst stores you want to create.

After you have created your Catalyst store, some additional tabs are displayed where you can check the store details, control clients permissions for each Catalyst store, and check searchable objects divided by category (data jobs, outbound and inbound copy jobs).