4 4 3 Beefalo:HPE StoreOnce Backup

From SEPsesam
Other languages:

Copyright © SEP AG 1999-2022. 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/5.0.0 Jaglion. For previous documentation version(s), check documentation archive.


Overview

You can use Hewlett Packard Enterprise (HPE) StoreOnce Catalyst stores as backup storage (≥ 4.4.3 Beefalo). For system requirements and supported configurations, see Support Matrix: SEP sesam integration with HPE StoreOnce Catalyst.

Before configuring SEP sesam backup to StoreOnce Catalyst stores, your HPE StoreOnce backup appliance must be set up and all requirements must be met, as described in HPE StoreOnce Configuration.
Once your HPE StoreOnce appliance is set up and Catalyst stores are created on the StoreOnce system, you have to configure the HPE StoreOnce data store(s) in the SEP sesam GUI. Then configure your HPE StoreOnce backup as described below.

Configuring backup to HPE StoreOnce

Configuring a backup to StoreOnce Catalyst store consists of the following steps:

  1. The HPE StoreOnce data store must already be configured; for details, see SEP sesam HPE StoreOnce Configuration.
    • Note that you cannot use HPE Cloud Bank store as a backup target; HPE Cloud Bank storage is supported only as a Catalyst copy target.
    • In addition to HPE StoreOnce Catalyst store, you can use HPE Cloud Volumes as backup storage. For more information, see Backup to HPE Cloud Volumes.
  2. Create a media pool for the backup.
  3. Back up to the HPE StoreOnce data store.

Creating a media pool for backup

After configuring an HPE StoreOnce data store, you have to create a media pool for backup to HPE StoreOnce. Note that you can create media pools while configuring a data store by clicking the Create Media Pool button or later in the HPE StoreOnce data store properties, as described here.

  1. Double-click the HPE StoreOnce data store and in the Properties window click Create Media Pool.
  2. Enter a media pool name, for example, MP_StoreOnce-2_dly.
  3. Set the Retention time for which the media from the pool are protected from writing (see What is retention time and EOL).
    If you have set the StoreOnce immutability (retention) period for your backups when you created the Catalyst stores, the data will be protected for the specified immutability period, even if the SEP sesam EOL has expired. If the SEP sesam EOL is longer than the defined immutability period, the data is protected as defined by SEP sesam. For details, see StoreOnce immutability period.

Backing up to HPE StoreOnce

Configuring a backup to HPE StoreOnce Catalyst store in the SEP sesam GUI involves creating a backup task, setting up a backup schedule (specifying when you want to back up your data) and linking the schedule with a backup event (specifying how and where to back up the data). For general details on backup configuration and prerequisites, see Standard Backup Procedure.

SEP Tip.png Tip
If you prefer to watch a video, you can learn all the steps of the backup procedure by watching Catalyst-based backup, replication and restore of HPE StoreOnce with SEP sesam on the SEP sesam YouTube channel.
  1. From Main Selection -> Tasks -> By Clients, select the HPE StoreOnce client and click New Backup Task. The New Backup Task window opens.
  2. Specify the Source. You can either browse for the savesets you want to include in the backup or enter their names followed by a comma. Note that by browsing the source (and not when you enter it manually), the task type and task name are set automatically.
  3. HPE StoreOnce bck task.jpg
  4. If you want to define other options (such as pre/post backup and restore commands, encryption or compression, the credentials to access resources on the target client, consolidating individual tasks under a specific task group, or assigning a task to the schedule), click the corresponding tabs in the New Backup Task window.
  5. Information sign.png Note
    If you already enabled encryption when you created the Catalyst store, you cannot use SEP sesam encryption.

    Click OK to create the task.

  6. If you want to start the newly created task immediately, right-click the name of the task and click Immediate Start. If you want to create a periodic backup, you have to create a schedule for your backup task: Click New schedule under Main Selection -> Scheduling -> Schedules and set up a schedule. For more details, see Creating a Schedule.
  7. SEP Tip.png Tip
    You can add your backup task to an existing schedule by double-clicking the backup task, selecting the tab Schedules and adding it to one or more schedules. You can also group your backup tasks into task groups. For details, see Adding a Task to the Task Group.
  8. Once you have configured a schedule, you need to create a new backup event for it; right-click the schedule and select New Backup Event. For general information on creating a backup event, see Creating a Backup Event.

Option HPE StoreOnce Bandwidth Optimized Data Transfer

You can set the HPE StoreOnce Bandwidth Optimized Data Transfer option (≥ 4.4.3 Beefalo V2) in the properties of the HPE StoreOnce backup event: Double-click the existing HPE StoreOnce backup event to open its properties and select the option HPE StoreOnce Bandwidth Optimized Data Transfer. By selecting it, application-side deduplication is used by transferring only the changed blocks to the backup server during the backup to optimize bandwidth usage. To use this option, at least one transfer policy must be set to Low Bandwidth. For details on where to set the transfer policy, see HPE StoreOnce Configuration: Creating HPE StoreOnce Catalyst store.

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 policies in the Catalyst settings, this option – application-side deduplication cannot be performed on the client. In this case, data is transferred directly from the client to the StoreOnce system with target deduplication, without deduplicating the data in advance at the source by the client. For details on deduplication modes, see HPE StoreOnce Configuration: Creating HPE StoreOnce Catalyst store.
  • HPE StoreOnce Bandwidth Optimized Data Transfer is important mainly for WAN clients. If you enable 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 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 is SESAM_DRIVE, which must 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. For details, see example below.

HPE StoreOnce bck event.jpg

Configuring SESAM_DRIVE and SESAM_TAPESERVER for SAP Oracle backups

To send data directly from the SAP Oracle client to the HPE Catalyst Store, a local STPD connection must be established. In the SAP UTIL_FILE or in 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 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 directly in the RMAN script or with the sbc_rman -d and -S switch. For details, see Backing up the Oracle database.

Monitoring backups

You can view the status of your backup jobs in the GUI (Monitoring -> Last Backup State or Job State -> Backups) or SEP sesam Web UI. The backup status overview provides detailed information about the last run of backup jobs, including task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

Troubleshooting HPE StoreOnce backups

For more information, see the Troubleshooting Guide.