Source:SEP Cloud RDS: Difference between revisions

From SEPsesam
(Draft ready for review.)
(Prepared for translation.)
Line 22: Line 22:
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate>
|}</div></noinclude>
|}</div></noinclude>
The ''SEP Cloud RDS'' method enables you to continuously [[Special:MyLanguage/SEP_sesam_Glossary#replication|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 due to the [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam RDS]] (in this case SEP Cloud RDS Server) configured in the offsite location. For details on replication, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]].  
<translate>The ''SEP Cloud RDS'' method enables you to continuously [[Special:MyLanguage/SEP_sesam_Glossary#replication|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 [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam RDS]] (in this case SEP Cloud RDS Server) configured in the offsite location. For details on replication, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]].  


The dedicated connection between the SEP sesam Server and RDS ensures that data is kept separate between the individual connected clients and is end-to-end encrypted. The SEP Cloud RDS solution supports automated[[Special:MyLanguage/SEP_sesam_Glossary#migration|migration]] of data to tape, reducing the cost of tape drives and loaders for the customer.  
The dedicated connection between the SEP sesam Server and RDS ensures that data is kept separate between the individual connected clients and is end-to-end encrypted. The SEP Cloud RDS solution supports automated [[Special:MyLanguage/SEP_sesam_Glossary#migration|migration]] of data to tape, reducing the cost of tape drives and loaders for the customer.  


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


===Requirements===
===Requirements===</translate>


*A secure VPN connection is required to connect to the remote location.
*<translate>A secure VPN connection is required to connect to the remote location.</translate>
*SEP sesam replication requires a special license ''SEP sesam Si3R Storage Pool Replication''  which also includes SEP Cloud RDS Server. The required licenses are already included in a volume-based license. For details, see [[Special:MyLanguage/Licensing|Licensing]].
*<translate>SEP sesam replication requires a special license ''SEP sesam Si3R Storage Pool Replication''  which also includes SEP Cloud RDS Server. The required licenses are already included in a volume-based license. For details, see [[Special:MyLanguage/Licensing|Licensing]].


==Implementation examples==
==Implementation examples==
Line 41: Line 41:
Selected data is permanently replicated to the ''remote'' (offsite) location and can be restored locally or at the remote location if required. The block-based data can be migrated to tape as ''native file data''.
Selected data is permanently replicated to the ''remote'' (offsite) location and can be restored locally or at the remote location if required. The block-based data can be migrated to tape as ''native file data''.


[[File:SEP-Cloud-RDS.jpg|900px|link=]]
[[File:SEP-Cloud-RDS.jpg|900px|link=]]</translate>
<br clear=all>
<br clear=all>


==={{anchor|scenario_2}}Scenario 2: Replicating backed up virtual machines (VMs)===
<translate>==={{anchor|scenario_2}}Scenario 2: Replicating backed up virtual machines (VMs)===


===={{anchor|VMware}}VMware====
===={{anchor|VMware}}VMware====
Line 50: Line 50:
Selected VMs are permanently replicated to the ''remote'' location and available again to the local ESX DataStore by using automated restores. The block-based data can be migrated to tape as ''native file data''. For more details on VMware, see [[Special:MyLanguage/VMware|SEP sesam VMware documentation]].
Selected VMs are permanently replicated to the ''remote'' location and available again to the local ESX DataStore by using automated restores. The block-based data can be migrated to tape as ''native file data''. For more details on VMware, see [[Special:MyLanguage/VMware|SEP sesam VMware documentation]].


[[File:SEP-Cloud-RDS-VMware.jpg|900px|link=]]
[[File:SEP-Cloud-RDS-VMware.jpg|900px|link=]]</translate>
<br clear=all>
<br clear=all>


===={{anchor|Citrix}}Citrix Hypervisor (XenServer)====
<translate>===={{anchor|Citrix}}Citrix Hypervisor (XenServer)====


Selected VMs are permanently replicated to the ''remote'' location and available again via the local Citrix Xen pool. The block-based data can be migrated to tape as ''native file data''. For more details on Citrix, see [[Special:MyLanguage/Citrix_XEN_Server|SEP sesam Citrix Hypervisor documentation]].
Selected VMs are permanently replicated to the ''remote'' location and available again via the local Citrix Xen pool. The block-based data can be migrated to tape as ''native file data''. For more details on Citrix, see [[Special:MyLanguage/Citrix_XEN_Server|SEP sesam Citrix Hypervisor documentation]].


[[File:SEP-Cloud-RDS-Citrix-XEN-Server.jpg|900px|link=]]
[[File:SEP-Cloud-RDS-Citrix-XEN-Server.jpg|900px|link=]]</translate>
<br clear=all>
<br clear=all>


==={{anchor|scenario_3}}Scenario 3: Replicating selected solutions, platforms and databases===
<translate>==={{anchor|scenario_3}}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 [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer|mounting]] the local Si3 deduplication store thus eliminating the need for restore. The block-based data can be migrated to tape as ''native file data''.
Chosen applications, such as databases (e.g., Exchange), can be continuously replicated to the ''remote'' location, where they can be accessed by [[Special:MyLanguage/Cross-Platform_Recovery_File_System_Layer|mounting]] the local Si3 deduplication store thus eliminating the need for restore. The block-based data can be migrated to tape as ''native file data''.</translate>


{{Note|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 [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring Si3 Deduplication Store]].}}
{{<translate>Note</translate>|<translate>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 [[Special:MyLanguage/4_4_3_Grolar:Configuring_Si3_Deduplication_Store|Configuring Si3 Deduplication Store]].</translate>}}


[[File:SEP-Cloud-RDS-Application.jpg|900px|link=]]
<translate>[[File:SEP-Cloud-RDS-Application.jpg|900px|link=]]</translate>
<br clear=all>
<br clear=all>


==={{anchor|scenario_4}}Scenario 4: BaaS (Backup as a Service)===
<translate>==={{anchor|scenario_4}}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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|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.
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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|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.


[[File:SEP-Cloud-RDS-BaaS.jpg|900px|link=]]
[[File:SEP-Cloud-RDS-BaaS.jpg|900px|link=]]</translate>
<br clear=all>
<br clear=all>


==See also==
<noinclude><translate>==See also==
[[Special:MyLanguage/4_4_3_Beefalo:About_Replication|About Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]] – [[Special:MyLanguage/Configuring_Migration|Configuring Migration]]
[[Special:MyLanguage/4_4_3_Beefalo:About_Replication|About Replication]] – [[Special:MyLanguage/4_4_3_Beefalo:SEP_Si3_Replication|SEP Si3 Replication]] – [[Special:MyLanguage/Configuring_Migration|Configuring Migration]]</translate></noinclude>

Revision as of 11:28, 4 February 2021

Other languages:

Template:Copyright SEP AG en

Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.


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 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 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 kept separate between the individual connected clients and is end-to-end encrypted. The SEP Cloud RDS solution supports automated migration of data to tape, reducing the cost of tape drives and loaders for the customer.

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.

Requirements

  • A secure VPN connection is required to connect to the remote location.
  • SEP sesam replication requires a special license SEP sesam Si3R Storage Pool Replication which also includes SEP Cloud RDS Server. The required licenses are already included in a volume-based license. For details, see Licensing.

Implementation examples

The following examples describe four different implementation scenarios for replicating to SEP loud RDS Server.

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. The block-based data can be migrated to tape as native file data.

SEP-Cloud-RDS.jpg

Scenario 2: Replicating backed up virtual machines (VMs)

VMware

Selected VMs are permanently replicated to the remote location and available again to the local ESX DataStore by using automated restores. 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 available again via the local Citrix Xen pool. 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: 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. The block-based data can be migrated to tape as native file data.

Information sign.png Note
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.

SEP-Cloud-RDS-Application.jpg

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.

SEP-Cloud-RDS-BaaS.jpg

See also

About ReplicationSEP Si3 ReplicationConfiguring Migration