The SEP Cloud RDS method enables you to continuously replicate block-based data from a local SEP Si3 deduplication store to a remote (offsite) Si3 deduplication store. However, this data can still be immediately used due to the SEP sesam RDS (in this case SEP Cloud RDS Server) configured at 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 kept separate between each connected client and is end-to-end encrypted.
This article describes different implementation scenarios for replicating to SEP Cloud RDS Server. Compliance requirements can thus be implemented with little effort and without the need to build up local infrastructure.
- A secure VPN connection is required to connect to the remote location.
- SEP sesam replication to SEP Cloud RDS Server requires additional licenses: for example, in the classic license model with the Si3R license, you need to enable the required number of nodes for Si3 replication; also required are RDS licenses and the Si3 TB for the original and the replication Si3 data store. (This licensing does not apply if the configuration is running in an MSP environment.) For details, see Licensing or contact SEP support.
Deduplication store types
SEP sesam v. 5.0.0 Jaglion has introduced a new generation Si3 deduplication store: Si3 NG. Si3 NG offers significantly higher performance for backup, restore and migration, as well as backup to S3 cloud and backup to Azure, the new immutable storage feature SiS, resulting in improved performance, scaling, and resource savings.
To learn how to upgrade from Si3 to Si3 NG by configuring a new Si3 NG on the same host and creating a replication job to replicate from Si3 to Si3 NG, see Configuring Si3 NG Deduplication Store.
Note that the implementation examples are the same for both types of deduplication store. Si3 NG is therefore not explicitly mentioned, but the term Si3 store is used for both types of deduplication store.
The following examples describe four different implementation scenarios for replicating to SEP Cloud RDS Server.
Scenario 1: Simple data replication
Selected data is continuously replicated to the remote (offsite) location and can be restored locally or at the remote location if required.
Scenario 2: Replicating backed up virtual machines (VMs)
SEP sesam supports replicating backed up VMs for all supported hypervisors. The same concept as shown in the below examples for VMware and Citrix can therefore be applied to any supported hypervisor.
Selected VMs are continuously replicated to the remote location and available again to the local ESX data store by using automated restores. For more details on VMware, see SEP sesam VMware documentation.
Citrix Hypervisor (XenServer)
Selected VMs are continuously replicated to the remote location and available again via the local Citrix Xen pool. For more details on Citrix, see SEP sesam Citrix Hypervisor documentation.
Scenario 3: Replicating selected solutions, platforms and databases
Chosen applications, such as databases (e.g., Exchange), can be continuously replicated to the remote location, where they can be accessed by mounting the local Si3 deduplication store thus eliminating the need for restore.
|SEP sesam supports different applications, solutions, and databases be accessed directly on the Si3 DedupStore without prior restore of the data. For the Si3 deduplication store requirements and configuration, see Configuring Si3 Deduplication Store.|
Scenario 4: BaaS (Backup as a Service)
SEP Backup as a Service (BaaS) is used by managed service providers (MSP) to enable their customers to have their data backed up while MSP takes over the complete administration of the data backup. A central SEP sesam Server is used in the data center, which performs a local backup (on-site) via distributed cloud RDS servers located at the customer's location. In the data center, the data is then replicated to a dedicated Cloud RDS Server. The RDS servers are deployed in the data center as virtual machines designed to deliver the required performance. This ensures data is kept separate for each customer served in this configuration.