Could you please check the script, customer is using for creating backup and the device files associated with it.
There is possibility that script is issueing a command on a device file which is not supported on that.
For Example:
Using a script to write to the tape device is producing the following message in syslog.log:
vmunix SCSI TAPE: dev=0xcd032040 I/O error during close
The tape and tape drive are both OK.
the script is issuing the mt(1) command
against a no-rewind device file which produced the IO error.
The mt command works best when used with the Berkeley style device file. This is explained in the man page:
WARNINGS: Only raw, no-rewind Berkeley-type devices should be specified. This type of device will not reposition the tape upon close. An example of such a device is /dev/rmt/0mnb. Please refer to mt(7) for more details.
When the /dev/rmt/0mnb device is used, the problem went away.
Time has a wonderful way of weeding out the trivial