FRP is a server based product and to offer all features it must reside in the Operating system of the drives at both ends.
A NAS or SAN does not support the installation of the FRP client therefore, real time replication from the NAS, compression, encryption and some other features are disabled on the NAS.
A further condition for connection to a NAS is the use of a UNC path or mounted volume on other OSes, windows drive mappings are not supported to a NAS.
While Real Time events can't be detected on a NAS or SAN, Normal repeating jobs can be run since scheduled jobs read the directories rather than rely on real time file system events.
In the scenario where your business requirements call for real time replication, we recommend a "near realtime alternative": a repeating job with a high frequency such as every 1 or 2 minutes. This will cause the logging of more jobs in the FRP logs, but the impact to system resources is pretty low.
Some NAS setups have a low level of Windows integration. It is possible that your NAS system will not work with FRP. Please make use of our 45 day unrestricted trial copy to test with your NAS or SAN prior to purchase.
To attempt working with a NAS or SAN Network Attached Storage device, use the UNC Universal Naming Convention path to the drive. In many cases this will work.
Sample of a UNC path:
\\ComputerName\SharedFolder\Resource
For your server selection select any server in the dropdown list. This field must be populated, however with the use of the UNC path
it is not important which server you select.
For more information
This may be critical to your success: If FRP refuses to see the device when you use the UNC path during the job validation, FRP may be
running on a system account without rights to see the device\path. This is particularly a concern on Windows servers where FRP is running as a service.
By default, windows runs services under a local system account and not under the account you use to login in from. You can change the account used
by the FRP services using the properties windows or through the SC command.
Follow these steps:
First verify that you can browse the path on the device with the account you are currently logged in as.
When you have proven that your account can see the device and path, then stop the FRP services,
change the account FRP is running on to match your currently logged in account, and restart the FRP services.