I have recently installed the 6.1.4 networker client and the MS SQL
networker businessuite agent 2.0.1 patch3 on a W2K server running MS-SQL
6.5 SP5a. Most of the databases are getting backed up without any
problems, but there is one database that complains about the transaction
log maintenance. I wonder why this error/message occurs, and what can be
done to fix it? As far as I can see the database has 500MB of log space
allocated, but 0MB is available on the log device. I have tried truncating
the logs manually, but the log space doesn't get freed up anyway. The
backup is running at the incr level. Clues anyone? Log below (from savegrp
-v):


* sasql31.i.customer.se:MSSQL: nsrsqlsv: DUMP database SONNY TO
pipe='\\.\pipe\sql\bsmsql452411' WITH stats
* sasql31.i.customer.se:MSSQL: nsrsqlsv: MS SQL Server v6.50 reports 10
percent dumped
[snip]
* sasql31.i.customer.se:MSSQL: nsrsqlsv: MS SQL Server v6.50 reports 90
percent dumped
* sasql31.i.customer.se:MSSQL: nsrsqlsv: MS SQL Server v6.50 reports
100 percent dumped
* sasql31.i.customer.se:MSSQL: nsrsqlsv: Did NOT truncate the
transaction log for SONNY because -lxlog is allowed.


I guess Legato doesn't support this either?

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=