Jump to content


Photo

We need a simple REAL 100% Migration & Why save metadata with media is bad!

migration metadata nfo database

  • Please log in to reply
30 replies to this topic

#21 BAlGaInTl OFFLINE  

BAlGaInTl

    Advanced Member

  • Members
  • 681 posts
  • Local time: 02:03 PM

Posted 15 January 2019 - 11:43 PM

 
There is always one final But :)

 

Yes it is going closed source, yes this has been talk about a lot and yes it is a deal breaker for some.

 

I see you are already over on the Jelly reddit page and they look to be engaged with your post.

https://www.reddit.c...ation_why_save/
 

Also on their dev discussion page about your issue:

https://view.matrix.....org&offset=180

 

Plus Luke as said from what I can see that your migration scenario has been addressed in the latest V 4.0 of Emby.

 

So really you have a bunch of people listening to you and taking on what you are saying  :)

 

Certainly seems to be handled um... "differently" in that dev discussion.



#22 kaizo OFFLINE  

kaizo

    Member

  • Members
  • 10 posts
  • Local time: 07:03 PM

Posted 16 January 2019 - 02:33 AM

Plus Luke as said from what I can see that your migration scenario has been addressed in the latest V 4.0 of Emby.
 
So really you have a bunch of people listening to you and taking on what you are saying  :)

You are right, as im getting more and more information it seems that things are going in a good direction :)
Hmm, when the news about going closed source is true, will there be a collboration with other forks or will everything be devided from now on?
 
 

Only if you enable nfo metadata saving, which is off by default.

Well we've always had this. This is the default and has always been. Local metadata saving has always been off by default.

