HP Storage Mirroring Software - Manual (Page 15)

Storage Mirroring Data Migration requirements Page 14 of 135
the drive where the encrypted file is located is out of space, when it actually
may be the location where the temporary file is trying to be created that is out
of disk space.
6. If you are using mount points, keep in mind the following.
a. By default, the mount point data will be stored in a directory on the target.
You can create a mount point on the target to store the data or maintain the
replicated data in a directory. If you use a directory, it must be able to handle
the amount of data contained in the mount point.
b. Recursive mount points are not supported. If you select data stored on a
recursive mount point, mirroring will never finish.
7. Storage Mirroring Data Migration supports transactional NTFS (TxF) write
operations, with the exception of TxF SavePoints (intermediate rollback points).
a. With transactional NTFS and Storage Mirroring Data Migration mirroring,
data that is in a pending transaction is in what is called a transacted view. If
the pending transaction is committed, it is written to disk. If the pending
transaction is aborted (rolled back), it is not written to disk.
During a Storage Mirroring Data Migration mirror, the transacted view of the
data on the source is used. This means the data on the target will be the
same as the transacted view of the data on the source. If there are pending
transactions, the Storage Mirroring Recover Target Data State will indicate
Transactions Pending. As the pending transactions are committed or
aborted, Storage Mirroring Data Migration mirrors any necessary changes to
the target. Once all pending transactions are completed, the Target Data
State will update to OK.
If you see the pending transactions state, you can check the Storage
Mirroring Data Migration log file for a list of files with pending transactions. As
transactions are committed or aborted, the list is updated until all transactions
are complete, and the Target Data State is OK.
b. During replication, transactional operations will be processed on the target
identically as they are on the source. If a transaction is committed on the
source, it will be committed on the target. If a transaction is aborted on the
source, it will be aborted on the target.
c. When failover occurs any pending transactions on the target will be aborted
before the source identity is assigned to the target.
d. Storage Mirroring Recover restore functions as a mirror, except the roles of
the source and target are reversed. The transacted view of the data on the
target is restored to the source. As pending transactions are committed or
aborted on the target, Storage Mirroring Recover restores any necessary
changes to the source. Once all pending transactions are completed, the