Link to home
Start Free TrialLog in
Avatar of Pierre Ammoun
Pierre AmmounFlag for Lebanon

asked on

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 ?
Avatar of pgm554
pgm554
Flag of United States of America image

What are you using in terms of failover software?
ASKER CERTIFIED SOLUTION
Avatar of Philip Elder
Philip Elder
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Pierre Ammoun

ASKER

"You can run the failover steps from within Hyper-V Manager"

Is there anything else than right-click and FailOver ?

Regards
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
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
PowerShell. :)
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 ?
A managed failover is done in either the Hyper-V Manager console or PowerShell. Turning off the VMs does nothing as replication continues.