August 3, 2016 at 12:05 pm
Question is it best practice to let new upgraded node run in PROD for couple days then once there are no errors we can upgrade the other node and failover to it? Or is it better to upgrade both nodes and then let PROD users back on? Appreciate the help.
August 3, 2016 at 1:59 pm
JP10 (8/3/2016)
Question is it best practice to let new upgraded node run in PROD for couple days then once there are no errors we can upgrade the other node and failover to it? Or is it better to upgrade both nodes and then let PROD users back on? Appreciate the help.
Business rules should dictate that the upgrade has already been proofed in a dev and\or test environment. The upgrade to Prod should be high confidence and mitigated as fully as possible.
So, upgrade both nodes
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 3, 2016 at 3:26 pm
Problem is in dev, test and staging these are stand alone servers and in PROD they are clustered does that make a difference?
August 8, 2016 at 1:13 pm
JP10 (8/3/2016)
Problem is in dev, test and staging these are stand alone servers and in PROD they are clustered does that make a difference?
Not from a testing standpoint. a stand alone server will let you know the upgrade differences and what will be needed to fix any issues,if any, moving to 2014. Once you are completely confidant of what is needed to upgrade to 2014 then your upgrade path in production should basically be determined by your downtime/SLA's.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply