1a. preparing a new source by reinstalling windows, 1b. reusing your source, 1a preparing a new source by reinstalling windows – HP Storage Mirroring Software User Manual
Page 514: 1a preparing a new, Source by reinstalling windows, 1a preparing a new source by, Reinstalling windows, 1b reusing, Your source, Preparing a new source by reinstalling windows
Failback and restore
Page 513 of 677
remaining instructions.
Note: If possible, you can attach any virtual hard disks that survived the
failure event to a new virtual guest. Reusing any undamaged disks
will decrease the time required to restore data because you can use a
difference mirror.
As an alternative to manually creating a new virtual guest, you can let
Storage Mirroring Recover automatically provision (create) the new
virtual guest for you. If you choose this option, you will need to use the
instructions for Storage Mirroring Recover
and
instead of the instructions in this section.
l
Reusing virtual guest—If the failure did not damage the virtual guest and
you want to reuse it, start with
and then continue
with the remaining instructions.
1A. Preparing a new source by reinstalling Windows
1. Install or reinstall Windows on your physical or virtual server using unique,
temporary server information. See your Windows documentation for details on
installing the operating system.
2. After the operating system installation is complete,
using the activation code from your original target.
3. After Storage Mirroring Recover is installed, continue with
from the source to the original or new source and failing over
.
1B. Reusing your source
1. Disconnect the original source from the network. For a physical server, you may
want to disconnect the network cable. For a virtual server, remove it from the
network using your virtual console. You must make sure the original source is
completely disconnected before proceeding.
2. After the original source is disconnected from the network, remove the target server
identity from Active Directory. You should remove the target's original identity, not
the identity of the source which the original target hardware now holds.
3. Keeping the original source disconnected from the network, reboot it and login as
the local administrator.