Wait a minute. So that would mean that im a pretty unlucky guy. Because these options where turned on automatically by default after i ran some update (can't remember which one it was) But i have to admit that i have my installation for a long time now. This fact made me open this thread in the first place. Maybe everything was big unlucky accident. Thanks for the clarification Luke.
 

You cannot move the installation across operating systems because there are native binaries built specifically for each OS & cpu architecture. What you can do is move the contents of the server's program data folder, since that's really what you're after anyway.

Yeah thats right. I meant only moving the databases and datafiles without the server binaries across multiple plattforms.



#23 sfatula OFFLINE  

sfatula

    Advanced Member

  • Members
  • 335 posts
  • Local time: 01:03 PM
  • LocationCalera, OK

Posted 16 January 2019 - 03:40 AM

Can all the nfo metadata files simply be purged via a find command after migration and emby index? Does emby suck that nfo data into it's database? If so, there's a possible path.

#24 BAlGaInTl OFFLINE  

BAlGaInTl

    Advanced Member

  • Members
  • 681 posts
  • Local time: 02:03 PM

Posted 16 January 2019 - 08:15 AM

Can all the nfo metadata files simply be purged via a find command after migration and emby index? Does emby suck that nfo data into it's database? If so, there's a possible path.

 

I think one the bigger issues for the OP was that Emby started modifying nfo data that they had set the the way they like. As I'm reading, he/she wants the nfo, but just to keep an old one.  Basically, without Emby ever modifying anything in the media file folders.



#25 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 46041 posts
  • Local time: 02:03 PM

Posted 16 January 2019 - 10:07 AM

Hmm, when the news about going closed source is true, will there be a collboration with other forks or will everything be devided from now on?

 

The exact same people who have been working hard on Emby for the past several years still are and will continue to be.  Thanks.


  • BAlGaInTl and neik like this

#26 Kewjoe OFFLINE  

Kewjoe

    Newbie

  • Members
  • 5 posts
  • Local time: 02:03 PM

Posted 22 January 2019 - 03:27 AM

Right, ideally, this would have been possible with older versions, but we have found issues with them relating to this. Thanks.

 

Is there a recommended approach to "refreshing" an install so that I can be sure I can restore it in the future? or am I asking for a long of headache? I've had Emby installed (via Docker) for years, so I assume my installation would be included as one that would not fall under the "can be moved anywhere" with a fresh 4.0+ install. I'm wondering what it would take to start fresh and yet not start from scratch. If i followed the manual backup instructions with a fresh install, would that remove any remnants of the old installation?



#27 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 134369 posts
  • Local time: 02:03 PM

Posted 22 January 2019 - 03:53 AM

Is there a recommended approach to "refreshing" an install so that I can be sure I can restore it in the future? or am I asking for a long of headache? I've had Emby installed (via Docker) for years, so I assume my installation would be included as one that would not fall under the "can be moved anywhere" with a fresh 4.0+ install. I'm wondering what it would take to start fresh and yet not start from scratch. If i followed the manual backup instructions with a fresh install, would that remove any remnants of the old installation?

 

It really depends. What version are you on now? What version did you originally install? 

 

I will have to review, but once you've upgraded to 4.0 you may be good to go after that, because the database upgrade will help with this.



#28 Kewjoe OFFLINE  

Kewjoe

    Newbie

  • Members
  • 5 posts
  • Local time: 02:03 PM

Posted 22 January 2019 - 10:29 AM

It really depends. What version are you on now? What version did you originally install? 

 

I will have to review, but once you've upgraded to 4.0 you may be good to go after that, because the database upgrade will help with this.

 

I'm on 4.0.1.0. I have no idea where I started. As mentioned, it has been years ;) I have a backup server. When i find some free time, I'll try to restore there and see if it goes well.



#29 cayars OFFLINE  

cayars

    Advanced Member

  • Alpha Testers
  • 2937 posts
  • Local time: 02:03 PM

Posted 22 January 2019 - 10:52 AM

So in essence, this solution already exists. Just not a direct path to it from old versions.

@kaizo, so they aren't ignoring... the improvement you are seeking is already there.

Everything that you are describing that you don't like that Emby does, to most, is the essence of what a media server does. It organizes and updates everything automatically. Seems like what you want is just a media viewer instead of a complete management system. Nothing wrong with that, it just isn't what Emby is. Setting everything to read only by Emby eliminates many of its finest features. One of my biggest use cases is as a PVR. That wouldn't be possible if Emby was read only.

 

There is a way around this that can give you the best of both worlds.  Most OS have either built in or 3rd party the ability to POOL drives.  Thus you can access all your media via one mount point or drive letter.

 

In doing this all you have to do is be a bit creative.  For example on Windows with DrivePool I can set my actual media drives as READ-ONLY to everyone but the administrator (me who puts the media there).  Thus no program ran as another user can delete this data.  BUT THEN I add another drive to this pool that has WRITE access.

 

Now I've got a POOL that Emby/Plex (whatever) can write to for storing images, NFO, etc but can't delete or touch my actual media.  Since you only allow one drive to have this WRITE access it's the only drive where the posters, NFO, etc will be stored.  To Emby ALL THE DATA is there in one folder but in reality this is on different drives. 

 

Now before an update or anything else I think could radically change my posters or NFO I can easily make a copy of that WRITE Drive parent folder.  It's not going to be big like my media drives!

 

BEST OF BOTH WORLDS because you can keep your media locked while still allowing the use of NFO and locally stored posters (with an easy way to backup).  No more fighting with Emby to get the features you want/need.


Edited by cayars, 22 January 2019 - 10:56 AM.


#30 stuartsjg OFFLINE  

stuartsjg

    Advanced Member

  • Members
  • 50 posts
  • Local time: 06:03 PM

Posted 26 February 2019 - 07:52 PM

I agree, and going forward, if you install 4.0 fresh, you will be able to pick up the installation and move it around as much as you like.

 

Is this applicable to the windows server or all versions?   I have yet to get emby working properly since changing back in October.



#31 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 134369 posts
  • Local time: 02:03 PM

Posted 27 February 2019 - 12:55 AM

4.0 wasn't released until January. I've removed the parts of your post that are not related to backup, which is what this topic is about. We will help you in your freebsd topic. thanks.


  • stuartsjg likes this





Also tagged with one or more of these keywords: migration, metadata, nfo, database

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users