Jump to content

Search the Community

Showing results for tags 'errors'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. I wanted to take several older external USB hard drives, some of them containing non-Retrospect data folders, others containing Retrospect Backup Sets, and transfer all of them into a single backup set I named "Consolidation." I did this by using both Immediate backups to capture (backup) non-Retrospect data folders into the Consolidation set, and using Transfer Backup Set scripts to transfer any Retrospect backup sets on an older external USB drive to the newer Consolidation Backup Set. The process worked well and ended up spanning two new external 4TB drives (the 2nd drive is barely full yet so there's room for further growth/consolidation). I'd say it's about 5 or 6TB of data spanning two 4TB external USB drives. Then I wanted to create a duplicate or "backup" of that single Consolidation set... just in case the first one ever had issues, I would have at least two copies. To do this, I am using a Transfer Backup Set script to transfer from the original Consolidation backup set to a secondary newly created "Consolidation2" backup set (the number '2' appended to the name, a different backup set but ultimately a duplicate of Consolidation). During the Transfer from Consolidation to Consolidation2, I hit the dreaded "bad backup set header found" message... so far the Activity monitor shows about a 18000 count. My system: MSI GT72S 6QD (a web search yields its specs and support page)... at first I had been using a powered USB hub without issue for most of my backups and stuff. Not sure if that's related, but based on a Retrospect KB article (https://www.retrospect.com/en/support/kb/troubleshooting_bad_backup_set_header_and_other_similar_errors) I decided to plug directly into my laptop's USB 3.0 ports, but I still see those errors. I also see them on another laptop as well. Some questions... 1) I think my experience above indicates with relative certainty that the original Consolidation set has some corrupted files/backup data... correct? Okay, so to assess the damage and move forward, I'm trying to gain insight into the following... I'm currently letting the Transfer from Consolidation to Consolidation2 continue despite the 18000 errors because it seems to be continuing and transferring (copying) files. But I'm left with some important questions... 2) I see this error message "bad backup set header found", but Retrospect is showing me no feedback as to what files are affected. It's unclear what snapshots or backups were affected. This might help me understand the impact and how much effort I should take to resolve it... the corrupted files may not be that critical to me but I can't tell... Retrospect is only emitting the lower level error message. Is there a way to get Retrospect to give me a user-friendly set of information about what files were affected? ... and perhaps what snapshots, Sessions, etc. from the original Consolidation are not reliable or missing after the transfer to Consolidation2? Or, is there a way to diff Consolidation and Consoldation2's catalogs to see what made it successfully to Consolidation2? That information seems imperative to assess damage. 3) Given I see about 18000 "bad backup set header found" errors, but the Transfer operation is continuing, apparently continuing to copy good/accessible files, what will the new Consolidation2 Backup Set look like when complete? Will it contain only good data that could be retrieved? Will it include garbage data based on a best effort to copy from the partly corrupted source set? etc. While this question seems similar to #2 above, I'm asking something different here... I'm trying find out what data from the corrupted files in the source set, if any, make to the destination. I'm guessing none of the corrupted data makes it, that it is ignored, but I want to find out for certain. 4) What about backup sets in the partly corrupted source set... will the "good" not corrupted parts be copied, while ignoring the corrupted parts? Does this mean the snapshot is transferred to the new Consolidation2 without the corrupted files? Or are the corrupted file names still moved to the destination even if the destination data archive is missing or contains bogus data? I can't imagine Retrospect copying over garbage data... but I don't want to involve my personal assumptions here... want to get the facts. Basically, Retrospect is encountering errors during a transfer due to corruption in the source set but it's unclear how Retrospect is going to deal with those errors from a very specific concrete level... meaning what will the result of its work, the new destination Consolidation2 set, look like (assuming the destination drive is good and there is no new corruption)? Based on the answer to the above, my plan is to continue to let the transfer complete, and once completed, I want to go back over all the older external USB drives which were used to create the original Consoldation set, and re-back them up to Consolidation2. After all that, I'll erase Consolidation and recreate it using a Transfer from Consolidation2 (the new one and only "good" one) to a newer recreated Consolidation. My goal here is to salvage what was good about the first round of backups to create Consolidation in hopes that going back over all the older USB external drives will go quickly given files will already be in the Consolidation2 set. Keep in mind these Consolidation and Consolidation2 sets are essential archival in nature... I don't really need the structure as much as the file history... though I want to retain the snapshot data as best as possible. So far Retrospect seems to transfer that data just fine. Does the approach in the prior paragraph sound reasonable? My Transfer operation is vanilla except I checked "Transfer any needed intermediate database Snapshots." Thanks for any insight!
  2. Hello Dantz, We run Retrospect Single Server w/Unlimited Clients in our office. All of our backup clients are mobile, so with people moving around and disconnecting frequently, there are several incompleted backups throughout the day. We had to turn email alerting off, because we received alerts for each incomplete backup. I think that alerts about clients that have not been backed up in X days would be very helpful. Thanks.
  3. - 01/06/2015 4:00:06 AM: Copying Local Disk (C:) Backing up 0 out of 7 files using block level incremental backup, storing full backups for remaining 7. ... File "C:\Windows\SysWOW64\log.txt": can't read, error -1020 ( sharing violation) VssWSetCompResult: res =1,101 Writer "COM+ REGDB Writer" backup failed, error -1101 ( file/directory not found). Component "COM+ REGDB" backup failed, error -1101 ( file/directory not found). 01/06/2015 4:10:52 AM: Snapshot stored, 252.6 MB Is there anything I can do to address the COM+ REGDB errors? They occur while backing up files on the backup server itself. This has been happening for several months since before the current version. I have Single Server
  4. A good piece of SW behaves correctly. A really great piece of SW behaves correctly even in the face of errors, and provides useful information when things go wrong. Retrospect 10.5 is not yet great. I have an occasional problem with my external firewire disks. I dont know where the errors originate, but they are "sticky", in that they are not intermittent once they appear. I have taken to running a "verify" script regularly on the media sets to ensure that the underlying HW is functioning correctly. These errors usually appear in clusters, affecting multiple media sets in a burst, and then staying "stable" between occurrences. In this case, out of 14 media sets, errors appeared on 7 of them. 6 of them are of the form: (blah blah) !Media Set format inconsistency (2 at 19357344) !Media Set format inconsistency (2 at 19971744) !Media Set format inconsistency (2 at 20586144) !Media Set format inconsistency (2 at 21200544) !Media Set format inconsistency (2 at 21814944) !Media Set format inconsistency (2 at 22429344) !Media Set format inconsistency (2 at 23043744) !Media Set format inconsistency (2 at 23658144) !Media Set format inconsistency (2 at 24272544) !Media Set format inconsistency (2 at 24886944) !Media Set format inconsistency (2 at 25501344) !Media Set format inconsistency (2 at 26115744) !Media Set format inconsistency (2 at 26132288) Remaining: 550 files, 0 B Completed: 3770 files, 34.6 GB Note that there are 550 files "remaining", and the 3770 is less than the number expected (by 550 files). The other type of error is: - 12/14/14 10:30:50 AM: Verifying v9_Virtue2 !Generated MD5 digest for file "/Volumes/VirtueHD/private/var/servermgrd/sessions/root@4B101fgg23MYmjL4Hhq9pNXY9pN1Idb5-admin" does not match stored MD5 digest. Completed: 467630 files, 29.3 GB Performance: 3,860.5 MB/minute Duration: 00:08:08 (00:00:22 idle/loading/preparing) These "MD5" errors seem to be rarer. I presume that these errors are some sort of data transfer problem with the disk, because when I read the disks in raw mode (or copy the files) no errors are detected in the disk operations. For some reason, data appears to have been lost in the transfer of the data from memory to the disk. Given the (lack of) data protection in the data path in essentially "consumer" HW, this is not so surprising. -- What is surprising is that the VERIFY operation detects errors, and a media set COPY runs WITHOUT error. What I have done (several times now) is copy the media set to another, and then copy it back. When I do this, I get the expected number of files reported by the verify, but *no errors*. Something is not right. 1. What does retrospect do with those missing 550 files if I try to restore from that media set? I have never seen an error reported from a restore saying it tried to restore a file and it was "unavailable". 2. Why does verify detect errors that copy ignores? (can't see?) Retrospect exists to protect my data. It needs to be explicit with me about what it fails to backup/preserve/restore. What's up with this? Is it different in retro 11.x?
  5. Retro 9.0.2 (107), on OS X 10.6 mini with 8 GB memory. tape drive is HP storage works Dat 72 usb I am trying to copy a media set from disk to tape. Total size is about 90 GB. On the second tape, I get errors. I've tried this 3 times, and the error is about the same. twice it has happened on the same file. Once on another file "nearby". Log excerpts: + Executing copy_iCompute_year at 12/7/12 (Activity Thread 1) To Backup Set v9_iCompute_2012t... - 12/7/12 5:43:14 PM: Transferring from v9_iCompute_2012 - 12/7/12 9:11:55 PM: Verifying v9_iCompute_2012t - 12/8/12 12:42:17 AM: Transferring from v9_iCompute_2012 - 12/8/12 4:22:35 AM: Verifying v9_iCompute_2012t !Backup Set format inconsistency (4 at 302823168) !Generated MD5 digest for file "Joy_HD_X/Users/cjl/Pictures/Bruce_9_13_09/Originals/2009/Jun 25, 2009/" does not match stored MD5 digest. !Backup Set format inconsistency (5 at 302822304) !Backup Set format inconsistency (4 at 302818176) !Backup Set format inconsistency (4 at 302817088) !Backup Set format inconsistency (4 at 302816064) (repeated many times....) previous + Executing copy_iCompute_year at 12/7/12 (Activity Thread 1) To Backup Set v9_iCompute_2012t... - 12/7/12 12:22:11 AM: Transferring from v9_iCompute_2012 - 12/7/12 3:51:42 AM: Verifying v9_iCompute_2012t - 12/7/12 10:42:37 AM: Transferring from v9_iCompute_2012 - 12/7/12 2:22:52 PM: Verifying v9_iCompute_2012t !Backup Set format inconsistency (4 at 302786496) !Generated MD5 digest for file "Joy_HD_X/Users/cjl/Pictures/Bruce_9_13_09/Originals/2009/Jun 26, 2009/" does not match stored MD5 digest. !Backup Set format inconsistency (5 at 312139968) !Backup Set format inconsistency (4 at 312262592) !Backup Set format inconsistency (4 at 332547344) !Backup Set format inconsistency (4 at 317140112) (repeated many times....) and previous... + Executing copy_iCompute_year at 12/5/12 (Activity Thread 1) To Backup Set v9_iCompute_2012t... - 12/5/12 1:40:33 PM: Transferring from v9_iCompute_2012 - 12/5/12 5:09:11 PM: Verifying v9_iCompute_2012t - 12/5/12 9:21:03 PM: Transferring from v9_iCompute_2012 - 12/6/12 1:02:50 AM: Verifying v9_iCompute_2012t !Backup Set format inconsistency (4 at 297431856) !Generated MD5 digest for file "Joy_HD_X/Users/cjl/Pictures/Bruce_9_13_09/Originals/2009/Jun 25, 2009/" does not match stored MD5 digest. !Backup Set format inconsistency (5 at 316160816) !Backup Set format inconsistency (4 at 316426624) !Backup Set format inconsistency (4 at 315258976) (repeated many times....) I already tried using a different tape. The first two were the same tape, the third try was a different tape (different manufacturer, too). After the second failure, I did a verify on the source media set, and it came through clean. This looks like some sort of bug to me. Tape is relatively imprecise in the face of errors and bad media. I would expect that if this were a device or media problem with recording the data, the error would change from run to run, but this is a little too consistent. I also would expect it to behave differently with a different physical tape. It would be nice to have timestamps on the errors. I could at least tell whether this is happening at the beginning, end, or middle of the tape. As it is, I have no idea. Writing these tapes takes hours. Despite all these errors, is any of the data written to these tapes retrievable? I'm inclined to treat the whole set as worthless if the copy process does not come through "clean". Is there some different procedure I can use to make this work?
  6. I include my log (below). Note that there are quite a few "errors". The summary says "3 errors" on completion. (see snap - included) Which 3 are THE errors? How are they counted? -dgl- + Normal backup using Weekly_desktop at 6/4/12 (Activity Thread 2) To Backup Set v9_iCompute... - 6/4/12 9:58:21 AM: Copying Joy_HD_X on Joy 6/4/12 11:14:26 AM: Snapshot stored, 114.9 MB 6/4/12 11:14:34 AM: Comparing Joy_HD_X on Joy *File "Joy_HD_X/Library/Caches/com.apple.LaunchServices-023504.csstore": didn't compare *File "Joy_HD_X/private/var/log/system.log": different data size (set: 1641, vol: 1804) *File "Joy_HD_X/private/var/log/windowserver.log": different data size (set: 40808, vol: 40972) *File "Joy_HD_X/private/var/log/asl/2012.06.04.asl": different data size (set: 2230, vol: 2389) *File "Joy_HD_X/private/var/log/asl/StoreData": didn't compare *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Eudora Log": different data size (set: 406400, vol: 84601) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Eudora Settings": different resource size (set: 252001, vol: 252055) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Eudora Settings.bkup": different resource size (set: 251677, vol: 252037) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Eudora Statistics.xml": different data size (set: 12571, vol: 12573) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Personal Nicknames": didn't compare *File "Joy_HD_X/Users/cjl/Documents/eudora folder/UsageStats": different data size (set: 3080, vol: 4623) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Eudora Items/Plugins/Esp/Esp.log": different data size (set: 9996, vol: 10200) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/IMAP Folder/sysadmin1/Inbox/#&$*- Hidden": didn't compare *File "Joy_HD_X/Users/cjl/Documents/eudora folder/IMAP Folder/sysadmin1/Inbox/Inbox": didn't compare *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Mail Folder/In": different data size (set: 1437094, vol: 1425361) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Mail Folder/Out": different data size (set: 200079, vol: 198207) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Mail Folder/Trash": different resource size (set: 911495, vol: 913475) *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Spool Folder/In.temp": didn't compare *File "Joy_HD_X/Users/cjl/Documents/eudora folder/Spool Folder/Out.temp": didn't compare *File "Joy_HD_X/Users/cjl/Library/Caches/com.apple.Safari/Webpage Previews/114C2EFC50BDB16438695C35C14CF2E9.jpeg": different data size (set: 45005, vol: 45904) *File "Joy_HD_X/Users/cjl/Library/Caches/com.apple.Safari/Webpage Previews/114C2EFC50BDB16438695C35C14CF2E9.png": different data size (set: 132337, vol: 134638) *File "Joy_HD_X/Users/cjl/Library/Preferences/.GlobalPreferences.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.dock.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.iWork.Pages.plist": different data size (set: 9664, vol: 9330) *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.PreferenceSync.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.Preview.bookmarks.plist": different data size (set: 8923, vol: 8969) *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.Preview.plist": different data size (set: 6835, vol: 6625) *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.print.custompresets.plist": different data size (set: 15144, vol: 15148) *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.recentitems.plist": different data size (set: 24371, vol: 24557) *File "Joy_HD_X/Users/cjl/Library/Preferences/com.apple.Safari.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/com.nowsoftware.nowcontact.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/ByHost/com.apple.iCal.helper.001451173bcc.plist": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/FileMaker Preferences/FileMaker Pro 8.0A Prefs": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/Now Contactâ„¢ Prefs/Now Contactâ„¢ Prefs (4.0)": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/Now Up-to-Date Prefs/Now Up-to-Date Printing Prefs": didn't compare *File "Joy_HD_X/Users/cjl/Library/Preferences/Now Up-to-Date Prefs/QuickDay X Events": different data size (set: 5074, vol: 3511) *File "Joy_HD_X/Users/cjl/Library/PubSub/Database/Database.sqlite3": different data size (set: 76680192, vol: 76810240) *File "Joy_HD_X/Users/cjl/Library/PubSub/Feeds/1c35aca2530ae5680f0856e77db55d2feeb30bbd.xml": different data size (set: 25379, vol: 33798) *File "Joy_HD_X/Users/cjl/Library/PubSub/Feeds/600e4cdbdbd613b6f88c22fb55bf7b8d9dc3c251.xml": different data size (set: 43132, vol: 42224) *File "Joy_HD_X/Users/cjl/Library/PubSub/Feeds/73de2d277fc5a895287ab76a68c912be73a637b6.xml": different data size (set: 10875, vol: 11187) *File "Joy_HD_X/Users/cjl/Library/Safari/History.plist": different data size (set: 116897, vol: 113114) *File "Joy_HD_X/Users/cjl/Library/Safari/HistoryIndex.sk": different data size (set: 1548288, vol: 1499136) *File "Joy_HD_X/Users/cjl/Library/Safari/LastSession.plist": different data size (set: 597, vol: 899) *File "Joy_HD_X/Users/cjl/Library/Safari/WebpageIcons.db": didn't compare 6/4/12 11:56:38 AM: 3 execution errors Completed: 107197 files, 16.6 GB Performance: 326.4 MB/minute (272.1 copy, 407.5 compare) Duration: 01:58:17 (00:13:57 idle/loading/preparing)
  • Create New...