Exch2010 Sp1 v14.1 Build 218.15 upgrade to Sp3

Okay so can go straight to sp3ur2 without having to apply in between releases?

So I only have two member servers so can't use script, right?

I actually block failover, via eps command now and for past year, at the secndary site bc it happens willy nilly and was causing havoc.
So finally do you apply patch to each member server?

Thx

 The plan is since that loc is closing I was ging to take opportunity to break\dismantle dag.  I dot have complete plan for that process yet either.  Any imput?

Finally, with two members u applying sp3u2 to both servers, right= or wrong?

To summarize your questions in pretty bullet points..

- You can do Exchange 2010 SP3, and then UR2 for SP3. That covers it all.
- As for the Stop/StartDagServerMaintenance.PS1 script, I believe the two node thing was fixed back in SP2. You can try it, but I would rather do it by hand since the original script was created for 3+ node DAGs
- It is highly recommended to be at the same OS patch level AND Exchange patch level on all member exchange servers in the environment (e.g: servers that are running Exchange 2010)


Breaking the DAG is a pretty easy thing, depending on how broken it is already :) I would recommend opening another questions as I do not want to derail this one, as I can see that turning into a long thread. Essentially you are trying to peacefully remove the broken node and then rebuild it. Unfortunately, sometimes the DAG is so broken where you have to evict the node, and that is where it gets complex.

Great thanks... let me review the link and info on this thread.

i posted DAG break/dismantle via new https://www.experts-exchange.com/questions/28248118/Breaking-Dismantle-DAB-Exchang2010-2-member-node-HOW-To.html 

Please comment on that if you would.

I will assign points to this  thread after review and before Thursday/fri b/c if going to patch going to do at end of week/weekend.  

Thx

k so in reviewing the link real quick seems you have to move active copies to passive node first. this is a must?  

This is where i worry i will have problems getting them back from the passive to the main loc, which is what i consider the primary/preferred server.  

Before i set my DAG passive to block anytime the four dbs it would fail-over i'd will nilly as mentioned.   I'd wind up having to seed and it would take hours to get things back, while on one occasion had to get them to overnight the dbs on a thumb-drive to me because it just wouldn't seed/ and move due to whatever major errors .  since that is when i looked up and found the block command for all db on passive node and have been using until ready to dismantle DAG.

thx

looks like the script simply moves the active databases to the other DAG member, pauses the node in the cluster and set the databaseutoactivationplicy to *blocked*.  I have been blocking activation for a year now like i said due to the willy nilly and poor performance when fail-over happens out of the blue to the passive member.  After this is run you then load patches/updates. Then you run the stop script.

Also, seems you can use the  "overrideMinimumTwoCopies" in order to execute this script  on a DAG memberserver which hosts databases that have only two copies of a specified database. If not then you get errors.

Cant I just stop the store, ensure blocked is on. Run the updates on my passive node.  Repeat the same for my Primary Node and then restart primary InfoStoreand and then the Passive.  Obviously doing this all on a Friday night and over the weekend?