How Microsoft IT Deploys Windows Server 2008 Failover Clusters for File Services

1. Dondi Vigesaa Operations Engineer Microsoft Corporation dondiv@microsoft.com How Microsoft IT Deploys Windows Server 2008 Failover Clusters for File Services

2. Microsoft IT File Service Utility group situation Method for updating Windows Server 2008 failover cluster nodes Approach for migrating from Windows Server 2003 to Windows Server 2008 cluster nodes Lessons learned Best practices Agenda

3. What We Will Cover Microsoft IT business drivers Windows Server 2008 failover clustering technologies Distributed File System services Storage Area Network concepts

4. Understanding of General server concepts High-level failover clustering concepts Basic networking concepts Basic Storage Area Network concepts Prerequisite Knowledge Level 200

5. SituationMicrosoft IT File Services Utility (FSU) Group Provides file services in four primary datacenters Dublin, Ireland Kawaguchi, Japan Redmond, WA, USA Singapore, Singapore Provides access to over 200 TB of data Handles shares from 20 GB to 300 GB in size

6. SituationMigrationBusiness Drivers Simplified administration Support for more users with the same number of administrators Increased uptime through the use of fewer administrative consoles Support for more users through Distributed File Services namespace Support for larger cluster disk volumes

7. Reasons for Using Windows Server 2008 Key Benefits SCSI-3 persistent reservations used Domain user account not required by cluster service Node names, cluster name, and network names are Active Directory Computer Name Objects (CNOs) Kerberos-only authentication is the default authentication mechanism

8. Reasons for Using Windows Server 2008 Key Benefits (cont’d) Full support for Volume Shadowcopy Service (VSS) for easier backups Support for disk volumes larger than 2 TB Centralized administration interface leverages MMC 3.0

9. SolutionRequirements Protection of disk resources during migration In-place migration that requires no new server hardware or storage hardware Clearly defined and reliable roll-back plan by keeping one or more Windows Server 2003 cluster nodes in reserve Simple process that does not require a large team

10. SolutionRequirements (cont’d) Availability of service during migration Clearly communicated and managed migration process Scheduled migrations during hours of least impact to users

11. SolutionOverview Move cluster resources to a single active node Install Windows Server 2008 on passive node in a new cluster group Migrate cluster resources to Windows Server 2008 node Install Windows Server 2008 on remaining cluster node

12. demonstration Migration Process • Move all cluster resources to a single node • Take passive node offline • Unmask storage from passive node • Format and install Windows Server 2008 on passive node • Mask storage

13. Migrating to Windows Server 2008Typical Configuration • Active/Passive configuration • Shared storage • Dedicated cluster heartbeat connection • Dedicated public network connection

14. Migrating to Windows Server 2008Consolidate resources on single node • Move all cluster resources to the active node

15. Migrating to Windows Server 2008Take passive node offline • Shut down passive node • Mask SAN storage from passive node (note the disconnected storage on the passive node)

16. Migrating to Windows Server 2008Install Windows Server 2008 • Format the passive node, and install Windows Server 2008

17. Migrating to Windows Server 2008Configure new node & unmask storage • Unmask SAN storage • Configure shared storage in Windows Server 2008 • Configure a new, distinct cluster group

18. Migrating to Windows Server 2008Migrate resources to new node • Check to make sure that no clustered applications or file shares have dependencies set for cluster group resources • Use the Cluster Resource Migration wizard to migrate clustered file shares and applications to the Windows Server 2008 failover cluster

19. Migrating to Windows Server 2008Take remaining node offline • After all applications and file shares are migrated and tested, power down the remaining Windows Server 2003 node • Mask storage from the remaining Windows Server 2003 node

20. Migrating to Windows Server 2008Install and configure new node • Install Windows Server 2008 on the new cluster node

21. Migrating to Windows Server 2008Move cluster resources back to original locations • Unmask SAN connection • Join the new node to the cluster group • Move cluster applications and resources back to original locations

22. demonstration Cluster Failover Process • Take active node offline • Update or repair offline node • Bring passive node online to support cluster resources

23. Updating Windows Server 2008 Failover ClustersTypical Configuration • Active/Passive configuration • Shared storage • Dedicated cluster heartbeat connection • Dedicated public network connection

24. Updating Windows Server 2008 Failover ClustersConsolidate resources • Move all cluster resources to the active node • Failover process streamlined in Windows Server 2008 failover clusters – faster than ever • Install updates on the offline node

25. Updating Windows Server 2008 Failover ClustersMove resources to updated node • Move all cluster resources to the recently updated node • Test and verify application updates

26. Updating Windows Server 2008 Failover ClustersUpdate offline node • Install updates on the offline node

27. Updating Windows Server 2008 Failover ClustersMove resources back to original node • Move all cluster resources to the original node

28. Benefits Support for more cluster nodes, now a maximum of 16 per cluster group Support for larger volumes, now greater than 2 TB with GPT partitions Centralized management with new MMC 3.0–based console Migration wizard Greatly simplifies moving cluster resources from Windows Server 2003 to Windows Server 2008 clusters

29. Best Practices Cluster resources Clearly define cluster dependencies to reduce resource conflicts during migrations Migration wizard Use to simplify moving cluster resources from Windows Server 2003 to Windows Server 2008 clusters Storage signatures Windows Server 2008 SCSI-3 signatures do not overwrite Windows Server 2003 cluster signatures

30. Best Practices(cont’d) Storage masking Allows for existing hardware to be re-used without risking production data Allows for simple disconnect and reconnect of production storage during the upgrade process Phased migration Provides the ability to apply lessons learned from previous deployments, improving the migration approach

31. Lessons Learned Active/Passive node pairs provide a scalable approach to deploying clusters Distributed File System namespace allows a single cluster to provide DFS services to multiple namespaces, even disjoined namespaces New management interface provides greater functionality, empowering administrators with greater control and efficiency

32. Session Summary Windows Server 2008 failover clusters bring many new benefits for highly available services and applications Migration wizard greatly simplifies migrations Optimized cluster components offer greater performance and manageability

33. Next Steps For more information about Microsoft, visithttp://www.microsoft.com For more information about Microsoft IT, visithttp://www.microsoft.com/technet/itshowcase Windows Server 2008 resources:http://www.microsoft.com/windowsserver2008

34. Visit TechNet at www.microsoft.com/technet For additional information about books, courses, and other community resources that support this session, visit http://technet2.microsoft.com/windowsserver2008/ and http://www.microsoft.com/learning/windowsserver2008/default.mspx For More Information…

35. Questions and Answers Submit text questions by using the “Ask” button Don’t forget to fill out the survey For upcoming and previous live webcasts, visit www.microsoft.com/webcasts Got webcast content ideas? E-mail us at http://go.microsoft.com/fwlink/?LinkId=41781 Today’s webcast was presented by using Microsoft Office Live Meeting. Get a free 14-day trial at http://www.microsoft.com/presentlive