ADSM-L

Re: BA client 5.2.2 and Server 2003

2004-04-19 21:20:35
Subject: Re: BA client 5.2.2 and Server 2003
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 19 Apr 2004 09:05:06 -0600
The error message you see would appear to be related to an attempt to back
up the Windows 2003 system state. I don't see how the temp directory has
any bearing on this.

ANSnnnnx messages are client messages. You need to look in the Messages
manual; alternatively you can run "dsmc help" to look up client messages.

If you are interested in backing up only C: and D: (and not system state),
then put this in your options file:

   DOMAIN C: D:

If you care only about local drives, regardless of drive letters, then
use:

   DOMAIN -SYSTEMSTATE -SYSTEMSERVICES



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

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



Mike Bantz <mbantz AT RSINC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/19/2004 07:35
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
BA client 5.2.2 and Server 2003






I've just installed the 5.2.2 baclient on a Server 2003 machine, trying to
back up to a Version 5, Release 2, Level 0.2 TSM server.

The dsm.opt file looks like this:

        PASSWORDACCESS  GENERATE
        TCPSERVERADDRESS        10.17.10.13
        dirmc directory
        ERRORLOGRETENTION       5 D
        SCHEDLOGRETENTION       5 D

This opt file backs up every local drive on any other machine we've got it
on.

I'd just like to back up the C$ and D$, default mgmt class. Problem is,
the
server will back up the C$, "process" the D$, then kick back an error
ANS1950E, that Backup via Windows Shadow Copy failed.

I cannot query the error on the server (no text found).

I've tried explicity including the d:\temp directory, etc to no avail.

This is something obvious, isn't it? :-)

Mike Bantz
Systems Administrator
Research Systems, Inc