ADSM-L

Re: [ADSM-L] Problem with Open File Support

2009-02-19 03:19:00
Subject: Re: [ADSM-L] Problem with Open File Support
From: Yudi Darmadi <yudi AT NIAGAPRIMA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 19 Feb 2009 15:14:06 +0700
OS : Windows Server 2003 SP2.
The TSM CLient version is 5.4.0.2



Best Regards,


Yudi Darmadi
PT Niagaprima Paramitra
Jl. KH Ahmad Dahlan No.25  Kebayoran Baru, Jakarta Selatan 12130
Phone: 021-72799949; Fax: 021-72799950; Mobile: 081905530830
http://www.niagaprima.com

----- Original Message -----
From: "Clark, Robert A" <Robert.Clark AT PROVIDENCE DOT ORG>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Saturday, February 14, 2009 3:07 AM
Subject: Re: [ADSM-L] Problem with Open File Support


What is the OS and SP level? What is the client version?

[RC]

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Yudi Darmadi
Sent: Friday, February 13, 2009 6:19 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Problem with Open File Support

Dear all,

I have a two question here, and i need your advice:

1>. On one client, I didn't use the Open File support, so the backup
schedule failed (some files couldn't back up), but if I use the open
file support, the machine stop responding during backup proccess. Is the
problem on the TSM or in the Windows' Volume Shadow Copy Service? (As
far as i know, TSM Open file support uses this windows service).

2>. I have a TSM Server and also TSM client on 1 machine. I set a
2>scheduled
backup. But it seems the backup stopped, and if i see in the task
manager, there's no "dsmc" proccess, and in the TSM, the server's
session was "idle".

Here's the dsmsched.log:
02/13/2009 11:00:03 Schedule Name:         DAILY_1111
02/13/2009 11:00:03 Action:                Incremental
02/13/2009 11:00:03 Objects:
02/13/2009 11:00:03 Options:               -su=yes -domain='all-local
-d:'
02/13/2009 11:00:03 Server Window Start:   11:00:00 on 02/13/2009
02/13/2009
11:00:03 ------------------------------------------------------------
02/13/2009 11:00:03 Command will be executed in 2 minutes.
02/13/2009 11:02:03
Executing scheduled command now.
02/13/2009 11:02:03 Node Name: DAILY_1111
02/13/2009 11:02:03 Session established with server DAILY_1111: Windows
02/13/2009 11:02:03   Server Version 5, Release 4, Level 3.0
02/13/2009 11:02:03   Server date/time: 02/13/2009 11:02:03  Last
access:
02/13/2009 11:00:03

02/13/2009 11:02:03 --- SCHEDULEREC OBJECT BEGIN DAILY_1111 02/13/2009
11:00:00
02/13/2009 11:02:03 Incremental backup of volume '\\server1111\c$'
02/13/2009 11:02:03 Incremental backup of volume '\\server1111\f$'
02/13/2009 11:02:03 Incremental backup of volume 'SYSTEMSERVICES'
02/13/2009 11:02:03 Backup System Services using shadow copy...
02/13/2009 11:02:04 Backup System Service: 'Terminal Server Licensing'.

02/13/2009 11:02:04 ANS1959W Removing previous incomplete group '\TLS'
Id:0-232267947
02/13/2009 11:02:05 Backup System Service: 'Event Log'.

02/13/2009 11:02:05 ANS1959W Removing previous incomplete group
'\EVENTLOG'
Id:0-232267949
02/13/2009 11:02:05 Backup System Service: 'WMI Database'.

02/13/2009 11:02:05 ANS1959W Removing previous incomplete group '\WMI'
Id:0-232267948
02/13/2009 11:02:05 Incremental backup of volume 'SYSTEMSTATE'
02/13/2009 11:02:05 Backup System State using shadow copy...
02/13/2009 11:02:05 Backup System State: 'System Files'.

02/13/2009 11:02:05 Backup System State: 'COM+ Database'.

02/13/2009 11:02:05 Backup System State: 'Registry'.

02/13/2009 11:02:05 ANS1959W Removing previous incomplete group
'\SYSSTATE'
Id:0-232267950


