Skip to main content

We have recently noticed that the download folder on the mobile web server has grown to approx 150GB and is taking up a significant amount of the space on the disk. 

 

 

Upon investigation it appears that these image and document files migrate to the m5 attachments folder which we maintain on a dedicated file share server and are accessible through the FSM client.

There was an idea submitted related to this that was denied:

Change to files saved to the Downloads folder in the Mobile server.

 

In the absence of a proper systemic way of dealing with this folder (e.g. to purge the files after X days), are there any best practices or guidelines on how to manage this folder besides just adding disk space?

Thanks,

Richard

Hi Richard,

the Downloads folder on the Mobile Server is used for streamlining the Users Mobile Database as well as Attachments. Upon device initialization the mobile database will be created on the App Server (or some other destination as you set it in the MOBILE_DATABAE_DIRECTORY app param) and then streamed to the Downloads folder on the Mobile Server. The Attachments will be streamed from the folder specified in the ATTACHMENT_DIRECTORY app param to the Downloads folder on the Mobile Server. Afterwards the device can pick it up from there. More on this also in the FSM6Mobile documentation.

Thus, the data in the Downloads folder becomes obsolete after it’s synced to the device, and you should be fine with cleaning up the folder occasionally. However, if you run a deletion while a device is trying to fetch data it will get stuck. As there is no official guidance given in the documentation, you may want to raise a Case in the Support Portal.

Best regards
Roman

Reply


Terms & ConditionsCookie settings