Database Archiving for the Future

by Trevor Eddolls
June 12, 2008

• Keep data in the archive authentic
• Block unauthorized access (via a super user command or back door) that allows data to be changed
• Provide easy access and retrieval of the archived data by authorized users
• Facilitate the production of reports about the data
• Support e-discovery tools used to review and retrieve the data in the event of litigation
• Apply a policy-based system to automatically delete unwanted data.

There are available database archiving solutions that address the characteristics discussed here. One option uses standards such as Java, proven techniques such as object encapsulation, and an open platform (Linux) in an appliance-style approach that lets users define policies, create archive jobs, etc. You should carefully examine your organization’s IT infrastructure, business needs, and budget (among other important criteria), when evaluating specific products or services. Cost is always a key factor, but remember to assess how much it will cost not to comply with regulations, to cover penalties for failure to produce relevant documents in a timely manner or for deletion of required documents needed in a court case. (In the case of Serra Chevrolet vs. General Motors, court penalties were $50,000 per day for late responses to discovery requests. )

With the growth in regulation, your organization needs a database archive solution that can help your company comply with regulations and avoid or cope with legal problems. This article has identified some key features you should look for in a database archive solution that can remain viable for perhaps as long as 30 years.