HP OpenView Storage Mirroring User Guide (360226-002, May 2004)

11 - 4
5. Source shares are created on the target allowing shared resources on the source to be accessible on the target machine.
Any drives shares that existed on the target prior to failover are stored so that they can be reestablished after failback.
6. Failover sends updates to routers and other machines with IP to MAC address mappings allowing clients to seamlessly
attach to the target machine. All user and application requests destined for the source machine are routed to the target
machine.
7. If specified, a post-failover script executes on the target. This script is user-defined and optional. This may be used to
start services that will be needed after the target assumes the identity of the failed source. Scripts can also send network
messages notifying administrators that failover is complete.
8. Failover is complete.
How Failback Works
1. The network administrator disconnects the failed source machine from the network and repairs it.
2. The network administrator manually initiates failback.
3. If specified, a pre-failback script executes on the target. This script is user-defined and optional. This may be used to stop
services on the target that will not be needed or may be in conflict after the target reinstates its own identity. Scripts can
also send network messages notifying administrators that failback is about to occur.
4. The source’s identity is removed from the target or the mapped aliases and drives are removed.
5. For Windows, shares created on the target during failover are deleted. Any original shares that existed are restored.
6. Failback sends updates to routers and other machines with IP to MAC address mappings. This mapping is now the
original mapping before failover occurred. At this time, users may see a pause at their workstations while the failback
process completes.
7. If specified, a post-failback script executes on the target. This script is user-defined and optional. This may be used to
start services that will be needed after the target reinstates its own identity. Scripts can also send network messages
notifying administrators that failback is complete.
8. Failback is complete and you are given the choice to continue monitoring the source machine.
9. The original source machine can be reattached to the network.
10. If specified, a post-failback script executes on the source. This script is user-defined and optional.
11. Failback is complete.
NOTE: When replicating data using Storage Mirroring, only shares that are within the Storage Mirroring
replication set will be created on the target machine during the failover process. Shares outside of the
replication set will not be created on the target.
NOTE: Users who were using the name or address of the source machine were actually attached to the target
machine and will lose their connection to the server at this point.
WARNING: After the source machine is back online, if you need to restore the data on the original machine by
mirroring data from the target’s copy of the replication set, do not let users logon to the source until the
restore process is complete.