5 0 0:HPE Cloud Volumes Backup

From SEPsesam
Jump to: navigation, search

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.

This page is a draft. Treat the information on this page with caution as it may be incomplete.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 5.0.0 Jaglion. For previous documentation version(s), check documentation archive.


With SEP sesam v. 5.0.0 Jaglion, you can use HPE Cloud Volumes as backup storage in addition to HPE StoreOnce Catalyst stores and HPE Cloud Bank storage. The HPE Cloud Volumes solution provides efficient direct backups (unlike HPE Cloud Bank store), replication, and restore.

Although you can use HPE Cloud Volume store for direct backups, it is recommended that you use it more as a secondary target repository for replication (Catalyst copy job). For details on replication, see HPE StoreOnce Replication.

Before configuring a SEP sesam backup on HPE Cloud Volumes, your HPE StoreOnce backup appliance must be set up and your Catalyst store(s) must be properly configured as described in HPE StoreOnce Configuration.


To ensure error-free operation of SEP sesam and improve performance, ensure that the following conditions are met in addition to the requirements for the HPE StoreOnce backup appliance:

  • HPE system ≥ 4.2.3
  • SEP sesam Server (≥ 5.0.0 Jaglion) must be connected to the HPE StoreOnce Catalyst via Ethernet for backups and restores.
  • On Linux, secure PROXY Client (secure_client) is required to access HPE Cloud Volumes data store. An RDS should be used for this client if possible, see How to create a Remote Device Server (RDS).
  • When configuring HPE Catalysts stores, make sure that low bandwidth is set as transfer policy. It affects how the backup data is transferred between SEP sesam and the HPE Catalyst store. Note that the HPE Cloud Volumes service does not support high bandwidth data transfer. See HPE StoreOnce Configuration.


  • Replication (Catalyst copy) from HPE Cloud Volumes to local HPE StoreOnce Catalyst store or Cloud Bank Storage is not supported.
  • Data immutability, which can be defined when creating HPE StoreOnce Catalyst store is not supported for HPE Cloud Volumes.

Configuring backup to HPE Cloud Volume data store

Configuring a backup to HPE Cloud Volume store consists of the following steps:

  1. The HPE Cloud Volume data store must already be configured; for details, see SEP sesam HPE StoreOnce Configuration.
  2. Create a media pool for the backup.
  3. Back up to the HPE Cloud Volume data store.

Creating a media pool for backup

After you configure an HPE Cloud Volume data store, you must create a media pool for backup to HPE Cloud Volume. Note that you can create media pools beforehand during configuration of a data store (by clicking the Create Media Pool button) or later in the HPE Cloud Volume data store properties, as described here.

  1. Double-click the Cloud Volume data store and click Create Media Pool in the Properties window.
  2. Enter a media pool name, such as MP_Cloud_Volume-2_dly.
  3. Set up the Retention time for which the media from the pool is protected from writing (see Managing EOL).

Backing up to HPE Cloud Volume

Configuring a backup to HPE Cloud Volume data 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 to a backup event (specifying how and where to back up the data). For general details on backup configuration and prerequisites, see Standard Backup Procedure.

  1. From Main Selection -> Tasks -> By Clients, select the HPE Cloud Volume 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 when you browse the source (and not when you enter it manually), the task type and task name are set automatically.
  3. If you want to specify additional options (for example, pre/post backup and restore commands, encrypting or compressing data, credentials for accessing resources on the target client, consolidating individual tasks under a specific task group, or assigning a task to the schedule), click the appropriate tabs in the New Backup Task window.
  4. Click OK to create the task.

  5. If you want to start the newly created task immediately, right-click the task name and click Immediate Start. If you want to create a periodic backup, you have to create a schedule for your backup task: Go to Main Selection -> Scheduling -> Schedules, click New schedule, and set up a schedule. For more details, see Creating a Schedule.
  6. SEP Tip.png Tip
    You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the Schedules tab, 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.
  7. Once you have configured a schedule, you must 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.

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 the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

See also

HPE StoreOnce ConfigurationHPE StoreOnce ReplicationMonitoring and Reporting