Backuptask crashed

[uiharu]

@girish I'm also facing a similar issue with my ~600GB nextcloud instance. I'm backing up to a (physically separate) minio instance, both tgz and rsync results in crashes. How may I further investigate? Are there instructions for doing manual backups? Thank you.

[uiharu]

I finally upgraded cloudron by switching to no-op

[necrevistonnezr]

relates to the discussion here: https://forum.cloudron.io/topic/1288/support-encrypted-rsync-backups-to-onedrive-dropbox-etc/7

I think Cloudron would benefit greatly from a working encrypted backup solution....

[timmmmyboy]

FWIW switching to rsync fixed the original issue of this thread in my case. Figured I'd update here to let folks know.

[girish]

@uiharu As you probably know, Cloudron always takes a complete app backup because updating an app. Overall, would you prefer that Cloudron have an option to disable backups a per-app level or would you prefer the backup to actually work?

[uiharu]

@girish ofc we need a working (reliable) backup mechanism!

imo the current disable option is already good enough and allows me to easily go around backup errors that prevent upgrades etc.

Maybe...

• differential backup/hard-linking support for some remote backup destination will help with stability
• btrfs, zfs offers more stable snapshots and should be supported in the future

[necrevistonnezr]

If I was to push an rsync cloudron backup to a remote location, it should be sufficient to backup the "snapshot" folder, correct? not the folder named "2018-05-XX-XXXXXXXX" as well.

[girish]

@necrevistonnezr yes, correct. The snapshot directory is the "working directory" for backups. It gets rotated as-is into the timestamped directory. For filesystem, you will notice that the files between snapshot directory and time stamped directory are hard-links.

[necrevistonnezr]

@girish
rcloning the "snapshot" directory works. However, I'm getting two errors:

2018/06/04 13:57:51 ERROR : Attempt 3/3 failed with 2 errors and: invalidRequest: nameContainsInvalidCharacters: Path (/LiveFolders/cloudron/205.oDD_s5s39188-3p61-1336-5p10-p26tp62t1oo5/154.qnGn/134.uJGwLA/19.ilohv/251.cmkxxoBZBy/1.ZkzsoBuBkw PsxkxJox Exn foBCsmroBExq ) contains invalid trailing character.

2018/06/04 13:57:51 Failed to sync: invalidRequest: nameContainsInvalidCharacters: Path (/LiveFolders/cloudron/205.oDD_s5s39188-3p61-1336-5p10-p26tp62t1oo5/154.qnGn/134.uJGwLA/19.ilohv/251.cmkxxoBZBy/1.ZkzsoBuBkw PsxkxJox Exn foBCsmroBExq ) contains invalid trailing character.

Is that problematic in a case of restore?

[girish]

@necrevistonnezr What rclone backend are you using? It looks like rclone is complaining that the backend does not like having files with a trailing whitespace.

[necrevistonnezr]

@girish I'm using the Onedrive backend via the crypt backend (https://rclone.org/crypt/) and obfuscated file names.

[necrevistonnezr]

@girish I also realized that the mysqldump for the TT-RSS app is huge (679 MB in my case). Could you implement some compession in the database dumps (and use PostgreSQL as recommended by the author)?