Skip to main content
(844) 422-7000

Mount Pleasant managed IT

Disaster recovery for coastal businesses

Decide which systems come back first, maintain offsite copies, and rehearse restores on a schedule so the business knows exactly how long a real recovery takes.

IT disaster recovery services

Plans for losing a site or its systems

Internet backup and battery backup keep a site running through short outages. A disaster recovery plan covers losing the site or its systems entirely.

  1. 1

    Decide what comes back first

    Each system gets targets dictating how long you can be without it and how much recent work you can afford to lose.

  2. 2

    Keep copies somewhere else

    Recovery runs cloud to cloud on Microsoft Azure, so a business can be brought back up somewhere other than its own office.

  3. 3

    Rehearse the recovery

    Restores are performed on a schedule and the elapsed time is recorded. A backup job reporting success shows only that a copy was written.

Plans built for specific business requirements

Professional offices, clinics and trades operate on different software and schedules. Every business decides a recovery order based on its own calendars and records.

Select a business type

Example recovery order

    Preparations for hurricane season

    Atlantic hurricane season runs from June 1 to November 30. National Hurricane Center tracking shows most activity between mid-August and mid-October, peaking around September 10.

    Dates: National Hurricane Center.

    Targets set for each system

    Work starts by deciding with the business which systems must come back first. Targets dictate how long you can be without it and how much recent work you can afford to lose.

    Recovery time objective

    NIST definition outlines how long a system's components can be in recovery before an outage seriously harms business operations.

    Recovery point objective

    Measured as time since the last good backup, defining how much recent work you can afford to lose.

    Azure Site Recovery portal page for a replicated server: Replication Health Healthy, Status Protected, RPO 2 mins, with the Failover and Test Failover buttons in the toolbar
    Protected server showing replication health, status and RPO, with Failover and Test Failover buttons.
    Azure Site Recovery Failover pane with the failover direction, a recovery point chooser set to latest processed, and a checkbox to shut down the machine before failover
    Failover pane displaying a choice of recovery point, such as the latest processed.

    Microsoft Learn, Azure Site Recovery tutorial.

    Scheduled tests find hidden gaps

    Recovery is rehearsed so the business knows how long a real recovery will take before it needs one. Rehearsing a recovery finds gaps a written plan hides.

    Rehearsal findingsExample
    Missing license key
    Software installations require valid license keys to activate on replacement hardware.
    Unknown admin password
    Administrative access was restricted by an admin password only one person knew.
    Missing vendor phone number
    Support requests were delayed by a missing vendor phone number.
    Corrected recovery order
    Written order was corrected after the first run revealed a system that had to come back before another.
    Findings are an example
    A woman in a cream cardigan works at her desktop computer in the bright front office of a Mount Pleasant accounting firm, smiling, while a grey-haired engineer in a light blue shirt stands beside her; a live oak with Spanish moss and a wet sidewalk outside the large window

    Protected layers and applications

    Lists of protected systems, with schedule and retention, are written down and reviewed as systems change.

    Software

    How it is protected

    Brings back

    Plans required by frameworks

    Guidelines and regulations mandate documented preparation for business continuity.

    HIPAA for medical practices

    Medical practices must have a disaster recovery plan and an emergency mode operation plan, and test and revise them.

    FTC Safeguards Rule

    Covered financial businesses keep a written incident response plan covering roles, communications, remediation and review.

    CISA recommendations

    Maintain offline, encrypted backups and test them. Keep updated golden images and spare hardware. Restore critical services first.

    Ready.gov business continuity

    Business continuity planning involves forming a continuity team, writing a plan, and testing it. Testing concludes the six steps.

    Disaster recovery questions

    Call to build a plan

    Book a walkthrough or call (844) 422-7000 to begin.

    CharlestonMount PleasantNorth CharlestonIsle of PalmsFolly BeachKiawahBeaufortBlufftonHilton HeadSavannah
    Call (844) 422-7000
    CloudCentric · Mount Pleasant, SC · serving Charleston and the Lowcountry(844) 422-7000