Consider the requirements in this section before you configure Dynamic File Services pairs:
Dynamic File Services supports the NTFS file system for the primary and secondary locations in pairs.
For cloud storage, Dynamic File Services works with the native storage technology used by the provider. It maintains information about the ACLs and other metadata for files stored on secondary cloud storage locations in retention pairs.
Devices that the system considers to be native storage devices can be used for the primary path and the secondary path. This includes Fibre Channel, iSCSI, and direct-attached storage devices (internal or external). The devices must be online and available to the Dynamic File Services server when you create, manage, and use the pair.
For iSCSI devices that are hosted in a cloud, we recommend that the device be used only for secondary paths.
The native storage devices used in a pair must have a static drive letter assigned so that the drive letter remains the same through server restarts. If you plan to change the drive letters or modify paths, you must unlink the paths by removing the pair definition, and create a new pair that uses the new locations.
Dynamic File Services does not support using CDs, DVDs, floppy drives, or flash drives in a pair. It also does not support using mapped drives.
Remote storage is supported for the following pair configurations:
Standard Pair: Secondary path. A local path is required for the primary in order to provide merged access to the files.
Retention Pair: Primary path or secondary path.
The remote path can be a network share on either of the following target storage locations. It is not necessary for Dynamic File Services to be running on the target location.
Any Windows Server running an operating system that is supported by DynamicFS
Network attached storage or a network filer (such as NetApp and EMC)
IMPORTANT:To avoid potential data loss and conflicts, use only dedicated volumes when using remote paths.
A remote share must be online and available to the Dynamic File Services server when you create, manage, and use the pair.
For an Active Directory environment, the remote share must be published in Active Directory and must reside in the same domain/forest as the Dynamic File Services server. For configuration requirements, see Section 4.9, Using Remote Shares in an Active Directory Domain.
For a Workgroup environment, the remote share must exist in the same workgroup as the Dynamic File Services server. For configuration requirements, see Section 4.10, Using Remote Shares in a Workgroup.
Cloud storage is supported as the secondary path in a retention pair. You must set up an account with your preferred cloud provider and authorize the Dynamic File Services software to interact with the files stored there on your behalf. For information, see Section 11.0, Creating and Managing Cloud Accounts.