Jump to content

manual migration from VM to docker


Loke
Go to solution Solved by Luke,

Recommended Posts

Hello,

I have been trying emby in docker for some time and I decided to try and migrate my existing installation from a VPS to docker on a dedi.

I have read the instructions on the ~wiki and some threads here. I ended up:

  • just tar-ing all the contents of /var/lib/emby while emby on the VPS was shutdown via the webui
  • stopping emby container
  • erasing contents of the bind mount
  • dumping the tar in the host dir

It appears to work perfectly fine, users work fine, libraries and watched content is intact (I use mergerfs and kept the libraries paths the same).

So my question is, any reason I shouldn't have done it this way? Should I have preferred a more complex cherry picking of dirs and migrating data from the {old,new} sqlite DBs as I have seen in other threads?

cheers

Link to comment
Share on other sites

Just for the sake of discussion (if you got the time for it), is there another method that is considered better? Afaik it's just that or the backup plugin (which doesn't migrate everything).

Link to comment
Share on other sites

On 5/28/2022 at 6:55 AM, Loke said:

Just for the sake of discussion (if you got the time for it), is there another method that is considered better? Afaik it's just that or the backup plugin (which doesn't migrate everything).

Those are the two options.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...