Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

The request could not be performed because of an I/O device error. Backup Exec 8.6

Posted on 2004-04-29
3
55,431 Views
Last Modified: 2013-12-01
Hey guys, I'm stumped on this.  I've been doing backups now for several months, not changing anything about where and what the backup covers.  Everything has been working smoothly.  Until a week ago.  

Give you a bit of History, The person that was over the IT department where I work was demoted but was allowed to stay on as a Network Administrator.  About the same time this happened I started having problems with the backup.  Not saying this is the cause but it does throw up a red flag to me.  Below is a copy of the last backup I attempted and it shows that all was backed up but when it went to verify Mags4/backup failed... (Mags4/backup is the most important directory in our company)

The key here is that is a share that some how continues to get removed or loses its connection ..For people that have much greater knowledge than me about Veritas and backups please have a look to see if I have a problem.  I'm trying to narrow down what it could be.

Windows 2000 Server
Veritas 8.6


Thanks in advance

Kid



======================================================================
Job server: Server
Job name: NIGHTLY BACKUP
Job started: Tuesday, April 27, 2004 at 11:59:02 PM
Job type: Backup
Job Log: BEX42.txt
======================================================================

Drive and media information from media mount:
Robotic Library Name:
Drive Name: COMPAQ 1
Slot: 0
Media GUID: {ACC1C9CA-080F-4CE3-B0F8-A208A4E372D9}
Media Label: 4MM000023
Overwrite Protection Time Left: None
Append Time Left: Infinite
Targeted Media Set Name: Media Set 1

======================================================================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================
Performing Remote Agent backup

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "\\MAGS1\D$ "
Backup set #1 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 12:00:09 AM.
File "WC 04-01-04.doc" in use - Backed up.

Backup completed on 4/28/2004 at 12:53:51 AM.
Backed up 36082 files in 4969 directories.
1  file was in use
Processed 5,264,950,539 bytes in  53 minutes and  42 seconds.
Throughput rate: 93.5 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "\\MAGS2\E$ "
Backup set #2 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 12:54:04 AM.

Backup completed on 4/28/2004 at 1:05:23 AM.
Backed up 13923 files in 3396 directories.
Processed 1,033,586,657 bytes in  11 minutes and  19 seconds.
Throughput rate: 87.1 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "\\MAGS3\G$ "
Backup set #3 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 1:05:38 AM.

Backup completed on 4/28/2004 at 1:19:55 AM.
Backed up 23254 files in 1508 directories.
Processed 1,662,170,758 bytes in  14 minutes and  17 seconds.
Throughput rate: 111.0 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "\\mags4\apps$ "
Backup set #4 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 1:20:05 AM.

Backup completed on 4/28/2004 at 2:07:58 AM.
Backed up 80374 files in 217 directories.
Processed 3,700,937,504 bytes in  47 minutes and  53 seconds.
Throughput rate: 73.7 MB/min
----------------------------------------------------------------------
Performing Remote Agent backup

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "\\mags4\backup "
Backup set #5 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 2:08:07 AM.

Backup completed on 4/28/2004 at 4:50:37 AM.
Backed up 106 files in 1 directory.
Processed 21,612,854,426 bytes in  2 hours,  42 minutes, and  30 seconds.
Throughput rate: 126.8 MB/min
----------------------------------------------------------------------

Media Name: "Media created 4/27/2004 11:59:06 PM"
Backup of "C: "
Backup set #6 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 4/28/2004 at 4:50:40 AM.

Backup completed on 4/28/2004 at 5:14:00 AM.
Backed up 22631 files in 3019 directories.
Processed 1,557,370,050 bytes in  23 minutes and  20 seconds.
Throughput rate: 63.7 MB/min
----------------------------------------------------------------------

======================================================================
Job Operation - Verify
======================================================================

Verify of "\\MAGS1\D$ "
Backup set #1 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Verify started on 4/28/2004 at 5:15:12 AM.

Verify completed on 4/28/2004 at 5:53:16 AM.
Verified 36082 files in 4969 directories.
0 files were different.
Processed 5,264,950,539 bytes in  38 minutes and  4 seconds.
Throughput rate: 131.9 MB/min
----------------------------------------------------------------------

Verify of "\\MAGS2\E$ "
Backup set #2 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Verify started on 4/28/2004 at 5:53:16 AM.

Verify completed on 4/28/2004 at 5:59:59 AM.
Verified 13923 files in 3396 directories.
0 files were different.
Processed 1,033,586,657 bytes in  6 minutes and  43 seconds.
Throughput rate: 146.8 MB/min
----------------------------------------------------------------------

Verify of "\\MAGS3\G$ "
Backup set #3 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Verify started on 4/28/2004 at 5:59:59 AM.

Verify completed on 4/28/2004 at 6:10:20 AM.
Verified 23254 files in 1508 directories.
0 files were different.
Processed 1,662,170,758 bytes in  10 minutes and  21 seconds.
Throughput rate: 153.2 MB/min
----------------------------------------------------------------------

Verify of "\\mags4\apps$ "
Backup set #4 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Verify started on 4/28/2004 at 6:10:21 AM.

Verify completed on 4/28/2004 at 6:32:46 AM.
Verified 80374 files in 217 directories.
0 files were different.
Processed 3,700,937,504 bytes in  22 minutes and  25 seconds.
Throughput rate: 157.4 MB/min
----------------------------------------------------------------------

Verify of "\\mags4\backup "
Backup set #5 on storage media #1
Backup set description: "NIGHTLY BACKUP"
Verify started on 4/28/2004 at 6:32:46 AM.

Storage device "COMPAQ 1" reported an error on a request to read data from media.

Error reported:
The request could not be performed because of an I/O device error.

^ ^ ^ ^ ^



Verify completed on 4/28/2004 at 6:47:55 AM.
Verified 5 files in 1 directory.
0 files were different.
Processed 19,655,930 bytes in  15 minutes and  9 seconds.
Throughput rate:  1.2 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: Wednesday, April 28, 2004 at 6:48:01 AM
Job completion status: Failed
======================================================================
0
Comment
Question by:dglidewell
3 Comments
 
LVL 22

Accepted Solution

by:
dovidmichel earned 500 total points
ID: 10952195
The I/O device error is a very generic SCSI error and all is known from it is that there was some disruption in the communication between the OS and the device.

It could be controller, controller driver, cable, terminatore, the tape drive itself or a tape, in other words just about anything. Looking at the log it can be asked if in this case did the drive have a problem reading a tape and that caused the I/O error or did something else cause the I/O error and that resulted in the failure to read the tape. From this log it really is not possible to tell.

Check for an updated driver for the controller and the tape drive, that's a good place to start.
Next check for consisancy. Does it only happen with this tape? or only during verify? or only on full backup... look for any patern or to is if there is no pattern at all.

Check the Windows Event Viewer, the Compaq/HP Insight Manger, and Compaq Survey logs for those errors. They can be very helpful in tracking down these type of errors.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
Are you looking to recover an email message or a contact you just deleted mistakenly? Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question