Jump to content

cgiandomenico

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cgiandomenico

  • Rank
    Occasional Forum Poster
  1. The following applies to Retrospect 7.7.341 (64-bit) running on 64 bit Windows 7 Home. I have just "recovered" a backup set (that threw errors during grooming) by transferring it to a new backup set. During the the transfer, 9660 errors were generated. The new backup set contained about ~9000 fewer files and was 4% smaller than the source backup set. It contained 1 less session (from the middle of the session list) but the same number of snapshots. Many sessions in the new backup set have fewer files than the source backup set. Subsequently, the new backup set was groomed successfully and appears to be error free except for the fact that it contains fewer files than the source. My question is: Can I rely on the integrity of the snapshots in this transferred Backup set? I was forced to transfer the backup set after an automatic grooming failed with the following error: "Grooming Backup Set HPE350-1 failed, error -2241 ( Catalog File invalid/damaged)." The backup set continued to throw this error even after its catalog was repaired. In a last ditch effort to salvage the backup set, I used Retrospect's "Transfer Backup Sets" feature to transfer the damaged backup set to a new empty backup set. A large number of errors were generated during transfer but the resultant backup set can be groomed and appears to be error free. During transfer there were half a dozen initial errors of the type shown below: Additional error information for Disk Backup Set member "1-HPE350-1", Can't read to file X:\Retrospect\HPE350-1\1-HPE350-1\AA000214.rdb, error -1101 ( file/directory not found) Trouble reading: "1-HPE350-1" (31969656), error -102 ( trouble communicating) Trouble positioning: "1-HPE350-1" (32172945), error -102 ( trouble communicating) Followed by thousands of the following 2 types of error: Bad Backup Set header found (0x020d4a33 at 132,397,797) Backup Set format inconsistency (10 at 137369677) Note: Both the original and new backup sets are on the same external USB drive. I intend to delete the original.
  2. FYI Did you know it is possible to install 32bit Retropsect on a 64bit Windows 7? I managed to do this by copying the install files that were used to install Retrospect on my retired XP machine onto my replacement x64 Win 7 machine. Retrospect installs fine and appears to backup, except that it won't launch scheduled backups. It produces a -630 error: Failed to load extension C:\Program Files\Retrospect\Retrospect 7.7\rdu64.rpx, error -630 ( bad program extension) I uninstalled and reinstalled from the full Retro-EN_7_7_325.exe. So far it appears that no permanent damage was done and I can perform a scheduled backup.
  3. cgiandomenico

    Function of Activity Monitor?!

    The function of the new retrospect activity monitor escapes me. All it seems to do is display a progress bar with no information about what volume it is operation on, whether it is backing up or comparing. Even worse pressing the "power button" thingy aborts the backup! The developers should be working on how to allow users to work on other backup tasks while a backup is in-progress (such as creating a new backup script), not preventing access to useful execution information.
  4. cgiandomenico

    Finish is NOT EXIT

    Sorry, version 7.7.
  5. cgiandomenico

    Finish is NOT EXIT

    A minor quibble with the Disaster recovery disk... The button marked Finish is actually a QUIT or EXIT button. It is slightly annoying to wait until the disk has finished loading to discover that one has exited the recovery process by pressing the finish button.
  6. cgiandomenico

    7.7 Disaster Recovery compatible with OEM OS disks?

    Excellent!
  7. Is the new disaster recovery system in 7.7 independent of the OEM Windows OS disks provided by computer manufacturers such as Dell? In other words, does it work with systems where the Windows OS was provided on OEM disks other than retail Microsoft disks?
  8. cgiandomenico

    Error -1132 Trying to Create Disaster Recovery ISO Image

    Does anyone know if Retrospect 7.6 allows one to use Dell OEM disks to prepare a disaster recovery ISO image?
  9. cgiandomenico

    Error -1132 Trying to Create Disaster Recovery ISO Image

    I'll keep that in mind. Unfortunately as I'm tiny business that buys from Dell I don't really have a choice in the matter.
  10. cgiandomenico

    Error -1132 Trying to Create Disaster Recovery ISO Image

    I notice that at least two other's disaster recovery preparation fails while attempting to create the same five files. It occurred to me that I am using a Dell OEM copy of Windows XP (a green CD) to build the disaster recovery set. Could this be the problem? I don't have any other copies of the operating system to try.
  11. cgiandomenico

    Can't backup Iomega NAS. error -1017 insufficient permissions

    Windows XP SP2. I have resolved the 1017 error issue. While I do not know the exact cause I believe it was related to some modifications I made to my system that were unrelated to retrospect. While investigating the problem I discovered that regedit could not export registry keys. The solution I found was: (1) Restore Windows using an image file (not made with retrospect). (2)Restore using retrospective to a recent time point when both retrospect and regdedit worked. I can now backup my local drive and my NAS without incurring any 1017 errors. Thank-you for your follow-up.
  12. cgiandomenico

    Can't backup Iomega NAS. error -1017 insufficient permissions

    It seems the problem with the NAS was coincidental. All of my backups, including of local drives, are failing with a -1017 error. I rolled back Windows to a time when Retrospect was working. No luck. Next steps are a repair of Windows followed by a reinstall of Retrospect.
  13. cgiandomenico

    Can't backup Iomega NAS. error -1017 insufficient permissions

    I didn't think this document applied because I had configured the NAS to allow complete access to all Workgroup members without passwords. However, I also experimented with share permissions and learned something. (Note, this NAS is very basic, it only supports share-level protection with only two access states: Full Access/No Access.) When I assigned password protection to a share I was able to produce the -1017 error in Retrospect by suppling an incorrect username & password when prompted while making a subvolume. I could access the subvolume by supplying the correct credentials. I could also access any subvolume without supplying credentials if the share was not password protected. Next I setup an Immediate Backup and entered the correct login credentials in the "Enter network password" automatic login dialog. I also set up Retrospect to startup under my account which is able to access the NAS shares. I checked the automatic login properties of the backup set which is located on my local hard drive. These properties were greyed out. I think this covers all three login aspects covered by the document. I ran the immediate backup and got the same error as before: Can't initialize Snapshot file, error -1017 (insufficient permissions)
  14. I am attempting to backup an Iomega NAS model: "Home Network Hard Drive" with Retrospect 7.5. This NAS uses an unknown operating system and the drive is formatted as FAT32. The NAS is part of a windows Workgroup. Retrospect 7.5 is able to preview the contents of NAS volumes from within the Immediate Backup pane. I have tried using all reasonable automatic logon credentials including: nothing, Administrator, Local User, & the NAS Administrator. The backup is failing with an error -1017. The details are shown below. I haven't loaded any backup client software on the NAS. It doesn't have an interface to permit program installation. The Iomega NAS came with Retrospect Express HD 2.0 and I have successfully backed it up using this software. I had assumed if a cut down version of Retrospect worked with this NAS my Retrospect Professional would too... Does anyone have any thought about what might be happening and how to fix it? + Retrospect version 7.5.508 Launched at 3/24/2008 10:22 AM in user account WELLREAD3\Administrator + Driver Update and Hot Fix, version 7.5.13.100 + Executing Immediate Backup at 3/24/2008 10:24 AM To Backup Set junk... - 3/24/2008 10:24:54 AM: Copying Pictures on Iomega500 Can't initialize Snapshot file, error -1017 (insufficient permissions) 3/24/2008 10:24:55 AM: Execution incomplete Duration: 00:00:00
  15. cgiandomenico

    Error -1132 Trying to Create Disaster Recovery ISO Image

    The errors occur with the latest version and Hot fix (see below). By watching the event viewer in the Retrospect activity monitor, one can see that the error occurs while the Disaster Recovery Preparation is duplicating the files of the snapshot that the emergency disk will be based on. It writes the files necessary for the .iso image to "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State". The files that generate the "cannot write" error are ultimately written to this directory. The disaster recovery preparation continues by writing the .iso image, but ultimately the process fails and Retrospect deletes the .iso image the and the contents of the directory mentioned above. Only then does Retrospect write the following error message in the operations log. + Retrospect version 7.5.508 Launched at 2/22/2008 12:21 PM + Driver Update and Hot Fix, version 7.5.13.100 + Executing Prepare for Disaster Recovery at 2/22/2008 12:25 PM From Backup Set D600 - 01, Snapshot Local Disk (C:) 2/22/2008 12:00 AM To CD-ROM image file Restore Local Disk.iso... File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\atl.dll": cannot write, error -1132 (file creation error on destination volume) File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\mfc42.dll": cannot write, error -1132 (file creation error on destination volume) File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\mfc42u.dll": cannot write, error -1132 (file creation error on destination volume) File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\msvcp60.dll": cannot write, error -1132 (file creation error on destination volume) File "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State\comctl32.dll": cannot write, error -1132 (file creation error on destination volume) 2/22/2008 12:38:11 PM: 5 execution errors
×