Hey all - just wondering if anyone else has had the same issue as me.
My current backup solution is to run multiple Hyperbackup tasks to an offsite Synology with external hard drives plugged into it. (The synology internal disks are used as a space for snapshot replication for current projects)
So I will tons of video footage organized by year. Each year is its own backup task which points to a ‘usbshare’ external hard drive formatted as exfat on my remote Synology.
Over time, all backup tasks have failed and now display as “Destination Corrupted - Restore Only”
I recently deleted the entire backup, started from scratch, and created new tasks. Within a week they had all failed again. I am thinking maybe it’s because the files are stored on an exfat volume instead of BTRFS, so the single 8-12tb .HBK file is highly likely to get corrupted.
Just wondering if anyone had any thoughts on this, thanks!
Maybe the best option for me is to skip the Hyperbackup altogether and just copy my archived video files to external drives as a backup and store them offsite - as they won’t be changing over time anyway.
I use a 4TB SAN Disk attached to my NAS for Hyper Backup. It is formatted ext4 and has proved to be very reliable with no issues encountered with data loss.
@reissigree I don’t have a solution, but I just wanted to piggyback off of your comment to say that I’m experiencing the same issue.
I currently backup my DS923+ to a USB external drive, and recently all my integrity checks have been resulting in “Destination Corrupted - Restore Only”. Even when I delete the existing task and create a new one, it will eventually revert to “Destination Corrupted - Restore Only”.
I’ve restored some of the files, and everything seems fine. The USB drive is less than a year old and passes all health checks. I’ve also tried several memory tests with Synology assistant, and no issues there either.
Did you have any luck with the link @NewLeaf shared? Seems like it has helped a lot of people. I tried it, no luck though. Might revert to using USB Copy instead of Hyper Backup.
I did not try that fix mentioned in the other forum. In my mind - even if it works to fix the Backup Task, it seems like it would just fail again - considering what we have experienced with HyperBackup corrupting even brand new backup tasks. Seems like maybe a recent update to HyperBackup itself is causing this as I’ve used this for years without issue.
My backups are 10-12TB, and my offsite location is 2 hours away - so recreating a task is quite a pain.