venom_zx Posted January 12, 2011 Report Share Posted January 12, 2011 (edited) the verification script i run contains this (error?) "1 files were not verified" in the user manual it says that verification errors will result in the original file being copied again during the next backup. i've tried running another backup but i still receive the same message when i run the verification. i'm assuming that the file no longer exists. - how do i resolve this? - do i have to create a new backup-set and start from scratch? i'm using retrospect 7.5 Edited January 12, 2011 by Guest Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted January 13, 2011 Report Share Posted January 13, 2011 Start by posting the part of the log file where it says WHY the file wasn't verified. Most likely, you don't have to do anything. Quote Link to comment Share on other sites More sharing options...
venom_zx Posted January 13, 2011 Author Report Share Posted January 13, 2011 (edited) i never used to get this message. this is the Operations log: ================================= + Executing Verify at 10-1-2011 22:34 (Execution unit 1) To Backup Set user0 disk C,D,X... 1 files were not verified 11-1-2011 01:33:12: 1 execution errors Remaining: 16161 files, zero KB Completed: 88342 files, 55.4 GB Performance: 561.6 MB/minute Duration: 02:58:41 (01:17:50 idle/loading/preparing) ================================= Ctrl+L gave me a different operations log i didn't see before: ================================= Trouble reading: "1-user0 disk C,D,X" (237707118), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017491.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237707119), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", ... (it goes on like this for a while) Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017491.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711946), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017521.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711947), error -102 (trouble communicating) Additional error information for Disk Backup Set member "1-user0 disk C,D,X", Can't read to file C:\Machines\user0w\Retrospect\user0 disk C,D,X\1-user0 disk C,D,X\AA017521.rdb, error -1101 (file/directory not found) Trouble reading: "1-user0 disk C,D,X" (237711948), error -102 (trouble communicating) 16-4-2010 22:56:26: Remaining: 12575 files, zero KB Completed: 98719 files, 181.1 GB Performance: 24.1 MB/minute Duration: 5 09:47:55 (02:05:55 idle/loading/preparing) 2,131 files were not verified 16-4-2010 22:56:27: 4,810,542 execution errors Total duration: 5 10:56:01 (02:39:24 idle/loading/preparing) ================================= could the the storage drive be corrupt? Edited January 13, 2011 by Guest Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted January 14, 2011 Report Share Posted January 14, 2011 could the the storage drive be corrupt? Yes, but it could be other things, too. The log says the Retrospect server says there is communications problems with the backup set's media. That can be a hardware problem or a software problem: Bad/old hardware drivers. How is the drive connected? SCSI? Bad SCSI termination? Old firmware on the SCSI card? How is the drive connected? iSCSI? Bad network? Try these devices outside Retrospect. You get the idea, perhaps? Quote Link to comment Share on other sites More sharing options...
venom_zx Posted January 15, 2011 Author Report Share Posted January 15, 2011 (edited) i'ts simply a SATA drive that is on the same system as retrospect (yeah i know i have to rearrange this soon). strangely other backup-sets on the same drive don't have this issue. when i posted the second log... i did not realize that it was such an old one. i've had to re-catalog this backup-set once because the catalog became corrupt after a power failure in the building. so the errors may be related to that. - could the "1 files were not verified" message also be related to having repaired the catalog? Edited January 15, 2011 by Guest Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.