Hi Bo!
Check the tdpsql.log, the dsierror.log and the dsmerror.log. Maybe you will
find more usefull information there?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Bo Nielsen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 12:44
To: [EMAIL PROTECTED]
Subject: SQL backup failed.
Importance: High


Help.

I'm running a backup on a SQL server 7.0.
Sometime everything is OK, but mostly fail some
of the DB's with the follow errors from the SQL log:

BackupVirtualDeviceSet::Initialize: Open failure on backup device
'TDPSQL-sqladsm-2001021544-3180'. Operating system error -2147024891(error
not found).

>From the TSM log:

06/27/2001 02:15:52,Backed up - FMRK, type: DB, size: 231583513, actual
bytes: 0, secs: 0,00, Kb/Sec: 0,00, SQL server: FDB033, TSM server: dsm, SQL
status: DB-LIB message: Backup or restore operation terminating abnormally.
, TSM status: TSM operation cancelled.

The configuration is:

TSM server OS/390 version 4.1.30
SQL server 7.0 on NT 4 sp5
TDP SQL agent 1.1.2

Why is the scheduled event '  ' completed successfully,
when the backup is terminated for some DB's??????

Regards,
Bo Nielsen

FDB data                                    Phone: +45 4386 4671
Roskildevej 65                             Fax:     +45 4386 4990
DK-2620 Albertslund                    E-mail: [EMAIL PROTECTED]
Denmark


**********************************************************************
This e-mail and any attachment may contain confidential and privileged material 
intended for the addressee only. If you are not the addressee, you are notified that 
no part of the e-mail or any attachment may be disclosed, copied or distributed, and 
that any other action related to this e-mail or attachment is strictly prohibited, and 
may be unlawful. If you have received this e-mail by error, please notify the sender 
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart 
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for 
the incorrect or incomplete transmission of this e-mail or any attachments, nor 
responsible for any delay in receipt.
**********************************************************************

Reply via email to