HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

369 of 739
Special configurations
Storage Mirroring Recover can be implemented with very little configuration necessary
in small or simple networks, but additional configuration may be required in large or
complex environments. Because an infinite number of network configurations and
environments exist, it is difficult to identify all of the possible configurations. Select a link
to review configuration information for particular network environments.
● Domain controllers
● Routers
● NetBIOS
● WINS
● DNS
● Macintosh shares
● NFS Shares
Domain controllers
Failover of domain controllers is dependent on the Storage Mirroring Recover
functionality you are using.
● Domain controller role—If you want to failover a domain controller, including the
roles of the domain controller, you should create full-server or virtual workload
protection.
● Non-domain controller role—If you are only protecting data, you can failover a
domain controller, but the roles of the domain controller are not included. The
server will be a member server after failover. In this case, you need to keep in mind
that the unavailability of some of the FSMO (Flexible Single Master Operation)
roles can cause immediate issues such as the inability to extend the Active
Directory schema or to add a domain to a forest.
● Global catalog server—If your source is a global catalog server, you should have
other global catalog servers throughout the network to ensure that the failure of the
source will not impact users.
Routers
Depending on the type of router you are using, failover may or may not be advisable. For
example, failover across a NAT router is not advisable, because you would only be able
to monitor the IP address of the NAT, not the IP address of the source. In that case,
failover would occur when the NAT router was unavailable, not when the source was
unavailable.