Just installed 5.2.2.9 with the same dsm.opt file. No luck. It will *not*
back up that drive.

Just no errors any more...

Mike Bantz
Systems Administrator
Research Systems, Inc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Stefan Holzwarth
Sent: Monday, April 19, 2004 9:15 AM
To: [EMAIL PROTECTED]
Subject: AW: BA client 5.2.2 and Server 2003


There are many problems - also that you described with the levels before
5.2.2.5
We use 5.2.2.9 and it seems that this version is quiet ok.
For open userprofiles we use ntbackup per preschedcmd, since TSM does not
support that at the moment on Windows 2003.

Kind Regards

Stefan Holzwarth

----------------------------------------------------------------------------
--
Stefan Holzwarth
ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste)
Am Westpark 8, 81373 München, Tel.: (089) 7676-5212, Fax: (089) 76768924
mailto:[EMAIL PROTECTED]


> -----Ursprüngliche Nachricht-----
> Von: Mike Bantz [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 19. April 2004 16:36
> An: [EMAIL PROTECTED]
> Betreff: 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
> 

Reply via email to