| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNINA9910437973803321 |
|
|
Autore |
Cummins Stephen |
|
|
Titolo |
Pro SharePoint disaster recovery and high availability / / Stephen Cummins |
|
|
|
|
|
|
|
Pubbl/distr/stampa |
|
|
New York : , : Apress, , 2013 |
|
|
|
|
|
|
|
ISBN |
|
|
|
|
|
|
Edizione |
[2nd ed. 2013.] |
|
|
|
|
|
Descrizione fisica |
|
1 online resource (xxi, 242 pages) : illustrations (some color), maps |
|
|
|
|
|
|
Collana |
|
The expert's voice in SharePoint Pro SharePoint disaster recovery and high availability |
|
|
|
|
|
|
|
|
Altri autori (Persone) |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
|
|
Soggetti |
|
Data recovery (Computer science) |
Intranets (Computer networks) |
Web servers |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
"Be prepared for when bad things happen to good portals"--Cover. |
Includes index. |
|
|
|
|
|
|
|
|
Nota di contenuto |
|
""Contents at a Glance""; ""Contents""; ""About the Author""; ""About the Technical Reviewer""; ""Introduction""; ""Chapter 1: Steering Away from Disaster""; ""The Real Cost of Failure""; ""Why Disasters Happen and How to Prevent Them""; ""Success/Failure""; ""Your SharePoint Project: Will It Sink or Float?""; ""High Availability: The Watertight Compartments""; ""Disaster Recovery""; ""Recovery Time Objective and Recovery Point Objective""; ""Networks and the Cloud""; ""IaaS vs. SaaS""; ""SharePoint in the Cloud""; ""Why Is Infrastructure Moving to the Cloud?"" |
""Will SharePoint Administrators Become Extinct?""""SharePoint Is a Complicated Beast""; ""Practical Steps to Avoid Disaster""; ""What Role Will You Play?""; ""Stakeholders and Strategy""; ""Dependencies""; ""Clear Measurements of Success: Reporting, Analysis, and Prevention""; ""Applied Scenario: The System Is Slowing Down""; ""The Solution""; ""What Is Upper Management's Responsibility ?""; ""Technology Is Just a Tool""; ""Applied Scenario: It's Never Simple""; ""Some Terminology""; ""Summary of the Options""; ""Option 1: Log Shipping/Mirroring""; |
|
|
|
|
|
|
|
|
|
|
|
""Option 2: Stretched Farm"" |
""Option 3: Disaster Recovery Farm""""The Solution""; ""Summary""; ""Chapter 2: Planning Your Plan""; ""Getting the Green Light from Management""; ""Barriers to Consensus""; ""Weak Metaphors""; ""Long, Long Ago . . .""; ""Long Ago . . .""; ""Another Weak Metaphor: Snapshots""; ""Stronger Metaphors""; ""Business Impact Assessment""; ""Who Sets the RTO and RPO ?""; ""The Goldilocks Principle""; ""Consensus""; ""People""; ""Physical Dependencies""; ""Architectural Impact""; ""Risk Assessment""; ""Synchronicity""; ""Synchronous Replication: Mirroring""; ""Latency"" |
""Asynchronous Replication: Log Shipping""""Recovery Tiers""; ""20/20 Hindsight""; ""Service Level Agreements""; ""Disaster Coordination""; ""4Ci""; ""Command""; ""Control""; ""Communications""; ""Computers""; ""Intelligence""; ""A DR Script""; ""Last but Not Least: Supply Stores and Restaurants""; ""Summary""; ""Chapter 3: Activating Your Plan""; ""Welcome to the University of Newbridge""; ""What Is a Process?""; ""Do I Need to Define My Processes and Procedures?""; ""Benefits of Defining Your Processes and Procedures""; ""Applied Scenario: A Disaster Recovery Plan"" |
""The University of Newbridge Disaster Recovery Plan""""Introduction""; ""Context and Communication""; ""General Facility Risks""; ""Communication""; ""Setting Priorities""; ""SharePoint Recovery Priority Tiers""; ""Plan Location and Contents""; ""Getting the Go Signal""; ""Disaster Recovery Plan Activation""; ""Interdependency""; ""Decision Makers""; ""Disaster Recovery Team""; ""Actions and Tasks""; ""Plan of Action""; ""Time to Restore SharePoint !""; ""Summary""; ""Chapter 4: High Availability""; ""High Availability Overview""; ""Measuring Business Impact""; ""The Nines""; ""Resilience"" |
""Platform"" |
|
|
|
|
|
|
Sommario/riassunto |
|
Few IT professionals take the time to learn what needs to be known to do disaster recovery well. Most labor under the pretense that good administration equals close to five-nines uptime. Most technical people do not see the value of planning for disasters until the unexpected has already happened, and the effects of a disaster involving a SharePoint farm—which today houses business information, line-of-business applications, sensitive information, extranets, and other highly important assets—can be staggering. Pro SharePoint Disaster Recovery and High Availability, Second Edition will take you through a step-by-step process to show how to build an awareness and reaction plan for the inevitable. With a focus on real-world experiences and war stories, author Stephen Cummins weaves an expert tale of woe response and offers you: Ways to see the warning signs of disaster, and ways to avoid it Ways to respond to a disaster while it is happening Perhaps most importantly, how to develop a plan to deal with disaster when it inevitably does happen. |
|
|
|
|
|
|
|
| |