Jump to content

Search the Community

Showing results for tags 'Bad backup set header'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. 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
  2. The following log is for a media set copy beetween FW disks. Log for Script: daily_user_rotate_last_tmp_copy Date: 2/1/2015 + Executing daily_user_rotate_last_tmp_copy at 2/1/2015 2:37 AM (Execution unit 2) To Backup Set v9_daily_user_last_tmp... - 2/1/2015 2:37:44 AM: Transferring from v9_daily_user_last !Bad Backup Set header found (0x044801bf at 1867514) 2/1/2015 3:37:41 AM: 1 execution errors Completed: 507563 files, 103.6 GB Performance: 1782.9 MB/minute Duration: 00:59:56 (00:00:29 idle/loading/preparing) - 2/1/2015 3:37:41 AM: Verifying v9_daily_user_last_tmp 2/1/2015 3:59:59 AM: Execution completed successfully Completed: 507563 files, 103.6 GB Performance: 4753.2 MB/minute Duration: 00:22:18 2/1/2015 4:00:03 AM: Script "daily_user_rotate_last_tmp_copy" completed with 1 errors I see no evidence that the "error" reported has caused any problems. The source verifies without error, and so does the copy. What, exactly, doe the error mean? Is this likely to be a transient error caused by the inherent less-than-perfect electronics and the enormous amount of data being transferred? Are the "headers" re-calculated" when the new file is written? If transient, when getting such an error, does Retro re-read the data to ensure that the subsequent read does not get the error? Do tell. I would like to know more about exactly what this error means. I do not want to lose confidence in the media sets with this error. OTOH, if this IS a real error, I want to re-do the operation and/or track it down. Thanks
×