Let Infuse use a NAS as the backup point

Let Infuse use a NAS as the backup point for all configs, metedata, etc.


I suggested same in original thread. Store metadata on source in an SQL database. That would be not a big size too.
It could be an option: store metadata in iCloud or on Source.

1 Like

Storing on NAS can be either es local XML files or SQL database (setting on same NAS), just let schema known, allow to add address and use local SQL base for all data storage.

1 Like

Agreed. We need a way to backup metadata. Storing them in the cloud doesn’t seem to retain that information, resulting in having to edit metadata several times because metadata is being wiped out.

Seems like this would also make migration to a new drive easier.

This would be better then doing a cloud sync backup as well. +1 for this.

Just now, for no reason at all, I closed Infuse, then opened back and all my watch history, and even images, got wiped :frowning:
Ability to save metadata on NAS would be really big help with this.


Being able to backup infuse would be awesome

Have had it happen on a few occasions where all library content, etc is lost

1 Like

+1 this would be huge

1 Like

I second this 1000% as trying to make the updates across multiple devices to fix thumbnails and such is painful when I have everything on my local NAS. you can then either have a setting that allows multi-master or designate one device as the main editor if changes need to be made.

+1 :slight_smile:

That would be great if you could do that please.

So, James… what are your thoughts on giving us this option?

James? What do you say?

Backing up your metadata to a hard drive is a suggestion that’s been around for years. I’ve read a few older messages, but I saw no reason given why It’s not possible, or why it’s not been added.
All the recent problems with wrong or missing metadata would have been fixed by restoring a saved backup. This would be an improvement over iCloud and not to replace current methods but as an additional option.
Hope this feature appears in some future update.

I would also like to see this added. It seems like storing backups and image caches to a Samba share would be relatively simple.

I will also re-iterate that we need better control on clearing metadata and deleting files that are not metadata (e.g. subtitles).

Also also would like to see this added. Store metadata, including images etc. in a target folder, like a SMB share, FTP or whatever Infuse supports as a source of media.


I have a question: Is it possible, to store the actual Metadata and covers from movies and TV-Shows on the NAS in the corresponding Folders?

So I don’t have to create a XML-File for each movie an TV-Show, because Infuse could create this file. So I could use this Info on different accounts (I have 2 ATV4 with different accounts), connecting to the same NAS. With this Feature I could organize and optimize the library on one account, store all data on the NAS and the second device could load this Information automaticly.

Thanks a lot for this great Software!


While there are multiple ways or ideas on how to keep track of video file metadata (I am more interested in watched/not watched since all images are stored on the same NAS as actual video files and there is no need to download them from anywhere and save locally) they all have some issues.

Local data saving sometimes got deleted by Apple OS to clean some space while holding data on iCloud (or any other online place) require you to be online for that to work and at some point will expect you to pay for that cloud service because free version will not be enough.

There is another simple way how to sort such problem - save data locally into the SQL database. All that is needed for that is to know schema that Infuse uses and username/password for your local database.

This might be more advanced user feature because of the need to know how to set up that database, etc., but on the other hand, it can give a unique opportunity to such advanced users because they would be able to create they own software to interact with the same database for whatever needs they require.

I would assume that adding direct SQL support is more straightforward than adding metadata storage in iCloud, while the user base for that functionality might be much more limited, but what such users could get out of it would be more beneficial.

1 Like

Why doesn’t Infuse use a global database (SQLite for example) which is stored on the server? Would certainly be much more efficient than every user always has to go through a scan to get the same results that another user had already received.

You could create a global database on the server, where all informations about all files/movies/series are stored. Then you can also manage which users have access to which shares/libraries.

The eternal scanning is annoying, especially when the pages that are used for metadata take a long time to respond. Also, an initial scan of a large library takes an extremely long time when a new device or a new user uses Infuse and he must then manually correct all incorrectly recognized movies and series again.

The whole data processing of Infuse is not efficient, not up to date and also not well thought out. There is really extreme potential for improvement, since years.

1 Like