Source:HPE StoreOnce Replication - Jaglion
Overview
As of v. 4.4.3 Beefalo, you can use Hewlett Packard Enterprise (HPE) StoreOnce Catalyst stores as a backup storage. HPE StoreOnce fully controls the backup data and enables you efficient replication, deduplication, encryption and recovery. SEP sesam supports the replication of savesests from one HPE Catalyst store to another. 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.
With v. 4.4.3 Beefalo V2 (HPE StoreOnce v. ≥ 4.1), it is recommended to use HPE Cloud Bank (public or private cloud) storage as a Catalyst copy target for replicating 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. The Cloud Bank store is very similar to a regular Catalyst store. Note that before you configure a SEP sesam replication to HPE Cloud stores, your HPE StoreOnce backup appliance must be set up and all the requirements must be met (e.g., minimum supported version of HPE system, HPE StoreOnce Catalys store and HPE Cloud Bank store licenses, 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 the secondary StoreOnce remote system, i.e., HPE Cloud Bank Storage which stores the data to public or private cloud storage from different services, e.g., Amazon AWS S3, Microsoft Azure and Scality.
Configuring HPE StoreOnce replication with SEP sesam
SEP sesam replication is designed to consistently replicate data between SEP sesam Remote Device Servers (RDS), which can also be SEP sesam Servers. SEP sesam replication searches only for new blocks of data on the source media pool and replicates those changes to a target media pool according to 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 ability to control your network usage by scheduling replication. For details on SEP sesam replication and its prerequisites, see Replication.
Step-by-step procedure
To replicate the data to a HPE Cloud Bank store (recommended) or HPE Catalyst store, proceed as follows:
- Create a HPE StoreOnce Catalyst store. For details, see HPE StoreOnce Configuration.
- If you want to replicate to HPE Cloud Bank Storage, set up a HPE Cloud Bank store and enter credentials of the Amazon AWS S3 or Microsoft Azure object store.
- In the SEP sesam GUI configure the HPE StoreOnce store or HPE Cloud Bank store, if you want to replicate your data to HPE Cloud Bank Storage.
- Configure source and target media pool(s) for your HPE Catalyst store or HPE Cloud Bank store.
- Create a backup task for backing up to HPE StoreOnce Catalyst store. 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. For details on backup configuration, see HPE StoreOnce Backup.
- Then configure replication.