HPE replication with SEP sesam enables efficient and secure transfer of backup data between HPE StoreOnce Catalyst stores. SEP sesam also supports replication to HPE Cloud Bank Storage and offers compatibility with various cloud storage providers, such as Amazon AWS S3, Microsoft Azure, or others.
You can use Hewlett Packard Enterprise (HPE) StoreOnce Catalyst stores as backup storage. HPE StoreOnce fully controls backup data and enables efficient replication, deduplication, encryption and recovery. SEP sesam supports replication of savesets from one HPE Catalyst store to another, and from HPE Catalyst store to an external object storage – HPE Cloud Bank Storage (HPE StoreOnce v. ≥ 3.18) or HPE Cloud Volumes Storage (HPE StoreOnce v. ≥ 4.2.3).
- HPE Cloud Bank Storage
- SEP sesam supports HPE Cloud Bank Storage as a Catalyst copy target for replicating your data. HPE Cloud Bank Storage stores data to public or private cloud storage from various services, i.e., Amazon AWS S3, Microsoft Azure, and Scality, as opposed to regular HPE StoreOnce Catalyst stores where data is written to disk in the HPE StoreOnce system. It is especially suitable for long-term retention and archiving of backups and offsite backup copies intended for disaster recovery. It also allows you to follow the 3-2-1 backup strategy. For details, see SEP sesam HPE StoreOnce Configuration.
- HPE Cloud Volumes
- You can also back up and replicate data from local Catalyst store (not Cloud Bank store) to HPE Cloud Volumes. Note that replication from HPE Cloud Volumes to local HPE StoreOnce Catalyst store or Cloud Bank Storage is not supported. For details, see Backup to HPE Cloud Volumes.
Replication between HPE StoreOnce appliances is optimized for bandwidth efficiency, minimizing the impact on network resources and ensuring a more efficient data transfer process. In addition, replicating to HPE Cloud Bank Storage can improve data protection by storing a copy in a secure cloud environment and extend the geographical separation of your backup data.
|If you prefer to watch a video, you can learn all the steps of the replication procedure by watching Catalyst-based backup, replication and restore of HPE StoreOnce with SEP sesam on the SEP sesam YouTube channel.
Before you start configuring HPE StoreOnce replication, ensure that your environment fulfills the following prerequisites:
- SEP sesam environment:
- SEP sesam Server with at least one configured RDS (refer to How to configure RDS).
- Matching SEP sesam versions on the Server and RDS (refer to Release Versions).
- Java installed on RDS and deduplication clients (refer to Java Compatibility Matrix).
- HPE StoreOnce backup appliance:
Set up an configure your HPE StoreOnce backup appliance. Ensure it meets the minimum supported version of the HPE system and acquire the necessary licenses for HPE StoreOnce Catalyst stores.
- HPE Cloud Bank Storage:
To replicate to HPE Cloud Bank Storage, create and set up the Cloud Bank store(s) using the HPE StoreOnce Management Console. Enter the required credentials for the target object store (for example, Amazon AWS S3, Microsoft Azure...).
Follow these steps to configure HPE replication with SEP sesam:
- Create an HPE StoreOnce Catalyst Store in the StoreOnce system.
- Optionally, configure the Cloud Bank Store. If replicating to HPE Cloud Bank Storage, create the Cloud Bank store using the HPE StoreOnce Management Console. Enter the necessary details such as name, service provider, storage account information, and container name.
- Configure two different HPE StoreOnce data stores according to your Catalyst stores configuration, designate one as the replication source and the other as the replication target (remote Catalyst store, Cloud Bank store, or HPE Cloud Volume store).
- Create source and target media pools for each data store, specifying the retention time for data protection.
- Run test backups on both HPE StoreOnce stores to ensure that your data is backed up properly.
|If immutability (retention) period is set when the Catalyst store is created, the data is protected for the specified 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 is protected as defined by SEP sesam.
Setting up the replication process
After successful configuration, set up the replication process. This ensures that only changed data blocks are sent over the network during replication. This involves the following steps:
- Create a replication task.
- Define source and target media pools, specify the network interface, and set the time frame for the backups to be replicated. For detailed instructions see Creating a Replication Task.
- Run the initial replication.
- Transfer all data from the source to the destination. Keep in mind that the initial replication process requires significant CPU resources, network bandwidth, and time for successful completion. For detailed instructions see section Initial replication.
- Schedule replication.
- Decide on the schedule for replication cycles and then create and schedule a replication event. This ensures that subsequent replications occur automatically at specified intervals. For detailed instructions see Creating a Replication Event.