Jump to content

error -102 (trouble communicating)


Recommended Posts

I've been using Retrospect Desktop Backup 5.6 (RDU 3.0, then 3.1, then back to 3.0 based on the error I'm having with no diff. So I'm back to 3.1 again) to back up a large file collection that is modified daily. The 81K+ files are taking up about 21GB on an IDE 40GB drive. The backup (with some files filtered out using a custom selector, therefore needing about 16GB on the backup drive) is to a file backup (.rbf) on another IDE 80G drive (about 12G free with 8GB of the backup .rbf present, 21G free if the backup set is cleared during a recycle) on the same PC.

 

 

 

The PC specs are: 500MHz 500MHz, 512M RAM, Windows 2000 SP2. Boot drive with OS 12GB (Retrospect installed here). Separate 40GB drive for data and 80GB drive for backups. All drives are IDE and NTFS formatted (allowing 1TB files) Norton Utilities 2002 says that the file structures on all drives show no errors. I have other PCs backed up to the same 80GB backup drive (over a 10/100 network), with the largest single backup file being 25GB. I'm logged in with an Admin-level account (relevant with running Retrospect manually) and the Retrospect Launcher service is set with the same Admin-level account (ID and password) when running automatic schedules. Compression is enabled but file verify is off.

 

 

 

The backup had been working fine until last night when the schedule did a recycle. The (recycle) backup failed, complaining about "TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001" and "Trouble writing: "XDrivePics_to_RDrive" (375327232), error -102 (trouble communicating)."

 

 

 

I've tried to recycle the backup a couple of times with the same results. I've also tried to do a few "Normal" (incremental) backups after I allow the "Recycle" backup to run and fail. On each "Normal" backup Retrospect gets a little further (backing up some more files) until the same failure occurs. I've let these subsequent backups run to completion, including the Snapshot.

 

 

 

