云环境下数据保护与可用性保障策略

需积分: 10 52 浏览量更新于2024-07-19 收藏 6.44MB PDF 举报

《数据保护确保数据可用性》是一本由CRC Press和Taylor & Francis Group出版的专业书籍，重点关注在当今数字化时代中的数据备份、保护和归档策略。这本书旨在提供关于如何设计有效数据保护系统以确保数据始终可访问的关键信息，特别是在云计算环境中，这是一个越来越重要的议题。在现代企业中，数据是核心资产，因此数据可用性至关重要。作者深入探讨了数据保护的方法和技术，包括但不限于： 1. **数据备份策略**：本书详细阐述了定期备份的重要性，以及不同类型的备份（如全量备份、增量备份和差异备份）之间的区别，以及如何选择最适合组织需求的备份方案。 2. **灾备和冗余**：介绍了如何通过设置灾备系统来防止数据丢失，以及如何利用冗余存储技术（如RAID）提高数据安全性。 3. **加密与隐私保护**：讲解了数据加密在保障数据隐私和安全传输中的作用，以及如何选择适合的加密算法和技术。 4. **合规性和法规遵从**：针对不同的法规要求（如GDPR、HIPAA等），讲述了如何确保数据处理符合法规，以避免法律风险。 5. **云环境下的数据保护**：着重讨论了云服务商提供的数据保护措施，如多区域复制、数据主权、访问控制和安全服务，以及如何在云环境下实施有效的数据管理。 6. **灾难恢复计划**：书中还涉及如何制定和执行灾难恢复计划，确保在突发情况下能够快速恢复数据，减少业务中断。 7. **持续监控和风险管理**：强调了实时监控数据健康状况和定期进行风险评估的重要性，以便及时发现并解决潜在威胁。 8. **技术更新与趋势**：书中紧跟行业动态，分析最新的数据保护技术和趋势，如区块链、AI在安全领域的应用等，帮助读者适应不断变化的技术环境。《数据保护确保数据可用性》是一本实用指南，为IT专业人士提供了全面的数据保护框架和实战建议，帮助他们在复杂的信息环境中保持数据的安全和可访问性。无论是组织内部的数据管理还是应对外部环境挑战，这本书都是不可或缺的参考资源。

xvContents

21.6.3 Provide an Estimate of How Long the Recovery

Will Take .................................................................. 355

21.6.4 Provide Updates during Recoveries ......................... 355

21.6.5 Don’t Assume a Recovery Can Be Done

If It Hasn’t Been Tested ............................................ 356

21.6.6 Run Recoveries from Sessions That Can Be

Disconnected from/Reconnected To ........................ 356

21.6.7 Know the Post-Recovery Conguration Changes .... 357

21.6.8 Remember Quantum Physics ................................... 357

21.6.9 Be Patient ................................................................. 357

21.6.10 Document the Current Status of the Recovery ........ 358

21.6.11 Note Errors, and What Led to Them........................ 358

21.6.12 Don’t Assume the Recovery Is an Exam .................. 358

21.6.13 Ensure the Recovery Is Performed

by Those Trained to Do It ........................................ 359

21.6.14 Write a Post-Recovery Report .................................. 359

21.6.15 Update Incorrect Instructions ................................... 359

21.6.16 Considerations Specic to Tape ...............................360

21.7 Disaster Recovery Considerations ......................................... 361

21.7.1 Maintenance Backups .............................................. 361

21.7.2 Avoid Upgrades ........................................................ 361

21.7.3 Read the Documentation Before Backups

ArePerformed .......................................................... 361

21.7.4 Disaster Recoveries Must Be Run

by Administrators ..................................................... 362

21.7.5 Use Compatible Infrastructure ................................. 362

21.7.6 Know the System Dependencies .............................. 362

21.7.7 Keep Accurate System Documentation .................... 363

21.7.8 Do You Know Where Your Licenses

Are at1am? ............................................................ 363

21.7.9 Disaster Recovery Exercises .................................... 363

21.8 Protecting the Protection Environment .................................364

21.9 Historical Considerations and Data Migration ......................366

21.10 Isolated Recovery Sites .......................................................... 367

21.11 Summary ............................................................................... 369

Chapter 22 Choosing Protection Infrastructure .................................................. 371

22.1 Introduction ........................................................................... 371

22.2 It’s Never About the Technology ........................................... 371

22.3 It’s Always About the Technology ......................................... 372

22.4 Coverage ................................................................................ 372

22.4.1 Value Products That Value Protection ..................... 372

22.4.2 Value Frameworks Over Monoliths ......................... 373

22.4.3 Don’t Assume ........................................................... 374

22.4.4 Functionality Checklist ............................................ 375

xix

Acknowledgments

Every book is an amalgam of ideas and feedback, and that’s before you start to

consider all the long-term background learning that goes into the foundation con-

cepts. There’s also the inevitable lost time with friends and family that comes from

investing so much of yourself into a long-term creative project. So inevitably there’s

a host of people who specically need to be called out in gratitude and thanks for

their help in bringing this book to completion.

First and foremost, I have to thank my partner, Daz Woolley, for always being

there for me—not only while I’ve been working on the book, but also throughout

my career. He’s been my continuously available backup, and every other pun you can

think of for data protection for nigh on 20 years.

My parents put me on an IT path when I was relatively young, and actively encour-

aged me in my interests as I was growing up, culminating in funding university for

me, letting me concentrate on my study throughout my time there. Lynne and Peter,

I can never repay what you did for me all those years ago.

The book wouldn’t have happened without the suggestion, feedback, encourage-

ment, and patience of my editor, John Wyzalek, and I remain grateful for his insights

and support over the years.

Of course I need to thank colleagues from around the world who donated

their time to review and provide feedback for all the content of the book: Berin

Smithson, Brendan Sandes, Conrad Macina, Danny Elmarji, Deborah van Petegem,

Geordie Korper, German Garcia, Jerry Vochteloo, Jim Ruskowsky, Michael Arnold,

Michael Levit, Mike van der Steen, Nicolas Groh, Pawel Wozniak, Peta Olson, Peter

Hill-Cottingham, Rajesh Goda, Russell Brown, Steve de Bode, Tony Leung, Vedad

Sapcanin, and Warren PowerJones. They are all spiritual brothers and sisters who all

share a passion for data protection, and I’m hoping I didn’t forget to mention anyone!

There’s another group of people that need to be called out in thanks: my custom-

ers. Over the years I’ve been graced with a plethora of customers from the smallest

to the largest, in pretty much every industry vertical, and it’s been their trust in my

work and my recommendations, and their collaboration with me on data protection

projects, that’s given me the depth and breadth of experience, both technical and

business, that served as the foundations of this work.

Finally of course, I have to thank you, the reader, for having the interest in and

desire to learn more about data protection: for being willing to invest your time to

read what I have to say on the topic. I truly hope that if you’re not actually already

passionate about data protection, I’ll have imparted some of my passion to you by

the time you nish the book.

剩余422页未读，继续阅读

Xesian

粉丝: 0
资源: 1

云环境下数据保护与可用性保障策略

The Data Warehouse ETL Toolkit中文版

data wranglers

master data

redis cluster

this.$set(this.getForm, res.data)

error in type convert default data[[i]]

name 'data_df' is not defined

--master-data

Multiple Spring Data modules found, entering strict repository configuration mode!

最新资源