Large data files can often exist on an FME Server instance but these don't always need to be retained during a backup/restore, or included in a Project. It would be great to have the option to exclude specific files to reduce the size of a backup/restore or Project.
Currently backup/restore is an all or nothing affair, so it may be opening up a can of worms to include this functionality but Projects do allow for specific content to be defined for Resources, but only to the folder level.
My current use-case is that I have a Project defined with multiple items, including a Resources folder. I need the content of the Resources folder but there's a 6GB file in there that I don't need and it's causing my download to fail because I don't have that much empty space on my hard drive....
I agree, all or nothing backup & restore option is not usable in our case when we upgrade. We have a 2 TB filesystem and backing up the filesystem to migrate doesn't make sense, when we can just point our new server to the existing file system. We still need backup and restore to backup our system configuration and anything that is not stored in the filesystem, so it would be really nice to have such an option where we can choose to backup objects/modules stored in the database separately from the filesystem.
Hi. Here is the tricky part if we allowed you to select items within a Resource Folder to exclude, if the Resource Folder contains a large number of items—7000 for example—it would make the UI crash unless we added pagination and then a search filter. The suggested workaround as of 2023.2. is to add the Resource Folder to the Project, then just before export remove the large file, perform the migration and then add the file back in. Not ideal. Maybe you could move the large file to object storage such as AWS S3 so then you don't need to migrate it.