5 0 0:Backup to HPE Cloud Volumes

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.

Draft.png WORK IN PROGRESS
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.


Overview

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 backup, replication, and restore - unlike HPE Cloud Bank storage, which cannot be used as a backup target.

Although you can use HPE Cloud Volumes storage for direct backups, in accordance with HPE policy, it is recommended that you use it more as a secondary target repository for replication (Catalyst copy job) due to potential bandwidth and latency constraints. For details on replication, see HPE StoreOnce Replication.

Requirements

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, the secure PROXY Client (secure_client) is required to access the HPE Cloud Volumes data store. See below Creating a Backup Store and setting up the secure client.
  • When configuring HPE Catalysts stores, make sure that low bandwidth is set as the transfer policy. It affects how backup data is transferred between SEP sesam and HPE Catalyst store. Note that the HPE Cloud Volumes service does not support high bandwidth data transfer. See HPE StoreOnce Configuration.

Restrictions

  • Replication (Catalyst copy) from HPE Cloud Volumes to local HPE StoreOnce Catalyst store or Cloud Bank Storage is not supported.
  • No support for instant recovery, live mount, or single file restore.

Configuring backup to HPE Cloud Volume data store

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

  1. Create a Backup Store in HPE CV web portal and set up a secure client
  2. Configure HPE StoreOnce data store for HPE Cloud Volumes
  3. Create a media pool for the backup
  4. Back up to the HPE Cloud Volume data store

Creating a Backup Store and setting up the secure client in HPE CV

  1. Create a Backup Store Log in to the HPE CV web portal, go to Backup Stores, and click New Store. Enter a Store Name (it must be a single word with less than 50 lowercase characters and contain only letters, numbers, and dashes), a Description, and select the Region closest to your physical location. Click Create Store.
  2. Download the text file that contains your connection credentials (your username and password) and click Close.
  3. Download and set up the Secure Client. The secure client (secure_client) is a Linux-based proxy server that is required to set up and run to backup data to HPE Cloud Volumes.
    For this secure client, you should use a Remote Device Server (RDS) on Linux. If you are not familiar with configuring RDS in SEP sesam, see How to create a Remote Device Server (RDS).
    For detailed instructions on secure client setup, see official HPE documentation HPE Cloud Volumes - Help: Downloading the Secure Client and Creating a Backup Connection Using the Secure Client.

Configuring the HPE StoreOnce data store for Cloud Volumes in SEP sesam

SEP sesam HPE StoreOnce data store is a special device type used to write savesets directly to HPE StoreOnce Catalyst stores and to HPE Cloud Volumes. The HPE Cloud Volume is addressed via Linux Proxy where secure_client is running and SSH keys to access the HPE Cloud Volume are installed.

  1. In the Main selection -> Components, click Data Stores to display the data store contents frame.
  2. From the Data Stores menu, select New Data Store. A New Data Store dialog appears.
  3. In the Name field, enter the exact name of the backup store you created in the HPE CV web portal, for example, Cloud_Volumes_Store_1.
  4. From the Store type drop-down list, select HPE StoreOnce.
  5. Make sure that the Create Drive option is enabled under the Drive parameter properties. The predefined value for the drive is automatically added to the Drive number field.
    Then check Create new drive group. By enabling this option, SEP sesam will automatically create a new drive group.
  6. The predefined number of channels is already displayed in the Max. channels drop-down list. The number of available channels depends on your SEP sesam Server package. The standard license supports 10 concurrent streams, enabling 10 backup processes to run simultaneously. For details on SEP sesam licenses, see Licensing.
  7. Enter the name of the device server. This is the name of the Linux-based proxy server that you used to set up the secure client.
  8. Cloud Vol-StoreOnce data store.jpg

  9. Size and Disk space usage
    The SEP sesam data store Disk space usage option for HPE StoreOnce Catalyst Store supports Catalyst Store Physical Storage Quota and Logical Storage Quota (Beefalo V2). Depending on your StoreOnce store configuration at the time of this setup, the Capacity and High watermark values are set automatically according to the HPE Catalyst store storage quotas or its overall size (if no quotas are set). For details on quotas, see HPE StoreOnce Configuration – Storage Quotas. The following applies:
    • If Physical Storage Quota is set, the Disk space usage shows the Used/Total/Free values that correspond to the physically occupied space for the HPE Catalyst Store.
    • If Logical Storage Quota is set, the Disk space usage values are set to reflect the Logical Storage Quota specific values.
    • If neither storage quota is set, the calculation considers the overall HPE StoreOnce sizes. Note that Catalyst stores may consume capacity from the common storage pool and the values displayed indicate the actual disk space usage of the latter.
  10. Switch to the HPE Credentials tab, click New and create a new credential set. Enter the same credentials that you set up when you created the HPE Cloud Volumes Backup store.
  11. You can create the media pool(s) for the HPE StoreOnce data store immediately by clicking the Create Media Pool button, or later in the HPE StoreOnce data store properties. If you chose to create the media pool(s) later, click OK to configure your StoreOnce data store.

Creating a media pool for Cloud Volumes backups

After you configure the HPE StoreOnce data store for Cloud Volumes, you must create a media pool for backup to HPE Cloud Volumes. 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 StoreOnce data store properties, as described here.

  1. Double-click the HPE StoreOnce data store you created earlier and click Create Media Pool in the Properties window.
  2. Enter a name for the media pool, for example MP_Cloud_Volumes-1_dly.
  3. Set the Retention time for which the savesets from the pool are protected from writing. For details, see What is retention time and EOL).

Backing up to HPE Cloud Volumes

Configuring a backup to HPE Cloud Volumes in the SEP sesam GUI includes 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 source 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 regular 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 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.

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 ReportingSupport Matrix: SEP sesam integration with HPE StoreOnce Catalyst