- Microsoft SharePoint 2013 Disaster Recovery Guide
- Peter Ward Peter Abreu Pavlo Andrushkiw
- 181字
- 2021-04-02 10:27:56
Thinking of interruptions and not disasters
Most people think of disaster recovery as a plan that is in place in case of a disaster, such as:
- Weather related events, such as floods, tornadoes, hurricanes, and forest/brush fires
- Earthquakes
Any of these disasters can disable your primary datacentre and you would have to failover to your DR datacentre. However, most application interruptions are due to more mundane everyday occurrences, such as:
- Facility fires
- Fiber or communication lines are cut – loss of network
- Power failures – outage or sporadic service
- Cut power line
- Security breach – hacking and/or malicious code
- Water pipe breaks in a facility
- Human error, such as a redundant system's failure that goes unnoticed
These interruptions can cripple a business if the business does not have a proper DR plan in place.
Another dimension to this point is covered in Chapter 8, Disaster Recovery Techniques for End Users. Think of who is interrupted: sales force, trading floor, executives, or end users.
This may seem like a trivial point, but IT has only so much manpower to dedicate to issues.
推薦閱讀
- Vue.js設計與實現
- Hands-On Image Processing with Python
- INSTANT Weka How-to
- OpenShift在企業中的實踐：PaaS DevOps微服務（第2版）
- Julia高性能科學計算（第2版）
- HTML5權威指南
- 零代碼實戰：企業級應用搭建與案例詳解
- Fastdata Processing with Spark
- Scala Functional Programming Patterns
- 3D Printing Designs：The Sun Puzzle
- Python趣味創意編程
- R語言數據分析從入門到實戰
- Learning Apache Thrift
- ASP.NET Core 2 High Performance（Second Edition）
- Python程序設計