[281] in Enterprise Print Delivery Team
ASPCC Bullets for Jim Bruce
daemon@ATHENA.MIT.EDU (David F. Lambert)
Fri Jun 9 17:53:40 2000
Message-Id: <10006092153.AA25103@MIT.EDU>
Date: Fri, 09 Jun 00 17:51:47 EDT
From: "David F. Lambert" <LAMBERT@MITVMA.MIT.Edu>
To: Backup Team <backup-t@mitvma.MIT.EDU>,
Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
Backup & Print Teams,
Below you'll find the bullets I provided to Jim at his request in
prep for the ASPCC meeting with Curry on the 21st. Sorry there
was no time for you to review it first...
-Dave
ENTERPRISE BACKUP (Administrative Server Backup Project)
The Teams:
Discovery: Dave Kalenderian, Pete Kelley, Dave Lambert (project
leader), Fran McLaughlin, Sebastien Sabre & Grant Young representing
four different standing I/T Service Teams
Delivery: Jody Housman, Pete Kelley, Fran McLaughlin, Sebastien Sabre,
Rachel Sage (project leader) & Grant Young representing three
different standing I/T Services Teams
Charter:
The existing model for providing backup services does not scale
to the increasing storage requirements of the administrative
applications. There also exists a greater demand for higher
availability systems. The project teams are chartered to develop
an architecture and implement a new backup service to address
these needs.
The initial rollout will be targeted for use by SAP. The new backup
service will then be rolled out to the other servers as those servers
are renewed. The same rollout model will be used to bring the
non-SAP servers into the new Storage Area Network (SAN) and Enterprise
Storage infrastructure. The project did not include replacing
the current desktop backup service provided by IS.
The Current Model:
- storage is directly attached to the server
- tape drive(s) is/are directly attached to the server
- systems are shutdown to obtain consistent data backup
- MIT written programs run on each server to move data from disk to tape
- backup tapes are mounted manually
- backup tapes are moved offsite each morning
The New Model:
- utilizes Automated Tape Libraries (ATLs)
- shared Enterprise Storage is connected to servers via high speed switches
- ATL tape drives are shared via high speed switches
- commercial software (Veritas) will run on two backup servers using a
three tiered architecture
- utilizes "live" online backup techniques to minimize application downtime
- when the fiber is available on campus, data will be backed up
to remote ATLs in real time
Justification:
- the current model does not scale to the current environment; data center
storage increased from ~2.5TB to 7.5TB with the SAP 4.5b upgrade;
Gartner predicts a doubling of storage annually
- the current model does not address the current business requirements
for higher availability systems and is not flexible
- improves efficient utilization of administrative I/T assets; the
current model does not share tape drives; more than $1M in tape drives
would be required in the current model
- takes full advantage of Oracle and SAP ability to perform "live" backups
- moves MIT into automated tape systems allowing for human resources
to be more fully utilized in other ways
- more fully utilizes the newly installed Storage Area Network
- provides a global backup solution for all administrative servers
in keeping with the ASAP/ASOP model
- takes full advantage of our campus environment with remote real time backups
replacing movement by vehicles
Timeline:
7/1/2000 discovery project ends
10/1/2000 all SAP systems completed
10/1/2001 remote backup using new Single Mode Fiber
7/1/2004 all administrative servers are using the new model
Funding:
The ATLs were acquired at the time the SAP 4.5b storage was purchased.
Funding for the software and remaining hardware was budgeted as part
of the SAP 4.5b upgrade.
ENTERPRISE PRINTING (Centralized Printing Services)
Who:
The delivery team membership is Kip Bruggeman, Mary Ellen Bushnell,
Rocklyn Clarke, Lynne Durland, Dave Lambert and Cecilia Talamantes
Charter:
Implement a new centralized printing system to manage print queues
and printers based on the recommendations of the discovery project.
The current central printing services are provided by the IBM
mainframe. Most applications have migrated off the mainframe.
Justification:
- the mainframe is being phased out
- simplify the ability to move print files from application servers to
the print management system
- the mainframe printing services do not support Postscript files; CAO
requires large volume Postscript printing services
Solution:
- implement IBM's InfoPrint Manager
- support network attached printers in a heterogeneous environment
- utilize existing I/T assets across the legacy and new server
environments more efficiently and cost effectively
Timeline:
7/1/2000 finalize hardware and software configurations
8/1/2000 rollout initial service
9/1/2000 rollout large volume Postscript service
Funding:
Funding will be provided from the existing ASAP and ASOP budgets.
