The capitalization of "SQL Server" would imply Microsoft SQL Server,
which in turn implies Windows OS?

I do wonder, as Microsoft continues to tighten up access control, and
adds "features" to its file system semantics, that at some point the TSM
client may "lock" a file by requesting some form of exclusive read
access.

I remember at least a few times where the client has been broken by
service packs or hot fixes. I'm fighting with the unresolved IC56269
right at the moment. This doesn't feel like a Tivoli created problem, so
it must be the OS that is changing.

Throw in odd felsites things like DiskXtender, Polyserve, etc, and who
knows what the client can or cannot expect to get a file handle on.

[RC] 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Tuesday, June 17, 2008 8:13 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Can TSM locks file during backup ?

On Jun 17, 2008, at 10:13 AM, David Rigaudiere wrote:

> Hi *SMers,
> I have a DBA clustomer who claims that dsmc locked files during 
> incremental backup, lock which prevent SQL Server to restart the 
> database en setting status to 'Suspect'.
>
> Is TSM can locks file during full incremental backups ?
> I never seen this before with "classic" backups.

David -

I concur - I've never seen the TSM client lock files for backup, nor
seen any documentation suggesting that it does.

I perceive that the DBA made the claim without providing you with any
evidence.  Have them provide you with evidence from any tool they used
to detect such a condition.  More to the point, the SQL Server error log
should have detailed info on why it flagged the database as Suspect -
which can have many causes.

The larger issue is why TSM physical backup should apparently be running
at the same time as the SQL Server.  That would constitute a "fuzzy
backup", which would probably not result in a consistent, usable object
if restored.  Generally speaking, to use physical (i.e., TSM B/A client)
backup tools on a database, the database server needs to be down.  If
striving to keep SQL Server up during backups, the TDP would be the way
to go.

    Richard Sims


DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.