What to expect when pausing Remote Replication

Answer

The application has the ability for a user to pause backing up to a remote server by right-clicking on the system tray icon and selecting "Pause Remote Replication" from
the menu. Once remote replication is paused the user can resume the backup by right-clicking on the system tray and selecting "Resume all Replication".

The behavior of this pause operation varies depending on the capabilities of the remote target.

If the remote target is a file server or an Apache webdav server it can be paused indefinitely. After "Resume all Replication" is selected the backup will resume from where it left off.
If the application was paused while a file was being backed up then the backup of that file will resume from the point in the file where the backup left off.

If the remote target is a Tivoli Storage Manager Server (TSM server) or a Microsoft Internet Information Server (IIS server) then the connections being used to copy a file may expire while remote replication is paused.

If the user pauses remote replication while backing up to a TSM server or an IIS server, after a long period of time the application will indicate a "network error" by changing the "Remote Storage" icon on the gui from blue to yellow. This pop-up message may also be displayed :

The replication daemon has detected a network error condition that is likely correctable;
(Perhaps the network is temporarily not available, or, perhaps the current logon
information is incorrect). Please check access to the network yourself.
The system will keep waiting and retrying.

The amount of time that goes by before indicating a "network error" depends on server and client settings.

After indicating the "network error" the application will not resume the backup until the user selects "Resume all Replication". After "Resume all Replication" is chosen the software will continue the backup of the last file from the beginning of the file. Once this file is successfully transferred this message will pop-up:

The network appears to be functioning again.
The replication daemon will now resume.

and the "Remote Storage" icon will change from yellow to blue.

NOTE: Immediately after selecting "Resume all Replication" you may see the "Remote Storage" icon turn blue very briefly but it will turn yellow again and remain yellow until the file is completely and successfully backed up.

When the target is an IIS webdav server the backup of the file may not resume and the user will not see the "network error" indicated for a minimum of 8 minutes after the
the network error is actually detected. This is to give the IIS server time to error-out and remove the aborted file before the application transfers a new copy.
The length of time of this delay is controlled by the restart-delay setting in fpa.txt.

To set this setting: open Task Manager and kill FilepathSrv.exe, edit the fpa.txt file by adding:

<dav-config restart-delay="480"/>

just above the last line </fp-database> then reboot the system for the change to take effect.

The 480 indicates the number of seconds the application will wait after experiencing an error that indicates that a file transfer has been interrupted by a network error.
A user or administrator will only need to increase this setting if they see errors when the application resumes backing up a file to a webdav server after the"network error" is indicated.

In summary what the application does after pausing remote replication for an extended period of time depends on the target type. Here is a chart that summaries how different backups handle extended periods of pausing.

	File server	Apache WebDav server	IIS Webdav server	TSM Server
Pausing for a "long time" can cause the "Network Error" to be indicated.	No	No	Yes	Yes
After Resuming file backup resumes from where it left off.	Yes	Yes	No, the file transfer is restarted from the beginning after a minimum wait period. see: dav-config restart-dealy setting above	No, the file transfer is restarted from the beginning.