HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)
738 of 739
modifying existing files, creating new files, deleting files, and changing permissions and
attributes.
1. On the source, browse through the directories and files.
2. Select four data files from your source and record the file name, date, time, and file
size for each file.
3. On your target, locate those same four files that you just identified on your source.
The files on the target match the files on the source.
4. Back on your source, view the contents of one of your data files and note the file
contents.
5. On your target, view that same file that you just viewed on the source. The file
contents on the target match the file contents on the source.
6. On your source, edit the file that you viewed above and save your changes.
7. Modify the other three files so that the date, time, and/or size is updated.
8. Verify the changes that you made on the source have been applied to the target
copy of the file.
Note:
Because of the way the Windows Cache Manager handles memory,
machines that are doing minimal or light processing, as you are in this
evaluation, may have file operations that remain in the cache until
additional operations flush them out. This may make Storage Mirroring
Recover files on the target appear as if they are not synchronized. When
the Windows Cache Manager releases the operations in the cache on the
source, the files will be updated on the target. To make sure this does not
impact your testing, flush the cache by copying a couple of files from one
directory to another and then deleting them.
4. Simulating a failure
To fully evaluate failover, you need to simulate a failure. To do this, power off the source.
Watch as the status changes to Failover condition met.
5. Starting failover
When a failover condition is met, you will want to start failover. You can actually start
failover without a failover condition, as long as protection is enabled. For example, you
may want to force a failover when upgrading to a better source server.
Note:
If you are testing failover and your source is a domain controller, do not let the
domain controller communicate with any other production domain controllers
after failover. Otherwise, when the original source domain controller is brought
online after the test, it may create a USN rollback scenario if the test domain