Hi all,
We run FSM 6 Update 29 on-premise, with the Mobile Service on its own server in our DMZ. The Mobile Service download folder has grown to about 85 GB and nearly 100k files, and nothing in it ever seems to be removed.
We've compared our setup with the U29 baseline database and can't find any scheduled process or app parameter that manages this folder. MOBILE DEVICE CLEANUP removes old device records and their messages from the database, but it doesn't touch the files on the Mobile server.
From what we can see, the folder holds:
- cached attachments (plus .zip copies of older ones)
- device init databases (PERSON__DEVICESEQ.zip). Every init seems to get a new device sequence and old ones are never removed, so one user has 25 of them going back to 2021.
- image zips
- a few hundred .tmp files left over from downloads that seem to have been interrupted
How do other on-premise customers handle this?
1. Do you clean up this folder, and if so, how (a scheduled script, an IFS-provided job, a setting)?
2. Has anyone deleted old init database zips? We expect they're only needed until the device finishes initialising.
3. Has anyone purged cached attachments? A missing attachment doesn't seem to be fetched again when a device requests it. It only seems to come back when the attachment is synced to the device again, so we're wary of deleting them. What did you see on the devices?
4. Has anyone else seen leftover .tmp files stop an attachment from being cached again (the device gets a 404)?
Thanks!