Real World Disaster Recovery Scenarios

This page is designed to give realistic examples of recovering your data when using one of the backup services we provide.

We are assuming you arrive at the office to find your server, and all your data, is gone. It does not matter if it is the result of theft, damage caused by old age, natural disaster or malicious destruction. All of your data is now missing. We are going to assume that several workstations have been damaged at the same time.

The first task in accessing your data is to contact Daily Data. In many cases, we can provide a temporary “loaner” machines and begin work on setting it up for you. This will also alert us to the need to react rapidly as access to your data is needed while your machine(s) are replaced.

The time it takes to “be functional” depends on which backup service you use, from around an hour for Server Replication to several days for the off-site backup service (though access to a limited number of files during the recovery process is available in all scenarios).

Server Replication Scenario

During the process of setting up your replicated server, we would have determined how to access the replica when needed. Here, we’ll assume you have a site-to-site vpn connection between your office and the remote site which contains the replica server.

Time Estimate: 1 hour

Recovery Cost: Cost of replacement server. Cost to replicate the data back to new server is included in service.

  1. Daily Data logs into the remote server
    1. Determine if a backup completed between the last time changes were made on the server and the time the disaster occurred. Report results to client.
    2. Modify the configuration on the replica server, turning it into the primary server.
    3. E-mail/phone/visit on site instructions on accessing the replica server, if necessary.
  2. Clients log into replica server
    1. Validate state of files modified the previous day if replication did not complete prior to loss
    2. Begin work
  3. Determine if “Road Warrior” access to the replica server is required (ie, people working from home or alternate office). If so, set up “Road Warrior” access for those employees.
  4. Replace lost equipment
    1. Purchase equipment
    2. Configure, using configurations stored on remote server
    3. Copy data from replica server to new primary
    4. Workers access primary server

Note that in this scenario, if desired the replica server could be physically moved from its remote location to the office, becoming the primary machine.

Owncloud File Synchronization Scenario

Time Estimate: Determined by the amount of data to be recovered and the network speed. From a few hours to a few days.

Recovery Cost: Cost of replacement machine

  1. Replace lost device
  2. Install Owncloud client, configuring to replicate to your Owncloud account
  3. Wait for file synchronization to complete

During this process, your data files are available to any machine you can use to log into the web based interface.

Off-site Backup Services Scenario

Time Estimate: 2-5 days

Recovery Cost: Price of replacement server plus hard disk if that option is chosen. Labor to copy the data is included in the service.

  1. Replace lost server
    1. Configure server based on data stored on backups
    2. Copy data from backup service to new server using one of the following procedures
      1. Hand carry new server to our Network Operations Center (NOC) and copy most recent backup to it OR,
      2. Purchase an appropriately sized drive, carry to NOC, copy the most recent backup, return the drive to your office, copy data from the drive to the new server OR,
      3. Initiate a copy from our backup server to your new server over the Internet. This scenario is only viable for smaller data stores (less than 5 gigabytes, depending on your network speed), and also is a security risk for your network.

During this procedure, Daily Data can copy a limited number of important files and make them available to you so some limited business can continue. Also, Daily Data will make available a “loaner” server (if available) while the new server is ordered and configured.