Any ideas? Under W2K NTFS the file size shouldn't be a problem and I have other backups that are bigger (file size). The number of files is large but I've backed up entire harddrives with more total files. There's nothing wrong with either IDE drive, both connected to Promise IDE cards (for almost a year). The "error -102 (trouble communicating)" message cause doesn't seem to correspond to the descriptions listed in the Dantz Retrospect Knowledgebase. If the error is due to being out of space (doesn't seem likely), the larger number of files, etc. a better error message would be very helpful.

 

 

 

I could try breaking up the files into subsets and backing up to multiple smaller backup sets. But this is inconvenient, shouldn't be needed since I have and am backing up larger sets, and I'm not confident that the problem won't occur with other sets since I don't understand the cause.

 

 

 

 

 

------------------------------------------------------------------------------------------------------

 

 

 

+ Retrospect version 5.6.127

 

Automatically launched at 7/24/2002 4:50 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_Pics_to_RDrive at 7/24/2002 7:32 AM

 

To backup set XDrivePics_to_RDrive...

 

 

 

- 7/24/2002 7:32:38 AM: Copying Pics on DRIVE_X (X:)

 

7/24/2002 8:05:23 AM: Snapshot stored, 33.9 MB

 

7/24/2002 8:05:25 AM: Execution completed successfully

 

Completed: 111 files, 12.3 MB, with 0% compression

 

Performance: 66.6 MB/minute

 

Duration: 00:32:46 (00:03:29 idle/loading/preparing)

 

 

 

Quit at 7/24/2002 8:05 AM

 

 

 

------------- had been working OK. Upgraded to RDU 3.0 on evening before Recycle was about to happened based on the scheduled script (just luck of the draw... I hadn't noticed that the schedule would be doing a recycle overnight)

 

 

 

 

 

+ Retrospect version 5.6.127

 

Automatically launched at 7/25/2002 4:55 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Recycle backup using XDrive_Pics_to_RDrive at 7/25/2002 4:55 AM

 

To backup set XDrivePics_to_RDrive...

 

7/25/2002 4:55:14 AM: Recycle backup: The backup set was reset

 

 

 

- 7/25/2002 4:55:14 AM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrivePics_to_RDrive" (392169984), error -102 (trouble communicating)

 

7/25/2002 7:49:03 AM: Execution stopped by operator

 

Remaining: 16201 files, 5.4 GB

 

Completed: 64341 files, 8.1 GB, with 0% compression

 

Performance: 49.7 MB/minute

 

Duration: 02:53:48 (00:02:38 idle/loading/preparing)

 

 

 

Quit at 7/25/2002 7:53 AM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 7:56 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Recycle backup using XDrive_Pics_to_RDrive at 7/25/2002 8:00 AM

 

To backup set XDrivePics_to_RDrive...

 

7/25/2002 8:00:44 AM: Recycle backup: The backup set was reset

 

 

 

- 7/25/2002 8:00:44 AM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

can't read data, BackupRead failed, X:\My_Data\Pics\alt.binaries.pictures.autos\2001_red_corvette.jpg, winerr 1450, error -1001

 

File "X:\My_Data\Pics\alt.binaries.pictures.autos\2001_red_corvette.jpg": can't read, error -1001 (unknown Windows OS error)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrivePics_to_RDrive" (382732800), error -102 (trouble communicating)

 

7/25/2002 8:37:46 AM: Execution stopped by operator

 

Remaining: 16204 files, 5.5 GB

 

Completed: 64338 files, 8.1 GB, with 0% compression

 

Performance: 228.9 MB/minute

 

Duration: 00:37:01 (00:00:53 idle/loading/preparing)

 

 

 

Quit at 7/25/2002 8:37 AM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 8:39 AM

 

+ Retrospect Driver Update, version 3.1.103

 

Quit at 7/25/2002 8:39 AM

 

 

 

 

 

-------------------- tried putting RDU 3.0 back thinking that was the culprit, but no diff (manual recycle)

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 7:14 PM

 

+ Retrospect Driver Update, version 3.0.101

 

 

 

+ Recycle backup using XDrive_Pics_to_RDrive at 7/25/2002 7:15 PM

 

To backup set XDrivePics_to_RDrive...

 

7/25/2002 7:15:43 PM: Recycle backup: The backup set was reset

 

 

 

- 7/25/2002 7:15:43 PM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrivePics_to_RDrive" (375327232), error -102 (trouble communicating)

 

7/25/2002 7:49:02 PM: Execution stopped by operator

 

Remaining: 16216 files, 5.5 GB

 

Completed: 64337 files, 8.1 GB, with 0% compression

 

Performance: 280.2 MB/minute

 

Duration: 00:33:16 (00:03:38 idle/loading/preparing)

 

 

 

Quit at 7/25/2002 7:49 PM

 

 

 

---------------------- Need to backup up almost 16GB, failed about 8GB in

 

 

 

---------------------- so put RDU 3.1 back and tried again

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 7:50 PM

 

+ Retrospect Driver Update, version 3.1.103

 

Quit at 7/25/2002 7:51 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 7:55 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

 

 

----------------- did a file backup set "Repair" just to maek sure things were fine and bacause I had stopped the backp during the Snapshot before

 

 

 

+ Executing Recatalog at 7/25/2002 7:56 PM

 

To backup set XDrivePics_to_RDrive...

 

7/25/2002 8:02:03 PM: Execution completed successfully

 

Completed: 64337 files, 8.4 GB

 

Performance: 1513.2 MB/minute

 

Duration: 00:05:39

 

Quit at 7/25/2002 8:05 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 8:07 PM

 

+ Retrospect Driver Update, version 3.1.103

 

Quit at 7/25/2002 8:08 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 8:41 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_Pics_to_RDrive at 7/25/2002 8:57 PM

 

To backup set XDrivePics_to_RDrive...

 

 

 

- 7/25/2002 8:57:20 PM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrivePics_to_RDrive" (1371441664), error -102 (trouble communicating)

 

7/25/2002 9:33:37 PM: Snapshot stored, 33.9 MB

 

7/25/2002 9:33:39 PM: 1 execution errors

 

Remaining: 15729 files, 4.5 GB

 

Completed: 526 files, 947.1 MB, with 0% compression

 

Performance: 195.2 MB/minute

 

Duration: 00:36:18 (00:00:56 idle/loading/preparing)

 

 

 

Quit at 7/25/2002 9:34 PM

 

 

 

-------- Normal backup, backed up a little more then failed

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/25/2002 9:35 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_Pics_to_RDrive at 7/25/2002 9:36 PM

 

To backup set XDrivePics_to_RDrive...

 

 

 

- 7/25/2002 9:36:12 PM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrivePics_to_RDrive.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrivePics_to_RDrive" (2144807424), error -102 (trouble communicating)

 

7/25/2002 10:08:45 PM: Snapshot stored, 33.9 MB

 

7/25/2002 10:08:50 PM: 1 execution errors

 

Remaining: 15615 files, 3.9 GB

 

Completed: 114 files, 701.6 MB, with 0% compression

 

Performance: 701.5 MB/minute

 

Duration: 00:32:37 (00:02:50 idle/loading/preparing)

 

 

 

-------- Normal backup, backed up a little more then failed

Link to comment
Share on other sites

I tried deleting the backup set and creating a new one (backup2.rbf) from scratch. I saw the same "MapError: unknown Windows error 1,450; TFile:: Write... winerr 1450, error -1001' error -102 (trouble communicating)" problem, with the error happening after backing up a nearly identical amount (8.1GB completed, 5.5GB remaining; the last file backed up just a couple of files further than previously seen).

 

 

 

I ran this backup with the RDU.rpx 3.0.101 file rather than the 3.1. Looking back further in the logs (to a few months ago), the 3.0 was the last one for which a successful backup was run on this backup set/file collection. So it doesn't *seem* like RDU 3.0 vs. 3.1 (or even 2.8 and older since these also show successful recycles in the log) is the culprit.

 

 

 

And, as before, I can then run multiple subsequent "Normal" backups to keep backing up a little more (e.g. another 800MB or so each time) of the set before the error occurs again. So if I run the program another eight times or so I *may* be able to back up the set. The other options may to be to break the set into multiple smaller backups. But this problem calls into question my entire Retrospect backup strategy since I don't know the cause and what size (file size, number of files in a backup) will work reliably.

 

 

Link to comment
Share on other sites

Well, I've tried a few more things, and Retrospect has pretty much self-destructed--the worst case for any program that I've ever seen. The embedded C++ class error messages in the log aren't very useful and some better "translate into the real world" error messages would be useful.

 

 

 

I tried to break the backup into two smaller backups (thinking that the size or number of files could be an issue). Both smaller backups failed in the same way (error -102). I then ran a full Norton Utilities scan and allowed it to clean up a number of minor issues on the drives (pretty standard stuff that happens over time). I've also tried to Repair/Reinstall Retrospect (thinking that the installation might have become somehow corrupted) then recopied RDU3.1 and also ran a W2K Scandisk on both the "From" X drive and "To" R Drive (no errors reported). So far I haven't resorted to a full deinstall & reinstall of Retrospect (how would I do this without losing my scripts, custom selectors, etc. ?) nor a reinstall of Windows 2000.

 

 

 

I *have* managed to complete new backup sets (assuming these are OK--so far the errors seem to indicate that the backups halts but not that the actual files in the backup have any problems) by running multiple sequential "Normal" backups, allowing the errors to occur and then allowing the snapshot to complete. I ran Retrospect Verify scans on both backups (around 7GB each) and they showed one or more "Bad backup set header found" messages (one less than the number of backups sessions)--what does that mean and what do I do about it (doing a Tools/Repair didn't fix it)? I did another Recycle on one of the backup sets in an effort to clean things up but I got the same failure and same "Bad backup set header found" messages in the log when I did a another verify. So, even though I can see the files in the backup set, I'm not confident that I can recover them due to these "Bad backup set header found" messages.

 

 

 

No other programs are failing and no programs (diagnostic or otherwise) are reporting any errors with the drives, file systems or Windows OS. All files (almost all data-jpeg, mpeg, rar, etc.) on all drives are accessible and can be opened and viewed normally, so no program other than Retrospect is having trouble reading or writing them. I have not trouble accessing either the X or R backups drives using the Windows OS/Explorer or any other programs. No relevant errors are shown in the W2K Event Viewer (although the even viewer does say that the "To" R backup drive is "near capacity" with 6GB free out of 80GB total). I've also run a virus scan with the latest Virus Defs using Norton AntiVirus 2002 and it didn't report anything.

 

 

 

Below are the logs (edited for brevity--e.g. redundant errors deleted, long paths and filenames reduced, etc.), with several additional errors.

 

 

 

----------------------------------------------------------------------

 

 

 

- 7/26/2002 6:50:50 PM: Copying NewsBin on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

can't read data, BackupRead failed, X:\My_Data\Pics\VacationPic1.jpg, winerr 1450, error -1001

 

File "X:\My_Data\Pics\VacationPic1.jpg.jpg": can't read, error -1001 (unknown Windows OS error)

 

MapError: unknown Windows error 1,450

 

TPCFileLoc::GetInfo: UFindFirstFile failed, X:\My_Data\Pics\VacationPic2.jpg, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TPCFile::BackupReadOpen: UCreateFile failed, X:\My_Data\Pics\VacationPic2.jpg, winerr 1450, error -1001

 

File "X:\My_Data\Pics\VacationPic2.jpg": can't read, error -1001 (unknown Windows OS error)

 

7/26/2002 7:08:17 PM: Snapshot stored, 11.5 MB

 

7/26/2002 7:08:18 PM: 23 execution errors

 

Remaining: 7687 files, 2.7 GB

 

Completed: 501 files, 920.3 MB, with 0% compression

 

Performance: 391.5 MB/minute

 

Duration: 00:17:27 (00:00:57 idle/loading/preparing)

 

 

 

Quit at 7/26/2002 7:09 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/26/2002 7:45 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_NewsBin_to_RDrive at 7/26/2002 7:45 PM

 

To backup set XDrive_Newsbin_to_RDriv...

 

 

 

- 7/26/2002 7:45:35 PM: Copying NewsBin on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

can't read data, BackupRead failed, X:\My_Data\Pics\VacationPic3.jpg, winerr 1450, error -1001

 

File "X:\My_Data\Pics\VacationPic3.jpg": can't read, error -1001 (unknown Windows OS error)

 

MapError: unknown Windows error 1,450

 

TPCFileLoc::GetInfo: UFindFirstFile failed, X:\My_Data\Pics\VacationPic4.jpg, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TPCFile::BackupReadOpen: UCreateFile failed, X:\My_Data\Pics\VacationPic4.jpg, winerr 1450, error -1001

 

File "X:\My_Data\Pics\VacationPic4.jpg": can't read, error -1001 (unknown Windows OS error)

 

MapError: unknown Windows error 1,450

 

TFile::Write: WriteFile failed, R:\Backups\WSERV\X_Drive_Pics\XDrive_Newsbin_to_RDriv.rbf, winerr 1450, error -1001

 

Trouble writing: "XDrive_Newsbin_to_RDriv" (1263217152), error -102 (trouble communicating)

 

MapError: unknown Windows error 1,450

 

 

 

 

 

---- what is this about? The program is reporting some sort of problem with its internal files. I don't see a "intv0004.reh" file but the "launcher.dat" file is present and opens with Notepas (although, as a binary file, the contents are meaningless).

 

 

 

TFileLoc::Delete: UDeleteFile failed, C:\Program Files\Dantz\Retrospect\intv0004.reh, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFolderLoc::StartFind: UFindFirstFile failed, C:\Program Files\Dantz\Retrospect, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFolderLoc::StartFind: UFindFirstFile failed, C:\Program Files\Dantz\Retrospect, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFolderLoc::StartFind: UFindFirstFile failed, C:\Program Files\Dantz\Retrospect, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFile::Open: UCreateFile failed, C:\Program Files\Dantz\Retrospect\intv0004.reh, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFileLoc::Delete: UDeleteFile failed, C:\Program Files\Dantz\Retrospect\intv0004.reh, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFile::Open: UCreateFile failed, C:\Program Files\Dantz\Retrospect\launcher.dat, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFileLoc::Delete: UDeleteFile failed, C:\Program Files\Dantz\Retrospect\launcher.dat, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TFile::Open: UCreateFile failed, C:\Program Files\Dantz\Retrospect\launcher.dat, winerr 1450, error -1001

 

7/26/2002 8:03:18 PM: Snapshot stored, 11.5 MB

 

7/26/2002 8:03:19 PM: 5 execution errors

 

Remaining: 7557 files, 1.9 GB

 

Completed: 130 files, 846.2 MB, with 0% compression

 

Performance: 626.7 MB/minute

 

Duration: 00:17:44 (00:00:21 idle/loading/preparing)

 

 

 

Quit at 7/26/2002 8:04 PM

 

 

 

+ Normal backup using XDrive_NewsBin_to_RDrive at 7/26/2002 8:43 PM

 

To backup set XDrive_Newsbin_to_RDriv...

 

 

 

- 7/26/2002 8:43:50 PM: Copying NewsBin on DRIVE_X (X:)

 

7/26/2002 9:00:44 PM: Snapshot stored, 11.5 MB

 

7/26/2002 9:00:45 PM: Execution completed successfully

 

Completed: 7397 files, 1.2 GB, with 0% compression

 

Performance: 274.8 MB/minute

 

Duration: 00:16:54 (00:01:08 idle/loading/preparing)

 

 

 

Quit at 7/26/2002 9:00 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/26/2002 9:02 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Executing Verify at 7/26/2002 9:04 PM

 

To backup set XDrive_to_RDrive...

 

Bad backup set header found (0x01000480 at 6,336,519)

 

7/26/2002 9:09:23 PM: 1 execution errors

 

Completed: 52081 files, 7.0 GB

 

Performance: 1482.3 MB/minute

 

Duration: 00:04:48

 

 

 

+ Executing Verify at 7/26/2002 9:11 PM

 

To backup set XDrive_Newsbin_to_RDriv...

 

Bad backup set header found (0xeb0c5001 at 3,571,743)

 

Bad backup set header found (0xfa4f0c2f at 4,545,026)

 

Bad backup set header found (0x01010000 at 5,427,933)

 

Bad backup set header found (0x20000000 at 6,104,240)

 

7/26/2002 9:15:51 PM: 4 execution errors

 

Completed: 28574 files, 7.1 GB

 

Performance: 1545.6 MB/minute

 

Duration: 00:04:41

 

 

 

+ Executing Recatalog at 7/26/2002 9:25 PM

 

To backup set XDrivePics_to_RDrive...

 

Bad backup set header found (0x01000480 at 6,336,519)

 

7/26/2002 9:30:53 PM: 1 execution errors

 

Completed: 52082 files, 7.0 GB

 

Performance: 1408.9 MB/minute

 

Duration: 00:05:03

 

Quit at 7/26/2002 9:38 PM

 

 

 

+ Retrospect version 5.6.127

 

Automatically launched at 7/27/2002 4:30 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_Pics_to_RDrive at 7/27/2002 4:30 AM

 

To backup set XDrivePics_to_RDrive...

 

 

 

- 7/27/2002 4:30:12 AM: Copying Pics on DRIVE_X (X:)

 

7/27/2002 5:01:54 AM: Snapshot stored, 33.9 MB

 

7/27/2002 5:01:56 AM: Execution completed successfully

 

Completed: 2 files, 222 KB

 

Performance: 2.1 MB/minute

 

Duration: 00:31:43 (00:03:02 idle/loading/preparing)

 

 

 

+ Normal backup using XDrive_NewsBin_to_RDrive at 7/27/2002 5:02 AM

 

To backup set XDrive_Newsbin_to_RDriv...

 

 

 

- 7/27/2002 5:02:10 AM: Copying NewsBin on DRIVE_X (X:)

 

7/27/2002 5:02:10 AM: No files need to be copied

 

7/27/2002 5:16:00 AM: Snapshot stored, 11.5 MB

 

7/27/2002 5:16:01 AM: Execution completed successfully

 

Duration: 00:13:51 (00:00:55 idle/loading/preparing)

 

 

 

Quit at 7/27/2002 5:16 AM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 7:18 AM

 

+ Retrospect Driver Update, version 3.1.103

 

Quit at 7/27/2002 7:19 AM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 8:11 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Executing Verify at 7/27/2002 8:11 AM

 

To backup set XDrivePics_to_RDrive...

 

Bad backup set header found (0x01000480 at 6,336,519)

 

7/27/2002 8:16:32 AM: 1 execution errors

 

Completed: 52084 files, 7.0 GB

 

Performance: 1469.0 MB/minute

 

Duration: 00:04:52

 

 

 

+ Recycle backup using XDrive_Pics_to_RDrive at 7/27/2002 8:17 AM

 

To backup set XDrivePics_to_RDrive...

 

7/27/2002 8:17:02 AM: Recycle backup: The backup set was reset

 

 

 

- 7/27/2002 8:17:02 AM: Copying Pics on DRIVE_X (X:)

 

MapError: unknown Windows error 1,450

 

can't read data, BackupRead failed, X:\My_Data\Movie1.mpg, winerr 1450, error -1001

 

File "X:\My_Data\Movie1.mpg": can't read, error -1001 (unknown Windows OS error)

 

MapError: unknown Windows error 1,450

 

TPCFileLoc::GetInfo: UFindFirstFile failed, X:\My_Data\Movie2.mpg, winerr 1450, error -1001

 

MapError: unknown Windows error 1,450

 

TPCFile::BackupReadOpen: UCreateFile failed, X:\My_Data\Movie2.mpg, winerr 1450, error -1001

 

File "X:\My_Data\Movie2.mpg": can't read, error -1001 (unknown Windows OS error)

 

Trouble writing: "XDrivePics_to_RDrive" (2204109312), error -102 (trouble communicating)

 

7/27/2002 8:56:08 AM: Snapshot stored, 34.0 MB

 

7/27/2002 8:56:13 AM: 5 execution errors

 

Remaining: 735 files, 825.6 MB

 

Completed: 51368 files, 5.9 GB

 

Performance: 285.6 MB/minute

 

Duration: 00:39:10 (00:02:13 idle/loading/preparing)

 

 

 

+ Normal backup using XDrive_Pics_to_RDrive at 7/27/2002 8:58 AM

 

To backup set XDrivePics_to_RDrive...

 

 

 

- 7/27/2002 8:58:18 AM: Copying Pics on DRIVE_X (X:)

 

7/27/2002 9:31:00 AM: Snapshot stored, 34.0 MB

 

7/27/2002 9:31:06 AM: Execution completed successfully

 

Completed: 735 files, 825.6 MB, with 0% compression

 

Performance: 450.3 MB/minute

 

Duration: 00:32:47 (00:03:01 idle/loading/preparing)

 

 

 

Quit at 7/27/2002 9:31 AM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 9:31 AM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Executing Verify at 7/27/2002 9:37 AM

 

To backup set XDrivePics_to_RDrive...

 

Bad backup set header found (0x01020000 at 6,346,774)

 

7/27/2002 9:42:20 AM: 1 execution errors

 

Completed: 52103 files, 7.0 GB

 

Performance: 1471.0 MB/minute

 

Duration: 00:04:50

Link to comment
Share on other sites

OK, "Uncle" -- Retrospect is toast.

 

 

 

I tried to backup up from the "X" drive on the PC with Retrospect to an 80GB (for backups, plenty of free space) "E" on another PC running WinXP over a 100Mb LAN. I do cross network backups like this all the time with Retrospect, so this was nothing new. On the first try Retrospect failed part way thru the backup with several cryptic C++ class errors.

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 12:16 PM

 

+ Retrospect Driver Update, version 3.1.103

 

 

 

+ Normal backup using XDrive_Pics_to_EDrive15 at 7/27/2002 12:21 PM

 

To backup set XDrive_Pics_to_EDrive15...

 

 

 

- 7/27/2002 12:21:17 PM: Copying Pics on DRIVE_X (X:)

 

Trouble writing: "XDrive_Pics_to_EDrive15" (1919552000), error -102 (trouble communicating)

 

TFile::SetEOF: SetEndOfFile failed, \\Awpc15\e\Backups\AWPC8\Pics\XDrive_Pics_to_EDrive15.rbf.rfc, winerr 6, error -1100

 

Can't create session, error -1100 (invalid handle)

 

7/27/2002 1:03:41 PM: Execution incomplete

 

Remaining: 9963 files, 4.1 GB

 

Completed: 70780 files, 9.5 GB, with 0% compression

 

Performance: 233.9 MB/minute

 

Duration: 00:42:24 (00:00:54 idle/loading/preparing)

 

 

 

TFile::SetPosFromEnd: SetFilePointer failed, \\Awpc15\e\Backups\AWPC8\Pics\XDrive_Pics_to_EDrive15.rbf.rfc, winerr 6, error -1100

 

Quit at 7/27/2002 1:08 PM

 

 

 

 

 

I took a look at the knowledgebase regarding uninstalling (and reinstallng) Retrospect. It says to move/copy your config55.dat and config55.bak (although I hope that these aren't part of the problem) and do an Add/Remove of Retrospect. But then is says delete all "Retro" entries in the W2K Registry. I couldn't find any (nor a Dantz entry) so I just did a Remove and then a Reinstall. I then put back the RDU.rpx (3.0) and restored the two config55.xxx files to restore my configs. When I tried to backup to across the network to an "E" drive, it complained about an OutOfSync catalog. So I ran the Repair and tried to run another Normal backup. More failures with more cryptic C++ class errors.

 

 

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 1:35 PM

 

+ Retrospect Driver Update, version 3.0.101

 

 

 

+ Normal backup using XDrive_Pics_to_EDrive15 at 7/27/2002 1:37 PM

 

To backup set XDrive_Pics_to_EDrive15...

 

 

 

- 7/27/2002 1:37:12 PM: Copying Pics on DRIVE_X (X:)

 

Catalog out of sync with backup set "XDrive_Pics_to_EDrive15".

 

To repair it, use Tools>Repair>Update Existing from the Directory.

 

7/27/2002 1:39:59 PM: Execution incomplete

 

Remaining: 80743 files, 13.6 GB

 

Completed: 0 files, zero KB

 

Performance: 0.0 MB/minute

 

Duration: 00:02:46 (00:02:19 idle/loading/preparing)

 

 

 

+ Executing Recatalog at 7/27/2002 1:40 PM

 

To backup set XDrive_Pics_to_EDrive15...

 

7/27/2002 2:04:00 PM: Execution completed successfully

 

Completed: 70780 files, 9.8 GB

 

Performance: 427.4 MB/minute

 

Duration: 00:23:27

 

Quit at 7/27/2002 2:12 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 2:37 PM

 

+ Retrospect Driver Update, version 3.0.101

 

 

 

+ Normal backup using XDrive_Pics_to_EDrive15 at 7/27/2002 2:39 PM

 

To backup set XDrive_Pics_EDrive15b...

 

 

 

- 7/27/2002 2:39:19 PM: Copying Pics on DRIVE_X (X:)

 

Trouble writing: "XDrive_Pics_EDrive15b" (1815874048), error -102 (trouble communicating)

 

Can't create session, error -1116 (can't access network volume)

 

7/27/2002 4:09:24 PM: Execution incomplete

 

Remaining: 10572 files, 4.2 GB

 

Completed: 70172 files, 9.4 GB, with 0% compression

 

Performance: 111.3 MB/minute

 

Duration: 01:30:04 (00:03:44 idle/loading/preparing)

 

 

 

TFile::SetPosFromEnd: SetFilePointer failed, \\Awpc15\e\Backups\AWPC8\Pics\XDrive_Pics_EDrive15b.rbf.rfc, winerr 6, error -1100

 

Quit at 7/27/2002 4:09 PM

 

 

 

+ Retrospect version 5.6.127

 

Launched at 7/27/2002 5:57 PM

 

+ Retrospect Driver Update, version 3.0.101

 

 

 

 

 

I ran more full Norton Disk Doctor and Norton Anti-Virus scans but turned up nothing. I'm at a loss as to what to try next, although I seem to be heading toward either a) a restore from a recent Retrospect backup of the "C" drive of the PC I'm having problems with (although Retrospect and its backups are suspect) or B) a full reformat and reinstall of the W2K OS and all programs including Retrospect. Before I go down that path, I'd like to hear something from Dantz tech support.

Link to comment
Share on other sites

Hi again!

 

 

 

I (almost) tried the same things as you, with the same results. I also experienced the first failure happening after about 7-8 GB and then concurrently afer about 1 or 2 more GB. I also have no clue where this comes form.

 

 

 

Hope we'll get an answer from Dantz Support soon...

 

 

 

DF

Link to comment
Share on other sites

It does seem to take many GB of backup before the timeout errors happen. I also have a sense that they're somewhat deterministic--that is, they happen in about the same place (i.e. on the same file) given the same set of files. But I don't think it's a problem with the files themselves (e.g. corrupted files) since I can open and use the files normally and they don't seem damaged at all. Also, adding or removing files causes the error to "shift" a bit (a few files earlier/later) which shouldn't happen if the problem was due to a particular file.

 

 

 

As an example, when I was backing up a directory as a single large directory, I had an error after:

 

Remaining: 16216 files, 5.5 GB (error at this point)

 

Completed: 64337 files, 8.1 GB, with 0% compression

 

 

 

for each of the several times I tried to run the backup (new backup set or as a Recycle).

 

 

 

When I divided the directory into two backups sets (each just under 7GB), one backup failed after backup up 5.9GB even though the previous run had been able to backup up 8.1GB before a failure occurred--so it's *not* just the size or number of files. I was then able to back up the other 760MB remaining in a single run. This was repeatable with the program failing at 5.9GB (although the amount of data in subsequent runs varied since I was adding and deleting files from the directories in the meantime).

 

 

 

For the other half of the split backup set (also about 7GB), the backup failed after 3.4GB (3.6GB remaining) each time I tried it. I was able to back up the remaining 3.6GB but not as a single run--runs would only go about 600MB-1.2GB before the same failure would happen again.

 

 

 

I don't know if this behavior strictly a matter of the amount of data or also a function of the number of files in the backup. Also note that the backup files do claim to be corrupted, with the "Bad backup set header found" so I don't know if I can reliably restore from the backups even though they claim that some data is backed up and the last backup runs without any errors.

 

 

 

Since the error seems to happen after the same amount of data is backed up, it doesn't seem as likely to be an asynchronous or external event (e.g. caused by another program)--if it were, we would expect the error to happen at different times and places during the backup rather than at the same place each time.

 

 

 

I have also tried to manually put my PC back to same state it was in over a month ago (e.g. disabling a few background programs, deinstalling a few others), etc. with no diff.

 

 

 

Hopefully we'll hear some comments & ideas from Dantz support.

Link to comment
Share on other sites

So I seem (two large recycles in a row... X) to be OK again, with Retrospect 5.6 RDU3.0 no longer reporting the "error -102 (trouble communicating)" problem and failure when I do a backup.

 

 

 

With nothing left to lose (i.e. starting to thing about OS reinstalls and reformats) I made the following changes:

 

 

 

1) I installed ServicePack3 (just released by MS) on this W2K (previously SP2) PC. Did this fix an actual bug that was impacting Retrospect (seems somewhat unlikely--Retro and SP2 had worked fine for months), repair/replace a file/DLL that had been installed by another program or change and was screwing up the OS or Retro?

 

 

 

2) I rearranged my harddrives (not trying to fix the Retro problem, just something I was doing at the same time). I had been meaning to replace a smaller backup drive with a new one (120GB) and when I did so I swapped the old "backup" drive with my smaller "data" drive and moved the later drive to another system. I then did an Explorer copy (drag) to move my data to the new data drive, so the amount of data (volume and # of files) is the same. My boot drive (W2K SP3) remained unchanged, and all drives are NTFS. The only thing that jumps out at me is that this would have had the effect of defragging my data and backup drives (since all the files were freshly copied from the old data drive to the new)--so defrag and a clean directory. Would fragmentation have caused Retrospect or the OS some problems?

 

 

 

So, I seem to be OK for now, but I'll keep an eye on things and report back. I would be interested to hear if just doing an SP3 update fixes this issue for Doktor_Faustus or others.

Link to comment
Share on other sites

It's certainly possible that bad fragmentation could have caused Retrospect to report the error -102; it does put both drives through some pretty hard use during the backup.

 

 

 

One thing I can't help but notice is the build of Retrospect 5.6 you're using-- .127. I've seen the .127 build put some odd filesystem API-call entries into the log (though the backups have been successful in the examples I've encountered). I would certainly try going up to the .132 build, which was the last publicly available build of version 5.6, and see if the problems could be reproduced with a new set.

 

 

 

