12/24Gb DAT

[Robert Bokros]

I use the same 5 tapes per week,one each day.
One stops working so I guess it has expired as it is 4 year old. I buy a new pack of 5 tapes, DDS3 12Gb/24Gb and cannot get them to work, Veritas just aborts the backup, and puts the job on hold,but I can label the new tapes OK.
The original tapes, 4 left,still work OK.
Any suggestions please?

[Devender Khatana]

Which OS & Veritas version you are running on ? As you told you are be able to label media but can not write to it. How did you verify and labeled it ? Does old media also was DDS3 only? Because it may be a compatibility issue of DDS3 media with your drive.

Regards,
Devender

[Dorothee Singer]

i would also suppose that there is a compability problem with your tape drive.
perhaps you can try to write on the new tapes with tar - if this also does not work, you know that your drive can not manage those tapes.

yours,
doro

[Robert Bokros]

Using W2K and Veritas Backup Exec 8.6 Server.
I renamed the tape 'Wednesday' to ensure I could write to it.
Two of the old tapes stopped working which is why I bought new. I have ran the cleaner 5 times to see if this helps but does not.
Is there a command in DOS to test the tape drive?
Maybe I just get a new tape drive?

[Mobeen_1]

Robert,
Can you please provide us with the following information -
1. Tape Drive you are using ?
2. What is the tape media you are using?

regards
Mobeen

[Robert Bokros]

Hello

I am using a 12/24Gg HP DAT C1537A SCSI Sequencial Device.

The tapes are TDK DDS-3 4mm Data 12/24Gb.

Rob

[Devender Khatana]

Robert,

I don't think there is some dos command in w2k to test this out, But you can surely use inbuilt backup utility of w2K. The path is

Programs->Accessories->System Tools->backup

I do't think this will help much but you will surely be able to come a conclusion that your drive is faulty.

HTH,
Devender

[Terry Auspitz · Accepted solution]

Within Veritas, if you check the job history are there any error messages?

[Robert Bokros]

I have looked at the veritas job logs and it says failed and the event log and there is no messages.

[Terry Auspitz]

Within Backup Exec, on the activity monitor tab, right click on a failed job (preferably the first one) and click properties. Click the job log tab, then scroll through the log to look for any errors.

Errors will usually, but not always, be indicated with "^ ^ ^ ^" markers under the error... the line or lines above that are the error.

If the job aborted, a reason will often be listed here as well.

If you could paste the job log or at least the error lines in here it would be tremendously helpful. Feel free to ---- out any file or server names if you need to.

-Terry