Recovery-As-A-Service (Raas); Retention And Archiving - Dell DL4000 User Manual

Tape library
Hide thumbs Also See for DL4000:
Table of Contents

Advertisement

replicate to the target site. After data has been transferred to the target core, the newly replicated
incremental recovery points automatically synchronize.

Recovery-as-a-Service (RaaS)

Managed service providers (MSPs) can fully leverage the appliance as a platform for delivering recovery as
a service (RaaS). RaaS facilitates complete recovery-in-the-cloud by replicating customers' physical and
virtual servers along with their data to the service provider's cloud as virtual machines to support recovery
testing or actual recovery operations. Customers wanting to perform recovery-in-the-cloud can
configure replication on their protected machines on the local cores to an AppAssure service provider. In
the event of a disaster, the MSPs can instantly spin-up virtual machines for the customer.
MSPs can deploy multi-tenant AppAssure RaaS infrastructure that can host multiple and discrete
organizations or business units (the tenants) that ordinarily do not share security or data on a single server
or a group of servers. The data of each tenant is isolated and secure from other tenants and the service
provider.

Retention and archiving

In your appliance, backup and retention policies are flexible and, therefore, easily configurable. The ability
to tailor retention polices to the needs of an organization not only helps to meet compliance
requirements, but does so without compromising on RTO.
Retention policies enforce the periods of time in which backups are stored on short-term (fast and
expensive) media. Sometimes certain business and technical requirements mandate extended retention
of these backups, but use of fast storage is cost prohibitive. Therefore, this requirement creates a need
for long-term (slow and cheap) storage. Businesses often use long-term storage for archiving both
compliance and non-compliance data. The archive feature supports extended retentions for compliance
and non-compliance data, it can also be used for seeding replication data to a target core.
Figure 6. Custom retention policy
In your appliance, retention policies can be customized to specify the length of time a backup recovery
point is maintained. As the age of the recovery points approaches the end of their retention period, the
recovery points age out and are removed from the retention pool. Typically, this process becomes
inefficient and eventually fails as the amount of data and the period of retention start grows rapidly. Your
19

Advertisement

Table of Contents
loading

Table of Contents