Upload
jacob-dobson
View
229
Download
3
Tags:
Embed Size (px)
Citation preview
Managing a Successful Managing a Successful UpgradeUpgrade
Jonathan Field
OrOr
“The Ten Upgrade “The Ten Upgrade Commandments”Commandments”
OrOr
“Sermon on the “Sermon on the Boat”Boat”
Why are you upgrading?Why are you upgrading?
Software Fix New Functionality Support for old
version is going
Unicorn VersionsUnicorn Versions
(98.x) 99.4 2000 2001 (2002) 2003
Fairly up to date!
Current Very Current! BETA Tester
Fantasy!!History!
Project PlanningProject Planning
Part of an overall SIRSI project (e.g.
migration, WebCat etc.) Customer Project
– Key action points– Who is actioned?
TimingTiming How frequently do
you want to upgrade?– bi-annually– annually
– never if I can help it! Convenience for all
– are SIRSI available?– down-time
ResponsibilitiesResponsibilities Who do you need?
– SIRSI?– Library staff?– IT staff?– End-users?– Contractors?
ResponsibilitiesResponsibilities Who’s managing it? Who’s organising
backups (and restores)?
Who’s doing the upgrade?
Who’s roling out new software?
ResponsibilitiesResponsibilities Who’s copying the live
to the test server? Who’s training/being
trained? Who’s getting the
documentation? Who’s getting the
software?
DocumentationDocumentation User Group letter (upgrade
notification)
Release Notes (for each version)
FAQs Multimedia
Tour/Seminars Known issues www.sirsi.com (you have got
your password haven’t you?)
TrainingTraining
Pre-upgrade training Post-upgrade training Staff/end-user
BackupsBackups
5 things to check
BackupsBackups
Who’s doing the backup
Who’s doing the restore!
Verified? Completed with
services down?
The Upgrade ProcessThe Upgrade Process Software Delivery
Service SIRSI vs DIY NT Upgrades Custom
reports/utilities
The Upgrade ProcessThe Upgrade Process SIRSI vs DIY
– SIRSI• need a consultant• need to book a time
– DIY• ensure someone will be around• think about getting the software• think about getting advice
The Upgrade ProcessThe Upgrade Process NT Upgrades
– Read the instructions completely prior to the upgrade
– Do not upgrade OS to Windows 2000– Services (including InetPub in
manual– re-boot server– Do NOT stop the upgrade– 5100 available in firewall?– Do NOT upgrade if you have been
having hardware problems– Disable any Anti-Virus
The Upgrade ProcessThe Upgrade Process Custom
Reports/Utilities– Test on test server first if
possible– Run it prior to the upgrade– Let SIRSI know beforehand if it
is critical to your operations
Post Upgrade ProcessPost Upgrade Process Who do you contact?
– Upgrade Consultant?– Helpdesk
Test ServersTest Servers Why do you want
one?– Test custom work– BETA test– Training
ConclusionConclusion No upgrade is ever
trouble-free (well - almost never!)
Can range from:- Few Problems
Disaster!
Questions?Questions?
Managing a Successful Managing a Successful UpgradeUpgrade
Jonathan Field