4 4 3 Beefalo:SEP Cloud RDS

From SEPsesam
Revision as of 16:51, 1 February 2021 by Sta (talk | contribs) (Draft according to existing DE version, in progress.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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 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.

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 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.

SEP-Cloud-RDS.jpg

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

VMware

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.

SEP-Cloud-RDS-VMware.jpg

See also

About ReplicationSEP Si3 Replication