Proper Collections Backup Strategy

[BuddahKat 17]

I have a question concerning the proper way to backup collections in Emby... I've seen other threads on this, especially since the 4.0 update, but still cant seem to get a good grasps on what is necessary. Is the collection information a part of what is backed up using the 'Backup' plugin? If not, I know the collection info is stored is in '\data\collections', so should I just back that up periodically?

 

More generally, if I use the backup plugin and store my metadata locally within the media folders, what else do I need to be backing up to ensure a smooth recovery if my PC crashes? Would it be wise to make a backup copy of the whole 'ProgramData' folder?? I know that's where chapter images and people images are stored, though I guess those are fairly easily recreated as long the media is preserved. I've read the backup wiki page but it seems a lot of emphasis is placed on the plugin so I just want to know what else is necessary. Thanks!

[Luke 42083]

Hi there, we have a brand new wiki article on this:

 

https://github.com/MediaBrowser/Wiki/wiki/Collections-%E2%80%93-Manual-Migration

 

Please let us know if you have any questions. Thanks !

 

@@cayars

[BuddahKat 17]

Yeh I saw that earlier... it's more focused on manually editing the collection info, whereas I just want to back it up properly. To answer my questions tho, I guess the gist is that the backup plugin is NOT backing up my collection info and that to properly do so I need to manually backup my 'data/collections' folder. Is that correct?

[Carlo 4561]

The super-de-duper way to backup is the old school way.  If for example you have everything installed on Drive C then use a conventional backup program and back up that volume.with Emby not running.

 

You could also setup a batch file to backup your Emby folder and all nested folders under it which would include your data/collections folder as well.  Then if you have "cache" location set to a different location (check the PATHS listing in the Dashboard) you could add that as another line in the batch file to backup.  Xcopy is great for this because it can use the "backup flag" and flip it upon the copy. Again, I'd do this with Emby shutdown.

 

Those methods work without plugins.

 

Those a just a couple of ways you can backup outside of Emby.  Emby itself offers a couple of plugins to help as well.

Server Configuration Backup

People Backup

 

These of course work while Emby is running and can be setup as scheduled tasks in the system.

 

I personally like the manual approach done once a week/month depending on how much new content you add or change things (like creating a bunch of new collections) combined with the use of the plugins. I like to do the "manual" approach before big Emby updates as well.

 

If you store your artwork and NFO settings with media, don't have a lot of collections made outside of BoxSets, etc then backing up might not be a big deal at all as the system can rebuild itself pretty fast.

 

How you choose to backup is a personal thing and could be different for each of us as we may have different needs.

[Luke 42083]

Correct the backup plugin does not handle collections at this time, although it's possible for the future. thanks.

[BuddahKat 17]

Awesome, thanks for the help and great suggestions!

[Carlo 4561]

Correct the backup plugin does not handle collections at this time, although it's possible for the future. thanks.

Luke, would you consider a new task that users could use to run scripts outside of Emby?

For example it would shutdown Emby and run said script process?

The script could start Emby back up again.

 

This would allow for scheduled backup one a week/month or whatever the user chooses to schedule.

 

OR provide a way to shutdown Emby externally from the command line or API. User could then schedule this type of thing outside of Emby but be assured of a proper shutdown.

[Luke 42083]

I would create a feature request topic. Thanks.

[Happy2Play 9783]

Luke, would you consider a new task that users could use to run scripts outside of Emby?

For example it would shutdown Emby and run said script process?

The script could start Emby back up again.

 

This would allow for scheduled backup one a week/month or whatever the user chooses to schedule.

 

OR provide a way to shutdown Emby externally from the command line or API. User could then schedule this type of thing outside of Emby but be assured of a proper shutdown.

 

Have you looked at systemservices in the api?  (/System/Shutdown)

[gortech 6]

Emby Team!  You amaze me!  What you've created and the level of assistance you provide is second to none.  Thanks for all you do for us.  Much appreciation. Cheers!