Hp Storage Mirroring V5 Software Bedienungsanleitung PDF herunterladen (Seite 142)

18 - 1

18 X Restoration and Failback for High Availability

Restoration and Failback for High Availability

With a high availability connection, failover occurred because the target was monitoring the source for a failure, and when a

failure occurred, the target stood in for the source. User and application requests that were directed to the failed source are

routed to the target.

While the users are accessing their data on the target, you can repair the issue(s) on the source. Before users can access the

source again, you will need to restore the data from the target back to the source and perform failback. Failback is the process

where the target releases the source identity it assumed during failover. Once failback is complete, user and application

requests are no longer routed to the target, but back to the source.

Ideally, you want to restore your data from the target back to the source before you failback. This allows users who are

currently accessing their data on the target because of failover to continue accessing their data. Restoration before failback

reduces user downtime. The procedure to restore and then failback varies widely with server and network configuration.

Another method, which may be easier in some environments, allows you to failback first and then restore the data from the

target to the source. A possible disadvantage to this process is that users may experience longer downtime, depending on the

amount of data to be restored, because they will be unable to access their data during both the restoration and the failback.

Restoration then failback

Restoration before failback allows your users to continue accessing their data on the failed over target, which is standing in

for the source, while you perform the restoration process. The key to this process is to keep the users off of the source, but

allow the source and target to communicate to perform the restoration.

1. Resolve the problem(s) on the source that caused it to fail. Make sure in resolving the problems, that you do not bring

the source on the network at this time because the target currently has the source’s identity because of failover.

2. Disable all of the NICs on the source.

3. Change one of the NICs on the source to a unique IP address that the target can access.

4. Configure that IP address so that it does not automatically register with DNS. This option is on the Advanced TCP/IP

Settings dialog box on the DNS tab.

5. From the Management Console on the source, login to the source by right-clicking on it and selecting Login. You will

have to login to the local machine, not the domain.

6. Once you are logged into the source, disconnect the source to target connection by right-clicking on it and selecting

Disconnect. If you have any issues with disconnecting the connection, you can also delete the connect.sts file from the

Storage Mirroring installation directory on the source.

7. Do not enable the modified NIC yet. If you do, you will receive a network name conflict, because the target has the

source’s identity because of failover. There are many variations for dealing with a name conflict, here are a few examples.

 Enable the modified NIC, knowing you will get the name conflict error. Disregard the error. Change the source name

to a unique name in the domain and reboot when prompted.

 Change the source name to a unique name in a workgroup, not in the domain, and reboot when prompted. Enable

the modified NIC.

 Stop the Workstation and Server services on the source. You may be prompted to stop other services. Stop those

services also and note the service names for later. Enable the modified NIC. The server will not broadcast its name

to the network because of the services you disabled.

8. Stop any applications that may be running on your source. The files must be closed on the source so that updated files

from the target will overwrite the files on the source.

9. At this point, confirm you have the following configuration.

 Your target is standing in for your source because of failover, and users are accessing their data from the target.

 Your source is back online with a unique IP address and no network name conflicts.

 The source and target can communicate with each other.

 All applications on the source are stopped.

1 2 ... 137 138 139 140 141 142 143 144 145 146 147 ... 211 212

Kommentare zu diesen Handbüchern

Keine Kommentare

Hp Storage Mirroring V5 Software Bedienungsanleitung Seite 142

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Lager Hp Storage Mirroring V5 Software