A service of Marietta PM

mariettapm.com

MPM Municipal Continuity Services · MPM Recovery Pod

When the building is lost, your servers run in Atlanta

Backups protect your data. The Recovery Pod puts your systems back in service. It is the recovery site included in MPM Vault DR.

What it is

Recovery capacity on MPM-VDC in Atlanta, reserved for each Vault DR agency at onboarding and sized from that agency's server inventory.

What it is for

The day your building is lost to fire, flood, a hurricane or site-wide ransomware. Your servers are restarted as virtual machines from your Vault backups.

How fast

Critical servers running within 8 hours of a declared disaster. Standard-tier servers within 48 hours.

How your staff connect

Through a private VPN into a recovery network isolated for your agency, with multi-factor authentication.

Where recovery happens

Most incidents never reach the Recovery Pod. This is where recovery happens for each kind of event, from a single file up to a regional event.

  1. A file, folder or single server fails; the building is fine

    From the local copy on your own backup hardware or Vault Edge appliance

    Vault Standard, Plus and DR · Tier recovery time (4 h Standard, 2 h Plus and DR)

  2. A file, folder or server fails, and there is no backup hardware on site

    From the Atlanta Vault, over your internet connection

    Vault Cloud · Set at the assessment, by data size and bandwidth

  3. Your local backup hardware is lost; the building is fine

    From the Atlanta Vault onto your repaired or replacement hardware

    Vault Standard, Plus and DR · Tier recovery time, plus time to obtain hardware

  4. The building is lost: fire, flood, hurricane, or ransomware across the site

    Your servers run as virtual machines on the MPM Recovery Pod in Atlanta

    Vault DR · Critical servers within 8 h; standard-tier servers within 48 h

  5. Atlanta itself is affected (a rare regional event)

    Backups restored from the Secondary Vault in Tampa onto rented compute

    All tiers' data is protected; Vault DR agencies recover first · Best effort, with no loss of backed-up data

  6. Recovery is over and your site is rebuilt

    Systems move back from the Recovery Pod to your site (failback)

    Vault DR · Scheduled with you

From declaration to failback

  1. 01

    Declare

    Your designated contact declares a disaster by phone. We confirm the recovery order you agreed in the DR runbook.

  2. 02

    Recover

    Critical servers are restored onto the Recovery Pod first, then standard-tier servers.

  3. 03

    Operate

    Your staff work on the recovered systems over the private VPN while your site is rebuilt. Backups continue.

  4. 04

    Fail back

    When your site is ready, we move systems back on a schedule agreed with you and confirm every one.

Tested every year

Vault DR includes an annual DR exercise on the Recovery Pod: we bring your critical servers up there, your staff confirm they work, and you receive a written report. The DR runbook is updated from what the exercise finds.

If a disaster needs more

If an incident needs more capacity than is reserved, we add compute during the incident in the same Atlanta facility. It is the same Recovery Pod service, scaled up, not a different product.

Which of your servers could you not be without for a day?

Get your free Recovery Readiness Self-Assessment

Free. No obligation, no purchase order, no credit card.

See assessment prices