Problems with Devices with Backup Exec 10.0

[Vidar_HAnsen]

We have a Backup Exec-installation where we experience strange problems with device access.

The installation consists of 3 Backup Exec servers - NOSKKDF1 that is running Windows Server 2003, NOSKKMX1 and NOSKKDB1 that is running Windows 2000. All servers are connected to a SAN and are using the SSO Option. The server NOSKKDF1 is running as ADAMM-server.

The tape-device that is used is the following SAN-connected device:

Quantum Model TR-S23XA-FF A05, SDLTi Series

R1-80014-01 / RBE08Y1488 / RevA06

Overland SCSI LVD Loader/Library



Problem description:

When the ADAMM-server NOSKKDF1 is newly started every operation seems to be functioning OK. After a normal backup run during the night strange things happen. For instance - if You then try to run a Long Erase from NOSKKDF1 the server just hangs and have to be rebooted. The same operation on NOSKKMX1 runs OK.

We also have problems with running a restore operation - the job is just queued and it seems to stay queued because the device is not released or ready. This happens regardless of which server the restore operations is started on. After a restart of all Backup Exec services on the ADAMM server (NOSKKDF1) the restore runs just fine from both servers.

It seems that everythings works fine as long as the NOSKKDF services are newly started and operations are run from NOSKKDF1 (ADAMM-server). When one of the other servers have accessed the device through a backup run the NOSKKDF1 server are experiencing problems with device-operations until the BE-services on that server are restarted.

If BE Diag files are need i have them to.

[priya_khire]

Hello,

It seems that be it the Long erase job or restore job, you need to restart the services on the ADAMM - server 'NOSKKDF1' so that the jobs run well. Ensure that you are refreshing the changes made on one client after every operation. Refer to the limitations of SSO option for the same:

Title: Known limitations of the Shared Storage Option (SSO)
http://support.veritas.com/docs/197903

Since when does the problems occur? You can alternatively create a backup -to- disk folder and verify if the jobs directed to back to disk succeed. Also try powercycling the entire SAN and test the results.

Hope this helps. If the issue persists, do write back to the forum.

However 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.

Regards.