Almost everybody agrees that backups are crucially important, but few organizations are able to invest the time and resources into making them happen. And that’s not a problem until you need to get back lost data. At which point, of course, it’s too late.
The first step in any backup project is to specify what is and is not included. Critical application data is a given. But what about the contents of user desktops? Should they be using shared drives for storage? In the event of a server loss, should we plan for a re-install or a bare metal recovery? Knowing what it means to have a backup is the place to begin.
Frequency and Retention
Next is to decide how often backups should occur, and how long data should be saved. For some operations, once a month is fine. For others, backups should be constant. And the length of time to hold onto information varies by industry and application. Talk with your team and your stakeholders to answer these key questions.
Implementation and Drills
When it’s time to build a backup strategy, the final step is not just setting up the jobs, but testing the recovery. Backup drills should be done frequently, identifying a target file or system and conducting a sample recovery. This will identify holes in your system and provide a path for what to do next.
Need help building your backups? Contact SineWave today.