Indeed, such failover to another geography can incur additional downtime impacting other systems that weren’t impacted by the initial catastrophe. These pointed disasters that affect only a portion of the larger environment and aren’t something requiring a failover to another geography. Note that these high-frequency events are not caused by a widespread catastrophe, thus the data center location infrastructure still exists and has remained available. All of these are common disasters that require restoration from backup. Then there is the intentional disaster caused by someone vandalizing the server. Operating system and application upgrades to a server can also go awry and require that a server be “rewound” to just before the upgrade. Users can inadvertently delete or otherwise mangle an individual file. Anecdotally, however, we know human-caused errors are generally behind the majority restores. Unfortunately, there isn’t a Bureau of Backup Statistics to do root-cause analysis and tell us how often restores occur and why. In what context do organizations use backup restores? It’s always good to keep this question in mind when considering the importance of operational backups.
Backups Protect Against Operational (Not System-Wide) Disasters
#Data backup policy how to
Finally, I’ll share how to keep your policy documentation as simple and user-friendly as possible. In this post, I’ll walk through the importance of operational backups as part of any IT business continuity plan, as well the considerations you’ll have to make before determining the frequency and retention policies best suited to your organization. Requirements vary from business to business depending on a range of operational, business and regulatory needs. Quite often, we get a response that says, “Do whatever is customary.” However, there is no “customary” set of backup policy rules.
How often to back up data and how long to retain those backups are questions that we ask of all prospects and customers.
0 kommentar(er)
