Hp Storage Mirroring V5.1 Software User Manual Page 18

  • Download
  • Add to my manuals
  • Print
  • Page
    / 27
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 17
5 - 4
Missed intervals—By default, the target can miss five (5) responses from the source before
assuming the source has failed. If desired, increase or decrease the number of responses that
can be missed before the source is identified as failed.
Pre-Failover Script and Post-Failover Script—If you want to execute a script on the target
before failover (Pre-Failover Script) begins or after failover has occurred (Post-Failover
Script), specify the path to the script on the target. You can also search for the script by
clicking Browse. The script will be processed using the same user account that is configured
to run the Storage Mirroring service. Scripts may contain any valid Windows command,
executable, batch, or script file. The Pre-Failover Script will be executed as soon as the
failover process is initiated. The Post-Failover Script will be executed after the failover
process ends and the target has been rebooted.
Network Mapping—Specify how you want to handle network configurations on the target after
failover.
Apply source network configuration to the target—If you select this option, the source
IP addresses will be failed over to the target. The IP addresses associated with each NIC on
the source will be mapped to the NIC you specify on the target. If the source has more NICs
than the target, some of the source NICs will not be mapped to the target, or the target NICs
may need to be used for more than one source NIC. If there are more NICs on the target than
the source, the additional NICs will still be available after failover. If you are using a LAN
environment, you should select this option.
Retain target network configuration—If you select this option, the source IP addresses
will not be failed over to the target. The target will retain all of its original IP addresses. If your
target is on a different subnet (typical of a WAN environment), you should select this option.
The following options are available if you want to update DNS.
DNS ServerThe source’s primary DNS server is selected by default. If desired, you can
select a different DNS server.
Source Server IP—Select the IP address from the source that you want to remap to an
IP address on the target.
Target Server IP—Select an IP adddress on the target that will be replace the source IP
address in DNS.
Username—Specify a user that has privileges to access and modify DNS records. The
account must be a DNS Admin for the domain in which the DNS server resides. You can
enter a user name for a different domain by entering a fully qualified user name. The fully
qualified user name must be in the format domain\username or username@domain. If
you enter a non-qualified name, the DNS domain will be used by default. The domain
name is obtained from the DNS server name, provided that reverse lookup in DNS is
enabled.
Password—Enter the password that is associated with the specified user name.
After you have entered the DNS information, click Test to validate that DNS is configured
correctly and that the specified credentials are sufficient to update DNS. When the DNS
configuration is complete, click OK to save your entries and return to the Configure
Protection window.
Route—By default, Full-Server Failover will select the default route for transmissions. If desired,
select a different IP address on the target that will be used for Full-Server Failover transmissions.
NOTE: Together, the Monitor interval and Missed intervals settings determine the
total time before failover would be triggered. For example, five missed checks
every five seconds would be 25 seconds to trigger failover. To achieve shorter
delays before failover, use lower values. To achieve longer delays before failover,
choose higher values.
NOTE: If you are protecting a cluster node and select Retain target network
configuration, the virtual IP addresses associated with the cluster will still be
failed over. The only IP address that will not be failed over is the physical IP
address of the cluster node.
Page view 17
1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 26 27

Comments to this Manuals

No comments