Security

Disaster Recovery Plan Policy

Security

Disaster Recovery Plan Policy

Security

Disaster Recovery Plan Policy

Disaster Recovery Plan Policy

Overview

The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLE GROUP S.A. (“we” or “Cloudback”). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service is considered.

Purpose

This policy defines the requirement for a baseline disaster recovery plan to be developed and implemented by Cloudback that will describe the process to recover IT Systems, Applications and Data from any type of disaster that causes a major outage.

Scope

This policy is directed to the Cloudback’s Support Team which is accountable to ensure the plan is developed, tested, and kept up-to-date. This policy is solely to state the requirement to have a disaster recovery plan, it does not provide requirements around what goes into the plan or subplans.

Policy

Contingency Plans

The following contingency plans will be created if required:

  • Computer Emergency Response Plan: Who is to be contacted, when, and how? What immediate actions must be taken in the event of certain occurrences?

  • Succession Plan: Describe the flow of responsibility when normal staff is unavailable to perform their duties.

  • Data Study: Detail the data stored on the systems, its criticality, and its confidentiality.

  • Criticality of Service List: List all the services provided and their order of importance.

  • It also explains the order of recovery in both short-term and long-term timeframes.

  • Data Backup and Restoration Plan: Detail which data is backed up, the media to which it is saved, where that media is stored, and how often the backup is done. It should also describe how that data could be recovered.

  • Equipment Replacement Plan: Describe what equipment is required to begin to provide services, list the order in which it is necessary, and note where to purchase the equipment.

  • Mass Media Management: Who is in charge of giving information to the mass media?

  • Also, provide some guidelines on what data is appropriate to be provided.

After creating the plans, it is important to practice them to the extent possible. The time will be set to test the implementation of the disaster recovery plan. Table top exercises should be conducted annually. During these tests, issues that may cause the plan to fail can be discovered and corrected in an environment that has few consequences.
The plan, at a minimum, should be reviewed an updated on an annual basis.

Policy Compliance

Compliance Measurement

The Cloudback’s Support Team will verify compliance to this policy through various methods, including but not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner.

Exceptions

Any exception to the policy must be approved by the Cloudback’s Support Team in advance.

Non-Compliance

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment.

  • GitHub

    Repository

    Backup

    Restore

    Organization

    Issues

    Labels

    Milestones

    LFS

    Metadata

    Storage

  • Storage

    Metadata

    LFS

    Milestones

    Labels

    Issues

    Organization

    Restore

    Backup

    Repository

    GitHub

  • Issues

    Labels

    Milestones

    LFS

    Metadata

    GitHub

    Repository

    Backup

    Restore

    Organization

  • LFS

    Metadata

    GitHub

    Repository

    Backup

    Restore

    Organization

    Issues

    Labels

    Milestones

The reliable way to back up GitHub repositories

1.4k+

happy customers

8k+

repositories secured

1.8m+

backups created


  • GitHub

    Repository

    Backup

    Restore

    Organization

    Issues

    Labels

    Milestones

    LFS

    Metadata

    Storage

  • Storage

    Metadata

    LFS

    Milestones

    Labels

    Issues

    Organization

    Restore

    Backup

    Repository

    GitHub

  • Issues

    Labels

    Milestones

    LFS

    Metadata

    GitHub

    Repository

    Backup

    Restore

    Organization

  • LFS

    Metadata

    GitHub

    Repository

    Backup

    Restore

    Organization

    Issues

    Labels

    Milestones

The reliable way to back up GitHub repositories

1.4k+

happy customers

8k+

repositories secured

1.8m+

backups created


The reliable way to back up GitHub repositories

1.4k+

happy customers

8k+

repositories secured

1.8m+

backups created


Automatic daily backups and instant restores of your GitHub repositories, metadata, and even LFS. Backup to any storage you want.

Automatic daily backups and instant restores of your GitHub repositories, metadata, and even LFS. Backup to any storage you want.

Automatic daily backups and instant restores of your GitHub repositories, metadata, and even LFS. Backup to any storage you want.