HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

590 of 739
● If you rename the root folder of a connected replication set, Storage Mirroring
Recover 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 /data included recursively and /data/old included
nonrecursively, the top level rule, /data/, will take precedence and the rule
/data/old will be discarded. If the rules are different types (for example, /data
is included and /data/old is excluded), both rules will be applied as specified.
● Including and excluding files
● Do not exclude Microsoft Office temporary files from your replication set.
When a user opens a Microsoft Office file, a temporary copy of the file is
opened. When the user closes the file, the temporary file is renamed to the
original file and the original file is deleted. Storage Mirroring Recover needs
to replicate both the rename and the delete. If you have excluded the
temporary files from your replication set, the rename operation will not be
replicated, but the delete operation will be replicated. Therefore, you will
have missing files on your target.
● When Microsoft SQL Server databases are being replicated, you should
always include the tempdb files, unless you can determine that they are not
being used by any application. Some applications, such as PeopleSoft and
BizTalk, write data to the tempdb file. You can, most likely, exclude
temporary databases for other database applications, but you should consult
the product documentation or other support resources before doing so.
● Some applications create temporary files that are used to store information
that may not be necessary to replicate. If user profiles and home directories
are stored on a server and replicated, this could result in a significant amount
of unnecessary data replication on large file servers. Additionally, the \Local
Settings\Temporary Internet Files directory can easily reach a few thousand
files and dozens of megabytes. When this is multiplied by a hundred users it
can quickly add up to several gigabytes of data that do not need to be
replicated.
● Creating replication sets that only contain one file may cause unexpected
results. If you need to replicate just one file, add a second file to the