Integrated Serverless Backup: Recent Beta Test Results

1
Integrated Serverless Backup Recent Beta Test
Results

• Russ AllenData Management CoordinatorMercy
  Medical Center, Cedar Rapids, Iowa

2
Current SAN Environment at Mercy Medical Center
3
SAN Backup Strategy for Meditech Servers

• Seven 64GB Magic OSAL servers attached to SAN
• Three FULL backups per server per day
• 600 a.m., 400 p.m.
• Backup to virtual tape drive disk array on SAN
  unit
• 830 p.m.
• Backup to tape vault at remote site
• Completion time lt 4 hours

4
Disaster Recovery Scenario 1

• Single primary Meditech OSAL server fails, SAN
  intact
• Bring up offsite hot spare OSAL server
• Attach to SAN volume belonging to failed live
  server
• 10-15 minute downtime

5
Disaster RecoveryScenario 2

• All primary Meditech OSAL servers and SAN fail
  (i.e. due to fire)
• Restore SAN backup tapes to SCSI-attached storage
  on offsite servers
• Route clients through redundant communication
  path
• Several hours downtime

6
Ideal Meditech SAN Environment

• Mirrored SAN
• Offsite location, preferably different geographic
  location
• Connected to primary SAN by redundant fiber and
  switches
• One hot spare OSAL server for each live OSAL
  server
• Offsite location, redundant connections

7
Disaster Recovery Scenario 3 (Ideal Environment)

• All primary OSAL servers and primary SAN fail,
  all offsite OSAL servers and offsite SAN intact
• Change to redundant communication path
• Continue business using offsite hardware
• Very little downtime

8
Thank You