Need to recreate library on a new drive. Will playlists survive?

[micklord]

I need to move my files to a new drive. on my network. How do I ensure that my playlists live after I backup my library and move them to a new hard drive?

As a related question, where to the playlists reside? Inside the Sonos system somwhere? In the controller?

Thanks.

[buzz]

micklord,

First post! Welcome to the forums.

There are two types of playlists. SONOS Playlists are stored in the ZonePlayers, Imported Playlists are stored in the shared folders. As SONOS is updating the music library index, any playlists encountered in the shares will be imported.

Imported playlists are simply text files that can be created manually with a text editor or by a music library management program or utility. Some music management programs will automatically update the playlists after a move, some will not. If you keep the same folder structure in the copy, and your music manager will not update the playlists, you could update them manually with a text editor in a few minutes.

In many cases you can be clever and keep the same drive, share name, and folder structure on the new drive and, as long as only one drive is visible at any point in time, the SONOS system will not notice the move.

SONOS playlists may be more of an issue. The library indexing routine is very good at recognizing moves and simply dealing with them, but this is not an official feature and it is not foolproof.

[Ubertaffy]

FWIW and I know this isn't technically a feature, I recently moved all my music from one NAS drive to another and the root name DID change (something simple like Volume_1 to Volume_2) and yet all my sonos playlists did just fine.

[spoekplumpen]

I was really nervous moving my music library to another NAS, but once again - it just worked! All SONOS playlists are still intact!

Thanks to you guys @ sonos for making such awesome products!

PS. I even skipped one top level directory (the music used to reside in a directory called "sonos" - now it's directly under the share's root) and the new share's name was different from the old one. Still no problem