4 4 3 Beefalo:SEP Cloud RDS

From SEPsesam
Revision as of 12:51, 3 February 2021 by Sta (talk | contribs) (In progress.)
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2022. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.


Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo/4.4.3 Beefalo V2. For previous documentation version(s), check Documentation archive.


Overview

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.

Requirements

  • A VPN connection to establish a connection to the 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.

Implementation examples

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 remote (offsite) location and can be restored locally or at the remote location if required. Additionally, the block-based data can be migrated to tape as native file data.

SEP-Cloud-RDS.jpg

Scenario 2: Replication of backed up virtual machines (VMs)

VMware

Selected VMs are permanently replicated to the remote 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. For more details on VMware, see SEP sesam VMware documentation.

SEP-Cloud-RDS-VMware.jpg

Citrix Hypervisor (XenServer)

Selected VMs are permanently replicated to the remote location and accessed via the local Citrix Xen pool. Additionally, the block-based data can be migrated to tape as native file data. For more details on Citrix, see SEP sesam Citrix Hypervisor documentation.

SEP-Cloud-RDS-Citrix-XEN-Server.jpg

Scenario 3: Replication of backed up applications

Selected applications such as databases (e.g., Exchange, etc.) are permanently replicated to the remote location and directly accessible by mounting the local Si3 deduplication store via VFSL (Virtual File System Layer) without being restored first. Additionally, the block-based data can be migrated to tape as native file data.

Information sign.png Note
SEP sesam supports different applications to be used directly on the Si3 deduplication store without restoring the data first. For Si3 deduplication store requirements and configuration, see Configuring Si3 Deduplication Store.

SEP-Cloud-RDS-Application.jpg

Scenario 4: BaaS (Backup as a Service)

The managed service providers (MSP; SEP sesam partners) use SEP sesam for offering their customers Backup as a Service (BaaS). This means that the MSP is responsible for the complete management of the backup data. For such backups, 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 respective customer's location. Additionally, the data is replicated to a dedicated cloud RDS server in the data center. These RDS servers run in the data center as a virtual machine on a server with the corresponding performance. Thus, data separation of the connected customers is ensured in this scenario as well.

SEP-Cloud-RDS-BaaS.jpg

See also

About ReplicationSEP Si3 ReplicationConfiguring Migration