Jump to content

lapimate

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lapimate

  • Rank
    Newbie

Profile Information

  • Gender
    Not Telling
  1. Perhaps one could use Windows to copy a Retrospect disk dataset+catalog file, or a Retrospect file dataset, to a Blu-ray disc for archiving purposes?
  2. lapimate

    VSS & CAPI2 errors

    Retrospect Client 10.5.0 (110) on Windows 10 Pro 64-bit 10586.14 I am submitting this to maybe assist others who encounter the same issues because AFAIK our Client system is “vanilla”. Windows 10 was clean installed on the Client, not as an upgrade. On the Client the Windows Event Viewer/Application log showed VSS 8194 “Errors” during Retrospect backup (ie not merely “Warnings” nor “Information”) This VSS issue was resolved by applying Rich_B_72’s solution . However then CAPI2 513 “Errors” became visible in the Client’s Windows Event Viewer/Application log during Retrospect backup. This CAPI2 issue was resolved by applying Fearless96’s version of the solution suggested by szz43.
  3. Thanks Scillonian. I do have InstantScan on, so instead of running the Duplicate soon after Backup, I'll try scheduling it for before the next Backup as a fuzzy workaround.
  4. Windows 10 Prof RTM. Retrospect Desktop 10.5.0.110. I have used the "sequential scheduling" method for several years, in particular to do a Backup, then a Duplicate (of the catalog files) where the Duplicate is scheduled to be run some minutes after the Backup is scheduled. Usually it works OK, but sometimes the Duplicate fails because Retrospect seems not to have closed the relevant Backup catalog file before starting the Duplicate so it complains 'File "... Catalog Files\xxx.rbc": appears incomplete', where xxx is a catalog file to be duplicated. Waiting and re-running the Duplicate later works without Retrospect complaining.
  5. lapimate

    Renaming a Subvolume

    ... Having multiple folders with identical names in the Subvolume list is crazy! ... When one examines the Properties of such a (XP Pro SP3, Retrospect 7.7) subvolume (eg "My Documents", where there are several users and thus a "My Documents" folder for each user), at least one can see the full path of the particular "My Documents" folder, but if one adds that folder into a Source Groups Container, there seems to be no way to discover which "My Documents" folder is referenced in the Source Groups Container by each "Documents" folder listed in the Source Group. It would be helpful if Retrospect made that information accessible in the Properties of a folder in a Source Group.
  6. lapimate

    "Can't Restore Removable Storage Manager Data"

    Retrospect online Help has an item for "Removable Storage Manager" [RSM] and says "... Retrospect stops the [RSM] service by default ...". The printed Guide for 7.5 (2006) has information about RSM on p49 & p269.
  7. lapimate

    Bluetooth License Check Failed

    I have since installed BlueSoleil 6.4.249 (more BT profiles available than the MS drivers) I have not seen any “Bluetooth license check failed†messages since.
  8. lapimate

    Rebuild Catalog for Restore

    See http://forums.dantz.com/showtopic.php?tid/28528/
  9. lapimate

    Best location for catalog files

    See http://forums.dantz.com/showpost.php?post/113508/
  10. lapimate

    Robustify location for catalog

    Thank you for "Duplicate" suggestion - will implement that; seems it likely will decrease potential for problems.
  11. A desirable aspect of maintaining the catalog on the external (or NAS) drive is that it maintains the catalog on a device independent of the backed-up C: drive. However EMC Insignia's recommendation is to maintain the catalog on the C: drive itself. I understand that this recommendation may sadly be necessary in the light of flaky communication and non-robust file operations in Windows or the application; this recommendation seems to somewhat defeat the purpose. I know the catalog can be rebuilt from the backup set, but this seems to be a time-consuming and sometimes fraught process, just when one is in a vulnerable recovery situation. So this is a request that Retrospect's catalog operations be made more robust to make storage of the catalog in a non-default location (eg network drive) properly reliable. Perhaps as a selectable option for those of us willing to sacrifice some speed for reliability.
  12. lapimate

    Best location for catalog files

    I understand that this recommendation may sadly be necessary in the light of flaky communication and non-robust file operations in Windows or the application. However one desirable aspect to me of maintaining the catalog on the external (or NAS) drive is that it maintains the catalog on a device independent of the backed-up C: drive! It seems to somewhat defeat the purpose to maintain the catalog on the C: drive itself? I know the catalog can be rebuilt from the backup set, but this seems to be a time-consuming and sometimes fraught process, just when one is in a vulnerable recovery situation. So I guess the implicit request is, cannot Retrospect's catalog operations be made more robust to make storage of the catalog in a non-default location more reliable so that your recommendation becomes unnecessary? Perhaps as a selectable option for those of us willing to sacrifice speed for reliability? PS: When I do an "archival" backup to DAT, I make a copy of the catalog, the Retrospect settings folder & the Retro-EN_7_6_111.exe to an SD card to store with the DAT.
  13. lapimate

    Bluetooth License Check Failed

    Thank you. What is your backup destination? NAS (Synology) drives. Note selective (ie non-full-C: drive) backups did not provoke the “Bluetooth license check failed â€; might have been duration of backup process but the backups take only a few minutes anyway (Wireless N 300Mb/s connection). Retrospect can disable the Removable Storage Manager, I am not sure if that is a factor or not. This sounds like a problem with the Bluetooth Drivers themselves. I do suspect the BT drivers’ behaviour. I have now removed the Broadcom/Widcomm BT software/drivers and installed the MS drivers as per this topic http://forum.eeeuser.com/viewtopic.php?id=38533&p=1 I have not seen any “Bluetooth license check failed†messages since. Frustrating that the problem occurred with up-to-date Broadcom/Widcomm software on a new machine with manufacturer-installed BT! When doing a backup to a hard disk or a NAS device, Retrospect sends copy commands to the file system and does not load any storage device drivers or even talk to the device manager. You can try to ignore devices from Configure>Devices>Environment. This may help reduce conflicts. I can’t report on that now, sorry, since having apparently eliminated the problem as above.
  14. lapimate

    Bluetooth License Check Failed

    Retrospect 7.6.111 for Windows with Driver Update and Hot Fix, version 7.6.1.101. Dell Vostro 1200 Windows XP Pro SP3 with Dell Wireless 355 Bluetooth module aka T60H928.06 (Broadcom 2045 Bluetooth 2.0 USB Device) and Broadcom/Widcomm Bluetooth software. When I run a Normal backup of the whole C: system drive, inevitably while Retrospect completes successfully an error message appears sometime during the process; “Bluetooth license check failed ...†and the Widcomm Bluetooth icon in the system tray turns red and the Bluetooth device cannot be re-started. (This problem does not arise if the backup is selective, such as Documents and Settings only.) This issue appears to be the same as that discussed (apparently unresolved) in the 2006 item bluetooth-license check failure when backing up system drive C: http://forums.dantz.com/showtopic.php?tid/23138/post/89871/hl/bluetooth/fromsearch/1/#89871 The Bluetooth entries in Device Manager seem to get into a confused state: the confused entries appear thus Bluetooth Devices [ie Widcomm entry] Bluetooth Bus Enumerator [broadcom 5.1.0.4200] Bluetooth Radios [Microsoft] Broadcom 2045 Bluetooth 2.0 USB Device [driver “unknownâ€, but details tab shows Broadcom 5.1.0.4000] instead of Bluetooth Devices [Widcomm] Bluetooth Bus Enumerator [broadcom 5.1.0.4200] Broadcom 2045 Bluetooth 2.0 USB Device [broadcom 5.1.0.4000] The DM can be repaired by “Uninstalling†the entry for the Broadcom 2045 under the Bluetooth Radios then “Scan for hardware changesâ€; then the Bluetooth device can be restarted. What is going on? What is Retrospect doing which upsets the Device Manager? Is there any Retrospect fix to prevent this problem arising? Is Retrospect probing ports or (USB) devices and thereby somehow conflicting with the Widcomm software, which conflict provokes corruption of the registry? I notice the OP of #89871 mentioned that the disk drive being used for backup was connected via USB. That is not my case since the C: drive is internal to the laptop, however there is a 16GB SD card installed in an adapter in the ExpressCard slot (which is reported as a USB connection). This drive is listed in the Retrospect Storage Devices window “Status†panel as “Content unrecognisedâ€. It is used for the RCB vault, so I am reluctant to uninstall it.
×