<div>
Hi,<br />
<br />
If my answer help you please close the question.
</div>


Hi,

If my answer help you please close the question.

<div>
<div class="content wysiwyg-content">
Hi All,<br />
<br />
I just wanted to get some opinions on Veeam Replication. I have a two server site, both servers are Hyper V hosts with two VM's on each, one VM on the first Host is a DC that holds all the FSMO roles, second server has a backup DC VM<br />
<br />
Both of these DC's are gettings backed up with Veeam to a NAS, I also have the DC with the FSMO roles replicating to the other Hyper V Host.<br />
<br />
Is it best practice to have this FSMO holding DC replicated which i could fail over with Veeam if i loose it, or is it better to just have the backup, if I lose the FSMO DC, rather seize the FSMO roles on the backup DC and build a new DC, transfer roles back etc.<br />
<br />
The replication job of the FSMO DC is working perfect with Application Aware enabled. <br />
<br />
Veeam's articles kinda suggest its ok but other forums suggest that FSMO transfer or Seize would be better.<br />
<br />
I appreciate any advice or suggestions<br />
<br />
Thanks
</div>
</div>


Hi All,

I just wanted to get some opinions on Veeam Replication. I have a two server site, both servers are Hyper V hosts with two VM's on each, one VM on the first Host is a DC that holds all the FSMO roles, second server has a backup DC VM

Both of these DC's are gettings backed up with Veeam to a NAS, I also have the DC with the FSMO roles replicating to the other Hyper V Host.

Is it best practice to have this FSMO holding DC replicated which i could fail over with Veeam if i loose it, or is it better to just have the backup, if I lose the FSMO DC, rather seize the FSMO roles on the backup DC and build a new DC, transfer roles back etc.

The replication job of the FSMO DC is working perfect with Application Aware enabled. 

Veeam's articles kinda suggest its ok but other forums suggest that FSMO transfer or Seize would be better.

I appreciate any advice or suggestions

Thanks

Veeam Replication of DC

Veeam® has pioneered a new market of Availability for the Always-On Enterprise™ by helping organizations meet recovery time and point objectives (RTPO™) of less than 15 minutes for all applications and data. Veeam develops backup, disaster recovery and virtualization management software for VMware and Hyper-V virtual environments. The company focuses on products that help with virtualized workloads, reduce downtime, and ensure the system Availability required by service-level agreements.

Veeam

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

A domain controller is a server that responds to security authentication requests within a computer network domain. It is a network server that is responsible for allowing host access to domain resources. It authenticates users, stores user account information and enforces security policy for a domain

Domain Controller

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.