This negates the need for constant whole disk copies when servers are updated/altered.

Map Branches

• Method 1 DISK COPIES DATA COPIES
  • Easy recovery for local recovery from OS disk failure.
    • Proven and successful
  • Data Copy
    • At any time system files etc change.
      • Mount copy disk and copy changed files to copy disk No need to constantly take the service down to copy disks.
      • This negates the need for constant whole disk copies when servers are updated/altered.
      • This should be scripted as a cron job.
      • Tar up directory structures / mount backup drive and untar
      • Do sector/size count to make sure backups and source are consistent.
  • Disk Copy
    • Annually
    • Only completed when Enterprise is in failover status.
• Method 2 SYBASE DUMPS
  • Fast recovery for DR (Disaster Recovery)
    • Need to recover quickly to support all customers needing DNS changes for DR
    • Current remote builds are configured to use either data-center.
      • Need to check new appliance set up?
  • Sybase Dumps
    • Take the sybase dumps and ftp them to Enterprise Server_2
      • Cron jobs running for dump and reload.
      • Every two hours.
    • Load sybase dumps into failover, Enterprise Server_2
    • Report on on the success/failure of the sybase load.
• Method 3 TAPE BACKUPS
  • Selective recovery from remote tape or disk store.
    • Allows for selective recovery of files or directories.
      • Tony to make additions or changes.
  • Tape Backups.
    • Take full backup of Enterprise_1
    • Take incremental backups from Enterprise_1
    • Periodical checks of tape media and recovery ability.
  • What is the cost involved?
• EXTRAS
  • Process to make sure backup QIP services are off line.
  • Norad to check database state on failover
• Enterprise Class backup requirement's.
  • KEY CHECKING PROCESSES
  • KEY BACKUP METHOD and QUESTIONS

Comments