Problems with BSM SQL 3 ,3.0.1 and 3.1(build 43)

[ulsj]

Hi!

I cought this in a different forum

From: Dan Reger [mailto:dreger@LEGATO.COM]
Sent: mardi 27 août 2002 21:58
To: NETWORKER@LISTMAIL.TEMPLE.EDU
Subject: [Networker] Problem Announcement for NetWorker SQL Module


Hi,

I am the product manager for the NetWorker Module for Microsoft SQL Server.
I wanted to inform you that we have discovered a problem with the module
which may affect you.

This issue could result in a situation where data is in fact NOT backed up,
despite a successful completion report. Therefore, if the original data
were lost, an attempted recovery of that failed backup would fail. This
could lead to a potential data loss situation.

Versions 3.0, 3.0.1 and 3.1 (build 43) of the NetWorker Module for Microsoft
SQL Server fail to report legitimate Microsoft SQL Server errors in the
NetWorker server savegroup completion report - instead reporting a
successful backup of a SQL 2000 or SQL 7 Server when the backup, in fact,
failed due to the SQL error.

This occurs during a scheduled backup, via a command line save from the
client, and via an ad hoc save using the NetWorker Module for MS-SQL Server
GUI. This issue ONLY occurs during a single stripe backup - multiple stripe
backups are not affected.

This defect has been identified as LGTpa42569 and the hot fix can be
downloaded from Legato's ftp site:
ftp://ftp.legato.com/pub/NetWorker/SQL/3.1/3.1.0_LGTpa42569

The full announcement can be found at the link below. Please consult it for
complete details:

http://www.legato.com/products/networker/modules/announcement.cfm

Similar Information is also available in Tech Bulletin 379:

http://www.legato.com/resources/bulletins/379.html

Thank you,
Dan Reger


Hopping no one is having this problem