Applies to: Official administrator relocation workflow; backup recommended

The useful distinctions

  • The documented procedure disables automatic emptying of trash first.
  • The server is stopped while content is copied.
  • The new location is added while the previous library location remains.
  • The old location is removed only after the new content is verified.

Plan the transition as two valid states

A relocation is easier to reason about when the old arrangement remains available while the new arrangement is checked. Record the old and new roots, the intended library and a few representative items before copying. Preserve a backup of server state as well as media. This makes it possible to distinguish a failed copy from a catalogue-association problem if the transition does not behave as expected.

Verify the copy before retiring it

Check that the new location contains the intended files and is visible to the server in its normal runtime context. Then inspect representative paths in the library after the new scan. A directory listing alone does not establish that the application can use the same location. Complete one library at a time so an error has a limited scope and the verification remains understandable.

Delay final cleanup

Do not remove the old configured root merely because the new scan has started. Wait until the expected associations and access have been checked. The synthetic migration note includes an ordinary film and a television item as examples of different layouts worth reviewing. Treat emptying trash and deleting the old media copy as separate final decisions with their own recovery consequences, after the relocation has been accepted.

A focused way to proceed

  1. Back up server data and disable automatic emptying of trash.
  2. Stop the server and copy authorised media to the new location.
  3. Start the server and add the new folder to one library while retaining its old folder.
  4. Scan and verify the new files and catalogue associations.
  5. Remove the old library location only after verification; review trash separately.

Worked example · synthetic

Library: Local Movies
Old root: /media/archive-old/Movies
New root: /media/archive-new/Movies
Pilot checks: one single-file movie; one movie with local subtitles
Cleanup: only after new paths and associations are verified

Read the comparison

A scan may associate new paths with existing items; verify the actual result before retiring old storage.

When to stop or ask for help

If associations differ, preserve both locations and server backup while reviewing the official relocation steps.