Jump to content

JohnW

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JohnW

  • Rank
    Occasional forum poster
  1. Error -106 keeps occurring

    I backup a few computers and then do a transfer of the backup to separate hard drives. This one transfer will always give me an error -106 even if I delete the entire backup and start over or recatalog and groom. The culprit is always that an empty file (actually 19,080 Kb) is created and cannot be accessed. In this case the empty file is AJ005329.rdb. If I delete the file and start the transfer over again, the transfer will continue just fine, but in another day, this will again happen. Also, the error log will just continue to grow into the 10's of thousands of errors. This, of course, effectively halts all backup operations until I come in in the morning and cancel this transfer. I then always do a recatalog because I have interrupted the backup. The recatalog takes most of the working day to complete. Meanwhile, not all the computers get backed up each day. + Executing Public_BU at 10/12/2017 3:06 AM To Backup Set Public BU... - 10/12/2017 3:06:40 AM: Transferring from Public [002] 10/12/2017 3:23:05 AM: Finished scanning backup set data files Additional error information for Disk Backup Set member "1-Public BU", Can't write to file L:\Retrospect\Public BU\1-Public BU\AJ005329.rdb, error -1023 (already exists) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] soccCallback: kNetSelectorConnect error 10061 [*] soccRecv: connection unexpectedly closed, error 0 Trouble writing: "1-Public BU" (534056960), error -106 (data overwrite attempt) - 10/12/2017 3:24:21 AM: Verifying Public BU - 10/12/2017 3:25:50 AM: Transferring from Public [002] Additional error information for Disk Backup Set member "1-Public BU", Can't write to file L:\Retrospect\Public BU\1-Public BU\AJ005329.rdb, error -1023 (already exists) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] xopFlush: flush failed, error -106 (data overwrite attempt) Trouble writing: "1-Public BU" (534056960), error -106 (data overwrite attempt) - 10/12/2017 3:25:50 AM: Verifying Public BU - 10/12/2017 3:25:51 AM: Transferring from Public [002] Additional error information for Disk Backup Set member "1-Public BU", Can't write to file L:\Retrospect\Public BU\1-Public BU\AJ005329.rdb, error -1023 (already exists) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] xopFlush: flush failed, error -106 (data overwrite attempt) Trouble writing: "1-Public BU" (534056960), error -106 (data overwrite attempt) - 10/12/2017 3:25:51 AM: Verifying Public BU - 10/12/2017 3:25:51 AM: Transferring from Public [002] Additional error information for Disk Backup Set member "1-Public BU", Can't write to file L:\Retrospect\Public BU\1-Public BU\AJ005329.rdb, error -1023 (already exists) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] xopFlush: flush failed, error -106 (data overwrite attempt) Trouble writing: "1-Public BU" (534056960), error -106 (data overwrite attempt) - 10/12/2017 3:25:51 AM: Verifying Public BU - 10/12/2017 3:25:52 AM: Transferring from Public [002] Additional error information for Disk Backup Set member "1-Public BU", Can't write to file L:\Retrospect\Public BU\1-Public BU\AJ005329.rdb, error -1023 (already exists) [*] xopFlush: flush failed, error -106 (data overwrite attempt) [*] xopFlush: flush failed, error -106 (data overwrite attempt) Trouble writing: "1-Public BU" (534056960), error -106 (data overwrite attempt) ... Repeats for 10's of thousands of lines. AJ005329.zip
  2. I am trying to update 12.0.0.188 to 12.5.0.177. I get to a screen that says: "The wizard ws interrupted before Retrospect 12.5 could be completely installed." This comes up the instant I press the button to install.
  3. Waiting for Execution unit

    I have version 10 and I am also having this problem. Right now I cannot back up at all. The top script in the "Waiting" tab states, "Waiting for execution unit." This has come up before in version 9. The last thing I did was cancel all executions by pressing the "pause" button on the ribbon. There are no little red bricks nor any indication of a script running. Being th ePro version, I cannot pick an execution unit. I have attached an image of the Execution screen. Solved by restarting Retrospect.
  4. In the backup report below there are obviously many errors. However, the final report is that the backup was successful. That would seem to be a bug to me. I don't know what the errors are and I have not been able to find some of the in the KB or the Forum. I found the one about "ASR Writer" failure, but not the "T16: MapError" or "TPCFolderLoc." Does anyone know what those errors are? Also, I see an OS error -3050. This error is not listed in the Retrospect Error Code List. Anyone know waht it is? Backup Report: + Normal backup using CSI08_Failsafe at 6/11/2014 1:43 PM To Backup Set CSI08_Failsafe... 6/11/2014 1:43:38 PM: Connected to CSI08 * Resolved container CSI08 to 1 volumes: Local Disk (C:) on CSI08 T-7: MapError: unknown Windows error -3,050 T-7: VssWAddComponentToSnapshot: UGetComponentInfo failed., osErr -3050, error -1001 - 6/11/2014 1:43:37 PM: Copying Local Disk (C:) on CSI08 T-16: MapError: unknown Windows error 1,920 T-16: TPCFolderLoc::NextFind: UGetInode failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Windows\Temp\7b4cb26d-5269-423d-bcb1-193c2f6ccc77\Program Files, osErr 1920, error -1001 T-16: MapError: unknown Windows error 1,920 T-16: TPCFolderLoc::StartFind: UGetInode failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Windows\Temp\7b4cb26d-5269-423d-bcb1-193c2f6ccc77\Program Files (x86), osErr 1920, error -1001 T-16: MapError: unknown Windows error 1,920 T-16: TPCFolderLoc::NextFind: UGetInode failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Windows\Temp\7b4cb26d-5269-423d-bcb1-193c2f6ccc77\Users, osErr 1920, error -1001 ... Many more lines (1000+) like the above Backing up 3 out of 8 files using block level incremental backup, storing full backups for remaining 5. Writer "ASR Writer" backup failed, error -1001 ( unknown Windows OS error). 6/11/2014 1:57:02 PM: Snapshot stored, 251.6 MB 6/11/2014 1:57:15 PM: Execution completed successfully Completed: 8780 files, 6.5 GB, with 66% compression Performance: 1533.7 MB/minute Duration: 00:13:38 (00:09:20 idle/loading/preparing) - 6/11/2014 1:57:19 PM: Verifying CSI08_Failsafe 6/11/2014 1:57:55 PM: Execution completed successfully Completed: 19236 files, 8.2 GB Performance: 16135.3 MB/minute Duration: 00:00:35 (00:00:04 idle/loading/preparing) 6/11/2014 1:57:57 PM: Script "CSI08_Failsafe" completed successfully
  5. Thanks for your interest and suggestions Lennart.
  6. I did both of the above. Specifically, I deleted the script to run CSI2 and recreated it. I still have the same problem.What next?
  7. I ran each script and it turns out that only one script produces the error. It is a backup script to local disk. Once it gets past the first "Matching CSI2" it starts another matching process and gives the error there. I think the simplest thing to do would be to (1) Verify the media, and if that fails, (2) Create a new script. I rebuilt the Catalog for CSI2 a few days ago and got two of these: "Backup Set format inconsistency (9 at 3)."
  8. Good questions Lennart. I am backing up to local disks. I will try to run each script to see what happens and answer your other questions.
  9. Running Single Server 7.7.620 under Win 7 Pro 32bit. I have been successfully running Retrospect SS for several years. This error is now reported for each disk based backup script I run. Disk space is available with hundreds of GB unused. I have rebuilt the catalogs from disk. I re-installed using the "Modify" option and rebooted. Scripts are working for the file based backups -- what I use to backup the backups to separate disks. I have inserted the last entry in "assert_log.utx" and attached the entire file. Thread ID: 00001200, Name: Main thread EAX:0022C350 CS:001B EIP:77917094 EFlags:00000246 EBX:00000000 SS:0023 ESP:0022C998 EBP: 0022C9B4 ECX:00000008 DS:0023 ESI:0022CA04 FS: 003B EDX:00000018 ES:0023 EDI:0022CDA8 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00046094 22CA04 0 0 0 3BDE10 22CA20 6065A40F 22CA04 bdrock20.dll UGetMessage +25 22CA04 0 0 0 3B6B80 0 370000 3BE288 meson.dll WinMsgBlocker::BlockForMsg +2F 22D06C 22CD3C 0 0 0 4E 0 22D018 meson.dll msgHelper +1EB 3BDE10 1 22D434 22D6F8 0 427BCC0 0 3BDE10 meson.dll doTask +246 'Msg ' 60638BD0 0 0 3BDE10 1 22D434 22D6F8 meson.dll TThread::TaskCall +85 3BDE10 'Msg ' 60638BD0 3BDE10 1 22D434 22D6F8 0 meson.dll TThread::MsgBlock +96 'Msg ' 22D6A4 6064E646 22DCE8 6064E646 'LopT' 3BDE10 0 meson.dll msgInTask +11 22DCE8 6064E646 'LopT' 3BDE10 0 0 22E348 6068099C meson.dll doTask +246 'MsgT' 60639CB0 0 0 22DCE8 6064E646 'LopT' 3BDE10 meson.dll TThread::TaskCall +85 3BDE10 'MsgT' 60639CB0 22DCE8 6064E646 'LopT' 3BDE10 0 meson.dll loopInTask +27 'LopT' 3BDE10 0 0 22E348 6068099C 0 22DD80 meson.dll doTask +246 'LopT' 60639C80 0 0 'LopT' 3BDE10 0 0 meson.dll TThread::TaskCall +85 3BDE10 'LopT' 60639C80 'LopT' 3BDE10 0 0 22E348 meson.dll TThread::MsgLoop +45 'LopT' 22E354 6064E646 60637E00 0 B 22E9A4 6064E646 meson.dll mesonGoLoop +14 60637E00 0 B 22E9A4 6064E646 0 22FEF8 6112CCF4 meson.dll doTask +246 'Task' 6062FCE0 0 0 60637E00 0 B 22E9A4 meson.dll TThread::TaskCall +85 3BDE10 'Task' 6062FCE0 60637E00 0 B 22E9A4 6064E646 meson.dll mesonGo +135 0 22FEF8 6112CCF4 0 0 0 0 73B000D8 meson.dll doTask +246 'Prog' 6062FBA0 0 0 0 22FEF8 6112CCF4 0 meson.dll TThread::TaskCall +85 3BDE10 'Prog' 6062FBA0 0 22FEF8 6112CCF4 0 0 meson.dll Meson +2C 0 0 0 0 73B000D8 0 800000 9 Retrospect.exe _WinMain +664 61100000 0 372332 A 90546B1F 0 0 7FFDF000 Retrospect.exe ___tmainCRTStartup +140 7FFDF000 22FFD4 7793377B 7FFDF000 7525857F 0 0 7FFDF000 kernel32.dll 0001:0004dd6c 7FFDF000 7525857F 0 0 7FFDF000 0 0 0 ntdll.dll 0001:0006277b ntdll.dll 0001:0006274e assert_log.zip
  10. I am getting the same error now for the last week every time I run a script. I was running 7.7.620 and I have also re-installed it. The error persists on a system that has been running Retrospect for 2 years.
  11. 7.7 Single Server

    I found a solution to 3) -- Delete the backup set and then open the catalog file on disk. This recreates the backup set. So the good news is that I was able to keep and use my scripts, backup files, and catalog files. Recreating the clients and backup sets is trivial compared to recreating all the scripts. btw, I'm not seeing any memory leaks whle running four execution threads. So, eating crow, I'd say that "STAY AWAY" is unjustified dramatic hyperbole.
  12. 1) Trying to figure out how to get a permanent license after purchasing the upgrade took a very long time, many tries, and finally some luck. I used a different computer and all of a sudden the activation process went from trying to sell me the software I had alredy purchased to giving me an activation code. 2) Installing has been a nightmare. I have been using Retrospect since version 5.0 and I have never had this much trouble. I went to each client machine and installed the new client and then found all the volumes in each client had been duplicated and I now had phantom volumes. So, delete each client and recreate. (I was unable to update each client from within Retrospect due to some error. Note that this error would come after I was informed that the client had been succesfully updated. In fact, the client had been deleted on the client machine and no new client installed.) 3) Backup sets: Not one backup set can find its respective catalog file. Even though the catalog file is on disk. I am queried as to where the catalog file is. I locate it with the file browser that pops up and select "Open" to open the catalog file. I get an error, "File could not be found. Check the name and try again." I have not been able to run this program to backup anything. I cannot even access my version 7.0 catalog files. Recommendation: Stay away until they can get it working.
  13. Hee is the URL: http://forums.dantz.com/showtopic.php?tid/26685/
  14. I disabled it on both as I wasn't sure which to do it on.
  15. Thanks for the quote. I am using ESET Smart Security 3.0. I haven't tried to find out what the vendor says because that problem is solved and I have another pressing one right now. However, searching ESET's KB for setupapi.log returned no hits.
×