Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 557
  • Last Modified:

Sharepoint 2010 sp1 upgrade Always on SQL s012

All,

Looking to move sharepoint 2010 to new app farm following sql farm move.

Moved SQL farm to new 2012 Always on group and set all db's into replication using SQL alias.

to move the app farm to new datacentre i have added teh new appservers to farm but to detach central admin and move it to new server i need to run SP configuration wizard on old server. Run this on old server and upgrade is pending.

Upgrade fails as the logging database cannot be set to simple mode as its part of a replication group.

i cannot follow usual method of stopping the mirror as the db is in Alwayson not a mirror.

the only method is below :
take the farm down
drop the logging db out of always on
point the  SQL alias  on the application and WFE at the primary node
run all the tasks to migrate to the new farm that involve the configuration wizard to ensure the logging db can go in and out of simple mode
once all tasks are complete re add the logging db into the always on farm
repoint all new farm servers at the Always on listener
bring farm back online

obviously thsi is going to have a big impact on downtime as prior to this discovery i was going to complete all reconfiguration, move of timer, crawl and central admin whilst the farm was online and the last task would be a repoint of DNS to the new WFE.

my question would be is their a method of running the configuration wizard without kicking the logging DB into simple recovery, or dropping the secondary replica but keeping the db active on the sql listener address so i dont need to repoint the sql alias.

Hoping someone can help with this,

jay
0
slam68
Asked:
slam68
  • 3
  • 2
2 Solutions
 
Ted BouskillSenior Software DeveloperCommented:
OK, did you realize you can't move a SharePoint 2010 farm?  It's not supported and just doesn't work.  Too much of the configuration is tied to the systems hosting the farm because not all the settings are stored in the databases.  Even if you installed the farm originally using fully qualified domain name instead of server names it's not supported.  Some people have pulled it off by upgrading hardware in a virtual LAN with servers that have the exact same names, copying the machine images, then shutting down the old farm, however, not everyone has enough resources and skill to do it.

The safest thing you can do is setup the new farm, systematically duplicate the configuration, then move the content databases over for the non-administration web applications.  There are articles online for moving content databases that walk you through it.

I guarantee the strategy you are using will lead to error after error and there will issues that might not become apparent for weeks until the right combination of events occur to expose them.
0
 
slam68Author Commented:
Hi Ted,

The process is fine and something I've followed multiple times in the past however never transferring the db's to an alwayson 2012 multi subnet failover. The process of moving to a new db farm is easily achieved using SQL alias and moving to new app wfe is again fairly easy using scale out process, transferring services, migrating wfe and re pointing DNS.

I have now resolved this using power shell to create a temporary logging db in the physical primary node, re pointing logging at this db and running the upgrade and transfer processes. Once these had completed and all migration tasks were complete I then transferred back to the original alwayson replicated db.
It's been a fun 24 hours but got there in the end!
0
 
Ted BouskillSenior Software DeveloperCommented:
I guarantee that if Microsoft found out you did this and tried to get support for the farm you wouldn't get any support without paying for it.  I wouldn't do it for my farm.
0
 
slam68Author Commented:
I work for a Microsoft finalist database partner and it's not a new process  or methodology on migration just not standard so not sure where the foundation fir your guarentee stems from but no problem thanks  for the input
0
 
Ted BouskillSenior Software DeveloperCommented:
My experience is with the SharePoint Development Team as a strategic partner.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now