Pkafkas
asked on
Using VEEAm to move Excahnge and Active Directory servers around
Hello:
At my work we have 3 ESXi hosts that have local storage. We do not have a SAN; but, we have used VEEAM backup and replication to move some Virtual machines to different hosts through the network.
I have discovered that our Database servers will require a new license file, from to the Vendor, after I move those VM's to another host (something about when changing the MAC address, it forces licensing to bring up a error); but never the less it is a lesson that one should not assume that one VM move will be just like every other VM move.
In the past I have been able to move Citrix servers without problems; but, i have never tried moving an Exchange or Active Directory server. This may be a silly question; but, I would rather ask and feel prepared instead of assuming and be wrong.
Since we have purchased a new ESXi host I must prepare to move some VM's around to different ESXi hosts in order to accommodate this new ESXi host.
My questions are:
1. Is there anything special that I must consider when I move our Microsoft Exchange server from one Esxi Host to another?
2. The same question goes for moving an Active Directory server?
At my work we have 3 ESXi hosts that have local storage. We do not have a SAN; but, we have used VEEAM backup and replication to move some Virtual machines to different hosts through the network.
I have discovered that our Database servers will require a new license file, from to the Vendor, after I move those VM's to another host (something about when changing the MAC address, it forces licensing to bring up a error); but never the less it is a lesson that one should not assume that one VM move will be just like every other VM move.
In the past I have been able to move Citrix servers without problems; but, i have never tried moving an Exchange or Active Directory server. This may be a silly question; but, I would rather ask and feel prepared instead of assuming and be wrong.
Since we have purchased a new ESXi host I must prepare to move some VM's around to different ESXi hosts in order to accommodate this new ESXi host.
My questions are:
1. Is there anything special that I must consider when I move our Microsoft Exchange server from one Esxi Host to another?
2. The same question goes for moving an Active Directory server?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I should mention that we have VMware version 5.5 Update 2.
What about Moving Exchange or Active Directly servers, from host to host? I am sure that must have happened at some point somewhere.
I am wondering if any special consideration is required for Exchange and Active Directory Servers?
What about Moving Exchange or Active Directly servers, from host to host? I am sure that must have happened at some point somewhere.
I am wondering if any special consideration is required for Exchange and Active Directory Servers?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK,
It sounds like the VEEAM backup /restore program can safely move Exchange and Active Directory servers from one host to another. That is good.
Regarding the database server, I did restore the Server to another host; but, I never powered it on. I wanted to test to see how long the restore process would take. Like I said I never powered the restored database server on; but, I did look at the MAC address. The MAC Address (while the restored server was still powered off) did not change.
It sounds like the VEEAM backup /restore program can safely move Exchange and Active Directory servers from one host to another. That is good.
Regarding the database server, I did restore the Server to another host; but, I never powered it on. I wanted to test to see how long the restore process would take. Like I said I never powered the restored database server on; but, I did look at the MAC address. The MAC Address (while the restored server was still powered off) did not change.
Very good. All seems to be in order.
ASKER
I was told from a consultant that while using vmotion to transfer an Active directory server the Active Directory Server does not actually turn off. And you are actually moving the same instance/server from one ESXi host to another. I was also told that migrating an Active Directory server with a backup program may be a little tricky. Because a company usually has at least 2 Active Directory Domain Controllers that are in constant communication with each other.
If you use any backup software (like VEEAM) to restore a new instance of Active directory to another location the original DC will need to be turned off. Then the restored DC will need to be turned on. The other Domain Controller, that was not restored will recognize that this is not the same server. Then the consultant told me that the 2 Domain Controllers will work; but will not be in sync with each other. Then you will eventually have trouble with AD not working correctly.
I was told that SQL Databases servers and Exchange servers are self contained, they do not have a constant link to another server such as Active Directory Domain Controllers do. Database servers and application servers are self contained. You are better off:
1. Powering off the Domain Controller that you would like to move.
2. Exporting the .vmdk files or the .ova files to a location.
3. Then importing the files to the new ESXi host.
Or
1. Power off the Domain Controller
2. Use VEEAM to make a full backup of the VM, while it is powered down DC.
3. Then use VEEAM to do a restore to of that VM to another ESXi Host.
Once you turn the migrated VM (Domain Controller) to a new host and actually turn it on, there is no turning back. The backup plan of powering off the Restored VM and then powering on the original will not work. Domain Controllers are different.
If you use any backup software (like VEEAM) to restore a new instance of Active directory to another location the original DC will need to be turned off. Then the restored DC will need to be turned on. The other Domain Controller, that was not restored will recognize that this is not the same server. Then the consultant told me that the 2 Domain Controllers will work; but will not be in sync with each other. Then you will eventually have trouble with AD not working correctly.
I was told that SQL Databases servers and Exchange servers are self contained, they do not have a constant link to another server such as Active Directory Domain Controllers do. Database servers and application servers are self contained. You are better off:
1. Powering off the Domain Controller that you would like to move.
2. Exporting the .vmdk files or the .ova files to a location.
3. Then importing the files to the new ESXi host.
Or
1. Power off the Domain Controller
2. Use VEEAM to make a full backup of the VM, while it is powered down DC.
3. Then use VEEAM to do a restore to of that VM to another ESXi Host.
Once you turn the migrated VM (Domain Controller) to a new host and actually turn it on, there is no turning back. The backup plan of powering off the Restored VM and then powering on the original will not work. Domain Controllers are different.
ASKER
If it does not, then that's cool.