Start a Conversation

Solved!

Go to Solution

2708

May 18th, 2022 03:00

DELL TL2000 DRIVE WARN OR CRIT TAPE ALERT

Hi, 

Since I update the version of veritas to a more recent one, the tape booth is continuously issuing messages of dive warn or crit tape alert and veritas marks the tapes as withdrawn.

Device      : <FLX15D48F@es.gestamp.com>

Attention : Drive Warn or Crit Tape Alert flag

 

            Event Code:                      0x84 - tape alert

            Element number:                  0x16, 22

            Drive number:                    0x01, 1

            Tape Alert Flag:                 0x04, 4

 

This message was generated automatically from

IBM      3573-TL        

 

can you help me??

 

Thank you

 

Moderator

 • 

8.5K Posts

May 20th, 2022 13:00

Thank you. 

 

The tape alerts you are seeing is somewhat common when doing a restore or reading the media, because if an error is caught during the initial backup you will see it displayed during the restore. The drive is healthy, although heavily used, it looks good. 

 

 

 

May 27th, 2022 04:00

Good afternoon

I took out all the tapes from the library and put only one and still gave me error. He continually asks me to clean the tape drive. That's with the tape to clean right? if not, will I have to replace it?

nventory Device 00057 -- The job failed with the following error: A backup storage read/write error occurred. If the storage is on tape, this error usually occurs because the tape drive's read/write heads are dirty. Clean the tape drive and try the job again. If the problem continues, try a different tape drive. You may need to check for cable, termination, or other hardware issues. If the storage is disk, check that the storage subsystem is working properly. Review the system logs or vendor-specific logs associated with the storage in order to determine the source of the problem. It is recommended that you refer to the vendor-specific documentation for troubleshooting recommendations. If the storage is in the cloud, check that there are no network connection problems. Run the CloudConnect optimizer to get a value for write connections that is appropriate for your environment, and use this value to run the failing backup job. Consult the specific documentation of the cloud provider in order to determine the source of the problem. If the problem continues, contact the cloud provider for further assistance

Thank you.

4 Operator

 • 

2.7K Posts

May 27th, 2022 08:00

Hello @sahernandez98,


Yes, you can try to use now a cleaning tape. But if the problem persist after that, you may need to replace it.


Regards.

No Events found!

Top