Source:HPE StoreOnce Configuration: Difference between revisions

From SEPsesam
(Removed link for saving encryption key.)
(Marked this version for translation)
(33 intermediate revisions by the same user not shown)
Line 4: Line 4:


<!--T:2-->
<!--T:2-->
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']]
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo''/''Beefalo V2'']]
|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|SEP sesam Archive]]}}</div></translate><br />
|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|SEP sesam Archive]]}}</div></translate><br />


Line 12: Line 12:
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--> [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]]</translate>
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5--> [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--> See also: [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup|HPE StoreOnce Backup]] –  [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6--> See also: [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]] – [[Special:MyLanguage/4_4_3_Beefalo:Saving_Encryption_Key_Store_for_HPE_StoreOnce_Catalyst|Saving Encryption Key Store for HPE StoreOnce Catalyst]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup|HPE StoreOnce Backup]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]] –  [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]]</translate>
|}
|}


Line 31: Line 31:


<!--T:93-->
<!--T:93-->
With SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']] it is recommended to use ''HPE Cloud Bank Storage'' (''HPE StoreOnce v. ≥ 4.1'') as a Catalyst copy target where you can replicate or restore your data. It cannot be used as a backup target due to its limited object size.
With SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']] it is recommended to use ''HPE Cloud Bank Storage'' (''HPE StoreOnce v. ≥ 4.1'') as a Catalyst copy target where you can replicate or restore your data instead of regular Catalyst stores. It cannot be used as a backup target due to its limited object size.  
''HPE Cloud Bank Storage'' is an extension of the HPE StoreOnce Catalyst store that enables Catalyst stores to use external object storage to increase the physical capacity managed by StoreOnce systems. ''HPE Cloud Bank Storage'' stores the data to public or private cloud storage from different services, i.e., Amazon AWS S3, Microsoft Azure and Scality, as opposed to a regular HPE StoreOnce Catalyst stores where the data is written to disk in the HPE StoreOnce system. It is especially suitable for long-term retention and archive of backups and offsite backup copies intended for disaster recovery. It also allows you to follow the [https://searchdatabackup.techtarget.com/definition/3-2-1-Backup-Strategy 3-2-1 data protection rule].


<!--T:94-->
<!--T:102-->
You can create a Cloud Bank store in a similar way to Catalyst store, as described in the section [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#cloud_bank_store|Creating HPE StoreOnce Cloud Bank store]].
You can create a Cloud Bank store in a similar way to Catalyst store, as described in [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication#cloud_bank_store|Creating HPE StoreOnce Cloud Bank store]].


==={{anchor|concept}}StoreOnce Catalyst concept and terminology=== <!--T:13-->
==={{anchor|concept}}StoreOnce Catalyst concept and terminology=== <!--T:13-->


<!--T:14-->
<!--T:14-->
HPE StoreOnce enables bandwidth efficient backup and restore over LAN, WAN and [[4_4_3_Beefalo:HPE_StoreOnce_Configuration#fibre_channel|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 StoreOnce enables bandwidth-efficient backup and restore over LAN, WAN and [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#fibre_channel|Fibre Channel]]. It provides the flexibility of using different deduplication modes, depending on your environment and performance (see section [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#deduplication|Catalyst data deduplication modes]]). Encryption is defined on the Catalyst store side individually for each Catalyst store; note that once encryption is enabled, it can no longer be disabled.  


<!--T:15-->
<!--T:15-->
Line 54: Line 53:
<li><translate><!--T:20--> '''Data job''': Any backup or restore.</translate></li>
<li><translate><!--T:20--> '''Data job''': Any backup or restore.</translate></li>
<li><translate><!--T:21-->
<li><translate><!--T:21-->
'''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,
'''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.</translate></li>
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.</translate></li>
<li><translate><!--T:141--> '''Transfer policies''': By selecting ''Low Bandwidth'' or ''High Bandwidth'' (HBW) it is defined how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs. See section [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#deduplication|Catalyst data deduplication modes]].</translate></li>
<li><translate><!--T:22--> '''Physical data size quota''': Maximum amount of data that can be written to the store after deduplication.</translate></li>
<li><translate><!--T:22--> '''Physical data size quota''': Maximum amount of data that can be written to the store after deduplication.</translate></li>
<li><translate><!--T:23--> '''Logical data size quota''': Maximum amount of data that can be written to the store before deduplication.</translate></li>
<li><translate><!--T:23--> '''Logical data size quota''': Maximum amount of data that can be written to the store before deduplication.</translate></li>
<li><translate><!--T:24--> '''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.</translate></li></ul>
<li><translate><!--T:24--> '''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.</translate></li></ul>
<translate>
==={{anchor|deduplication}}Catalyst data deduplication modes=== <!--T:142-->
StoreOnce Catalyst provides the flexibility of performing deduplication at backup server, target, or application source, depending on your environment and performance requirements. Catalyst stores can be configured individually for specific deduplication mode in the ''Advanced Settings'' by selecting the appropriate bandwidth type for ''Transfer Policies''. By specifying the transfer policy mode you define how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs.
====Source-side/server-side deduplication (HPE: ''Backup Server Deduplication'')==== <!--T:143-->
<!--T:144-->
The HPE StoreOnce Catalyst agent deduplicates data on the source side within the backup server, i.e. the backup server or RDS deduplicated before transferring it to StoreOnce. For this, the ''Primary Transfer Policy'' must be set to '''Low Bandwidth''' (is the bandwidth-optimized mode). This option is recommended for most use cases as it reduces the network load and improves backup performance.
====Target-side deduplication (HPE: ''Target Deduplication'')==== <!--T:145-->
<!--T:146-->
Target deduplication runs deduplication processing at the backup target, after the data is transported to HPE StoreOnce. For this, the Catalyst store must be in the performance-optimized mode by setting the ''Primary Transfer Policy'' to '''High Bandwidth'''. This option is recommended when there is a need to reduce the disk space required for backup data.
====Application-side deduplication (HPE: ''Application Source Deduplication'')==== <!--T:147-->
<!--T:148-->
Software-based source-side deduplication uses the SEP sesam Client (without RDS) to perform the deduplication process and writes the deduplicated data directly to HPE StoreOnce, without using the Media Server. As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], you can use the application-side deduplication by selecting the '''HPE StoreOnce Bandwidth Optimized Data Transfer''' option in the properties of the HPE StoreOnce backup event; for details, see [[Special:MyLanguage/HPE_StoreOnce_Backup#bandwidth_optimized|Option ''HPE StoreOnce Bandwidth Optimized Data Transfer'']]. By selecting this option, redundant data is removed before it is transmitted to the backup target (only the changed blocks are transferred) thus optimizing bandwidth utilization. Application-side deduplication requires '''at least one transfer policy''' to be set to '''Low Bandwidth'''.</translate>
{{<translate><!--T:149--> note</translate>|<translate>
<!--T:150-->
Keep the following in mind when using this option:</translate>
*<translate> <!--T:151--> If ''High Bandwidth'' is configured for both, the ''Primary'' and ''Secondary Transfer'' policy, the application-side deduplication '''cannot be performed''' on the client. In this case, the data is transferred directly from the client to the StoreOnce system with target deduplication, without deduplicating the data in advance at its source by the client.</translate>
*<translate> <!--T:152--> ''HPE StoreOnce Bandwidth Optimized Data Transfer'' is important mainly for WAN clients. By enabling it, SEP sesam establishes the connection between the local [[Special:MyLanguage/SEP_sesam_Glossary#STPD|STPD]] and HPE StoreOnce. This option is only available if the SEP sesam STPD service is part of the SEP sesam Client installation. This is the case with the SEP sesam Windows Client installation and in case of SEP sesam Linux [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]] installation.</translate>
*<translate> <!--T:153--> ''HPE StoreOnce Bandwidth Optimized Data Transfer'' can also be used for ''SAP Oracle (RMAN) backups'' and ''SAP Netweaver (Oracle) backups'' if the following parameters are configured before you start a backup: the first one is ''SESAM_DRIVE'' that has to be set to the HPE Catalyst Store, the second is ''SESAM_TAPESERVER'' where you specify the name of your SAP (on Oracle) client. These parameters can be configured in the SAP ''UTIL_FILE'' or in the ''RMAN script''.</translate>}}
<translate>
<!--T:154-->
;{{anchor|sesam_parameters}}Configuring ''SESAM_DRIVE'' and ''SESAM_TAPESERVER'' for SAP Oracle backups:
To send the data straight from the SAP Oracle client to the HPE Catalyst Store, a local STPD connection must be established. In the SAP ''UTIL_FILE'' or in the ''RMAN script'', the ''SESAM_DRIVE'' parameter must be set to the HPE Catalyst Store to define the connection to the HPE system and the ''SESAM_TAPESERVER'' parameter must be specified with the name of the SAP client (as it is configured in the SEP sesam GUI):
<!--T:155-->
SESAM_DRIVE=<nowiki>SMS:DS@+SO</nowiki>@''<DB:data_stores.name>''
SESAM_TAPESERVER=''<SAP_client_hostname>''
<!--T:156-->
;Example:
SESAM_DRIVE=<nowiki>SMS:DS@+SO</nowiki>@ix2-store-once-1
where the value after the second @ is <DB:data_stores.name>
SESAM_TAPESERVER=sapcertsles11.sep.de
where the name is the hostname of the SAP client as specified in the SEP sesam GUI</translate>
{{<translate><!--T:157--> tip</translate> |<translate> <!--T:158--> For Oracle RMAN, these parameters can be set in the RMAN script directly or by using <tt>sbc_rman -d</tt> and <tt>-S</tt> switch. For details, see [[Special:MyLanguage/SEP_sesam_Extension_for_Oracle##backup_db|Backing up the Oracle database]].</translate>}}


<translate>{{anchor|requirements}}
<translate>{{anchor|requirements}}
Line 67: Line 110:
<ul><li><translate><!--T:27--> {{anchor|licenses}}HPE StoreOnce VSA license and additional licenses, e.g., ''Cloud Storage'', ''Cloud Archive'', ''Security'' license, etc. For details, see section [https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00057041en_us&docLocale=en_US StoreOnce VSA licensing].</translate>
<ul><li><translate><!--T:27--> {{anchor|licenses}}HPE StoreOnce VSA license and additional licenses, e.g., ''Cloud Storage'', ''Cloud Archive'', ''Security'' license, etc. For details, see section [https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00057041en_us&docLocale=en_US StoreOnce VSA licensing].</translate>
<li><translate><!--T:28--> The Catalyst library is required to access the HPE StoreOnce Catalyst store.</translate></li>
<li><translate><!--T:28--> The Catalyst library is required to access the HPE StoreOnce Catalyst store.</translate></li>
<li><translate><!--T:29--> SEP sesam Server v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] or higher. Check [[Special:MyLanguage/Hardware_requirements|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate></li>
<li><translate><!--T:29--> SEP sesam Server v. [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']] or higher. Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]].</translate></li>
<li><translate><!--T:30-->
<li><translate><!--T:30-->
If you want to perform HPE source-side deduplication (on Linux or Windows), you have to configure RDS on the client. For details, see [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]].</translate></li></ul>
If you want to perform HPE source-side deduplication (on Linux or Windows), you have to configure RDS on the client. For details, see [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]].</translate></li></ul>


<translate>{{anchor|version}}
<translate>{{anchor|ports}}
===HPE StoreOnce connections=== <!--T:135-->
 
<!--T:136-->
The following (TCP) ports are used to allow the StoreOnce Catalyst traffic to pass to and from the SEP sesam Server:</translate>
* ''9387'' -> <translate><!--T:137--> command session port number the server will listen on by default</translate>
* ''9388'' -> <translate><!--T:138-->
data session port number the server will listen on by default
 
{{anchor|version}}
===Minimum supported version of HPE system=== <!--T:92-->
===Minimum supported version of HPE system=== <!--T:92-->
<!--T:103-->
The following list shows the minimum supported versions of HPE system ''Gen3'' and ''Gen4'' Storeonce platform. SEP sesam cannot assure support for releases older than the minimum supported version.</translate>
The following list shows the minimum supported versions of HPE system ''Gen3'' and ''Gen4'' Storeonce platform. SEP sesam cannot assure support for releases older than the minimum supported version.</translate>
{| border="2" cellpadding="4" cellspacing="0" style="width:30%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
{| border="2" cellpadding="4" cellspacing="0" style="width:30%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
Line 91: Line 145:


<!--T:57-->
<!--T:57-->
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).</translate>
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 2 of the procedure).</translate>
#<translate> <!--T:58--> [[4_4_3_Beefalo:HPE_StoreOnce_Configuration#prepare|Preparing HPE StoreOnce]]</translate>
#<translate> <!--T:59--> [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#create_catalyst_store|Creating HPE StoreOnce Catalyst store]]</translate>
#<translate> <!--T:59--> [[4_4_3_Beefalo:HPE_StoreOnce_Configuration#create_catalyst_store|Creating HPE StoreOnce Catalyst store]]</translate>
# <translate><!--T:60-->
# <translate><!--T:60-->
[[4_4_3_Beefalo:HPE_StoreOnce_Configuration#fibre_channel|Setting up Fibre Channel for HPE StoreOnce Catalyst store]]
[[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#fibre_channel|Setting up Fibre Channel for HPE StoreOnce Catalyst store]]


=={{anchor|prepare}}Preparing HPE StoreOnce== <!--T:31-->
=={{anchor|create_catalyst_store}}Creating HPE StoreOnce Catalyst store== <!--T:104--></translate>


<!--T:32-->
<ol><li><translate><!--T:41--> In the ''StoreOnce menu'' -> '''Data Services''' -> '''Catalyst Stores''', click '''Create Store''' option at the top right corner. The ''Create Store'' window opens.</translate></li>
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.</translate>
<li><translate><!--T:42--> Enter the ''name'' of your Catalyst store. The exact name is needed to add the Catalyst store to SEP sesam environment later, so write it down. Use underscores (_) or dashes (-) instead of spaces.</translate></li>
<ol><li><translate><!--T:33--> 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!</translate></li>
<translate><!--T:105--> [[Image:Creating_Catalyst_store.jpg|700px|link=]]</translate>
<li><translate><!--T:34--> Switch to the '''Clients''' tab and specify ''backup clients names'' and ''their permissions''.</translate> </li>
<br clear=all>
{{<translate><!--T:35--> note</translate>|<translate><!--T:36--> 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.</translate>}}
<li><translate><!--T:106--> {{anchor|period}}Optionally, under the ''Security Settings'', set the following options.</translate>
<translate><!--T:61--> 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 [[4_4_3_Beefalo:HPE_StoreOnce_Configuration#create_catalyst_store|Creating HPE StoreOnce Catalyst store]].</translate>
<li><translate><!--T:37--> 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.</translate></li>  
<li><translate><!--T:38--> 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.</translate></li></ol>


<translate>=={{anchor|create_catalyst_store}}Creating HPE StoreOnce Catalyst store== <!--T:39-->
<ul><li><translate><!--T:107--> ''Store Encryption'': If the proper license was applied, you can enable StoreOnce encryption. This built-in encryption of the Catalyst store can only be activated  individually for each Catalyst store during its setup. Once encryption is enabled, it can no longer be disabled. </translate></li>
{{<translate><!--T:108--> Note</translate>|<translate>


<!--T:40-->
<!--T:109-->
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.</translate>
*If you want to use encryption, SEP recommends to use ''StoreOnce encryption'' instead of SEP sesam built-in ''Task'' encryption, as the backup data cannot be deduplicated when SEP sesam encryption is enabled.</translate>
<ol><li><translate><!--T:41--> In the ''StoreOnce menu'', click '''Create''' button at the top right corner. The ''Catalyst Store Details'' tab opens.</translate></li>
 
<li><translate><!--T:42--> Enter the ''name'' of your Catalyst store and a ''description'';  use underscores (_) or dashes (-) instead of spaces. </translate></li>
<translate><!--T:110-->
<li><translate><!--T:43--> {{anchor|period}}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.</translate></li>
*If you have enabled ''StoreOnce encryption'', save your keystore information in a file that can be retrieved later. For details, see [[Special:MyLanguage/4_4_3_Beefalo:Saving_Encryption_Key_Store_for_HPE_StoreOnce_Catalyst|Saving Encryption Key Store for HPE StoreOnce Catalyst]].</translate>}}
<li><translate><!--T:44--> 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</translate>.<br /> <translate><!--T:55--> 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.</translate>
 
<li><translate><!--T:45--> 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.</translate><br />
<li><translate><!--T:111--> ''Data Immutability'' (retention) period for your data jobs and inbound/outbound copy jobs. This option can be used as additional protection for your data as you set up the retention policy when configuring SEP sesam. If set, 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 StoreOnce data immutability period, the data is protected as defined by SEP sesam EOL.</translate></li></ul></li>
<translate><!--T:46--> The ''logical data size quota'' sets the maximum amount of data that can be written to the store before deduplication occurs.</translate></li> 
 
<li><translate><!--T:47--> 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.</translate></li>
<translate><!--T:112--> [[Image:Catalyst_store_security_settings.jpg|350px|link=]]</translate>
{{<translate><!--T:48--> Note</translate>|<translate><!--T:49--> If you have enabled encryption, you have to save your key store information to a file that can be retrieved, if needed.</translate>}} 
<br clear=all> 
<li><translate><!--T:50--> 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 [https://h20195.www2.hpe.com/v2/GetDocument.aspx?docname=a00043317enw&doctype=Reference%20Architecture&doclang=EN_US&searchquery=&cc=us&lc=en HPE Cloud Bank Storage documentation].</translate></li>
<li>{{anchor|step_bandwidth}}<translate><!--T:44--> Under the ''Advanced Settings'', 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. Note that the selected mode for the primary and secondary policy affects how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs (see section [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#deduplication|Catalyst data deduplication modes]]). SEP sesam uses the ''primary (default) transfer policy'' for data transfer between the Remote Device Server and the HPE Catalyst store. The ''secondary transfer policy'' can be used for reaching a secondary StoreOnce appliance with the replication.</translate><br />  
<translate><!--T:52--> [[Image:Catalyst_store.jpg|900px|link=]]</translate>
{{<translate><!--T:139--> Tip</translate>|<translate><!--T:140--> As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], you can use the application-side deduplication by setting the ''HPE StoreOnce Bandwidth Optimized Data Transfer'' option in the SEP sesam GUI. To use this option, '''at least one transfer policy''' must be set to '''Low Bandwidth'''. For details on where to set this option, see [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup#bandwidth_optimized|HPE StoreOnce Backup: Option ''HPE StoreOnce Bandwidth Optimized Data Transfer'']].</translate>}}
<li><translate><!--T:113--> {{anchor|quotas}}'''STORAGE QUOTAS'''<br />You can also define the ''physical'' and ''logical data size quota'' for each Catalyst store. By setting the quota, you can distribute the physical capacity of the StoreOnce system among different users and effectively determine how much storage space on the HPE StoreOnce backup system can be used by a particular user. Applications with a better deduplication ratio can store more data.</translate>
 
<ul><li><translate><!--T:114--> ''Physical Storage 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.</translate></li>
{{<translate><!--T:115--> tip</translate>|<translate><!--T:116--> Normally the HPE StoreOnce is used for more than one HPE Catalyst Store. For this  multi-store approach, SEP recommends to set ''Physical Storage Quotas''.</translate>}}
<li><translate><!--T:117--> ''Logical Storage Quota'' sets the maximum amount of data that can be written to the store before deduplication.</translate></li></ul>
{{<translate><!--T:118--> note</translate>|
*<translate><!--T:119--> When quota limits are set and the quota limit is reached, backups will fail to prevent the quota from being exceeded. Restores are still allowed, but all new backups will fail. To solve this issue, increase the quota to the sufficient size.</translate>
*<translate><!--T:120--> As of [[SEP sesam Release Versions|Beefalo V2]], the SEP sesam data store Disk space usage option for HPE StoreOnce Catalyst Store supports Catalyst Store Physical Storage Quota and Logical Storage Quota. You can check the HPE StoreOnce storage quotas and the overall HPE StoreOnce storage sizes in SEP sesam GUI: ''Main selection'' -> ''Components'' -> ''Data Stores'', double-click your ''StoreOnce store'' and then click the ''HPE Catalyst Store State'' tab. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration#StoreOnce_store|Configuring HPE StoreOnce data store in SEP sesam]].</translate>}}</li>  
<translate><!--T:121--> [[Image:Catalyst_store_settings.jpg|350px|link=]]</translate>
<br clear=all>
<br clear=all>
<li><translate><!--T:53-->
<translate><!--T:122--> Click '''Create''' to create your first Catalyst store. Then repeat the procedure to create additional Catalyst stores.</translate>
Once your Catalyst store is created, some additional tabs are displayed. If you have enabled ''Client Access Permission Checking'' as recommended (see section [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#prepare|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).</translate></li></ol>
<li><translate><!--T:123--> {{anchor|client_access}}Once your Catalyst store is created, configure the ''Client Access'' permission for this store:</translate><br />
<translate><!--T:124--> Click '''Add Client''' and specify a user name and password. ''Catalyst Client Name'' is the user name.</translate><br />
<translate><!--T:125--> Note that this does not have to be the name of the backup server, you can choose whatever name you wish. Write down these credentials to create the store in SEP sesam later on. You can also change the ''Client Access'' permission later by using the ''Permissions'' tab of the already configured Catalyst store.</translate></li>
<translate><!--T:126--> [[Image:Client_access.jpg|350px|link=]]</translate>
<br clear=all></ol>


<translate><!--T:62-->
<translate><!--T:127-->
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.
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.


=={{anchor|cloud_bank_store}}Creating HPE StoreOnce Cloud Bank store== <!--T:95-->
=={{anchor|fibre_channel}} Setting up Fibre Channel for StoreOnce Catalyst store== <!--T:128--></translate>
 
<!--T:96-->
In the HPE StoreOnce v. ≥ 3.18, you can set up external object storage – ''HPE Cloud Bank Storage'' – where you can replicate your data. Note that creating an HPE Cloud Bank store requires an [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#licenses|HPE Cloud Bank licenses]] for the capacity of data written to the Cloud Bank stores. As of v. 4.4.3 ''Beefalo V2'' (HPE StoreOnce v. ≥ 4.1), SEP sesam supports ''HPE Cloud Bank'' (public or private cloud) storage as a Catalyst copy target for replicating or restoring your data. Configuration of a Cloud Bank store is a similar procedure to creating a Catalyst store, during which you specify a ''name'' and ''description'' for the HPE Cloud Bank store and set other configuration settings as described in the [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#prepare|steps 1-5 above]]. Afterwards, some additional steps are required:</translate>
<ol><li><translate><!--T:97--> Select the '''Cloud Bank Storage''' checkbox.</translate></li>
<li><translate><!--T:98--> From ''Cloud Service Provider'' drop-down list, select  '''Amazon AWS S3''' or '''Microsoft Azure''' object store.</translate></li>
<li><translate><!--T:99--> Enter the ''Account Name'' and ''Account Key'' of your object store storage account.</translate></li>
<li><translate><!--T:100--> Enter the ''Container Name'' of the object store storage account container.</translate></li>
<li><translate><!--T:101--> Click '''Create''' to create your first Cloud Bank store. Then repeat the procedure with the relevant settings for all the Cloud Bank stores you want to create.</translate></li></ol>
<translate>=={{anchor|fibre_channel}} Setting up Fibre Channel for StoreOnce Catalyst store== <!--T:63-->


<!--T:64-->
<!--T:64-->
{{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.}}
{{<translate><!--T:129--> note</translate>|<translate><!--T:130--> 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.</translate>}}


<!--T:65-->
<translate><!--T:131--> Consider the following when using StoreOnce Catalyst over Fibre Channel (CoFC):</translate>
Consider the following when using StoreOnce Catalyst over Fibre Channel (CoFC):</translate>
*<translate><!--T:66--> Backups are supported on StoreOnce Catalyst over a Fibre Channel interface and over Ethernet networks.</translate>
*<translate><!--T:66--> Backups are supported on StoreOnce Catalyst over a Fibre Channel interface and over Ethernet networks.</translate>
*<translate><!--T:67--> StoreOnce System to StoreOnce System connectivity through optimized StoreOnce Catalyst copy jobs is supported over both Ethernet and Fibre Channel.</translate>
*<translate><!--T:67--> StoreOnce System to StoreOnce System connectivity through optimized StoreOnce Catalyst copy jobs is supported over both Ethernet and Fibre Channel.</translate>
*<translate><!--T:68--> 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.</translate>
*<translate><!--T:68--> 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.</translate>
*<translate><!--T:69--> 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 [[4_4_3_Beefalo:HPE_StoreOnce_Configuration#zoning|zoning]], is set up correctly as recommended by HPE.</translate>
*<translate><!--T:69--> 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 [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Configuration#zoning|zoning]], is set up correctly as recommended by HPE.</translate>
*<translate><!--T:70-->
*<translate><!--T:70-->
Check the HPE StoreOnce Support Matrix for compatibility at https://www.hpe.com/Storage/StoreOnceSupportMatrix (login required).
Check the HPE StoreOnce Support Matrix for compatibility at https://www.hpe.com/Storage/StoreOnceSupportMatrix (login required).
Line 157: Line 211:
The following zoning considerations are recommended by HPE:</translate>
The following zoning considerations are recommended by HPE:</translate>
*<translate><!--T:73--> 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.</translate>
*<translate><!--T:73--> 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.</translate>
*<translate><!--T:74--> 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.</translate>
*<translate><!--T:74--> Zone the SEP sesam Server or every Remote Device 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 SAN fabrics. Multiple connections allow for higher availability.</translate>
*<translate><!--T:75--> 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.</translate>
*<translate><!--T:75--> 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 SEP sesam Server/Remote Device Server or to the StoreOnce. Zone StoreOnce Catalyst Copy over Fibre Channel source and destination copy devices the same way.</translate>
*<translate><!--T:76--> 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.</translate>
*<translate><!--T:76--> 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.</translate>
*<translate><!--T:77--> Use small Fibre Channel zones limiting the number of Fibre Channel ports in each zone.</translate>
*<translate><!--T:77--> Use small Fibre Channel zones limiting the number of Fibre Channel ports in each zone.</translate>
Line 166: Line 220:
==={{anchor|FC_config}}Fibre Channel configuration=== <!--T:79--></translate>
==={{anchor|FC_config}}Fibre Channel configuration=== <!--T:79--></translate>


<ol><li><translate><!--T:80--> 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''.</translate></li>
<ol><li><translate><!--T:80--> 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 as data address to access the Catalyst store over Fibre Channel and must be provided to SEP sesam during the creation of a new store. It is in the format COFC-<device-id>, e.g., ''COFC-1JB6Q36FMNR4JG0X''.</translate></li>
<li><translate><!--T:81--> Make sure ''Devices per Initiator Port'' is configured properly.</translate></li>
<li><translate><!--T:81--> Make sure ''Devices per Initiator Port'' is configured properly.</translate></li>
<translate><!--T:82--> 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.</translate>
<translate><!--T:82--> 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.</translate>
<ul><li><translate><!--T:83--> 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.</translate></li>
<ul><li><translate><!--T:83--> 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.</translate></li>
<li><translate><!--T:84--> ''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.</translate> </li>
<li><translate><!--T:84--> ''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.</translate></li>
<translate><!--T:85--> 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.</translate>
<translate><!--T:85--> 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.</translate></ul>
<li><translate><!--T:86-->
The number of possible paths between a SEP sesam Fibre Channel port and a StoreOnce Fibre Channel port is calculated as<br />
''number of a client's ports zoned to a StoreOnce System * number of StoreOnce System ports zoned to that client * devices per initiator count''</translate>
</li></ul>
<translate><!--T:87--> '''Example relationships between Device per Initiator Port and Number of Connections'''</translate>
 
{| border="2" cellpadding="4" cellspacing="0" style="width:70%; margin: 1em 1em 1em 0; background: #fcfcfc; border: 1px #aaa solid; border-collapse: collapse;"
|- style="background:#FFCC01; color:#002F55"
! scope="col" |
SEP sesam Server
! scope="col" |
HPE StoreOnce System
! scope="col" |
Devices per Initiator Port
! scope="col" | <translate>
<!--T:88-->
Max. FC connections between SEP sesam and StoreOnce FC ports</translate>
|-
|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     
|}
</ol>
</ol>
<translate><!--T:89--> Your system is now ready to configure [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup|backups]].</translate>
<translate>
<div class="noprint">
<div class="noprint">
<translate>== See also == <!--T:54-->
== What is next? == <!--T:132-->
[[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup|HPE StoreOnce Backup]] – [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]]</div></translate>
 
<!--T:133-->
Now create a new Catalyst store in the SEP sesam GUI. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_HPE_StoreOnce_Configuration|SEP sesam HPE StoreOnce Configuration]].
 
== See also == <!--T:54-->
 
<!--T:134-->
[[Special:MyLanguage/4_4_3_Beefalo:Saving_Encryption_Key_Store_for_HPE_StoreOnce_Catalyst|Saving Encryption Key Store for HPE StoreOnce Catalyst]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Backup|HPE StoreOnce Backup]] – [[Special:MyLanguage/4_4_3_Beefalo:HPE_StoreOnce_Replication|HPE StoreOnce Replication]] – [[Special:MyLanguage/How_to_create_a_Remote_Device_Server_(RDS)|How to create a Remote Device Server (RDS)]]</div></translate>

Revision as of 08:47, 6 April 2020

Other languages:

Copyright © SEP AG 1999-2024. 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/Beefalo V2. For previous documentation version(s), check SEP sesam Archive.


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.

With SEP sesam v. 4.4.3 Beefalo V2 it is recommended to use HPE Cloud Bank Storage (HPE StoreOnce v. ≥ 4.1) as a Catalyst copy target where you can replicate or restore your data instead of regular Catalyst stores. It cannot be used as a backup target due to its limited object size.

You can create a Cloud Bank store in a similar way to Catalyst store, as described in Creating HPE StoreOnce Cloud Bank store.

StoreOnce Catalyst concept and terminology

HPE StoreOnce enables bandwidth-efficient backup and restore over LAN, WAN and Fibre Channel. It provides the flexibility of using different deduplication modes, depending on your environment and performance (see section Catalyst data deduplication modes). Encryption is defined on the Catalyst store side individually for each Catalyst store; note that once encryption is enabled, it can no longer be disabled.

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.
  • Transfer policies: By selecting Low Bandwidth or High Bandwidth (HBW) it is defined how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs. See section Catalyst data deduplication modes.
  • 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.

Catalyst data deduplication modes

StoreOnce Catalyst provides the flexibility of performing deduplication at backup server, target, or application source, depending on your environment and performance requirements. Catalyst stores can be configured individually for specific deduplication mode in the Advanced Settings by selecting the appropriate bandwidth type for Transfer Policies. By specifying the transfer policy mode you define how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs.

Source-side/server-side deduplication (HPE: Backup Server Deduplication)

The HPE StoreOnce Catalyst agent deduplicates data on the source side within the backup server, i.e. the backup server or RDS deduplicated before transferring it to StoreOnce. For this, the Primary Transfer Policy must be set to Low Bandwidth (is the bandwidth-optimized mode). This option is recommended for most use cases as it reduces the network load and improves backup performance.

Target-side deduplication (HPE: Target Deduplication)

Target deduplication runs deduplication processing at the backup target, after the data is transported to HPE StoreOnce. For this, the Catalyst store must be in the performance-optimized mode by setting the Primary Transfer Policy to High Bandwidth. This option is recommended when there is a need to reduce the disk space required for backup data.

Application-side deduplication (HPE: Application Source Deduplication)

Software-based source-side deduplication uses the SEP sesam Client (without RDS) to perform the deduplication process and writes the deduplicated data directly to HPE StoreOnce, without using the Media Server. As of v. 4.4.3 Beefalo V2, you can use the application-side deduplication by selecting the HPE StoreOnce Bandwidth Optimized Data Transfer option in the properties of the HPE StoreOnce backup event; for details, see Option HPE StoreOnce Bandwidth Optimized Data Transfer. By selecting this option, redundant data is removed before it is transmitted to the backup target (only the changed blocks are transferred) thus optimizing bandwidth utilization. Application-side deduplication requires at least one transfer policy to be set to Low Bandwidth.

Information sign.png Note

Keep the following in mind when using this option:

  • If High Bandwidth is configured for both, the Primary and Secondary Transfer policy, the application-side deduplication cannot be performed on the client. In this case, the data is transferred directly from the client to the StoreOnce system with target deduplication, without deduplicating the data in advance at its source by the client.
  • HPE StoreOnce Bandwidth Optimized Data Transfer is important mainly for WAN clients. By enabling it, SEP sesam establishes the connection between the local STPD and HPE StoreOnce. This option is only available if the SEP sesam STPD service is part of the SEP sesam Client installation. This is the case with the SEP sesam Windows Client installation and in case of SEP sesam Linux RDS installation.
  • HPE StoreOnce Bandwidth Optimized Data Transfer can also be used for SAP Oracle (RMAN) backups and SAP Netweaver (Oracle) backups if the following parameters are configured before you start a backup: the first one is SESAM_DRIVE that has to be set to the HPE Catalyst Store, the second is SESAM_TAPESERVER where you specify the name of your SAP (on Oracle) client. These parameters can be configured in the SAP UTIL_FILE or in the RMAN script.
Configuring SESAM_DRIVE and SESAM_TAPESERVER for SAP Oracle backups

To send the data straight from the SAP Oracle client to the HPE Catalyst Store, a local STPD connection must be established. In the SAP UTIL_FILE or in the RMAN script, the SESAM_DRIVE parameter must be set to the HPE Catalyst Store to define the connection to the HPE system and the SESAM_TAPESERVER parameter must be specified with the name of the SAP client (as it is configured in the SEP sesam GUI):

SESAM_DRIVE=SMS:DS@+SO@<DB:data_stores.name>
SESAM_TAPESERVER=<SAP_client_hostname>
Example
SESAM_DRIVE=SMS:DS@+SO@ix2-store-once-1
where the value after the second @ is <DB:data_stores.name>
SESAM_TAPESERVER=sapcertsles11.sep.de
where the name is the hostname of the SAP client as specified in the SEP sesam GUI 
SEP Tip.png Tip
For Oracle RMAN, these parameters can be set in the RMAN script directly or by using sbc_rman -d and -S switch. For details, see Backing up the Oracle database.

Requirements

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

HPE StoreOnce connections

The following (TCP) ports are used to allow the StoreOnce Catalyst traffic to pass to and from the SEP sesam Server:

  • 9387 -> command session port number the server will listen on by default
  • 9388 -> data session port number the server will listen on by default

Minimum supported version of HPE system

The following list shows the minimum supported versions of HPE system Gen3 and Gen4 Storeonce platform. SEP sesam cannot assure support for releases older than the minimum supported version.

HPE system Version
Gen4 ≥ 4.1.3
Gen3 ≥ 3.18.7

Steps

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 2 of the procedure).

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

Creating HPE StoreOnce Catalyst store

  1. In the StoreOnce menu -> Data Services -> Catalyst Stores, click Create Store option at the top right corner. The Create Store window opens.
  2. Enter the name of your Catalyst store. The exact name is needed to add the Catalyst store to SEP sesam environment later, so write it down. Use underscores (_) or dashes (-) instead of spaces.
  3. Creating Catalyst store.jpg
  4. Optionally, under the Security Settings, set the following options.
    • Store Encryption: If the proper license was applied, you can enable StoreOnce encryption. This built-in encryption of the Catalyst store can only be activated individually for each Catalyst store during its setup. Once encryption is enabled, it can no longer be disabled.
    • Information sign.png Note
      • If you want to use encryption, SEP recommends to use StoreOnce encryption instead of SEP sesam built-in Task encryption, as the backup data cannot be deduplicated when SEP sesam encryption is enabled.
    • Data Immutability (retention) period for your data jobs and inbound/outbound copy jobs. This option can be used as additional protection for your data as you set up the retention policy when configuring SEP sesam. If set, 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 StoreOnce data immutability period, the data is protected as defined by SEP sesam EOL.
  5. Catalyst store security settings.jpg

  6. Under the Advanced Settings, 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. Note that the selected mode for the primary and secondary policy affects how the backup data is transferred between SEP sesam and HPE Catalyst store and where the deduplication process occurs (see section Catalyst data deduplication modes). SEP sesam uses the primary (default) transfer policy for data transfer between the Remote Device Server and the HPE Catalyst store. The secondary transfer policy can be used for reaching a secondary StoreOnce appliance with the replication.
    SEP Tip.png Tip
    As of v. 4.4.3 Beefalo V2, you can use the application-side deduplication by setting the HPE StoreOnce Bandwidth Optimized Data Transfer option in the SEP sesam GUI. To use this option, at least one transfer policy must be set to Low Bandwidth. For details on where to set this option, see HPE StoreOnce Backup: Option HPE StoreOnce Bandwidth Optimized Data Transfer.
  7. STORAGE QUOTAS
    You can also define the physical and logical data size quota for each Catalyst store. By setting the quota, you can distribute the physical capacity of the StoreOnce system among different users and effectively determine how much storage space on the HPE StoreOnce backup system can be used by a particular user. Applications with a better deduplication ratio can store more data.
    • Physical Storage 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.
    • SEP Tip.png Tip
      Normally the HPE StoreOnce is used for more than one HPE Catalyst Store. For this multi-store approach, SEP recommends to set Physical Storage Quotas.
    • Logical Storage Quota sets the maximum amount of data that can be written to the store before deduplication.
    Information sign.png Note
    • When quota limits are set and the quota limit is reached, backups will fail to prevent the quota from being exceeded. Restores are still allowed, but all new backups will fail. To solve this issue, increase the quota to the sufficient size.
    • As of Beefalo V2, the SEP sesam data store Disk space usage option for HPE StoreOnce Catalyst Store supports Catalyst Store Physical Storage Quota and Logical Storage Quota. You can check the HPE StoreOnce storage quotas and the overall HPE StoreOnce storage sizes in SEP sesam GUI: Main selection -> Components -> Data Stores, double-click your StoreOnce store and then click the HPE Catalyst Store State tab. For details, see Configuring HPE StoreOnce data store in SEP sesam.
  8. Catalyst store settings.jpg
    Click Create to create your first Catalyst store. Then repeat the procedure to create additional Catalyst stores.

  9. Once your Catalyst store is created, configure the Client Access permission for this store:
    Click Add Client and specify a user name and password. Catalyst Client Name is the user name.
    Note that this does not have to be the name of the backup server, you can choose whatever name you wish. Write down these credentials to create the store in SEP sesam later on. You can also change the Client Access permission later by using the Permissions tab of the already configured Catalyst store.
  10. Client access.jpg

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 the SEP sesam Server or every Remote Device 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 SAN fabrics. 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 SEP sesam Server/Remote Device 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 as data address to access the Catalyst store over Fibre Channel and must be provided to SEP sesam during the creation of a new store. 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.