Quest CEO Blog | Recovery

 

Quest CEO Blog

Thoughts on Technology, Business and the Management of Both.

 

Data backup/recovery best practice #10

by Tim Burke
Tuesday, December 13, 2011
Picture of hard drive and stethoscope.

 

This last of my backup/recovery best practices is far from the least of them:

 

#10 Conduct regular testing and reviews of your data recovery capabilities 

 

Backups can be corrupted (especially if they’re tape-based) and too often backups are performed incorrectly. Key files, directories, or components may have been excluded, especially if your infrastructure has undergone adds or deletes.

 

More...

Permalink | Comments (0)

Data backup/recovery best practices #3, #4, and #5

by Tim Burke
Tuesday, December 06, 2011
Ambulance parked on a hard drive

Last time, I described the first two backup/recovery best practices. Here are the next three:

 

#3 Make sure your backup/recovery strategy adheres to all governance and compliance rules that apply to your organization.

Rules abound about data privacy, security, retention — and vary by industry and region.

Look for a reputable advisor who has the experience needed to understand your compliance environment and who successfully completes SAS-70 Type II audits.

 

More...

Permalink | Comments (0)

Backup/recovery best practices #1 and #2

by Tim Burke
Thursday, December 01, 2011
keyboard and tech background.

As I see it, there are 10 best practices that can make the difference between backups that really do keep you in business and backups that seem to work okay — until you actually try to use them. Here are the first two:

 

#1 Understand your data so you can decide what needs to be backed up and how often. 


Base your decisions on the cost of loss, which you can get a sense of by noting the types of data your business relies on — emails, spreadsheets, databases, line-of-business apps, etc. — and determining the impact of losing that information for good and having to recreate it (if you can). Add in the cost of unhappy customers and potential regulatory/compliance violations — and do the math.

 

More...

Permalink | Comments (0)