HP StorageWorks Storage Mirroring for Linux User's Guide (T2558-96317, June 2009)

4 - 2
 Storage Mirroring will not replicate the same data from two different replication sets on your
source. The data will only be replicated from one of the replication sets. If you need to
replicate the same data more than once, connect the same replication set to multiple targets.
 If you rename the root folder of a connected replication set, Storage Mirroring interprets this
operation as a move from inside the replication set to outside the replication set. Therefore,
since all of the files under that directory have been moved outside the replication set and are
no longer a part of the replication set, those files will be deleted from the target copy of the
replication set. This, in essence, will delete all of your replicated data from the target. If you
have to rename the root directory of your replication set, make sure that the replication set
is not connected.
 When creating replication sets, keep in mind that when recursive rules have the same type
(include or exclude) and have the same root path, the top level recursive rule will take
precedence over lower level non-recursive rules. For example, if you have /var/data included
recursively and /var/data/old included nonrecursively, the top level rule, /var/data/, will take
precedence and the rule /var/data/old will be discarded. If the rules are different types (for
example, /var/data is included and /var/data/old is excluded), both rules will be applied as
specified.
 Virus protection
 Virus protection software on the target should not scan replicated data. If the data is protected
on the source, operations that clean, delete, or quarantine infected files will be replicated to
the target by Storage Mirroring. If the replicated data on the target must be scanned for
viruses, configure the virus protection software on both the source and target to delete or
quarantine infected files to a different directory that is not in the replication set. If the virus
software denies access to the file because it is infected, Storage Mirroring will continually
attempt to commit operations to that file until it is successful, and will not commit any other
data until it can write to that file.