INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: messed up database because of new NAS  (Read 537 times)

tiggerkater

  • Recent member
  • *
  • Posts: 47
messed up database because of new NAS
« on: April 16, 2023, 12:15:09 pm »

hello everybody,

I have a problem with my jriver database and before making things even worse (don't know if that's possible ;) ), I wanted to ask (too late) for the best solution:

I moved my media files to a new NAS (old one nearly 10 years old) and mapped the new NAS drives in windows-explorer, disconnected the old nas-drive-letters.
I should have used the "Rename, Move, and Copy Files" tool, but did not, because i thought mapping the drives and then change the path in "auto-import" would suffice.

So I let JRiver auto-import a while before I realised what happend: The old NAS was still online (I know, my fault)

About one third of my files have two entries: old NAS and new NAS. (after that I stopped auto-import)

the other files have only the old file path (pointing to the old NAS).

should i change now all paths to the new (mapped) drive? (with the "Rename, Move, and Copy Files" tool) and then run auto import to remove the duplicate items? (and of course disconnect the old NAS from the network before this)?
or should I disconnect the old NAS an the just run auto-import again, to do its job?

and one last question: is it better to point to the mapped drive in auto-import, or use the direct address/path like:  \\synology-nas\etc...

thanks for helping! kind regards!


Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72438
  • Where did I put my teeth?
Re: messed up database because of new NAS
« Reply #1 on: April 16, 2023, 12:20:52 pm »

Consider restoring a backup.  MC makes them automatically.  [Wiki]
Logged

tiggerkater

  • Recent member
  • *
  • Posts: 47
Re: messed up database because of new NAS
« Reply #2 on: April 16, 2023, 12:32:48 pm »

thanks jim,
yes, i could do this. would you recommend this over only running auto-import? and after restoring i should only change the path to the files using "Rename, Move, and Copy Files"?

which path to the new nas would you recommend? the mapped drive or the network address?

thanks!
Logged

lepa

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2033
Re: messed up database because of new NAS
« Reply #3 on: April 16, 2023, 01:00:05 pm »

If your files are already in the new nas, unplug old nas and restore backup with timestamp before messing up (hopefully you have a recent one. Always do backup when starting something big or unsure)

https://yabb.jriver.com/interact/index.php/topic,134520.0.html
You can skip first step if the files are already moved
Logged

tiggerkater

  • Recent member
  • *
  • Posts: 47
Re: messed up database because of new NAS
« Reply #4 on: April 16, 2023, 01:27:50 pm »

thanks again,
i hope so, too :) and of course, i should have backed up right before...  ::)
Logged

tiggerkater

  • Recent member
  • *
  • Posts: 47
Re: messed up database because of new NAS
« Reply #5 on: April 16, 2023, 04:12:19 pm »

thanks everybody,
restoring worked and after that "Rename, Move, and Copy Files" as posted before. everything is working as it should!
thanks again!
Logged

lepa

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2033
Re: messed up database because of new NAS
« Reply #6 on: April 16, 2023, 04:45:31 pm »

Nice  8)
Logged
Pages: [1]   Go Up