Copyright 2004-2007 David Russell
We all understand the importance of a backup.
Not quite as obvious is that operating system administrators do not necessarily know the proper state of the database for backups, nor do they necessarily distinguish between brands. Perhaps they've done it once for MySQL and it was fine (it isn't always), they may try the same method for MS SQL Server, or Sybase.
Administrators like "mirror images". Some operational databases may restore, perhaps depending on activity, or components and options installed. Or it might be possible to get an image running on a dedicated machine and extract the pieces you need to make production work. Perhaps. Perhaps not. When you mirror an operational database you capture a state; not necessarily a consistent state.
Restore your backups. Using a very small segment of the market as my history, I say that 90% of all backups do NOT restore the first time. How about YOUR backups? Have they been restored? Are you sure?
Once there is no development taking place, if you haven't done so already, you should look for your documentation and actually determine whether it contains sufficient depth to be useful in fifteen years. In the area of database this would mean that you should retain a database administrator (DBA) to help you understand your system and document that it works, or provide documentation where it's missing.
If you are looking for a DBA please see my page on "How to Hire a Junior DBA".
Are you ultimately responsible for the database?
Bring me in to review and test this or any other component of your environment.
Last Revised: April 2007