Loading ...
Sorry, an error occurred while loading the content.

Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

Expand Messages
  • jeelani basha
    Thanks kunal  the steps are v.informative , i have question here   i have active passive node environment   Active-passive cluster 1.       Backup
    Message 1 of 10 , Feb 26, 2010
    • 0 Attachment
      Thanks kunal  the steps are v.informative , i have question here
       
      i have active passive node environment
       
      Active-passive cluster
      1.       Backup System Databases.
      2.       Backup SystemResourceDatabase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
      3.       Apply SP3 on node A.
      4.       Apply SP3 on node B(tools only as tools are not cluster aware).
      5.       Reboot Node B.
      6.       Failover components from Node A to Node B.

      now in node B the  Database serivices won't be  applied with sp3 right ?  how to fix that ? 


      jeelani basha

      --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@...> wrote:


      From: kunal choudhary <nitin_mca_23@...>
      Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
      To: sqlcon@yahoogroups.com
      Date: Monday, February 22, 2010, 11:40 AM


       



      Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.
       
      Stand-alone server
      1.       Backup System Databases.
      2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
      3.       Apply SP3.
      4.       Reboot Server.
      5.       Backup System Databases (DO NOT overwrite backup taken in step 1).
      6.       Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
      7.       Apply Cumulative Update 3.
      8.       Reboot server.
       
      Active-active cluster
      1.       Backup System Databases on both the nodes.
      2.       Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
      3.       Apply SP3 on node A.
      4.       Apply SP3 on node B.
      5.       Failover components of Node A to Node B.
      6.       Reboot node A.
      7.       Failover all components from Node B to Node A.
      8.       Reboot Node B.
      9.       Once node B is back, Failover those components to node B which were on node B originally.
      10.   Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
      11.   Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
      12.   Apply Cumulative Update 3 on Node A.
      13.   Apply Cumulative Update 3 on Node B.
      14.   Failover components of Node A to Node B.
      15.   Reboot node A.
      16.   Failover all components from Node B to Node A.
      17.   Reboot Node B.
      18.   Once node B is back, Failover those components to node B which were on node B originally.
       
      Active-passive cluster
      1.       Backup System Databases.
      2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
      3.       Apply SP3 on node A.
      4.       Apply SP3 on node B(tools only as tools are not cluster aware).
      5.       Reboot Node B.
      6.       Failover components from Node A to Node B.
      7.       Reboot Node A.
      8.       Failover components  from node B to Node A.
      9.       Backup System Databases (DO NOT overwrite backup taken in step 1).
      10.   Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
      11.   Apply Cumulative Update 3 on Node A.
      12.   Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
      13.   Reboot Node B.
      14.   Failover components from Node A to Node B.
      15.    Reboot Node A.
      16.   Failover components  from node B to Node A.
       
       
      Please ignore CU3 upgrade if not required. 
       
      Thx Nitin

      ____________ _________ _________ __
      From: basha_21_99 <basha_21_99@ yahoo.com>
      To: sqlcon@yahoogroups. com
      Sent: Mon, 22 February, 2010 7:39:23 PM
      Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

       
      hi,

      Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

      Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

      [Non-text portions of this message have been removed]











      [Non-text portions of this message have been removed]
    • sunil john
      Hi, As per the docs, all the service packs are cluster aware, so you can just like that install sp3 on active node it will apply on both the nodes. before
      Message 2 of 10 , Feb 28, 2010
      • 0 Attachment
        Hi,

        As per the docs, all the service packs are cluster aware, so you can just like that install sp3 on active node it will apply on both the nodes. before making changes do all the system and user db backups .

        Best Regards


        Sunil John




        ________________________________
        From: jeelani basha <basha_21_99@...>
        To: sqlcon@yahoogroups.com
        Sent: Friday, February 26, 2010 17:18:37
        Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster


        Thanks kunal the steps are v.informative , i have question here

        i have active passive node environment

        Active-passive cluster
        1. Backup System Databases.
        2. Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
        3. Apply SP3 on node A.
        4. Apply SP3 on node B(tools only as tools are not cluster aware).
        5. Reboot Node B.
        6. Failover components from Node A to Node B.

        now in node B the Database serivices won't be applied with sp3 right ? how to fix that ?

        jeelani basha

        --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

        From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
        Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
        To: sqlcon@yahoogroups. com
        Date: Monday, February 22, 2010, 11:40 AM



        Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.

        Stand-alone server
        1. Backup System Databases.
        2. Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
        3. Apply SP3.
        4. Reboot Server.
        5. Backup System Databases (DO NOT overwrite backup taken in step 1).
        6. Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
        7. Apply Cumulative Update 3.
        8. Reboot server.

        Active-active cluster
        1. Backup System Databases on both the nodes.
        2. Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
        3. Apply SP3 on node A.
        4. Apply SP3 on node B.
        5. Failover components of Node A to Node B.
        6. Reboot node A.
        7. Failover all components from Node B to Node A.
        8. Reboot Node B.
        9. Once node B is back, Failover those components to node B which were on node B originally.
        10. Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
        11. Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
        12. Apply Cumulative Update 3 on Node A.
        13. Apply Cumulative Update 3 on Node B.
        14. Failover components of Node A to Node B.
        15. Reboot node A.
        16. Failover all components from Node B to Node A.
        17. Reboot Node B.
        18. Once node B is back, Failover those components to node B which were on node B originally.

        Active-passive cluster
        1. Backup System Databases.
        2. Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
        3. Apply SP3 on node A.
        4. Apply SP3 on node B(tools only as tools are not cluster aware).
        5. Reboot Node B.
        6. Failover components from Node A to Node B.
        7. Reboot Node A.
        8. Failover components from node B to Node A.
        9. Backup System Databases (DO NOT overwrite backup taken in step 1).
        10. Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
        11. Apply Cumulative Update 3 on Node A.
        12. Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
        13. Reboot Node B.
        14. Failover components from Node A to Node B.
        15. Reboot Node A.
        16. Failover components from node B to Node A.


        Please ignore CU3 upgrade if not required.

        Thx Nitin

        ____________ _________ _________ __
        From: basha_21_99 <basha_21_99@ yahoo.com>
        To: sqlcon@yahoogroups. com
        Sent: Mon, 22 February, 2010 7:39:23 PM
        Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster


        hi,

        Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

        Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

        [Non-text portions of this message have been removed]

        [Non-text portions of this message have been removed]





        New Email names for you!
        Get the Email name you've always wanted on the new @ymail and @rocketmail.
        Hurry before someone else does!
        http://mail.promotions.yahoo.com/newdomains/aa/

        [Non-text portions of this message have been removed]
      • Anand Kumar Reddy
        Hi,   Please can any one send me the details, how to connect query analyser from the local pc user to remote sql server.   1. Created the user from
        Message 3 of 10 , Mar 1 2:30 AM
        • 0 Attachment
          Hi,
           
          Please can any one send me the details, how to connect query analyser from the local pc user to remote sql server.
           
          1. Created the user from mycomputer\manage - Users option. (Local PC User)
          2. Given access to the remote SQL Server
          3. Now how to connect the remote SQL Server Query analyser or ODBC connectivity by using the above account.
           
          Thanks
          Anand  




          [Non-text portions of this message have been removed]
        • sunil john
          U can just type remote server name or IP and user name and pass in QA, u will get connected. Before that check the connectivity and port access. Best Regards
          Message 4 of 10 , Mar 1 5:10 AM
          • 0 Attachment
            U can just type remote server name or IP and user name and pass in QA, u will get connected.
            Before that check the connectivity and port access.

            Best Regards


            Sunil John




            ________________________________
            From: Anand Kumar Reddy <anandkreddy@...>
            To: sqlcon@yahoogroups.com
            Sent: Monday, March 1, 2010 13:30:46
            Subject: MUGH-SQLCON How to connect query analyser from the local pc user


            Hi,

            Please can any one send me the details, how to connect query analyser from the local pc user to remote sql server.

            1. Created the user from mycomputer\manage - Users option. (Local PC User)
            2. Given access to the remote SQL Server
            3. Now how to connect the remote SQL Server Query analyser or ODBC connectivity by using the above account.

            Thanks
            Anand

            [Non-text portions of this message have been removed]





            New Email names for you!
            Get the Email name you've always wanted on the new @ymail and @rocketmail.
            Hurry before someone else does!
            http://mail.promotions.yahoo.com/newdomains/aa/

            [Non-text portions of this message have been removed]
          • kunal choudhary
            You need to applay SP or HF only on active node. Database engine is cluster aware. You dont worry for node B as instance is running on node A and you have
            Message 5 of 10 , Mar 1 11:04 PM
            • 0 Attachment
              You need to applay SP or HF only on active node. Database engine is cluster aware. You dont worry for node B as instance is running on node A and you have applied SP or HF on this node.


              Nitin




              ________________________________
              From: jeelani basha <basha_21_99@...>
              To: sqlcon@yahoogroups.com
              Sent: Fri, 26 February, 2010 7:48:37 PM
              Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

               
              Thanks kunal  the steps are v.informative , i have question here
               
              i have active passive node environment
               
              Active-passive cluster
              1.       Backup System Databases.
              2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
              3.       Apply SP3 on node A.
              4.       Apply SP3 on node B(tools only as tools are not cluster aware).
              5.       Reboot Node B.
              6.       Failover components from Node A to Node B.

              now in node B the  Database serivices won't be  applied with sp3 right ?  how to fix that ? 

              jeelani basha

              --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

              From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
              Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
              To: sqlcon@yahoogroups. com
              Date: Monday, February 22, 2010, 11:40 AM

               

              Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.
               
              Stand-alone server
              1.       Backup System Databases.
              2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
              3.       Apply SP3.
              4.       Reboot Server.
              5.       Backup System Databases (DO NOT overwrite backup taken in step 1).
              6.       Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
              7.       Apply Cumulative Update 3.
              8.       Reboot server.
               
              Active-active cluster
              1.       Backup System Databases on both the nodes.
              2.       Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
              3.       Apply SP3 on node A.
              4.       Apply SP3 on node B.
              5.       Failover components of Node A to Node B.
              6.       Reboot node A.
              7.       Failover all components from Node B to Node A.
              8.       Reboot Node B.
              9.       Once node B is back, Failover those components to node B which were on node B originally.
              10.   Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
              11.   Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
              12.   Apply Cumulative Update 3 on Node A.
              13.   Apply Cumulative Update 3 on Node B.
              14.   Failover components of Node A to Node B.
              15.   Reboot node A.
              16.   Failover all components from Node B to Node A.
              17.   Reboot Node B.
              18.   Once node B is back, Failover those components to node B which were on node B originally.
               
              Active-passive cluster
              1.       Backup System Databases.
              2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
              3.       Apply SP3 on node A.
              4.       Apply SP3 on node B(tools only as tools are not cluster aware).
              5.       Reboot Node B.
              6.       Failover components from Node A to Node B.
              7.       Reboot Node A.
              8.       Failover components  from node B to Node A.
              9.       Backup System Databases (DO NOT overwrite backup taken in step 1).
              10.   Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
              11.   Apply Cumulative Update 3 on Node A.
              12.   Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
              13.   Reboot Node B.
              14.   Failover components from Node A to Node B.
              15.    Reboot Node A.
              16.   Failover components  from node B to Node A.
               
               
              Please ignore CU3 upgrade if not required. 
               
              Thx Nitin

              ____________ _________ _________ __
              From: basha_21_99 <basha_21_99@ yahoo.com>
              To: sqlcon@yahoogroups. com
              Sent: Mon, 22 February, 2010 7:39:23 PM
              Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

               
              hi,

              Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

              Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

              [Non-text portions of this message have been removed]

              [Non-text portions of this message have been removed]





              Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/

              [Non-text portions of this message have been removed]
            • jeelani basha
              so when we  failover to node B , does still the patch is applied? to nodeB also   its lot of confusion as i search in net regarding this   On a nutshell 
              Message 6 of 10 , Mar 4 2:23 AM
              • 0 Attachment
                so when we  failover to node B , does still the patch is applied? to nodeB also 
                 its lot of confusion as i search in net regarding this
                 
                On a nutshell  this is wat i believe  is correct, let me know if aim wrong
                 
                Apply sp3 patch on Node A(active node)
                apply sp3 patch on Node B(passive node) only tools will be updated
                restart Node B
                Failover from Node A to Node B
                restart Node A
                Failover back to Node A
                 
                is this the correct solution ?

                jeelani basha

                --- On Tue, 3/2/10, kunal choudhary <nitin_mca_23@...> wrote:


                From: kunal choudhary <nitin_mca_23@...>
                Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                To: sqlcon@yahoogroups.com
                Date: Tuesday, March 2, 2010, 1:04 AM


                 



                You need to applay SP or HF only on active node. Database engine is cluster aware. You dont worry for node B as instance is running on node A and you have applied SP or HF on this node.

                Nitin

                ____________ _________ _________ __
                From: jeelani basha <basha_21_99@ yahoo.com>
                To: sqlcon@yahoogroups. com
                Sent: Fri, 26 February, 2010 7:48:37 PM
                Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                 
                Thanks kunal  the steps are v.informative , i have question here
                 
                i have active passive node environment
                 
                Active-passive cluster
                1.       Backup System Databases.
                2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                3.       Apply SP3 on node A.
                4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                5.       Reboot Node B.
                6.       Failover components from Node A to Node B.

                now in node B the  Database serivices won't be  applied with sp3 right ?  how to fix that ? 

                jeelani basha

                --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

                From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
                Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                To: sqlcon@yahoogroups. com
                Date: Monday, February 22, 2010, 11:40 AM

                 

                Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.
                 
                Stand-alone server
                1.       Backup System Databases.
                2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                3.       Apply SP3.
                4.       Reboot Server.
                5.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                6.       Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                7.       Apply Cumulative Update 3.
                8.       Reboot server.
                 
                Active-active cluster
                1.       Backup System Databases on both the nodes.
                2.       Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                3.       Apply SP3 on node A.
                4.       Apply SP3 on node B.
                5.       Failover components of Node A to Node B.
                6.       Reboot node A.
                7.       Failover all components from Node B to Node A.
                8.       Reboot Node B.
                9.       Once node B is back, Failover those components to node B which were on node B originally.
                10.   Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
                11.   Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
                12.   Apply Cumulative Update 3 on Node A.
                13.   Apply Cumulative Update 3 on Node B.
                14.   Failover components of Node A to Node B.
                15.   Reboot node A.
                16.   Failover all components from Node B to Node A.
                17.   Reboot Node B.
                18.   Once node B is back, Failover those components to node B which were on node B originally.
                 
                Active-passive cluster
                1.       Backup System Databases.
                2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                3.       Apply SP3 on node A.
                4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                5.       Reboot Node B.
                6.       Failover components from Node A to Node B.
                7.       Reboot Node A.
                8.       Failover components  from node B to Node A.
                9.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                10.   Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                11.   Apply Cumulative Update 3 on Node A.
                12.   Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
                13.   Reboot Node B.
                14.   Failover components from Node A to Node B.
                15.    Reboot Node A.
                16.   Failover components  from node B to Node A.
                 
                 
                Please ignore CU3 upgrade if not required. 
                 
                Thx Nitin

                ____________ _________ _________ __
                From: basha_21_99 <basha_21_99@ yahoo.com>
                To: sqlcon@yahoogroups. com
                Sent: Mon, 22 February, 2010 7:39:23 PM
                Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                 
                hi,

                Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

                Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                [Non-text portions of this message have been removed]

                [Non-text portions of this message have been removed]

                Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                [Non-text portions of this message have been removed]











                [Non-text portions of this message have been removed]
              • jeelani basha
                Thanks  guys,     i got it now  just apply the sp3 patch on Active node it  will take care of the passive too jeelani basha ... From: jeelani basha
                Message 7 of 10 , Mar 8 2:51 AM
                • 0 Attachment
                  Thanks  guys,
                   
                   
                  i got it now  just apply the sp3 patch on Active node it  will take care of the passive too

                  jeelani basha

                  --- On Thu, 3/4/10, jeelani basha <basha_21_99@...> wrote:


                  From: jeelani basha <basha_21_99@...>
                  Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                  To: sqlcon@yahoogroups.com
                  Date: Thursday, March 4, 2010, 4:23 AM


                   



                  so when we  failover to node B , does still the patch is applied? to nodeB also 
                   its lot of confusion as i search in net regarding this
                   
                  On a nutshell  this is wat i believe  is correct, let me know if aim wrong
                   
                  Apply sp3 patch on Node A(active node)
                  apply sp3 patch on Node B(passive node) only tools will be updated
                  restart Node B
                  Failover from Node A to Node B
                  restart Node A
                  Failover back to Node A
                   
                  is this the correct solution ?

                  jeelani basha

                  --- On Tue, 3/2/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

                  From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
                  Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                  To: sqlcon@yahoogroups. com
                  Date: Tuesday, March 2, 2010, 1:04 AM

                   

                  You need to applay SP or HF only on active node. Database engine is cluster aware. You dont worry for node B as instance is running on node A and you have applied SP or HF on this node.

                  Nitin

                  ____________ _________ _________ __
                  From: jeelani basha <basha_21_99@ yahoo.com>
                  To: sqlcon@yahoogroups. com
                  Sent: Fri, 26 February, 2010 7:48:37 PM
                  Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                   
                  Thanks kunal  the steps are v.informative , i have question here
                   
                  i have active passive node environment
                   
                  Active-passive cluster
                  1.       Backup System Databases.
                  2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                  3.       Apply SP3 on node A.
                  4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                  5.       Reboot Node B.
                  6.       Failover components from Node A to Node B.

                  now in node B the  Database serivices won't be  applied with sp3 right ?  how to fix that ? 

                  jeelani basha

                  --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

                  From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
                  Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                  To: sqlcon@yahoogroups. com
                  Date: Monday, February 22, 2010, 11:40 AM

                   

                  Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.
                   
                  Stand-alone server
                  1.       Backup System Databases.
                  2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                  3.       Apply SP3.
                  4.       Reboot Server.
                  5.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                  6.       Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                  7.       Apply Cumulative Update 3.
                  8.       Reboot server.
                   
                  Active-active cluster
                  1.       Backup System Databases on both the nodes.
                  2.       Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                  3.       Apply SP3 on node A.
                  4.       Apply SP3 on node B.
                  5.       Failover components of Node A to Node B.
                  6.       Reboot node A.
                  7.       Failover all components from Node B to Node A.
                  8.       Reboot Node B.
                  9.       Once node B is back, Failover those components to node B which were on node B originally.
                  10.   Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
                  11.   Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
                  12.   Apply Cumulative Update 3 on Node A.
                  13.   Apply Cumulative Update 3 on Node B.
                  14.   Failover components of Node A to Node B.
                  15.   Reboot node A.
                  16.   Failover all components from Node B to Node A.
                  17.   Reboot Node B.
                  18.   Once node B is back, Failover those components to node B which were on node B originally.
                   
                  Active-passive cluster
                  1.       Backup System Databases.
                  2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                  3.       Apply SP3 on node A.
                  4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                  5.       Reboot Node B.
                  6.       Failover components from Node A to Node B.
                  7.       Reboot Node A.
                  8.       Failover components  from node B to Node A.
                  9.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                  10.   Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                  11.   Apply Cumulative Update 3 on Node A.
                  12.   Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
                  13.   Reboot Node B.
                  14.   Failover components from Node A to Node B.
                  15.    Reboot Node A.
                  16.   Failover components  from node B to Node A.
                   
                   
                  Please ignore CU3 upgrade if not required. 
                   
                  Thx Nitin

                  ____________ _________ _________ __
                  From: basha_21_99 <basha_21_99@ yahoo.com>
                  To: sqlcon@yahoogroups. com
                  Sent: Mon, 22 February, 2010 7:39:23 PM
                  Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                   
                  hi,

                  Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

                  Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                  [Non-text portions of this message have been removed]

                  [Non-text portions of this message have been removed]

                  Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                  [Non-text portions of this message have been removed]

                  [Non-text portions of this message have been removed]











                  [Non-text portions of this message have been removed]
                • Radhye
                  Yes , it will take care in the passive node but we need to do a failover and failback   Biswajit Das ... From: jeelani basha Subject:
                  Message 8 of 10 , Mar 8 3:58 AM
                  • 0 Attachment
                    Yes , it will take care in the passive node but we need to do a failover and failback


                     



                    Biswajit Das

                    --- On Mon, 3/8/10, jeelani basha <basha_21_99@...> wrote:


                    From: jeelani basha <basha_21_99@...>
                    Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                    To: sqlcon@yahoogroups.com
                    Date: Monday, March 8, 2010, 4:21 PM


                     



                    Thanks  guys,
                     
                     
                    i got it now  just apply the sp3 patch on Active node it  will take care of the passive too

                    jeelani basha

                    --- On Thu, 3/4/10, jeelani basha <basha_21_99@ yahoo.com> wrote:

                    From: jeelani basha <basha_21_99@ yahoo.com>
                    Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                    To: sqlcon@yahoogroups. com
                    Date: Thursday, March 4, 2010, 4:23 AM

                     

                    so when we  failover to node B , does still the patch is applied? to nodeB also 
                     its lot of confusion as i search in net regarding this
                     
                    On a nutshell  this is wat i believe  is correct, let me know if aim wrong
                     
                    Apply sp3 patch on Node A(active node)
                    apply sp3 patch on Node B(passive node) only tools will be updated
                    restart Node B
                    Failover from Node A to Node B
                    restart Node A
                    Failover back to Node A
                     
                    is this the correct solution ?

                    jeelani basha

                    --- On Tue, 3/2/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

                    From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
                    Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                    To: sqlcon@yahoogroups. com
                    Date: Tuesday, March 2, 2010, 1:04 AM

                     

                    You need to applay SP or HF only on active node. Database engine is cluster aware. You dont worry for node B as instance is running on node A and you have applied SP or HF on this node.

                    Nitin

                    ____________ _________ _________ __
                    From: jeelani basha <basha_21_99@ yahoo.com>
                    To: sqlcon@yahoogroups. com
                    Sent: Fri, 26 February, 2010 7:48:37 PM
                    Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                     
                    Thanks kunal  the steps are v.informative , i have question here
                     
                    i have active passive node environment
                     
                    Active-passive cluster
                    1.       Backup System Databases.
                    2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                    3.       Apply SP3 on node A.
                    4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                    5.       Reboot Node B.
                    6.       Failover components from Node A to Node B.

                    now in node B the  Database serivices won't be  applied with sp3 right ?  how to fix that ? 

                    jeelani basha

                    --- On Mon, 2/22/10, kunal choudhary <nitin_mca_23@ yahoo.co. in> wrote:

                    From: kunal choudhary <nitin_mca_23@ yahoo.co. in>
                    Subject: Re: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster
                    To: sqlcon@yahoogroups. com
                    Date: Monday, February 22, 2010, 11:40 AM

                     

                    Below are steps for SP3 upgrade. Make sure you are using domain level ID with local admin rights on all servers involved.
                     
                    Stand-alone server
                    1.       Backup System Databases.
                    2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                    3.       Apply SP3.
                    4.       Reboot Server.
                    5.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                    6.       Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                    7.       Apply Cumulative Update 3.
                    8.       Reboot server.
                     
                    Active-active cluster
                    1.       Backup System Databases on both the nodes.
                    2.       Backup SystemResourceDatab ase on both the nodes àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                    3.       Apply SP3 on node A.
                    4.       Apply SP3 on node B.
                    5.       Failover components of Node A to Node B.
                    6.       Reboot node A.
                    7.       Failover all components from Node B to Node A.
                    8.       Reboot Node B.
                    9.       Once node B is back, Failover those components to node B which were on node B originally.
                    10.   Backup System Databases on both the nodes (DO NOT overwrite backup taken in step 1).
                    11.   Backup SystemResourceDatab ase on both the nodes (DO NOT overwrite backup taken in step 2).
                    12.   Apply Cumulative Update 3 on Node A.
                    13.   Apply Cumulative Update 3 on Node B.
                    14.   Failover components of Node A to Node B.
                    15.   Reboot node A.
                    16.   Failover all components from Node B to Node A.
                    17.   Reboot Node B.
                    18.   Once node B is back, Failover those components to node B which were on node B originally.
                     
                    Active-passive cluster
                    1.       Backup System Databases.
                    2.       Backup SystemResourceDatab ase àCopy mssqlsystemresource .ldf and mssqlsystemresource .mdf (location  of these files is same as master’s files). SQL Server never lock these files so we can copy these files while SQL services are started.
                    3.       Apply SP3 on node A.
                    4.       Apply SP3 on node B(tools only as tools are not cluster aware).
                    5.       Reboot Node B.
                    6.       Failover components from Node A to Node B.
                    7.       Reboot Node A.
                    8.       Failover components  from node B to Node A.
                    9.       Backup System Databases (DO NOT overwrite backup taken in step 1).
                    10.   Backup SystemResourceDatab ase. (DO NOT overwrite backup taken in step 2).
                    11.   Apply Cumulative Update 3 on Node A.
                    12.   Apply Cumulative Update 3 on Node B (tools only as tools are not cluster aware).
                    13.   Reboot Node B.
                    14.   Failover components from Node A to Node B.
                    15.    Reboot Node A.
                    16.   Failover components  from node B to Node A.
                     
                     
                    Please ignore CU3 upgrade if not required. 
                     
                    Thx Nitin

                    ____________ _________ _________ __
                    From: basha_21_99 <basha_21_99@ yahoo.com>
                    To: sqlcon@yahoogroups. com
                    Sent: Mon, 22 February, 2010 7:39:23 PM
                    Subject: MUGH-SQLCON Help neede to upgrade SP3 on SQL2005 failover cluster

                     
                    hi,

                    Iam looking for step by step guide on how to upgrade SP3 on SQL2005 failover cluster .

                    Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                    [Non-text portions of this message have been removed]

                    [Non-text portions of this message have been removed]

                    Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads. yahoo.com/ in/internetexplo rer/

                    [Non-text portions of this message have been removed]

                    [Non-text portions of this message have been removed]

                    [Non-text portions of this message have been removed]











                    [Non-text portions of this message have been removed]
                  Your message has been successfully submitted and would be delivered to recipients shortly.