Jump to content

rbspies

Members
  • Posts

    9
  • Joined

  • Last visited

rbspies's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I believe the Media Verification failure is only an issue with a file backup set. >> Is there a product that is similar to Retrospect, except dependable and stable? << My experience is that all backup products, like all software, have their issues. I've found Retrospect to be more dependable and stable than most. I've been using Retrospect as a personal backup product. I've recently switched to Acronis True Backup, which isn't as polished as Retrospect, but has a quicker/easier disaster recovery restore. I don't think I'd recommend it for "professional" use (i.e., as a network administrator). Then again, I'm using the personal version, haven't tried the corporate version. Once gotcha--True Backup installs a device driver that appears to cause Retrospect to crash frequently during the disk scanning phase.
  2. When I back up to a File backup set, if I select Media verification, sometimes Retrospect crashes at the point it would normally start verifying. I see a status message that says something about "resynchronizing", which is immediately followed by "Assertion failure at "simp.cpp-342"". The beginning of assert_log.utx includes: ==================== OS: Windows XP version 5.1 (build 2600), Service Pack 2, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.285 Driver Update and Hot Fix version 7.5.5.103 Exception occurred on 7/27/2006 at 9:39:01 PM Error info: Assertion failure at "simp.cpp-342" Exception code: E0000000 ASSERTION Fault address: 7C81EB33 0001:0001DB33 kernel32.dll ==================== I can work around the problem by switching to "Thorough verification", which never results in the crash. I have never experienced this problem backing up to a Disk backup set. Ideas? Something buggy in Media verification? Thanks.
  3. Just had it happen again--this time with System Restore set to use the maximum (12% of hard drive) amount of space.
  4. Glad to head (I guess) I'm not the only one. Given that this is a generally-undesirable thing, it would be great if Dantz could analyze why it's happening and see if there's anything a user can do--or, if not, that Dantz can do--to keep it from happening. Thanks. - Bob
  5. System restore isn't/wasn't enabled for the USB drive, because it's considered a removable device. I tried increasing the amount of space allocated for system restore to the max (12% of my hard drive capacity, or about 4.5 GB). That seemed to do it. Interestingly, after the backup was complete, the total space taken by my system restore files is only about 751 MB. So maybe something during the backup requires extra space in the System Restore Area during the backup, but it's a temporary need? Thanks. - Bob
  6. >> How much disk space is the system restore feature set to use on each disk? << 2 GB on Drive C, the only drive on my system (other than the USB-connected backup drive). >> How much free space do you have available on each disk? << 21 GB on Drive C. >> I wonder if the temp space used in the backup process is enough to force system restore to get rid of old restore points? << I don't think so. The reason the KB article looked potentially relevant is that it appears something about the backup process may be causing System Restore to attempt to save some very large files within its 2 GB allocation. THAT would indeed purge old restore points. >> So if you backup every day you will always have only one restore point? << No, because my daily normal backup doesn't cause the problem. It only occurs weekly when I do a recycle backup. Thanks. - Bob
  7. I start System Restore. Choose "Restore my computer to an earlier time". At that point System Restore presents you with a list of Restore Points. Prior to doing a Restrospect Recycle Backup, there's a list of, say, 10 Restore Points. As soon as the Recycle Backup is complete, there's only one Restore Point left, created immediately after the backup was complete. There's a knowledge base article, 5727, that I suspect may be relevant. The problem it describes IS NOT the one I'm experiencing; however, the mechanism sounds like it could be the same. The article describes Retrospect causing System Restore to attempt to save an extremely large file, which would automatically purge Restore Points. The solution described in 5727 is to turn off System Restore, which in my case would simply take away all System Restore functionality rather than fixing the problem. Thanks.
  8. Every time I perform a recycle backup (to a disk backup set), all of my Windows XP System Restore Restore Points are purged. How can I keep this from happening? (This doesn't happen with regular backups, only with recycle ones.) I'm using Retrospect Professional 6.5. Thanks.
  9. A funny message recently appeared in my Retrospect 6.5 Professional Operations Log: "TTicker:GetMS: TTicker('@PNG') has reached 21 days of 49 max" Any idea what this is about? Thanks.
×
×
  • Create New...