/
Backup & Recovery Brick

Backup & Recovery Brick

Univ. of Hawaii - ITS Technical Architecture - Brick   

Backup & Recovery

Primary Architect:  Steven Sakata

Description:   

This brick describes the technologies that we use to backup and recover ITS systems and files.

 

Experimental

  • Windows snapshots 
  • Zerto

Strategic (3-5 Years)

  • Core Backup & Recovery

    • Bacula Enterprise

  • File System Snapshots

    • RHEL LVM snapshots

    • VMware snapshots

  • File System Replication

    • NetApp Replication   

Tactical (1-2 Years)

  • Core Backup & Recovery

    • Open Source Bacula and Bacula Enterprise

  • File System Snapshots

    • IBM Flashcopy

    • RHEL LVM snapshots

    • VMware snapshots

  • File System Replication

    • rsync

  • Database Utilities

    • Oracle: RMAN & export

    • MySQL: mysqlbackup

    • SQL Server: SQL backup

Containment

  • Core Backup & Recovery

    • Commvault Simpana

Retirement

  • Snapshots

    • Hitachi ShadowImage

Notes

  • 4/29/15 - DBAs have determined that they have no plans on using the backup agents.  They will continue to perform DB backups to local file systems (and these file systems get backed up).

  • snapshots are currently used as temporary backups (i.e., usually during maintenances), or to get a point-in-time image that gets backed up.

  • We need to get the DBAs involved to provide their input on what tools they use to backup the databases.

  • Synthesized backups are essential for staying within a backup window for a large file system.

  • Deduplication helps minimize the amount of space needed on the backup server.

  • We currently have our backups at DR Fortress.  Is there a need to have a copy out of state?

  • We need to decide how to depict snapshotting.  What role

Emerging Trends

  • Bare Metal Backups

  • VMWare level backups

  • Cloud-based backups

 


Change History

  • Brick first created April 2015


Definitions

Experimental

Someone in ITS is currently investigating or experimenting with this technology.

Strategic

ITS will be investing in this technology for 3-5 years.

Tactical

ITS will be investing in this technology for 1-2 years.

Containment

ITS will continue to use this technology for existing systems, but will no longer invest in this technology and/or grow its use.

Retirement

ITS has a firm plan (and timeline) to retire this technology.

Related content