Source:SEP Cloud RDS
The SEP Cloud RDS method enables you to permanently replicate block-based data from a local SEP Si3 deduplication store to a remote (offsite) Si3 deduplication store. However, this data can still be used directly due to the SEP sesam RDS (in this case SEP Cloud RDS Server) configured in the offsite location. For details on replication, see SEP Si3 Replication.
The dedicated connection between the SEP sesam Server and RDS ensures that data is separated between the individual connected clients and is end-to-end encrypted. Additionally, automated migration of the data to tape can be performed to avoid costs for tape drives and loaders.
This article describes different implementation scenarios for replicating to Cloud RDS Server. Note that you can implement compliance requirements easily without setting up a corresponding infrastructure locally.
- A VPN connection to establish a connection to a remote location.
- A SEP sesam Si3R Storage Pool Replication license (includes a SEP Cloud RDS Server). If a volume-based license is used, the required licenses are already included. For details, see Licensing.
In the below examples, four different implementation scenarios for replicating to Cloud RDS Server are described.
Scenario 1: Simple data replication
Selected data is permanently replicated to the offsite location and can be restored locally or at the offsite location if required. Additionally, the block-based data can be migrated to tape as native file data.
Scenario 2: Replication of backed up virtual machines (VMs)
Selected VMs are permanently replicated to the offsite location and then automatically restored to the local ESX data store. Additionally, the block-based data can be migrated to tape as native file data.