0

i'm tryin to build a lab farm where a sharepoint 2013 server will use a mirrored database. I read lots of stuff but i'm still not sure about the correct installation path. I would roughly proceed the following way:

  • Install SQL principal instance
  • Install SQL mirror instance
  • Install SQL witness instance (still no sql mirroring configuration done at this point)
  • Install SP pointing to the principal server as it was the only existing db (better create a sql alias first pointing to the principal and install SP using the alias?)
  • Copy all the system and sp databases to mirror and setup all the mirroring thing
  • Configure failover instance on Sharepoint

Does it make sense? do i forget something ? any help will be greatly appreciated!

RL

| improve this question | |
1

SQL Aliases are used for mobility. With mirroring (deprecated) or AlwaysOn Availability Groups (strongly preferred), there's no reason to use SQL Aliases as you already have that mobility in play.

But your steps sound correct.

| improve this answer | |
  • thanks Trevor. I'm trying to setup mirroring since i dont have any shared storage available. I'll set mirror server as failover instance. By the way, i'm asking you another question, cause what i found around leaves me unsure. What is the correct way to rollback from failover instance to primary? Does SP provides an automated way to do it? – RadioLontra Jan 17 '17 at 19:14
  • You do it SQL-side. There's nothing to do on the SharePoint side (though it may take a minute or two to recognize the new primary). – Trevor Seward Jan 17 '17 at 19:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.