You are here: Double-Take RecoverNow requirements > Cargo requirements

Cargo requirements

In addition to the source and repository server requirements, the following requirements apply to the Cargo archiving feature.

Operating system and file system—The following operating system and file system requirements apply to archiving.

You must use the NTFS file system. FAT and FAT32 are not supported for archiving.
Transactional files on Windows 2008 are not supported. Any request for a recall within a transaction will generate a sharing violation error and the recall will not occur. The application can open and read a byte outside of a transaction to cause the recall to occur and then proceed with the transaction.
Do not modify the system attributes on any file or folder. Incorrect system attributes could case data to be skipped for archiving, or it could cause source crashes because the full system files must remain available on the source.
Because the archiving feature uses the file access date and time, do not disable the Windows system setting that updates file access date and time. If this setting is disabled, the archiving functionality will not behave as expected.
Archiving can only be performed on non-system volumes. (The system volume is where the Windows system files are located.)

Network configuration—The following network configuration requirements apply to archiving.

The source and repository server should be member servers in a domain environment. If you want to use Double-Take RecoverNow in a workgroup, you will need to create an account with the same name and credentials on all servers. Use that account like you would an Active Directory account.
The source can be a domain controller as long as Active Directory and system data is not selected for archiving.

Security—Specific archiving security configuration must be completed before using the archiving functionality.
Anti-virus—You must configure your anti-virus software to skip archived files or the archived files will be recalled during virus scans. Additionally, you must configure your anti-virus software so that the Double-Take RecoverNow application is a low-risk process. Configure the low-risk processes so that they do not scan when writing to or reading from the disk. If you need assistance configuring your anti-virus software, see your virus software documentation. Keep in mind that your anti-virus software may refer to archived files differently, for example, offline, migrated, or sparse files.
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.
Double-Take RecoverNow will not archive the following file types.

Archiving is not a continuous process. It can be initiated manually or a schedule can be established.
Only data that is being protected by Double-Take RecoverNow 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.
Double-Take RecoverNow automatically creates a DTArchiveBin share on the repository server for archiving activity. Do not modify the name or security permissions of the share. If Double-Take RecoverNow 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.
Briefcase files cannot be archived and will cause an error in the Double-Take RecoverNow 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 or Atom file-level deduplication. If you use one, do not use the other.