Hp Storage Mirroring Software User Manual Page 66

  • Download
  • Add to my manuals
  • Print
  • Page
    / 678
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 65
Storage Mirroring Recover requirements Page 65 of 677
Cluster workload requirements
Make sure your cluster meets the general source and target server requirements as well
as the standard or GeoCluster requirements below, depending on your cluster
configuration.
l Standard cluster—If you will be protecting a standard cluster configuration, with a
shared SCSIdisk, there are two additional requirements.
l Network—The cluster's private network should be a unique subnet so that
Storage Mirroring Recover will not attempt to use an unreachable private
network.
l Volumes—The source and target should have identical drive mappings.
l GeoCluster—If you will be protecting a GeoCluster configuration, where data is
stored on volumes local to each node, there are several additional requirements.
l Operating system—The operating systems are limited to the Windows
Enterprise, Itanium, and Datacenter editions listed in the source and target
server requirements.
l Volumes—The source and target should have identical drive mappings.
l Hardware—Intel-based hardware is required. Microsoft support for MSCS
and MSCS-based Microsoft applications requires that the cluster
configuration appear on the Microsoft Hardware Compatibility List under
category Cluster.
l Cluster Network Name—Storage Mirroring Recover does not handle
dynamic changes to the cluster networknames, the names assigned to the
routes for network traffic. If a network name is changed for a network that is
used by a GeoCluster Replicated Disk resource, the resource must be taken
offline, the resource's network property must be changed, and then the
resource must be brought back online.
l Protocols and Networking—All of the networking requirements below must
be met.
l You must have TCP/IP connections between nodes.
l The cluster nodes must be members of the same domain.
l The cluster nodes must be on the same logical IP subnet.
l Your network can contain direct LAN connections or VLAN technology.
l The maximum round trip latency between nodes should be no more
than ½ second.
l Multiple networks are recommended to isolate public and private traffic.
l Forward and reverse lookups must be implemented on the primary
DNS server for the cluster name and individual nodes.
Page view 65
1 2 ... 61 62 63 64 65 66 67 68 69 70 71 ... 677 678

Comments to this Manuals

No comments