(05-20-2025, 11:43 AM)DarcyMullen Wrote:(08-20-2024, 04:01 AM)kjones120320 Wrote: Adding a second NAS at a different location can significantly improve your backup experience compared to using external USB drives. But there are more routes to choose from. Usually it's a good thing to diversify storage, I'm not sure if Hyper backup supports cloud options and not just other NAS, but an ideal set up would be NAS to cloud or NAS to NAS to cloud, for example. There are solutions like Nakivo that easily integrate with Synology to allow you create automated workflows with a much better user experience.dead plate
You're absolutely right to consider the benefits of diversifying your backup strategy.
Great solution but first problem with it. Any ideas on suggest next steps?
I am similar: (FYI 423+ NAS hyperbacks-up to 415+ offsite-has been great for months)
Got some messages. Wondering if hyperbackup will just make the file again or...?
• "Checksum mismatch on file [/volume1/BackupDestination/Media.hbk/Pool/chunk_index/1319.idx]"
Source 423+ HB hasn't tried destination 415+ again, yet, maybe it will fail? I am currently running SMART Extended and scrubbing before I try anything else.
FYI Likely Cause: Failed drive sectors and subsequent failed SHR:
• Original/initial backup finished OK as was its Integrity Scan, SMART Quick Scan, and Data Scrubbing. (good for many months)
• Got dozens messages in minutes: "I/O error at md0 disk [3], serial [....] sector... has been corrected"
• Got message "Storage Pool [1] degraded [3/4 of drives remaining]. Please repair it"
• Swapped out Bad drive 3 and rebuilt SHR (I didn't even try and do a SMART or IronWolf Scan on bad drive)
• During SHR rebulid, checksum mismatch message above appeared
• Got message: Files with checksum mismatch have been detected on a volume. Please go to Log Center and check the file paths of the files with errors and try to restore the files with backed up files.
Suggestions? Next Steps? Any ideas why this happened, why didn’t it stop using the bad drive etc.