SQL down-time required during the entire upgrade process (active and passive nodes) Less user interaction required: Uses the same volumes that are currently used by SQL (no spare volume is required). Strategy 2 - Serial upgrade using the original volumes Greater user interaction required: A spare volume must be mounted manually on secondary/passive nodes for temporary use during the upgrade process. Updating the secondary (disaster recovery) site does NOT require a global fail-over. Less maintenance time required, particularly when a large number of nodes are being updated (SQL down-time only required during the upgrade of the first/active node in the cluster)
Strategy 1 - Parallel upgrade using spare volumes This document describes two strategies for applying Microsoft SQL Server 2005 Service Pack 4 in a SFW/HA.
0 kommentar(er)
