Jump to content

mikemurphy324

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikemurphy324

  • Rank
    Newbie
  1. Hi, I've requested attention from tech support, but while I'm waiting for that, I thought I'd post here to see if anyone can offer insight or suggestions. Basic situation -- newly migrated to Windows 7 Professional 64-bit. Updated Retrospect to 7.7 for compatibility. Able to do backups to external hard drives successfully. I also like to backup to LTO-1 tapes, using an HP 230 external SCSI drive (I've been doing this with previous versions of Retrospect successfully for several years.) The HP 230 has the most current firmware. During the Windows 7 migration, I changed from an older Adaptec SCSI card to a 29160, and installed the latest Adaptec driver. Using HP library and tape tools, I've tested the drive with the new system/card/drivers, and it passed (report appended below). Immediately upon installing Retrospect 7.7, I did a test by creating a new backup tape set and backing up several gigs of files to it. This was successful. HOWEVER, when I tried to do an actual routine backup, Retrospect started having trouble. It logged some -102 errors (trouble communicating), then bypassed a partially used cartridge and asked for new media. After getting new media, it successfully added it to the set, but go no further. I had turned away from the machine for a few minutes. When I turned back, Retrospect had quit -- its window had simply disappeared. Since then, I've tried several cycles of creating a test backup set (successful), erasing a cartridge (successful), adding the cartridge to the set (successful), and trying to back up some files. It fails each time -- sometimes immediately asking for a new cartridge (and logging -102 errors (trouble communicating), sometimes simply quitting without explanation. Backups to hard disk and duplicate to hard disk still seems to be working. As a check, I've just run another HP StorageWorks tape tools test on the drive/card/drivers. It passed with no errors reported. One other possibly relevant piece of information. Upon installation of Retrospect 7.7, it was indicated to me that I should set it to "run as administrator," which I did. And, after one of the sessions, Windows gave me a message that there were some apparent incompatibilities with Windows 7, and that it was adjusting to run the application with compatibility settings (but did not specify what those were). Can anyone offer any suggestions? Where should I start looking for trouble? Are there settings I can adjust that might help? Etc, .... ----- Mike Murphy, HP Tape Tools test results: |__ Analysis Results |__ LTO Drive Assessment Test, version V01.09.2010 |__ Test run: Tue Nov 23 08:44:54 2010 |__ Drive serial number: IE72E01227 |__ Data Cartridge Information: |__ Vendor: FUJIFILM |__ Format: LTO-1 |__ Serial Number: 1170434069 |__ Barcode: Unknown |__ ANALYSIS OF HISTORICAL INFORMATION (from drive logs): |__ version: V14.09.2010 |__ Firmware rev E32D is up-to-date for Ultrium 1-SCSI as of Mon Aug 18 19:00:00 2003. |__ There were 18 rules checked. |__ Device Analysis has checked the historical information and no problems were found. |__ RESULTS OF TESTS ON THIS DRIVE |__ [Please note: the operations performed by this overwrite test will NOT be |__ reflected in the Support Ticket usage/health information.] |__ Amount of data required’ test option : Default |__ Iteration number: 1 of 1 |__ Overall Margin: Great margin (8.3 GB written) |__ The LTO Drive Assessment Test has checked the history and/or operation of the selected drive, and |__ The test has PASSED and the drive is GOOD.
  2. Thanks for your responses. I think I'll try the approach of excluding the folder from the Retrospect backup. I stage backups to hard disk first, then to tape, and those daily shadow copy gigabytes will quickly quickly eat up the disk! Can anybody watching this think of hidden "gotchas" about not backing up the System Volume Information directory? Will the only thing I'm missing be the restore points and "previous version" capabilities? (Which Retrospect handles separately.)
  3. Hi MRIS, About the idea of preventing Retrospect from backing up the System Volume Information folder altogether, I'm hesitant to take this step because I have the impression that Windows stores important information for system operation in that directory. Can you tell me what Windows system functions would be disabled or threatened on a machine that I restored from a Retrospect backup that didn't include System Volume Information? ---- MM
  4. Thanks for adding new information to this! I've noticed the "similar-but-changing" name pattern as well. It hadn't occurred to me that Retrospect might be actually creating these files rather than simply backing up something Windows Vista was doing. I don't have extensive Retrospect expertise, but I have read that Retrospect is now using Windows Shadow Copy mechanisms in its backup process. And, my understanding is that the hidden System Volume Information directory is where such Shadow Copy files reside. Is it possible that Retrospect is backing up its own large work file? Either from the current or a previous session? Here are a couple of speculative questions -- is there some flaw or mis-configuration that is preventing these files from being deleted when they're supposed to be? -- Would disabling Retrospect from using Shadow Copy prevent this bad behavior pattern (consuming backup space with up multi-gig hidden files of questionable origin with each backup pass)? -- Are lots of people having this problem??
  5. I've noticed that the backup of a machine running Windows Vista (most of mine use XP Pro) includes multiple files in the System Volume Information directory that are very large (largest today, 13 gigabytes!). Info I find via Google suggests these are files Vista prepares to enable restore points and the "previous version" functions. Seems like MANY gigabytes of backup will be consumed by these files. Is there a way to properly back up Vista systems without having to include these files? Is there a way to filter the Retrospect backup selection to not include them, without hindering the ability to properly restore the backed up system if it needs it? I suppose one way would be to disable the Windows restore function and previous version functions on the user's system -- but I'd like to find a solution that doesn't require me to do that.
  6. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, I've e-mailed and posted Seagate/Maxtor about this pattern, and I've disabled the OneTouch software for now. And, my system is back at work on a lengthy Retrospect backup sequence. Thanks for your help as we worked on the issue. And, thanks to MRIS for analyzing the crash minidumps that pointed to OneTouch! I have no idea whether OneTouch is really the ultimate "cause" of the behavior -- in my experience, some failures come from weird combinations of software interacting in specific, not-commonly-encountered circumstances. I'll spend a little more time trying to chase it down (my guess is that the Seagate/Maxtor folks will assert that it's not in their territory and point elsewhere), then decide to live with the workaround. After all, my real goal in this isn't mastery of IT troubleshooting skills, it's having reliable backups of our working materials and finished videos. Perhaps this thread will help some others reach working solutions more quickly if they have a similar problem. (Blue Screen of Death (BSOD) found to be related to Maxtor OneTouch software, workaround being to disable OneTouch as a startup item using MSCONFIG)
  7. mikemurphy324

    BSOD crash during backup on XP

    Hi, thanks for interpreting these for me! I also got a notice back from Microsoft that mentioned the Maxtor OneTouch software, after sending them one of the automated "recovered from serious error" reports. So, I removed OneTouch from the startup sequence using MSCONFIG, and was able to do a 173 GB backup and verify with no crashes or errors (it ran throughout most of the day today). So, disabling OneTouch works as a workaround for me! I've sent an inquiry to Maxtor/Seagate to see if they have a solution to this. I'd like to have their software running, as I use two of their 1.5 TB RAID drives, and I think the software handles reporting for the RAID. But I certainly am now much better off than I was a couple of days ago. There's an irony -- Retrospect (express) has been bundled with the Maxtor OneTouch series, and their standard install includes both Retrospect and the OneTouch software that can kill it. --- MM
  8. mikemurphy324

    BSOD crash during backup on XP

    Hi, thanks for your help. C disk has 64.5 GB of free space. I'll try the safe mode, disk checks, and defrag, and report back.
  9. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, I attempted a 26 GB backup to an external USB-attached hard drive. It also failed, with this error signature: BCCode : 1000008e BCP1 : C0000005 BCP2 : 00000000 BCP3 : F05A4B40 BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1 The difference between this a previous signatures is in BCP3 One thing that was different -- this time it got all the way through the "copy" portion of the cycle, and failed during the "compare" portion. The earlier crashes happened at various points in the copy portion. I was checking it periodically, was encouraged, and then disappointed when I came back and found it with the "recovered from serious error" and "terminated unexpectedly" messages. What could I check next? ----- MM
  10. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, Recognizing that it's something in the system, hardware, and configuration that's responsible for the failure and the Blue Screen, it's something about Retrospect's interaction with the system and hardware that's serving as the trigger. I'm hoping that you've dealt with it enough times that you can offer some insight on what the fix might be, or at least where to look for the problem, so I'll lose as little time as possible to the black hole of Windows error diagnosis.
  11. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, Can you clarify what you mean by the exchange logs? Is there more I can see beyond the logs in the XP Professional "Event Viewer" in System Administration?
  12. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, here's the next development -- the backup-to-tape session failed -- BSOD after 24 GB of backup (out of 179 GB). Possible clues? The system event log entries just before and after are: 8:59:41 System Event -- The IMAPI CD-Burning COM Service service was successfully sent a start control System Event -- The IMAPI CD-Burning COM Service service entered the running state. System Event -- Error code 1000008e, parameter1 c0000005, parameter2 00000000, parameter3 f0288b40, parameter4 00000000. [This is the BSOD crash, I believe -- MM] 8:59:47 System Event -- The IMAPI CD-Burning COM Service service entered the stopped state. 8:59:50 System Event -- The HTTP SSL service was successfully sent a start control. System Event -- The HTTP SSL service entered the running state. I have no idea of the significance, if any, of the IMAPI and HTTP events -- they're at the same time as the crash. There was no foreground application running except the Retrospect session. Here's the Microsoft Error Report Signature: BCCode : 1000008e BCP1 : C0000005 BCP2 : 00000000 BCP3 : F0288B40 BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1 Upon restart, there was this message from Retrospect: Execution terminated unexpectedly, possibly due to a power failure or system crash. I couldn't find any further details in the Retrospect History or Logs. Couldn't immediately recreate the catalog, perhaps because this was a new Backup Set, and Retrospect has no record of the first member. I'll try to do a similar backup to external HD and report what happens. ---- MM
  13. mikemurphy324

    BSOD crash during backup on XP

    Hi Robin, thanks for super-fast response! I'm in the middle of trying a backup-to-tape again at the moment (with Open File Backup off, so far successful, 20GB and counting...). I frequently backup to HD also, usually shorter runs, just a few GB at a time. I'm trying to recall whether I've had this problem in that mode. If I have, it certainly hasn't been as frequent and persistent. I'll try it as an experiment when the current backup finishes. In the meantime, do you have any useful thoughts, insights, hints about causes of the BSOD behavior that we should be aware of?
  14. mikemurphy324

    BSOD crash during backup on XP

    I'm repeatedly getting a Blue Screen of Death crash during backup. Here's the basic context -- --Windows XP Service Pack 2, behaving normally with other applications (Adobe graphics apps, video editing) --Retrospect 7.5.508 (Just updated from 7.0, in attempt to resolve this problem) --Backing up USB external hard drive, and a network hard drive (similar behavior with both) --Backing up both large (500 MB to multi-GB) and small files. --Backing up to HP ultrium 230 LTO-1 external SCSI tape drive. After a variable amount of backup (usually between 10 and 20 GB), the system crashes with a Blue Screen of Death. After a brief hold on the BSOD, it restarts, and says the system has recovered from a serious error. When I restart Retrospect, I attempt to get the Retrospect catalog straightened out with "Update existing catalog." Sometimes this works, and I can try again. Sometimes when I try to backup after the update it says the catalog is out of sync and to use Update to put it back in sync. The only way around this loop seems to be to tell Retrospect to skip the current member and continue with a new tape. I don't want to do this, because I shouldn't have to, and because the tapes are $32 a piece, and I'm likely to face the same problem again within an hour or two. I've seen various posts about problems similar to this, but I haven't yet found any really definitive discussion or explanation. Does anyone here understand this BSOD behavior pattern? Is there an easy fix? Is there a Windows file I need to replace? Is there a configuration or registry setting that would help? (I'm currently trying a backup with "backup Open Files" turned OFF. I don't know yet if it will succeed ... )
×