It's also possible that the installation of SP3 fixed something deep in the OS that Retrospect was stumbling on, so that's another possibility, as you mention.

 

 

 

I, too, am interested to know if SP3 fixes this for Faustus.

Link to comment
Share on other sites

Thanks for the info. I didn't even know there was a newer build of Retrospect (than .127)--I've just been using the one I downloaded when I bought the program. I had been applying the RDU updates and that the RDUs effectively updated Retro (I hadn't paid attention to the .NNN version in the logs).. Dantz doesn't make it easy to see updates (e.g. download latest version, download update, etc.).

 

 

 

I couldn't find a place to download an update or patch, so I thought I'd just download a new "Trial" version (assuming it's the latest) and see if it would accept my license code. But I try to do so I get:

 

 

 

"I was unable to retrieve a license code for this sku. Perhaps we ran out of license codes, or perhaps we do not permit this item to be downloaded for free."

 

 

 

Maybe this has something to do with the attempted update/conversion to 6.0??

 

 

 

Hey Dantz Support--would you please tell me where I can download the more recent (last) build of Retro Desktop 5.6 (.132 if ChuckS is correct). I haven't decided about 6.0 and don't plan to be one of the first customers to try it...

 

 

 

Thanks,

 

GoAWest

Link to comment
Share on other sites

Just for grins I went to the Dantz.com "Upgrade" area and download the latest upgrade from 5.5 to 5.6. I assumed that this would be the latest version (.132 instead of .127). But after going thru the trouble up installing it ("update existing" option), rebooting, restoring config files, RDU and service logins, Retro *stills* shows as version .127 (splash screen and log file). So wherever this .132 is, Dantz is doing a good job of hiding it...

Link to comment
Share on other sites

But all I want is the final build/verson (? .132) of 5.6. I'm already running build .127. . I may upgrade to 6.0 but don't want to do it immediately.

 

 

 

As a registered & paid user of 5.6, I'd appreciate a way to download the final build.

 

 

 

BTW, I also noticed in the "updates" section that RDU 2.8 is the latest version avaiable for 5.6--but 3.0 and 3.1 also came out after 2.8 and they're not posted.

 

 

 

It seems like Dantz is not only saying "no more support for 5.6--buy 6.0" but "buy 6.0 or else!" by removing *existing* updates (.132 build of 5.6, RDUs 3.0 and 3.1). This doesn't seem very fair or reasonable--making these final updates doesn't require *more* work, just a little website effort to make the *existing* downloads available.

Link to comment
Share on other sites

  • 4 months later...

I was having the same problem on our server and tracked it down to a lack of available physical memory, which resides is real, no paged memory. This is shared between the file cache, the OS kernal, which NT has a limit of 196 MB and Win 2000 of 340MB. I had our servers configured as "File Servers", which enables a large file cache (HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache=1. Using the MSD Memory tab or Task Manager Performance Tab, which shows the memory, I noticed when Retrospect Server got the error the available Physical Memory was almost 0 (5K or so) and my File Cache was about 3/4 of my Physical Memory. This mainly occurred when backing up large client systems (14 GB or more). Changing this registry entry to =0 to use regular file cache settings (or setting your Server optimization for balanced or minimize memory), this seems to limit the file cache to 1/4 Physical memory and leaves over 1/2 free whenever Retrospect is running, which eliminated this error!

Link to comment
Share on other sites

Guest psykoyiko

rmontrose may be on to something. If you investigate the windows error codes from your logs, you'll see that they pertain to lack of available system resources. SP3 may have fiddled with the registry to change some memory settings, and therefore solved your problem.

 

 

 

1450 0x05AA Insufficient system resources exist to complete the requested service.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...