Can't restore from backup after applying w2k3 sp1

[davsjo]

After installing Windows server 2003 service pack 1 the tape device driver from Veritas (for a Sony SDX-400C) was replaced with a driver from Microsoft. Now when I try to read from or write to any of the tapes I get the error 0x452 - When accessing a new tape of a multivolume partition, the current block size is incorrect or 0xa00084ca - The data being read from the media is inconsistent if I enable read SCSI pass-through mode. Erasing the tapes makes it possible to do new backups (that also can be read), but I need to restore data from one of the backups made prior to the sp1 installation. The device driver from Veritas (an old driver from 2003 included in the tape device driver package from Veritas BackupExecTapeDeviceDriverInstall_273853.exe) does not work after installing windows server 2003 service pack 1. I have tried to do a roll-back of sp1, but after that I get a "blue screen" whenever I access the tape device (page fault in the tape device driver).

[Joshua_Small]

You could try running tapeinst.exe (from the veritas program files directory) and ordering it to re-install the Veritas driver for the tape drive.

[davsjo]

I have no problem installing the tape device driver from Veritas, but it doesn't work with sp1 installed (I get a yellow ! and "device could not start" or something like that in the device manager).

[Chaitanya_Khurj]

Hello,

Please check if you have event IDs 5,7, 9, 11 or 15 in the System Logs.

If so refer to the following technote.

How to troubleshoot issues with a Robotic Library or Tape Drive in Backup Exec 9.x and 10.0

http://support.veritas.com/docs/255501

NOTE : If we do not receive your reply within two business days, this post would be marked '‘assumed answered’' and would be moved to '‘answered questions'’ pool.

[davsjo]

I do not have any of those events in the system logs, besides wouldn't those problems make me unable to use the tape device at all? The tape device works with the OEM driver, only it can't read any of the tapes that was written with the driver from Veritas. It seems that the drivers have different opinions about what block size was used when making the backups (error 0x452). The device driver from Veritas cannot be installed now that I have applied w2k3 sp1 (Windows cannot initialize the device driver for this hardware Code 37).

[Renuka_-]

Hello,
There is a problem in the device configuration, please try to disable, delete and power cycle the device and the media server.
Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[davsjo]

Tomorrow I will try uninstalling the device driver, shut down the server, remove the tape drive, starting the server without the tape drive, shut down the server again and plug in the tape drive again and see if that helps. As the device works with the OEM device driver I don't think that will help much though. I suspect it is simply the (very old) device driver from Veritas that is not compatible with w2k3 sp1 and I would very much want to know if that is the case or not.

[Sharvari_Deshmu]

Hello,

In addition to the steps please check the following:

I
please check whether the device is "tested" by backup Exec with the help of the list below:

If yes then please install latest veritas drivers.

Backup Exec 10.0 for Windows Servers robotic library Hardware Compatibility List (HCL)
http://support.veritas.com/docs/274348

Backup Exec 10.0 for Windows Servers Standalone Drives Hardware Compatibility List (HCL)
http://support.veritas.com/docs/274347

Latest veritas drivers:

Document ID: 273887
VERITAS Backup Exec (tm) 10.0 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only)

http://support.veritas.com/docs/273887

If the device is not tested in the hardware compatibility list then please install the latest OEM drivers.


II We would like to know whether you are using IBM server?

Also update us whether after deleting and recreating the device the problem persists.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.


Thanks,

[davsjo]

I. It is in the list, but can I install the drivers for BE10.0 even though I am using BE9.1?
II. Yes it is an IBM server.

[Sharvari_Deshmu]

Hello,

We apologize for the previous reply.

With the version 9.1 you cannot use 10.0 drivers hence please check in the compatibility list of 9.1.

please check whether the device is "tested" in the list below, if yes then please install latest veritas drivers from the link below:
http://support.veritas.com/docs/271383

VERITAS Backup Exec (tm) 9.1 - Device Driver Installer (20050115) - Includes Tape Driver Release (20041231) and Robotic Library Release (45) (Intel Only) http://seer.support.veritas.com/docs/273853.htm
HCL for stand alone devices:
http://seer.support.veritas.com/docs/273852.htm

If not tested then please install latest manufacturers and then verify the result.

Also you have mentioned that you are using IBM server and Win 2003 and that you get a Blue screen please see the technote below:
http://support.veritas.com/docs/261728
please note that the hotfix19 metioned in the technote is included with SP2
SP2 link:
http://support.veritas.com/docs/275247


Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.


Thanks,null

[davsjo]

The blue screen problem is only when I roll back the w2k3 sp1 installation (I guess the fix is included in sp1).

Still I would like to know if there is a compatiblity issue with the device driver from Veritas for Sony AIT tape drives and w2k3 sp1. It really seems there is, as I could use the Device driver from Veritas before I applied w2k3 sp1, and now I can't. If that is so you need to inform people about it and also the driver needs to be fixed.

[davsjo]

I am not sure what fixed the problem, but this is what I did:

1. I uninstalled the device driver package from Veritas
2. uninstalled the tape device driver
3. rolled back (uninstalled) w2k3 sp1
4. applied the fix from Microsoft (Microsoft Q article # 838894)
5. I did a repair of the BE9.1 installation (I had to do this to get the device driver package to install)
6. changed the registry value as described in the technote (http://support.veritas.com/docs/261728)
7. installed the device driver package from Veritas

Now the device driver from Veritas for the sony ait tape drive works again, and I can restore from my old backups.

I would advice people who are using the Sony ait device driver from Veritas to think twice before applying the w2k3 sp1. Also if you suddenly get the error message "0x452 - When accessing a new tape of a multivolume partition, the current block size is incorrect." on all your tapes when doing read or write operations, check if the device driver from Veritas has been replaced by the device driver from Microsoft. Tapes erased using the device driver from Veritas cannot be "understood" by the OEM or the Microsoft device drivers.

[Sharvari_Deshmu]

Hello,

Thanks for the update this thread will be archived.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.


Thanks,

[Josh_Church]

We had the same problem and found that the Microsoft drivers for our tape drive had been installed over the Veritas drivers. When we installed a Veritas driver pack dated 01/2005, the problem was solved.