Hi all,
Encountering an issue when trying to pull a file from one server to another. I’ve never seen this path before ‘fm-images’, but it is designated as the backup container folder in the client’s admin console.
Hey Amy,
Welcome to the community,
That error looks like its being passed back from the fmsadmin command. A quick search of the “invalid name” error led me here which suggests that there may be some conflicts with your folder names? Is the default backup directory a parent or sub-folder of the default databases directory?
-Kyle
Hi Kyle,
Thank you for your quick response. It seems the paths are different for backups vs databases. Is this the problem? It doesn’t seem to be a problem when the FMS takes a backup.
Ok interesting. Is the default backup folder (the one ending in “Data/Backups2/backups”) symlinked to that fms-images folder or something similar? OttoFMS is resolving the paths to their “real” path, and it looks like in this case the “Backups2” folder might be mapped to that “fms-images” folder somehow.
Kyle
Hi Kyle,
I don’t actually have access to their server directly (hence Otto). The below is from their IT:
fm-images is a linux mount that represents a RAID linked device that has storage available.
The default backup folder path contains a symbolic link to fm-images/backups. The location these backups go to is the only location on the server with a significant amount of storage available:
I believe it was done as a symbolic link, rather than simply specifying /fm-images/backups directly, because FileMaker Server “didn’t like it” if memory serves.
I suspect what happened is that FileMaker is not resolving the paths when it does it check to see if a folder is a child or parent of another. My recommendation would be to move the container data to a subfolder of the fm-images folder (ie. have fm-images/containers and fm-images/backups).
When OttoFMS creates the folder structure for the File Browser it creates symlinks to a number of folders. Symlinks cannot be created to another symlink, which is why we resolve the paths to their actual path. Once we’ve resolved the paths the check that FileMaker has to prevent making backups to a subfolder of the database or container data folders now works properly, which is giving you the error.
-Kyle
1 Like