hwmig2007cutover
Table of Contents
A checklist of stuff do do at cutover time
Before
- backup old tux one last time
- rsync to offsite locations and to new tux /old directory or spare partition
On site
- bring new tux to rgb's place
- bring old tux to runlevel 1
- bring new tux to runlevel 1
- dump the databases (listed on the TuxSoftware page) and tar up the /var/mail directory (check mailman too)
- copy the databases to new tux
- load the databases
- adjust networking on new tux (/etc/network/interfaces, /etc/hosts, /etc/resolv.conf, make bind9 runnable.)
- shut down old tux and new tux
- put new tux in old tux's place (logically speaking)
- boot up new tux
- test new tux to see if the services are running properly
- essential
- users/groups
- sudo
- networking
- ssh
- nice-to-have
- email
- apache
- phpwiki
- mailman
- if services are not running - make them run properly
- we're done (for cutover night)
- fix up remaining problems via ssh, later
Remote helper
- Test the services from remote
- networking
- ssh
- DNS
- mail
- apache
- mailman
- phpwiki
hwmig2007cutover.txt · Last modified: 2015/06/09 15:23 by 127.0.0.1