by SFA » Fri Dec 21, 2018 12:23 pm
I have a Synology NAS running on WIndows. The PC to NAS connection is VIA Wi-fi with the NAS connected to the network using a cable to a Wi-Fi range extender because cabling directly to the router is not an option.
I rarely use a catalog.
The NAS connection is OK but in general communicating with the NAS is not fast. Even the USB 3 NAS direct connection for copying from a self powered drive is not fast.
Is it possible that what you are seeing is a problem with a database lock file on the NAS that is not being removed when the catalog close process is run? There could be a problem, for example, if the backup process (either within Capture One or something on the NAS) either fails to complete or is still running when you try to open the catalog again. (Or the system thinks it is still running.)
If anything delays a process the lock file may exist for longer than expected.
If the process that sets the lock file is, for some reason, killed by some other process the lock file would never be removed.
My NAS also seems to have a habit of going into so me sort of ECO mode. I would like to think that it only does this when nothing important is running in its internal processing but sometimes it seems that might not be the case.
My NAS installation is quite basic. No backup to another device on the network. No backup to an external cloud service.
When I work with a Capture One session on the NAS things usually work OK but there are times when, for whatever reason, activity slows down. A session can also be locked to avoid multiple users trying to access it as the same time but I have not often seen this short term problem. However I usually work with files on internal drives. The NAS is for backup and archived work. If I need to access an archived session I will do so on the NAS but this is not part of my day-to-day activity. In that way I mostly avoid the possible NAS problems in my set up.
I hope this may suggest a few ideas to investigate for you own setup.
Grant