Backup Errors

[joseph]

The error message itself is coming from the service that you are backing up to. Since you mentioned synology, does it have some s3 logs?

[pdrupp]

Hey joseph, thx for your reply. No this error is when backing up using Cloudrons Backup Module to Wasabi S3. The Synology makes a complete VM Backup in the background, no errors there. I hadn't activated logging in S3, i will change that and run a new backup.

[pdrupp]

I'm thinking about the possibility that the length of the encrypted filenames might be too much for Wasabi... I'll dig deeper...

[james]

@pdrupp did you ever resolve this issue?

[pdrupp]

@james Hi james, in the end i attached a second storage to the vm and configured to backups using ext4 and rsync. This works better. I still get regular cp exited with code 1 signal null errors but currently i can live with that. I set my backup schedule to every 2 hours, if every 2nd backup fails with this error, i still have 6 backups per day.

[james]

Hello @pdrupp
Thanks for the follow-up.
So this is not really "solved" but "worked around".

If this issue is still this appeared even with a second storage directly backing up to ext4 with rsync, would you be willing to access to your system to the Cloudron team can look into it?
Access would be requested when the team has time.

I know that the team is currently very busy with the release of Cloudron 9, which also brings a lot of features and fixes to the backup system.
Might be already resolved with that.
So, after the release of Cloudron 9, could you please report back here if this issue persists?

[pdrupp]

@james Ok let's see what Cloudron 9 brings

[humptydumpty]

@james said in Backup Errors:

So, after the release of Cloudron 9,

Any clue on the progress made so far? ETA?

[james]

@humptydumpty

Soon™

[james]

Closing this issue for now.
Please report back when Cloudron 9 is released and this is still an issue.