LEADER 00938nam0-22003251i-450- 001 990003982000403321 005 20031205105944.0 010 $a88-464-3090-5 035 $a000398200 035 $aFED01000398200 035 $a(Aleph)000398200FED01 035 $a000398200 100 $a20031125d2001----km-y0itay50------ba 101 0 $aita 102 $aIT 105 $aa---a---001yy 200 1 $aGlobalizzazione, nuova economia e ICT$econoscerle per coglierne le opportunitą ed evitarne i rischi$fAugusto Leggio 210 $aMilano$cFranco Angeli$d2001 215 $a191 p.$d23 cm 610 0 $aSviluppo informatico 610 0 $aNew Economy 676 $a051.005 700 1$aLeggio,$bAugusto$0150240 801 0$aIT$bUNINA$gRICA$2UNIMARC 901 $aBK 912 $a990003982000403321 952 $a051.005.LEG$b5150$fDECGE 959 $aDECGE 996 $aGlobalizzazione, nuova economia e ICT$9473616 997 $aUNINA LEADER 02073oam 2200577M 450 001 9910715578503321 005 20191116081231.7 035 $a(CKB)5470000002512267 035 $a(OCoLC)1065967811 035 $a(OCoLC)995470000002512267 035 $a(EXLCZ)995470000002512267 100 $a20070221d1828 ua 0 101 0 $aeng 135 $aurcn||||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aNew Hampshire. Petition of farmers in New Hampshire, praying protection for the interests of agriculture and manufactures. January 22, 1828. Referred to the Committee on Manufactures 210 1$a[Washington, D.C.] :$c[publisher not identified],$d1828. 215 $a1 online resource (5 pages) 225 1 $aHouse document / 20th Congress, 1st session. House ;$vno. 81 225 1 $a[United States congressional serial set ] ;$v[serial no. 171] 300 $aBatch processed record: Metadata reviewed, not verified. Some fields updated by batch processes. 300 $aFDLP item number not assigned. 606 $aAgricultural industries 606 $aForeign trade promotion 606 $aForeign trade and employment 606 $aImports 606 $aManufacturing industries 606 $aProtectionism 606 $aTariff 606 $aWool fabrics 606 $aWool 608 $aLegislative materials.$2lcgft 615 0$aAgricultural industries. 615 0$aForeign trade promotion. 615 0$aForeign trade and employment. 615 0$aImports. 615 0$aManufacturing industries. 615 0$aProtectionism. 615 0$aTariff. 615 0$aWool fabrics. 615 0$aWool. 801 0$bWYU 801 1$bWYU 801 2$bOCLCO 801 2$bOCLCQ 906 $aBOOK 912 $a9910715578503321 996 $aNew Hampshire. Petition of farmers in New Hampshire, praying protection for the interests of agriculture and manufactures. January 22, 1828. Referred to the Committee on Manufactures$93264592 997 $aUNINA LEADER 05692oam 2200577 450 001 9910437973803321 005 20190911103509.0 010 $a1-4302-6329-6 024 7 $a10.1007/978-1-4302-6329-6 035 $a(OCoLC)864831262 035 $a(MiFhGG)GVRL6VNO 035 $a(EXLCZ)993710000000031164 100 $a20140415d2013 uy 0 101 0 $aeng 135 $aurun|---uuuua 181 $ctxt 182 $cc 183 $acr 200 10$aPro SharePoint disaster recovery and high availability /$fStephen Cummins 205 $a2nd ed. 2013. 210 1$aNew York :$cApress,$d2013. 215 $a1 online resource (xxi, 242 pages) $cillustrations (some color), maps 225 0 $aThe expert's voice in SharePoint Pro SharePoint disaster recovery and high availability 300 $a"Be prepared for when bad things happen to good portals"--Cover. 300 $aIncludes index. 311 $a1-4302-6328-8 327 $a""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?"" 327 $a""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"" 327 $a""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"" 327 $a""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"" 327 $a""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"" 327 $a""Platform"" 330 $aFew 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. 410 0$aExpert's voice in SharePoint. 606 $aData recovery (Computer science) 606 $aIntranets (Computer networks) 606 $aWeb servers 615 0$aData recovery (Computer science) 615 0$aIntranets (Computer networks) 615 0$aWeb servers. 676 $a004 676 $a005.368 676 $a005.7 700 $aCummins$b Stephen$4aut$4http://id.loc.gov/vocabulary/relators/aut 701 $aCummins$b Stephen$f1971-$01243155 801 0$bMiFhGG 801 1$bMiFhGG 906 $aBOOK 912 $a9910437973803321 996 $aPro SharePoint Disaster Recovery and High Availability$92883543 997 $aUNINA