Today's Useless Error Message of the Day™ is brought to you by Synology who should know better. From their Hyper Backup app: "Failed to backup applications."

That's it. I have to guess which app and why. It turns out that I removed the VPN app yesterday, which Hyper Backup knew when I checked what it was backing up. It told me VPN was invalid. So WTF didn't it put that important piece of information in the logs?!

Man some major companies sure hire lazy programmers.

#Synology #HyperBackup

Had to ditch VersityGW and go back to Garage to get my Dad's Synology NAS to use it as a S3 backup target.

It would auth and find the bucket, but not move on from there.

Luckily I was planning to use Garage on the real remote target, but was trying out VersityGW on my "Snowball"

https://blog.hardill.me.uk/2026/05/08/building-a-snowball/

#S3 #Synology #HyperBackup

2/2
Es gibt aber eine REST-Api für kDrive auf die man Zugriff hat. Also kurzerhand einen WebDAV Wrapper dafür gemacht mit Multi-Tenancy-Support (für die anderen Konten der Familie) und in einen LXC im Heimnetz gepackt. Jetzt können #Synology #CloudSync und #HyperBackup per #WebDAV mit kDrive reden.

Falls das jemandem weiterhilft, hier die Links:
https://github.com/thoros1179/kDriveWebDAV
https://codeberg.org/static_null/kDriveWebDAV

#UnplugTrump #Synology #CloudSync #HyperBackup #Infomaniak #myKSuite+ #kDrive #WebDAV

GitHub - thoros1179/kDriveWebDAV: A WebDAV wrapper layer for the Infomaniak kDrive REST-Api with multi-tenancy support.

A WebDAV wrapper layer for the Infomaniak kDrive REST-Api with multi-tenancy support. - thoros1179/kDriveWebDAV

GitHub
@Diogenes #HyperBackup is awesome! Depending on the size of the backup, and the NAS model it could take time, but it will do the job.

@tsherrygeo Manually via #HyperBackup, or not at all via any Syno package? Also, "Synology backup" means data on your NAS, or you want to backup "some" data onto the NAS itself?

Default HyperBackup with its GFS versioning should work out of the box with no issues. So the question really is what is your exact current setup that makes the backup not the most stable one?

#Synology's #HyperBackup: "We got an I/O error on one file so we're going to abandon the entire backup and leave your data unprotected. You're welcome."

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

In case you thought Arq Backup had useless error messages, I bring you today's example from Synology Hyper Backup 4. There is no indication what caused this or what I'm supposed to do about it, therefore useless.

#ArqBackup #Synology #HyperBackup

Immerhin .. Backup Server neu aufgesetzt. #Bareos läuft wieder und auch noch das kaputte #Synology #HyperBackup, was per #rsync lief - und nun nicht mehr - auf S3 und #Minio auf dem neuen Backup Server umgestellt / eingerichtet.