Backup file (for example, the zip file) path could be wrong if it is left blank on the System Configuration page.įor example, if the Backed-up Files Directory field entry is left blank (empty), the path in the FlowPort_Backup zip files could be wrong.This problem has been fixed in this patch. zip file gets too big, the FlowPort server may run out of memory and may hang up. Zip utility will run out of memory if the backup file gets too big.įor example, if the backup.

This patch ensures that if the backup time (3:00 PM) is ahead of the current time (2:00 PM), and the backup period is set to 'daily,' then the backup will happen on the same day at 3:00 PM. However, the next backup did not happen until 3:00 PM on the following day. Changing backup time does not cause the next backup to happen as expected.įor example, before this patch was created if you changed the backup time to 3:00 PM and the backup period was set to daily, and the current time is 2:00 PM, you expected the next backup to happen at 3:00 PM on the same day.This patch will make sure that an immediate backup is done if FlowPort starts up and finds one or more scheduled backups were missed. If the same process is repeated every time during the scheduled backup time, a backup would never happen. If FlowPort was shut down manually before a scheduled backup time and then started again after the scheduled backup time, that particular backup would be skipped. Backups are skipped if FlowPort is down during the scheduled backup time.įor example, before this patch was created a backup would happen as scheduled as long as FlowPort was running.The following is a list fixes implemented with FlowPort BackupPatch_2_1_2_56.jar fp212p02 patch: The installation instructions, as well as all fixes, on this patch are listed in the Readme file that is zipped with the downloadable patch. NOTE: This patch only applies to FlowPort version 2.1.2.56 (SP1). DocuShare Enterprise Content Management.

Service pack backup files