Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Manni]

As the title says, whenever I do a manual library backup, it often displays a "Library backup failed" message instead of the success one. However, the backup file IS created even when MC says it has failed. The file is large (1.5GB), but apart from that there is no obvious difference between a failed backup file and a successful one.

I attach two logs, one for a successful backup, one for a failed one.

I did one after the other: the first backup was successful, the second failed, the backup files are near identical (I assume both successful).

[Manni]

Anyone?

I'm getting this error all the time, from two different PCs. Every time the backup is made, but for some reason MC throws the "backup failed" error.

Also, I tried to restore the library, but despite the thumbnails being included (include thumbnails in backup option checked), they were not restored, so had to be re-generated.

On another attempt, the thumbnails were restored.

[Awesome Donkey]

There might be an issue in MC34 with restoring thumbnails that I reported on Mac that Hendrik fixed, though it might be an issue on all platforms. You'll have to see if the next build fixes it for you.

[Manni]

There might be an issue in MC34 with restoring thumbnails that I reported on Mac that Hendrik fixed, though it might be an issue on all platforms. You'll have to see if the next build fixes it for you.

Thanks. Weird if I'm the only one to get this "Library backup failed" with two different PCs. Anyway, the backups seem to work, so it's only an annoyance.

[Matt]

Are settings files in the backup? I think that's what is failing but I don't know why.

[Manni]

Are settings files in the backup? I think that's what is failing but I don't know why.

Hi Matt,

Yes, I think so, though the settings are saved too, as when I restore it restores the settings as well as the library.

Can anyone reproduce this with build 24, or is it just on my two PCs?

I can test to run a backup without the settings to confirm it's this causing the error.

[Matt]

Does it make any difference if you pick a really simple filename like C:\Back.zip?

It tries to save settings, but fails to add to the ZIP file for some reason.

Thanks.

[Manni]

Yes, it works fine if I save it to D:\
I'll change the backup path to a shorter one, but you might want to take a look to see why it fails with a long (but valid) path.
I guess that automatic backups don't include the settings, that's why there are no problem with these?
Talking of which, is there a way to disable automatic backups? My library is 1.5GB, so it adds up quickly...

[Matt]

Yes, it works fine if I save it to D:\
I'll change the backup path to a shorter one, but you might want to take a look to see why it fails with a long (but valid) path.
I guess that automatic backups don't include the settings, that's why there are no problem with these?
Talking of which, is there a way to disable automatic backups? My library is 1.5GB, so it adds up quickly...

Well that helps. What is the full path it's failing on?

[Manni]

The full path was the default path, but My Document is within Dropbox, so that's quite long (sorry no backslash on my mini keyboard):
D:/Users/Em/Dropbox/Documents/JRiver/Media Centre 34/Library Backups plus the auto/default backup name.

[Awesome Donkey]

That could be why, I imagine folders synced with Dropbox and OneDrive can cause issues when trying to create library backups. I've seen OneDrive cause all kinds of issues with some apps when it's syncing files and folders.

[Manni]

That could be why, I imagine folders synced with Dropbox and OneDrive can cause issues when trying to create library backups. I've seen OneDrive cause all kinds of issues with some apps when it's syncing files and folders.

Yes I'm aware (I stopped using Onedrive a long time ago for that reason, it was aweful), but that's not the issue here as Dropbox is usually much better behaved (unless you are handling thousands of small files that are inter-dependent on each other, like with Scrivener).

Anyway, with MC the backup file is always created. It's just adding the settings that throws an error for some reason (but the backup file is fine). So it's more an annoying message than anything else.

I think it has more to do with the path length, as Matt suggested.

[Awesome Donkey]

If it's path length that can easily be tested with a similar folder. Like in the D:/Users/Em/ folder create a Testing folder (same amount of characters as Dropbox) then inside that create a Documents then JRiver then Media Center 34 then Library Backups folder and repeat the library backup test.

If it still happens in the Testing folder then you can eliminate Dropbox as a possible cause and it could very well be a path length issue, however if it doesn't happen with a Testing folder but does with the Dropbox folder, it's likely Dropbox.