I had that done at one time, and commented them out for all of our SQL
clients. Those excludes are already in the sample dsm.opt, so does that
mean that they are recommended excludes? If so, I need to go back and
un-comment them all.  :)  Pardon my ignorance on SQL, but why would you
exclude the logs for master and msdb. Does that affect the full backup?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: Friday, February 24, 2006 8:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] SQL Transaction log backup failures for msdb and
master

Chip,

How about just excluding those databases from log backups?
You do that by adding this to the DSM.OPT file for
Data Protection for SQL:

     EXCLUDE "\...\master\...\log*"
     EXCLUDE "\...\msdb\...\log*"

Thanks,

Del

----------------------------------------------------

Del Hoobler
Tivoli Storage Manager Development
IBM Corporation



"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/23/2006
07:23:24 PM:

> I'm getting the following on a particular client...
>
>
>
>
>
> 02/15/2006 15:00:07 Backup of msdb failed.
>
> 02/15/2006 15:00:07 ACO5422E Received the following from the MS SQL
> server:
>
> 02/15/2006 15:00:07 [Microsoft][ODBC SQL Server Driver][SQL Server]The
> statement BACKUP LOG is not allowed while the recovery model is
SIMPLE.
> Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
>
> 02/15/2006 15:00:07 [Microsoft][ODBC SQL Server Driver][SQL
> Server]BACKUP LOG is terminating abnormally. Microsoft SQL-DMO (ODBC
> SQLState: 42000) (HRESULT:0x80041070)
>
>
>
> 02/15/2006 15:00:04 Backup of master failed.
>
> 02/15/2006 15:00:04 ACO5422E Received the following from the MS SQL
> server:
>
> 02/15/2006 15:00:04 [Microsoft][ODBC SQL Server Driver][SQL
> Server]Cannot back up the log of the master database. Use BACKUP
> DATABASE instead.
>
> 02/15/2006 15:00:04 [Microsoft][ODBC SQL Server Driver][SQL
> Server]BACKUP LOG is terminating abnormally. Microsoft SQL-DMO (ODBC
> SQLState: 42000) (HRESULT:0x80041074)
>
>
>
> Should I change the db recovery mode in SQL Enterprise Mgr to full? I
am
> not a SQL admin by any stretch, but we finally have those skill sets
> in-house. They are asking to run transaction log backups bi-hourly or
> hourly on some clients. In this particular case, the above errors
occur.
>
>
>
>
> Thanks all!
>
>
>
> God bless you!!!
>
> Chip Bell
> Network Engineer I
> IBM Tivoli Certified Deployment Professional (ITSM 5.2)
> Baptist Health System
> Birmingham, AL
> Office (205) 715-5106
> Pager (205) 817-0357
> Home (256) 739-0947
>
>
>
>
>
>
> -----------------------------------------
> Confidentiality Notice:
> The information contained in this email message is privileged and
> confidential information and intended only for the use of the
> individual or entity named in the address. If you are not the
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this information is strictly
> prohibited. If you received this information in error, please
> notify the sender and delete this information from your computer
> and retain no copies of any of this information.
>