If you suffer a data loss due to an onsite catastrophe, like a flood or fire, chances are your onsite backup will perish along with your database. While onsite backups can be handy, they shouldn’t be relied on solely. Discuss internally whether this archive should go back 30, 60, 90 days or another retention length. If a problem were to arise with a newer backup, having the archive allows you to restore to the next healthy backup before the corrupted one. An archive of older backups is a fall back plan for potentially corrupted, recent backups. Storage of older backupsīefore you plan your backup strategy, decide how far back your company would wish to recover data in the wake of a loss event. This will give you the ability to immediately restore your backup to another server and will cut out downtime. Rather than storing your backup on a local drive, which may be unavailable, backup to a network share. Onsite backupsĬreating an onsite backup of your database can get you back to work quickly if your server crashes. As you create your strategy, keep these 10 elements in mind. A good database backup strategy should have three objectives: comprehensive backup, quick backups, and speedy restores. Without the proper database backup strategy in place, your company could suffer massive amounts of downtime, contributing to lost profits, and unhappy customers. When databases crash the impact on your company can be devastating.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |