"Failed to export the system configuration" since DSM3.2

[Jahislove]

Hello

since my upgrade to dsm 3.2 all my backup are in error.

the error is "Failed to export the system configuration"

the backup are from disk 1 to disk 4 inside the Syno (DS 411J)

any idea ?

[Jahislove]

answering to myself :

since 3.2 , local backup can't use space in destination directory name.

[cantabrian]

since 3.2 , local backup can't use space in destination directory name.

Thanks so much for this, Jahislove... an enormous help.

I very annoyed with Synology that they made this change, didn't publicise or flag it, but most of all that the information in the so-called "logs" was so woefully inadequate and non-descriptive.

[fastcat1]

Yes, same thing happened to me after the DSM3.2 upgrade. So is there a solution?
Yes, I agree the backup log is not very descriptive.

thanks!

[dclancy]

Is there any fix so we can do our backups?

Dan

[collaborator]

I have exactly the same problem. Hope Synology support gives response to this.

[collaborator]

What does this mean ? or How can it help to solve the issue ?

I have scheduled back up job which backs up "photo" folder to a conneted USB HDD (USBSHARE1)root.
Even though I deleted scheduled backup job and created from scratch I still get the same error.

answering to myself :

since 3.2 , local backup can't use space in destination directory name.

[inian]

Hello

I had exactly the same error when trying to backup something. The reason was third party packages, to be more specific - Python, Sickbeard and SABnzbd. They are creating users which DSM doesn't like for some reasons... The solution was to remove packages and then to install them again. Now everything works just fine.

[collaborator]

My problems solved after I have upgraded to 3.2 - 1944

What does this mean ? or How can it help to solve the issue ?

I have scheduled back up job which backs up "photo" folder to a conneted USB HDD (USBSHARE1)root.
Even though I deleted scheduled backup job and created from scratch I still get the same error.

answering to myself :

since 3.2 , local backup can't use space in destination directory name.

[gormac]

I had exactly the same error when trying to backup something. The reason was third party packages, to be more specific - Python, Sickbeard and SABnzbd. They are creating users which DSM doesn't like for some reasons... The solution was to remove packages and then to install them again. Now everything works just fine.

Same problem here with DSM 3.2-1955 and removing Python and SABnzbd packages worked for me as well. Backup is currently running. Will re-install packages after backup finishes to see if next backup will succeed after re-installation.

[ariestav]

I'm also getting this error for my local backups to an external USB drive connected to my DS1511+ running DSM 3.2-1944, and I really cannot upgrade it for the next week or so.

I installed gitolite as a git hosting server, and thought that might be the problem, but I don't see how it could be--although to run the system, I had to create a new user named `git`. Could that be the issue?

I contacted tech support, and they said it was the drive, and that I should format it, and then it will back up again. I did that, but the backup failed.

Please, if anybody has any information as to how I can get the backups to work that would be greatly appreciated.

Thanks,
Arie