ADSM-L

Re: TDP for SQL exclude not working

2005-11-11 11:46:17
Subject: Re: TDP for SQL exclude not working
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 11 Nov 2005 11:44:20 -0500
Steve,

Can you be more specific on what you mean?
Something like:
   EXCLUDE "\...\db1\...\*"
Should exclude the "db1" database for whatever instance you are backing
up.
If you want to specify a certain instance in an exclude statement,
you can do that too. I will refer you to the DP/SQL User's Guide:
     "Appendix C. Advanced procedures"
         - Sample include/exclude statements
It discusses this and gives very specific details and examples.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/11/2005
08:51:17 AM:

> Thanks, Del.
> Does this also explain why I am having trouble excluding non-default
> instance databases, or do I need to add something to my exclude
> statement for those?
> -steve
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Del Hoobler
> Sent: Thursday, November 10, 2005 10:23 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TDP for SQL exclude not working
>
> Steve,
>
> You are excluding this correctly. The problem is that even though you
> have "excluded" it from TSM API backups, the Data Protection for SQL
> code still gets the database attributes. (This access happens prior to
> sending it to the TSM API, where the EXCLUDE statement takes effect.)
> That's what causes the error. This is a known issue.
> This has been reported as a requirement and we are addressing it.
> Look for a future release to have an option to be able to completely
> exclude databases.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/10/2005
> 01:05:31 PM:
>
> > TSM Server 5.2.2.0
> > TSM Client 5.3.0.5
> > TDP Client 5.2.1.0
> >
> > All,
> >
> > I've been trying to clean up some bogus failures in our TDp
> > environment by excluding databases that are offline or have known
> problems.
> > below I've pasted part of the log and the dsm.opt showing that
> > although I'm excluding a db (MSP), it still shows a failure trying to
> back it up.
> > I've also had problems excluding databases in SQL instances other than
>
> > the default (most of our SQL boxes have multiple instances, we script
> > the backups using the /sqlserver= parm).
> >
> > am I missing something in the exclude spec?
> > Steve Schaub
> > Systems Engineer, WNI
> > BlueCross BlueShield of Tennessee
> > 423-752-6574 (desk)
> > 423-785-7347 (cell)
> >
> >
> > ======================================================================
> > ==
> > =
> > 11/09/2005 21:00:44 Request                       : FULL BACKUP
> > 11/09/2005 21:00:44 Database Input List           : *
> > 11/09/2005 21:00:44 Group Input List              : -
> > 11/09/2005 21:00:44 File Input List               : -
> > 11/09/2005 21:00:44 Number of Buffers             : 4
> > 11/09/2005 21:00:44 Buffer Size                   : 8192
> > 11/09/2005 21:00:44 Number of SQL Buffers         : 0
> > 11/09/2005 21:00:44 SQL Buffer Size               : 1024
> > 11/09/2005 21:00:44 Number of Stripes specified   : 4
> > 11/09/2005 21:00:44 Estimate                      : -
> > 11/09/2005 21:00:44 Truncate Log?                 : -
> > 11/09/2005 21:00:44 Wait for Tape Mounts?         : Yes
> > 11/09/2005 21:00:44 TSM Options File              : C:\Program
> > Files\Tivoli\TSM\TDPSql\dsm.opt
> > 11/09/2005 21:00:44 TSM Nodename Override         : -
> > 11/09/2005 21:00:44 Sqlserver                     : CROAKER
> > 11/09/2005 21:00:44
> > 11/09/2005 21:00:49 Backup of SQL Database MSP will not be attempted.
> > 11/09/2005 21:00:49 SQL Database Status: Suspect
> > 11/09/2005 21:00:49 ACO5422E Received the following from the MS SQL
> > server:
> > 11/09/2005 21:00:49 [Microsoft][ODBC SQL Server Driver][SQL
> > Server]Database 'MSP' cannot be opened due to inaccessible files or
> > insufficient memory or disk space.  See the SQL Server errorlog for
> > details. Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x800403b1)
> > 11/09/2005 21:12:28 Total SQL backups selected:               29
> > 11/09/2005 21:12:28 Total SQL backups attempted:              28
> > 11/09/2005 21:12:28 Total SQL backups completed:              28
> > 11/09/2005 21:12:28 Total SQL backups excluded:               0
> > 11/09/2005 21:12:28 Total SQL backups inactivated:            0
> > 11/09/2005 21:12:28 Throughput rate:
> 13,144.47
> > Kb/Sec
> > 11/09/2005 21:12:28 Total bytes transferred:
> > 9,363,460,544
> > 11/09/2005 21:12:28 Elapsed processing time:                  695.65
> > Secs
> >
> > *=====================================================================
> > =*
> > * Include/Exclude Section (excludes normally refer to offline
> > databases)
> *====================================================================
> > INCLUDE                * WINSQL3
> > EXCLUDE                "\...\MSP\...\*"
> > * EXCLUDE                "\...\database-to-be-excluded\...\*"
> >
> > Steve Schaub
> > Systems Engineer, WNI
> > BlueCross BlueShield of Tennessee
> > 423-752-6574 (desk)
> > 423-785-7347 (cell)
> >
> > Please see the following link for the BlueCross BlueShield of
> > Tennessee
> E-mail
> > disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
> Please see the following link for the BlueCross BlueShield of Tennessee
E-mail
> disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

<Prev in Thread] Current Thread [Next in Thread>