4 4 3 Beefalo:HPE StoreOnce Replication
- 1 Overview
- 2 Configuring HPE StoreOnce replication with SEP sesam
- 3 See also
As of v. 4.4.3 Beefalo, you can use Hewlett Packard Enterprise (HPE) StoreOnce Catalyst stores as backup storage. HPE StoreOnce fully controls the backup data and enables efficient replication, deduplication, encryption and recovery. SEP sesam supports the replication of savesets from one HPE Catalyst store to another, and as of version HPE StoreOnce v. ≥ 3.18, from HPE Catalyst store to external object storage – HPE Cloud Bank Storage.
4.4.3 Beefalo V2 (HPE StoreOnce v. ≥ 4.1) introduced support for HPE Cloud Bank Storage as a Catalyst copy target for replicating your data. 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. HPE Cloud Bank Storage 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 3-2-1 data protection rule.
Configuring a Cloud Bank store as a replication target is pretty straightforward and does not differ much from the configuration of a regular Catalyst store. Before you configure SEP sesam replication for HPE StoreOnce, your HPE StoreOnce backup appliance must be set up properly with all the requirements met (e.g., the minimum supported version of HPE system, required licenses for the HPE StoreOnce Catalys store and HPE Cloud Bank store, etc.), as described in HPE StoreOnce Configuration.
HPE StoreOnce replication workflow
The replication process uses the following workflow:
- The Catalyst store is created in the StoreOnce system.
- All backed up data is sent from the backup server (SEP sesam Server or RDS) to StoreOnce, where the data is duplicated and stored in the HPE Catalyst store.
- Deduplicated data is replicated to a secondary HPE StoreOnce Catalyst store or HPE Cloud Bank Store.
Configuring HPE StoreOnce replication with SEP sesam
SEP sesam HPE StoreOnce replication enables you to replicate the data between the HPE Catalyst store and another HPE (remote) Catalyst store or HPE Cloud Bank store. SEP sesam replication only searches for new blocks of data in the source media pool and replicates these changes to a target media pool according to a defined schedule. Replication means that only changed data blocks are sent over a network and replicated to the target server. This reduces the data transferred over the network and gives you the ability to control your network usage by scheduling replication. For details on SEP sesam replication and its prerequisites, see Replication.
To replicate the data from HPE remote Catalyst store to HPE Cloud Bank store (recommended) or HPE remote Catalyst store, proceed as follows:
- Create an HPE StoreOnce Catalyst store.
- In order to replicate to the HPE Cloud Bank Storage, first set up the HPE Cloud Bank store(s) using HPE StoreOnce Management Console and enter the required credentials (for Amazon AWS S3 or Microsoft Azure object store, respectively).
- In SEP sesam, configure two different HPE StoreOnce data stores according to your HPE StoreOnce Catalyst stores configuration (local, remote or Cloud Bank).
- Create media pools for your HPE StoreOnce stores; replication requires one source media pool and one target media pool.
- Run a test backup to make sure that your backup works properly.
- Then create a replication task for the HPE Catalyst store.
Creating HPE StoreOnce Cloud Bank store
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. Configuring a Cloud Bank store is similar to creating a Catalyst store with some additional steps.
- In the StoreOnce menu -> Data Services -> Cloud Bank Stores, click Create Store option at the top right corner. The Create Store window opens.
- Enter the name of your Cloud Bank store. The exact name is needed to add the Cloud Bank to SEP sesam environment later, so write it down. Use underscores (_) or dashes (-) instead of spaces.
- From the Service Provider drop-down list, select the target object store, e.g., Amazon, Azure, etc. Available options depend on the selected service provider.
- Enter the Storage Account Name/Access Key and Account Key/Secret Key of your object store storage account.
- Enter the Container Name/Bucket Name of the object store storage account container.
- Optionally, under Security Settings and Advanced Settings, set other configuration settings, e.g., StoreOnce encryption, transfer policy, etc., as described in Creating HPE StoreOnce Catalyst store.
- Click Create to create your first Cloud Bank store. Then repeat the procedure to create additional Cloud Bank stores.
Once your Cloud Bank store is created, configure its Client Access permission, as described in Creating HPE StoreOnce Catalyst store.
Configuring HPE StoreOnce data stores
Once your HPE StoreOnce appliance is set up and the Catalyst stores and Cloud Bank stores are created, you can configure the HPE data stores in the GUI. SEP sesam HPE StoreOnce data store is a special device type used for writing savesets directly to HPE StoreOnce Catalyst stores.
You have to configure two different HPE StoreOnce data stores for replication. The first data store (Catalyst store) will be used as a replication source and the second as a replication target (remote Catalyst store or Cloud Bank store). You can also replicate the data from remote Catalyst store or Cloud Bank store back to the Catalyst store. When configuring the stores, you have to select the relevant store type HPE StoreOnce or HPE Cloud Bank Store and specify your credentials, as described in SEP sesam HPE StoreOnce Configuration.
Creating media pools
Each data store requires a media pool. Note that you can create the media pools during a data store configuration by clicking the Create Media Pool button or later in the HPE StoreOnce/Cloud Bank data store properties, as described here.
Replication requires a source and a target media pool to where the data is replicated.
- Double-click the relevant HPE StoreOnce data store and in the Properties window click Create Media Pool.
- Enter a media pool name, for example, MP_source_StoreOnce_weekly.
- Set up the Retention time for which the media from the pool are protected from writing (see Managing EOL).
|If the immutability (retention) period has been set when creating Catalyst store, 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.|
Once you created a source media pool, create another - target media pool for your second HPE StoreOnce/Cloud Bank store, for example, MP_target_StoreOnce_weekly.
Testing your backups
To make sure that your data is backed up properly, test backup to both HPE StoreOnce stores.
- Create a new backup task: In the Main Selection -> Tasks -> By Clients, select your HPE StoreOnce client and then click New backup task. Configure your backup task and save it. For details, see Creating a backup task.
- Test the backup on the source and target HPE StoreOnce data store: From the menu bar, select Activities -> Immediate start -> Backup. In the Immediate start: Backup dialog, select a source/target media pool as your backup target media pool. Click Start and check if your backup performed successfully.
Creating a replication task
If your test backups finished successfully, create a replication task for your Catalyst store.
- In the Main selection -> Tasks -> Replication Tasks, click New replication task. The Replication Task window is displayed.
- In the Name field, enter a meaningful name for the replication task, e.g., rep-source_StoreOnce_mediapool-to-target_StoreOnce_mediapool.
- Under the Media Pool, specify the following:
- Pool: Select the source media pool from which the data will be replicated, e.g., MP_source_StoreOnce_weekly.
- Drive: Select the drive number of the drive that will be used to read the data. By selecting the source media pool, the drive number is set automatically, however, you can select another drive from the drop-down list.
- Interface: Optionally, from the drop-down list select the network interface of the RDS through which the data transfer will be executed.
- Pool: Select the target media pool to which the data will be replicated, e.g., MP_target_StoreOnce_weekly.
- Drive: Select the drive number of the drive that will be used to write the data.
- Interface: From the drop-down list select the network interface of the RDS through which the data transfer will be executed.
|Only the savesets with status successful and with warnings are selected for replication, whilst savesets with errors and only partially restorable savesets (containing data from cancelled backups) are not replicated.|
If you want to start the newly created replication task immediately, right-click the name of the task and click Immediate start. Otherwise, you have to add your replication task to one or more schedules to automate your replication by clicking New Schedule under Main Selection -> Scheduling -> Schedules. Once you have configured a schedule, you must create a new replication event for it. For details, see Scheduling replication.
You can check the status of your replication task under the Main Selection -> Job state -> Migrations and Replications. The columns provide details on status, start/stop time, media pools, replication type, etc., used for the task. You can also examine the progress of the replication and see how much data is being transferred; you can check data size, physical and nominal data in the columns Data Size, Transferred, Transferred (Brutto) and Progress respectively. For details, see Checking replication status.