Hi.

I've just read the backup procedure described in the faq and wondered why it's not possible to back up the dynamic data partition.
Can't I just use dd for that?

Also, would it be possible to back up the database/playlist/tags files along with the music files and restore them later instead of rebuilding them?

Of course I'm assuming that the empeg is running the same software version at restore time that it was running at backup time.

I've not personally done it but I don't see why you couldn't dump out the entire 32MB dynamic data partition and then restore it later on.

- Trevor

Yes, dd works fine for dumping /dev/hda3 and then restoring it later. I did this during my migration from my Mark 2 to the Mark 2a that I bought in the fire sale.

Not sure why it's not in the FAQ currently. For the FAQ master to add:

To backup the data: (Asuming drives are in RW mode for this)
dd if=/dev/hda3 of=/drive0/filenametobackupto

To restore: (drives do not need to be in RW mode)
dd if=/drive0/filenametobackupto of=/dev/hda3

So, then...

a) "dd" is already on the player as part of the developer build?

b) It will work with the command lines you described regardless of the number of drives or model of player?

c) You are backing up to a loose file on /drive0 and then later making a copy of THAT onto the PC somewhere?

a) "dd" is already on the player as part of the developer build?

Yep. It's a very low level command for Linux users, similar to having ls, cp and such around.

b) It will work with the command lines you described regardless of the number of drives or model of player?

Correct, since the dynamic data is always on the first (/dev/hda) hard drive.

c) You are backing up to a loose file on /drive0 and then later making a copy of THAT onto the PC somewhere?

Yes. I choose drive0 since it should have enough space to hold a 32mb file. To restore, the user would have to put that file back on the empeg somehow.

Also, would it be possible to back up the database/playlist/tags files along with the music files and restore them later instead of rebuilding them?

Sorry, forgot to answer this. The best way would probably be to just let the empeg rebuild the database. But, if you do want to backup the database, save and restore the files in /empeg/var named database, fids and playlists.

>> c) You are backing up to a loose file on /drive0 and then later making a copy of THAT onto the PC somewhere?

> Yes. I choose drive0 since it should have enough space to hold a 32mb file. To restore, the user would have to put that file back on the empeg somehow.

Why don't you just use hijack and ftp down /dev/hdaX directly ?

I have a nightly backup of my dynamic data partition for the last half year;
And I hope one day I can use this to create listening stats....

I have a nightly backup of my dynamic data partition for the last half year;
And I hope one day I can use this to create listening stats....


hmm, neat idea. i wonder if it would take long if we got the empeg to just store the initial dynamic partition, then make a compressed diff everyday (or even as a part of the player startup)... and storing it in the music partition. changes cant be more than 50k/day compressed.

[hint]if only someone would reveal the structure of the partition...[/hint]