cancel
Showing results for 
Search instead for 
Did you mean: 

Extremely Slow Verify

John_Koval
Level 2
New installation of BE 10 on Windows 2000 Server with Travan 40 drive. First daily backup worked OK. Backup C: 40 minutes for 3.2 GB, D: 2:29 for 11.8 GB. Verify was 41 minutes for C: drive and 4:38 for D: drive. On the second try, backup and verify times for C: drive were still around 40 minutes. D: backed up in 2:23, but then we found the verify still running after 8-1/2 hours. The progress indicator showed 57%, and the job appeared to be progressing, but VERY slowly. Any idea why the verify would be so slow and what I could do to resolve this issue?
4 REPLIES 4

ashwin_pawar
Level 6
verification process entirely depends upon hardware configuration and speed to read/write data on to the media.

When checking the box 'Verify After Backup', Backup Exec will run an operation against the tape, to read the data that has been written. This does not ensure the integrity of the files; it only ensures that the tape can be read.


Suggestion:
1) Make sure drives firmaware is updated.
2) Make sure VERTIAS drivers have been installed.
3) Also check the SCSI controller performance.



SCSI ID recommendations:
SCSI ID 0,1 and 6 should not be used as these are reserved ID's.make use of ID from 2-5. If its a robotic library then Make the changer arm Tar-ID-1, Tape0-1 and tape1-2 etc.

John_Koval
Level 2
This answer doesn't address the inconsistency. Why would the verify run fine one day and then take two or three times as long the next day??

Vidyaj__Patneka
Level 6
Hi,

Inconsistency may be due to the Tape drive.The verify speed eventually depends on the Tape drive and the Tape media being read.

We suggest you to clean the Tape drive regularly and check the results.

Also try using a new Tape media.

Hope this helps.

Abhinav_Bindroo
Level 6
There is no response from the customer for 2 days now