You appear to be using external storage of container field data. That part of the Server backup is not re-performed except when the container data changes, so the Server keeps the container data that it backed up earlier and keeps it hard-linked to the new backups so everything stays intact.
This is a good thing, not an error, as long as only older container data is retained with the new backups.
1 of 1 people found this helpful
I have spent the last two weeks with support on exactly this and today they accepted it was a bug that QA could reproduce (Backup issue Filemaker Server 12 Error 685 [Case: 121121-000208]). I did not even need to send an example db.
I'm told turning external storage off and then back on may fix this but this is not something I can easily test as in my case the records are syncronized and for some 'difficult to understand' reason FM mark each record as changed when you change where the container stores it's data.
Lets hope it is fixed in the next release.
PS I found that some of my .jpgs in the folder did get deleted and that FMS stopped in a different file each time. In addition it was always the two folders that were most recent that could not be deleted. ie FMS could delete them on the third attemp
Yes, I am using external storage of container field data, but I have other databases in the same server with the same configuration and the data is erased when a new backup is made.
Thank you for your answer, Crispin.
I am happy knowing that I am not the only one. This bug is driving me crazy.
There have been other reports of older backups not deleting, and that is a reported bug. However, your first post indicated that it was just the container data which was not deleting, and that's not a bug if it still valid container data which should be hard-linked to the latest backup files.
These are two different issues, though I suspect the actual bug is also related to the new handling of container data by the server software. Since the FM team has indicated they are looking into this, we can hope that a server update will fix it soon, although this was first reported prior to the latest FM12 Server update.
I have just turned external storage off and then back on but it hasn´t fixed the problem. :-(
I wouldn't expect a toggle of the storage option to change the backups. They still hard-link to the container data. It might change if you were to turn off external storage, then stop the FMServer, and then run another backup. Once you turn external storage back on, I would expect the same hard-link structuring of backups to cause the same effect again.