Hi all,
I'm building a new 2016 RDS platform across two sites and wish to use both user profile disks and user environment virtualisation. The latter also being used for desktop clients. There will be a dedicated platform for this and I would like it to be highly available even in the event of a site outage.
This question is around disaster mitigation on the user profile disks platform, not RDS in general.
My design plan is as follows
Site A (Hyper V Cluster 1)
================
Server1 - Server 2016 DataCenter
Server2 - Server 2016 DataCenter
ServerFSW - Server 2016 Standard (HV Replica enabled between both HV clusters)
SAN 15k - 100gb LUN - Logs
SAN 7k - 500gb LUN - Data
Site B (Hyper V Cluster 2)
================
Server3 - Server 2016 DataCenter
Server4 - Server 2016 DataCenter
SAN 15k - 100gb LUN - Logs
SAN 7k - 500gb LUN - Data
The five servers are all virtual running on HyperV 2012 R2. Server1 and 2 will both share the storage on the SANs in SiteA. Servers3 and 4 will both share the storage on the SANs in SiteB.
I will create a stretched cluster across Servers 1, 2, 3 and 4 with Server5 as the file share witness.
Server 5 will be enabled for HyperV replication between both HV clusters.
My question is
Does having the witness server enabled for HV replication pose any risk? There maybe the possibility of moving this server into Azure, but not yet. This is the only design I can come up with which makes the platform highly available between sites and giving users access to their profile disks when roaming.
I'm building a new 2016 RDS platform across two sites and wish to use both user profile disks and user environment virtualisation. The latter also being used for desktop clients. There will be a dedicated platform for this and I would like it to be highly available even in the event of a site outage.
This question is around disaster mitigation on the user profile disks platform, not RDS in general.
My design plan is as follows
Site A (Hyper V Cluster 1)
================
Server1 - Server 2016 DataCenter
Server2 - Server 2016 DataCenter
ServerFSW - Server 2016 Standard (HV Replica enabled between both HV clusters)
SAN 15k - 100gb LUN - Logs
SAN 7k - 500gb LUN - Data
Site B (Hyper V Cluster 2)
================
Server3 - Server 2016 DataCenter
Server4 - Server 2016 DataCenter
SAN 15k - 100gb LUN - Logs
SAN 7k - 500gb LUN - Data
The five servers are all virtual running on HyperV 2012 R2. Server1 and 2 will both share the storage on the SANs in SiteA. Servers3 and 4 will both share the storage on the SANs in SiteB.
I will create a stretched cluster across Servers 1, 2, 3 and 4 with Server5 as the file share witness.
Server 5 will be enabled for HyperV replication between both HV clusters.
My question is
Does having the witness server enabled for HV replication pose any risk? There maybe the possibility of moving this server into Azure, but not yet. This is the only design I can come up with which makes the platform highly available between sites and giving users access to their profile disks when roaming.