How to fail over in a "safe" and smooth way ?

My layout is as follows:
I have a physical server that has 5 VMs - Host is Windows 2012 R2
1-Domain controller
1-Exchange (2013)
1-SQL Server 2012
1-Data Server
1-Application Server

I also have another Physical Server that has a replica of all of these VMs. Host is Windows 2012 R2
The replication is working fine.

I am running out of disk space on both physical servers and adding disk space need to turn off the servers which I cannot afford.

I got a new server (rented one for 1 week) with enough space.. and I did set it up as extended replicas from Server2.
and the extended replication is working fine.

Now I am about to take the step of "fail over" from the 3rd server (where I have the extended replication.)
But I have never done this and I am quite unsure about the steps...
Can someone please help me on how to do this "the safest" possible way ?
I was thinking of turning off my primary server (Host) and THEN fail over from the 3rd Server. THEN turn off the second server once all is ok.
If there is anything wrong,  I can then turn back ON the primary.
Is this the right way of doing things ?
Pierre AmmounIT ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pgm554Commented:
What are you using in terms of failover software?
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
You can run the failover steps from within Hyper-V Manager. There is no need to turn anything off.

Run your final sync and fail over to whichever server needs to have the VMs running. If that's tertiary then so be it.

Once the work is done on Server 1 reverse replication back from Tertiary to Server 1.

Once work on Server 2 has finished replication should pick back up where it left off (hopefully) and then Server 2 will pick up with Tertiary.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Pierre AmmounIT ConsultantAuthor Commented:
"You can run the failover steps from within Hyper-V Manager"

Is there anything else than right-click and FailOver ?

Regards
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Peter HutchisonSenior Network Systems SpecialistCommented:
For domain controllers, you can move the FSMO roles over with no downtime.
https://www.petri.com/transferring_fsmo_roles

For Exchange, you need a DAG setup so that you can failover mailbox databases to another Exchange server.
https://technet.microsoft.com/en-us/library/dd298187(v=exchg.150).aspx

For SQL you can either use Cluster servers or SQL Availability Groups to move databases.
https://technet.microsoft.com/en-us/library/hh510230(v=sql.110).aspx
0
ArneLoviusCommented:
to "failover" between hyper-v hosts with local storage and replication, the VM must be off.

it is also possible to "move" a live VM  and its associated storage between hosts, this does not require the VM to be off
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
PowerShell. :)
0
Pierre AmmounIT ConsultantAuthor Commented:
Why do I need to move roles ? All my servers and Virtual and My host is "only" having windows 2012 R2 with the VMs running on it.

I thought it is a matter of "turning' off the the VMs and firing up the replicas ?
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
A managed failover is done in either the Hyper-V Manager console or PowerShell. Turning off the VMs does nothing as replication continues.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.