And the dsmerror.log :
02/13/2009 11:12:39 ANS1959W Removing previous incomplete group '\TLS'
Id:0-232267951
02/13/2009 11:12:39 ANS1959W Removing previous incomplete group
'\EVENTLOG'
Id:0-232267952
02/13/2009 11:12:39 ANS1959W Removing previous incomplete group '\WMI'
Id:0-232267953
02/13/2009 11:12:40 ANS1959W Removing previous incomplete group
'\SYSSTATE'
Id:0-232267954

==================================================================

Best Regards,


Yudi Darmadi
http://www.niagaprima.com

----- Original Message -----
From: "Steve Stackwick" <sstackwick AT JASI DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Friday, February 13, 2009 8:35 PM
Subject: Re: [ADSM-L] TSM Client GUI hanging at initializing


Here's the output from the trace. Looks like Andy's VSS thoughts were
right on, because there's kind of a long gap (almost 4 hours!) between

the dsm start and it's appearance:

02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp          (1416):
VssRequestor::InitializeVss(): VSS[SetBackupState]
02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp          (2160):
VssQuerySystemWriters(): Entry --- querying for files to exclude from
backup..
02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp          (2166):
VSS[GatherWriterMetadata]
02/12/2009 17:25:05.745 [000700] [1096] : vssreq.cpp          (8431):
VssRequestor::QueryStatus(): VSS - waiting for asynchronous operation
to complete for caller 'VssQuerySystemWriters()'
02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp          (2185):
VssQuerySystemWriters(): Asynchronous GatherWriterMetadata finished.
02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp          (2189):
VSS[GetWriterMetadataCount]
02/12/2009 21:05:25.427 [000700] [1096] : vssreq.cpp          (2201):
VssQuerySystemWriters(): Number of writers that responded: 7

Now, what to do? I''ve told the admin that they may have a problem
with VSS on this server, but maybe it's a client bug?

Steve
On Thu, Feb 12, 2009 at 5:15 PM, Andrew Raibeck <storman AT us.ibm DOT com>
wrote:

My guess is that the slow startup is VSS-related.

Try adding this to  your options file:

  traceflags service
  tracefile c:\somefilename

(you can name the trace file whatever you want, enclose in double
quotes if the file name contains blanks)

Then start dsmc and wait for the prompt to appear.

After you get the prompt, quit out of the client.

Then look in the trace... while much of it might not make sense, what

you want to focus on is the time stamps that begin each line of trace
output.
Look for a large gap between two trace lines, which would indicate at

that point in the trace, the client attempted to call some function
and experienced a delay.

Alternatively, it might not be one big time gap, but lots of smaller
(but not insignificant) gaps in time.

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet
e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorage
Manager.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/12/2009
05:07:55 PM:

> Re: TSM Client GUI hanging at initializing
>
> Steve Stackwick
>
> to:
>
> ADSM-L
>
> 02/12/2009 05:09 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
 >
> Note that, on the same machine, I just installed the SQL Server TDP

> and
it
> works just fine, connects to the TSM server, backs up, etc. This
> has got
to
> be a client bug.
>
> On Thu, Feb 12, 2009 at 4:57 PM, Thomas Denier <
> Thomas.Denier AT jeffersonhospital DOT org> wrote:
>
> > -----Steve Stackwick wrote: -----
> >
> > >I have a W2K3 SP2 32bit server whose brand new TSM 5.5.1 client
> > >install is behaving peculiarly. The GUI hangs at Initializing
> > >(though it does start after a *LONG* time), the command line
> > >hangs at an open window, likewise.
> > >The usual suspects: this is not a cluster, and the admin sez he
> > >tried to apply the VSS fix and was told it was superseded by
> > >what was already on the machine. Any clues?
> >
> > Is there any chance that the DNS servers are specificed
> > incorrectly and you are waiting for a succession of queries to
> > time out? The quick test for this is to specify the server
> > address in dotted decimal form. This eliminates any dependence on

> > DNS, and hence will eliminate the delay if it is due to DNS
problems.
> >
>
>
>
> --
> Stephen Stackwick
> Jacob & Sundstrom, Inc.
> 401 East Pratt St., Suite 2214
> Baltimore, MD 21202-3003
> (410) 539-1135 * (866) 539-1135
> sstackwick AT jasi DOT com




--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick AT jasi DOT com


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.