3. Critical updates, could impact public safety. No more than 15 minutes of downtime. 3 databases 2 were updated on a regular basis 1 was updated once a week Total size was 300 GB Using SQL Litespeed for compression Database Maintenance was limited to backups (No Re-indexing to speak of) Outages are extremely hard to come by. Full Backups taken every Sunday, Diffs taken every night, T-Logs every 20 min.
56. Downtime Timeline Downtime ends Downtime starts Conn stringchanges DBs RW2008 DBsRO2000/2005 Backup log Stop allapps Start all apps Restore log Q: Can we do it in one step and faster?
114. Actual Migration On 2008 Instance 4. Restore last logs with no recovery 5. Check if all the logs were restored from the old server 6. Restore with recovery for all databases 7. Set all databases to read-write 8. Fix orphan logins 9. Change compatibility to 100
115. Actual Migration Changing Instance Identification 10. Take offline the old instance group Take offline the new instance group Delete the old and the new virtual IP and name DNS records from the DNS server
116. Actual Migration Changing Instance Identification Clear the DNS server’s cache Give the new server the old server’s virtual IP & name 15. Flush DNS cache clients of new server, Arpcache 16. Start the new instance group
117. Post-Migration Perform Sanity Checks Check NOC Alerts 3. Check SSIS, MSDTC and Job statuses 4. Run a Profiler’s Error Trace 5. Check SQL Error Log & Event Log 6. Check Performance Baseline 7. Run Full Backups
