4 4 3 Beefalo:HPE StoreOnce Configuration

From SEPsesam
Revision as of 17:47, 2 July 2019 by Sta (talk | contribs) (Link to HPE_StoreOnce Troubleshooting Guide)
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo. For previous documentation version(s), check SEP sesam Archive.


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.


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


Perform the following steps to use the HPE StoreOnce Catalyst Store as a storage library. You can connect SEP sesam Server to the HPE StoreOnce Catalyst over Ethernet or over Fibre Channel; in the latter case, use StoreOnce Management Console to set up the backup and restore connections between the ports on the StoreOnce System and the ports on the client servers (see step 3 of the procedure).

  1. Preparing HPE StoreOnce
  2. Creating HPE StoreOnce Catalyst store
  3. Setting up Fibre Channel for HPE StoreOnce Catalyst store

Preparing 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.
  3. Information sign.png 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.

    When client access permissions are enabled, you have to grant access for named clients for each Catalyst store you have created by using the Permissions tab. See section Creating HPE StoreOnce Catalyst store.

  4. 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.
  5. 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 prepared your HPE StoreOnce, you can create multiple Catalyst stores for different purposes, e.g., to clone, copy or replicate the savesets, or for each major data type you intend to back up, such as for VMware ESXi, Oracle database or Windows file system.

  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; use underscores (_) or dashes (-) instead of spaces.
  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. Set the primary (default) and secondary transfer policy. Depending on your environment, you can select low (LBW) or high bandwidth (HBW) for each transfer policy. By specifying the transfer policy value you define how the backup data is transferred between SEP sesam and the HPE Catalyst Store. Note that SEP sesam uses the primary (default) transfer policy for the data transfer between the Remote Device Server and the HPE Catalyst Store, while the secondary transfer policy can be used for reaching a secondary StoreOnce appliance with the replication.
    Low-bandwidth backup is using Catalyst source-side deduplication, while high-bandwidth backup is using Catalyst target-side deduplication. 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.
  7. Information sign.png 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.
  8. 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.
  9. 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.
  10. Catalyst store.jpg

  11. Once your Catalyst store is created, some additional tabs are displayed. If you have enabled Client Access Permission Checking as recommended (see section Preparing HPE StoreOnce), you have to define for each Catalyst store to grant access to clients that need access to the store: select an individual StoreOnce Catalyst store, then select the Permissions tab and enable or disable access for each configured client. Use other tabs to check the store details and check searchable objects divided by category (data jobs, outbound and inbound copy jobs).

You can use StoreOnce Catalyst over Fibre Channel or over Ethernet. As stated in the HPE StoreOnce documentation, both connections function in the same way and supported backup applications do not perceive a difference. However, if you intend to use HPE StoreOnce Catalyst over Fibre Channel, you have to perform some additional configuration, as described in the next step.

Setting up Fibre Channel for StoreOnce Catalyst store

Information sign.png Note
As stated in the HPE StoreOnce documentation, the Fibre Channel settings are only relevant to certain StoreOnce models and are only available if the StoreOnce system supports Fibre Channel.

Consider the following when using StoreOnce Catalyst over Fibre Channel (CoFC):

  • Backups are supported on StoreOnce Catalyst over a Fibre Channel interface and over Ethernet networks.
  • StoreOnce System to StoreOnce System connectivity through optimized StoreOnce Catalyst copy jobs is supported over both Ethernet and Fibre Channel.
  • Administrator privileges are required to run StoreOnce Catalyst over Fibre Channel to access OS-specific device files associated with StoreOnce Catalyst over Fibre Channel devices.
  • Non-optimal Fibre Channel SAN zoning can lead to a lack of Fibre Channel connectivity. The storage administrator must ensure that network segregation, such as zoning, is set up correctly as recommended by HPE.
  • Check the HPE StoreOnce Support Matrix for compatibility at https://www.hpe.com/Storage/StoreOnceSupportMatrix (login required).

StoreOnce Catalyst over Fibre Channel zoning considerations

The following zoning considerations are recommended by HPE:

  • StoreOnce Fibre Channel World Wide Names (WWN) are found in the StoreOnce Management Console -> Catalyst Settings- > Fibre Channel. Each StoreOnce port presents one CoFC WWN.
  • Zone every backup/media server with at least two Fibre Channel ports and at least two StoreOnce node Fibre Channel ports across different Fibre Channel cards. Ideally, they are also zoned across different SANs. Multiple connections allow for higher availability.
  • If a connection is broken, StoreOnce Catalyst over Fibre Channel will automatically attempt to connect on a different path without aborting the backup. The backup will fail only if no paths are available from the media/backup server or to the StoreOnce. Zone StoreOnce Catalyst Copy over Fibre Channel source and destination copy devices the same way.
  • StoreOnce Catalyst Copy over Fibre Channel is a two-way protocol. Zone the source Initiator WWN with the destination target WWN, and zone the destination Initiator WWN with the source target WWN. The source and destination must be able to communicate with each other over Fibre Channel.
  • Use small Fibre Channel zones limiting the number of Fibre Channel ports in each zone.
  • StoreOnce Catalyst over Fibre Channel does not use or rely on any external multipath drivers. Connections are balanced using StoreOnce Catalyst over Fibre Channel internal algorithms. Catalyst over Fibre Channel ignores installed multipath drivers.

Fibre Channel configuration

  1. In the StoreOnce GUI, go to HPE StoreOnce -> StoreOnce Catalyst -> Fibre Channel settings tab and locate the Identifier at the top of the Configuration window. This is the CoFC identifier that is used to identify the HPE StoreOnce Catalyst Server in SEP sesam and must be provided to SEP sesam during library configuration. It is in the format COFC-<device-id>, e.g., COFC-1JB6Q36FMNR4JG0X.
  2. Make sure Devices per Initiator Port is configured properly.
  3. Check the Number of Logins and Number of Devices per Login for each port. These values determine the number of concurrent backup/restore and copy connections allowed on each Fibre Channel port on the HPE StoreOnce system.

    • The Number of Logins does not relate to how many total sessions can be established over a StoreOnce port; it defines the number of client-side ports that are zoned to connect to that port.
    • Devices per Initiator Port determines the number of backup and restore connections that are allowed from each SEP sesam Server Fibre Channel port to the ports on the StoreOnce system. It is recommended to increase this value according to your needs. Note that when increasing the value, you must run a device file rescan on the client for the change to be recognized.
    • StoreOnce Catalyst over Fibre Channel presents a device type of Processor. In Windows Device Manager, these devices are shown as Other Devices. After zoning the devices or changing the number of Devices per Initiator Port, right-click Other Devices and then select Scan for hardware changes to detect the new devices.

    • The number of possible paths between a SEP sesam Fibre Channel port and a StoreOnce Fibre Channel port is calculated as
      number of a client's ports zoned to a StoreOnce System * number of StoreOnce System ports zoned to that client * devices per initiator count

    Example relationships between Device per Initiator Port and Number of Connections

    SEP sesam Server

    HPE StoreOnce System

    Devices per Initiator Port

    Max. FC connections between SEP sesam and StoreOnce FC ports
    1 port zoned to 4 ports 1 4
    2 ports zoned to 4 ports 1 8
    2 ports zoned to 2 ports 4 16
    2 ports zoned to 4 ports 8 64

Your system is now ready to configure backups.