We're planning on upgrading to WS2012 Standard and utilizing Hyper V to create two domain controllers, one File & Print server and one Accounting/CRM server VM's. The plan currently is to purchase a new server for site 1 with RAID 1 for OS & RAID5 for DATA/VHD's. We will re-purpose an existing server with the RAID1/RAID 5 setup as a second WS2012 Standard Hyper V replication host that will be located at a secondary site. A third server (also at secondary site) will be our backup server utilizing Altara Hyper V backup software primarily for single file restores and to have a bigger safety net in case of a worst case scenario. So, my questions are:
1. Since my primary and secondary Hyper V servers are not exactly the same as far as hardware, will I have problems if I need to spin up the VM's over at the secondary site? They both will be Intel based systems, but one will obviously be older than the new server we plan on purchasing.
2. In the event we have to fail over to our second site, how is that traffic to be routed/how will that work exactly?. i.e. Site 1=10.2.1.x subnet, Site 2=192.168.125.x subnet. So, if I spin up the replicated VM's at Site 2 in a disaster recovery situation, they will have IP addresses in the 10.2.1.x subnet and not the 192.168.125.x subnet. How can I have it where site 1, can communicate with the VM's at site 2 on the secondary host until we can get the primary site back up and running?
Thanks in advance!