mferraro

My current setup - Server Computer with Core 2 Duo, 4GB RAM - Retrospect 9.5.3 ; 3 executions running - Daily Snap shots stored to a ReadyNAS Pro with 10GB storage (RAID 6x2TB drive) - Weekly offsites to a USB 3.0 external HDD. Uses a PCIe USB3.0 card Backup sources - One windows server - one Synology NAS cluster acting as a file and SVN server. - 25+ client workstations. Several workstations average 10GB. Some people have 8+ years of email in outlook PSTs The ReadyNAS has a power supply failure 3 weeks ago, and two drives fail in one night. I need to do a complete overhaul of both the daily onsite and weekly offsite cloud storage has been taken off the table My first thought at a solution for the server + onsite http://www.abmx.com/1u-nas-server .. then i could have a powerful server with the RAID array built in. I already had a dedicated NAS and server for the backups; why not combine into one piece of hardware? Recommendations?

I'm using 9.5.3.103 I'm running a Groom job now to see if it identifies any RDB files. Last groom showed no errors Grooming Backup Set New Win2003... Groomed 24.1 GB from Backup Set New Win2003. 4/11/2015 3:45:15 AM: Groomed 24.1 GB from Backup Set New Win2003. Here is the results of last verify. There is one MD5 digest error. + Executing Verify at 4/11/2015 12:51 PM (Execution unit 2) To Backup Set New Win2003... Bad Backup Set header found (0x0a408c1e at 1,381,031,224) ... Bad Backup Set header found (0xcf9f7fb1 at 1,382,671,480) Bad Backup Set header found (0xe3ffe8c3 at 1,382,671,544) Generated MD5 digest for file "\\xxxxxxxxxx\2132 rear.png" does not match stored MD5 digest. Bad Backup Set header found (0x436f6e74 at 1,382,671,611) ..... Bad Backup Set header found (0x679f7d8e at 1,382,719,480) 4/11/2015 5:15:04 PM: 310 execution errors Remaining: 88 files, zero KB Completed: 573752 files, 842.3 GB Performance: 3419.2 MB/minute Duration: 04:23:10 (00:10:55 idle/loading/preparing) 4/11/2015 5:15:04 PM: Script "Verify" completed with 310 errors Any other suggestions? I was thinking of Creating a new backup set; then transferring all snapshots over; hoping that retrospect will skip the corrupt segments.

I have a very large backupset; getting close to 1TB. I recently did a verify, and it report 310 Bad Backup set header errors. So I decided to recreate the catalog, hoping that would fix it. Which it didn't They appear to be all in the range of Bad Backup Set header found (0x0a408c1e at 1,381,031,224) to Bad Backup Set header found (0x679f7d8e at 1,382,719,480) Is there anyway to identify which RDB files are corrupted are responsible for that sequence? It seems like it would be an easy thing just to delete the offending RDB files, rebuild the catalog, then let the regular backup script fill in the missing files. Thanks, Matt Ferraro