For folks who use Windows HyperV on a regular basis, in particular, Extended/Tertiary Replication. If you haven't used it please don't take on this question - we want real world experience - enough theory available via Google.
We are setting up Windows Server 2012 R2 HyperV Extended Replication. We have two servers at one office in different areas that are replicating to each other and we have a third server off site that we want the extended replication to target. To initially seed the replication at the main office we exported the relevant VM/VHD to a USB and imported into the target server and got things working fine. We then tried using the same export to seed the offsite server but it didn't seem to work - the VM could not be imported on the off-site server - all specs/OS same as main office. We need to seed as the size of the VM/VHD would mean it would take weeks for the first synch to take place.
Questions:
Should this work - import worked on the internal secondary host, why would it not work on the remote host? If not what would be the way to do an initial on site seed so as to not have the seed take place over the Internet.
If for some reason the secondary server at the office - the HyperV target were to have a problem, go out of commission, what is the best way to get the primary to synch with the remote extended/tertiary Replica host?
Any input from someone who has dealt with these issues is much appreciated.
