|
||
|
|
|
|
|
|
|||
|
The DataGuard Data Protection Newsletter April, 2006
Bullet Points
Learning Guide: Backup Solutions Security Issues With New PayPass Payment Devices World Virus Map Learn How to Secure Your Remote Environment Limiting Downtime
Welcome! If there are any topics you would like to see discussed in the future or if you have any comments, please contact me at JoeT@HighCaliber.com
Downtime is expensive. This is why we recently implemented our new InSite Service Programs which were specifically designed to minimize downtime. Keeping downtime to a minimum requires forethought, preparation, proactivity, practice and vigilance. Here are some ideas on the subject. Changes, upgrades and patches are one of the most common causes of downtime. This includes both the planned downtime it takes to install the changes and the unplanned downtime when things go wrong. (Most security related problems occur because machines were not properly patched.) Change and patch installation is a process that needs to be standardized, documented and controlled as much as possible. This is why we offer a patch management tool with InSite. The ability to instantly restore files or to roll back a system to a recent last-known-good state is a powerful tool for minimizing downtime. While they can't replace true backups, such techniques can solve many problems, especially the most common ones. High Caliber has been implementing these systems for clients for some time now. It is important to think ahead. Creating a Business Continuity Plan that states clear data recovery objectives is a great start. Make sure you prioritize your business-critical applications and plan to restore the most important first. Setting these goals isn't just a matter for the IT department. They should be set by, and bought into by, the entire organization. This not only lets everyone know what to expect, it also makes it easier to invest in needed equipment and training to meet those goals. Remember to plan carefully. It is impossible to think of every possible contingency ahead of time, but that shouldn't stop you from trying. Monitor constantly and be proactive. The best way to limit your downtime is to catch problems before you go down. Monitor your system's performance constantly and compare current performance in critical areas to a baseline record. Pay special attention to trends. Often you can spot hardware or software problems early and fix them before they shut you down. InSite Monitoring can provide automatic warning when critical parameters exceed pre-set levels or if an operation needs a large number of re-tries. Test and drill regularly. Unfortunately, a large number of emergency restores -- something like two-thirds by some estimates -- suffer significant problems or fail entirely. Even something as simple as a misplaced (or worse, mislabeled) tape can add hours to your down time. We are offering an automatic backup across the Internet service which alleviates alot of these problems. The only way to make sure you can execute your plan is to test it constantly. At the very least, make sure your restoration procedures work by doing test restores and comparing the results with the original files. It's better to test the entire recovery procedure from beginning to end, and best to conduct regular recovery drills to make sure everything works and everyone involved is prepared. When the system is down you should never have to guess and never have to experiment. Ideally, you should have all the information you need at your fingertips, including all the required procedures to get back up. This should all be filed and cross-indexed, and you should store at least one copy in a separate location other than the original computer. You should also keep a copy of your current documentation offsite. Among the items you need are the numbers of all the current versions of software and firmware you are using, including patches, complete system configuration information and a duplicate of your tape inventory detailing what is stored on which tapes. It's also a good idea to keep lists of where recovery-related procedures are found in the documentation and current lists of phone numbers for vendor contacts.
DataGuard archives: Click Here |