HP Storage Mirroring Software - Manual (Page 20)

18 of 195
●
Cargo functionality—Review the following requirements, limitations, and
informational notes before using the archiving feature.
●
Archiving supports a one-to-one or many-to-one source to repository server
configuration. A one-to-many protection job is not supported for archiving
because if there were multiple links, the source would not know which
repository server to recall from.
●
Storage Mirroring Replicate will not archive the following file types.
●
System files
●
Alternate data streams
●
Encrypted files
●
Reparse points
●
Archiving is not a continuous process. It can be initiated manually or a
schedule can be established.
●
Only data that is being protected by Storage Mirroring Replicate will be
archived. If you exclude data when configuring your source protection job,
that excluded data will not be eligible for archiving.
●
Modifying the attributes of a link file on the source will not recall the contents
of the file from the repository server. The attribute changes will be replicated
to the copy of the file on the repository server, but the source will remain a
link file.
●
Storage Mirroring Replicate automatically creates a DTArchiveBin share on
the repository server for archiving activity. Do not modify the name or security
permissions of the share. If Storage Mirroring Replicate does not find the
expected share name and permissions, users will be unable to recall their
data.
●
The DTArchiveBin maintains the only copy of your archived files. You may
want to consider regularly backing up the copy of the data on the repository
server and the DTArchiveBin, for example to a tape backup.
●
When an archived file is deleted, the link on the source is deleted. The
archived content in the DTArchiveBin will be deleted also if there is an active
protection job present with replication enabled.
●
Briefcase files cannot be archived and will cause an error in the Storage
Mirroring Replicate log. These files should be added to the list of files
excluded from the archive process.
●
Cargo archiving is not compatible with TimeData continuous data protection.
If you use one, do not use the other.