Jump to content

How to move part of the database to a new volume on the server


Recommended Posts

Posted

Hello,
I manage a large database (Emby Server with >10,000 files in 10 libraries) on a QNAP NAS. The first volume of the NAS (100 TB) is almost full. I plan to add and expansion as a new separate Volume. Would it be possible to move some of the libraries to the new volume while keeping the database structure and data ? How?
Thanks!

Posted

Hello olivierduc,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:


Thank you.

Emby Team

Posted

Hi, you will need to remove the old path and add the new one. There isn't a pure database way of doing this at this time, although we recognize the need for this and plan to add it in future updates. Thanks.

Posted

The proposed method is sub-optimal: it implies to rebuild the database for the moved libraries, which it lengthly when you have got thousands of entries.

Gilgamesh_48
Posted
On 12/24/2024 at 10:11 AM, olivierduc said:

Hello,
I manage a large database (Emby Server with >10,000 files in 10 libraries) on a QNAP NAS. The first volume of the NAS (100 TB) is almost full. I plan to add and expansion as a new separate Volume. Would it be possible to move some of the libraries to the new volume while keeping the database structure and data ? How?
Thanks!

Actually it is quite possible and pretty easy.

1. Get you new volume set up.
2. Do not remove anything from the library settings.
3. add the new directory to the library path, changing nothing else.
4. Move the files to the new location.
5. Scan the library, if it does not happen automagically.
6. after the scan is fully complete you can remove the old path from the library and scan again.

What should happen is that the new paths will replace the old paths to the files and nothing in the database should change. Be aware the what you want is for any library scan that happens finds the files in one of the two locations. I have done this several time and I never had to do much to the database or even to fix anything. But my experience is with smaller databases.

Be sure that you allow all scans to complete before you remove any path as there is a lot of behind the scenes stuff that is don on a scan.

BTW: This works even better if you had set up the metadata and images to be stored with the media.

 

  • Like 1
Posted
3 hours ago, olivierduc said:

The proposed method is sub-optimal: it implies to rebuild the database for the moved libraries, which it lengthly when you have got thousands of entries.

I understand and apologize. It's just what is currently available.

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...