Question about emby server behavior in situation when you not saving metadata to own media folders and you lost for some time access to your library storage.

[Mdaloha77 5]

So I found out that in situation when path to the media defined in emby library is not accessible(for example emby start sooner than file server and system running emby are not abble to mount media data sources) emby delete all cached metadata. After recovering from this by mounting media sources to emby server, emby starts to download all metadatas from scratch which is insane if you have a few TB of media files.

There should by a mechanism which will bound cached metada to specified library and until library or media files in it is manually deleted those data should stay on disk. You may ask why not go for saving data in own media folders. Well thats not a solution for me, because I dont want any external process to mess with my library and have write access to it.

[ebr 16199]

Hi.  This is exactly why we have the option to save the metadata with the media.  If you don't want to use that option then you have some trade-offs like this situation.

2 minutes ago, Mdaloha77 said:

There should by a mechanism which will bound cached metada to specified library and until library or media files in it is manually deleted those data should stay on disk

Emby is designed to be self-maintaining.  That means that it reacts to the contents of your file system instead of you having to go and "import" or delete things manually.  So there is really no way for the system to behave the way you are suggesting without the data consumption potentially exploding and never going down.

The mechanism to do what you are looking for is to save the metadata with the media.

[Happy2Play 9785]

At the same time just because a set library path is not available at a specific time should not purge all of the said data for that media (offline mode).  It should only be purged if the path is removed from library management.

[Mdaloha77 5]

5 minutes ago, Happy2Play said:

At the same time just because a set library path is not available at a specific time should not purge all of the said data for that media (offline mode).  It should only be purged if the path is removed from library management.

Yes, sir. Im not asking for nothing more.

[GrimReaper 4763]

11 minutes ago, Happy2Play said:

At the same time just because a set library path is not available at a specific time should not purge all of the said data for that media (offline mode).  It should only be purged if the path is removed from library management.

TBH, I took it for granted that it was designed in that way?

[ebr 16199]

19 minutes ago, Happy2Play said:

At the same time just because a set library path is not available at a specific time should not purge all of the said data for that media (offline mode).  It should only be purged if the path is removed from library management.

I think we already attempt to do that to an extent but Luke will have to comment on the exact current implementation.  Its a lot trickier than you might imagine.

[Carlo 4561]

I'm not sure why it should be hard.  If the mount point entered in the library is active the drive is alive.  If the mount point doesn't exist assume the drive is offline and not touch the contents of that mount point.

[Mdaloha77 5]

3 hours ago, cayars said:

I'm not sure why it should be hard.  If the mount point entered in the library is active the drive is alive.  If the mount point doesn't exist assume the drive is offline and not touch the contents of that mount point.

Exactly my point...

[Luke 42089]

Let's look at an example. Please see how to report a problem:

Thanks !