ADSM-L

Re: Windows 2003 Client Backup errors

2003-09-30 09:07:29
Subject: Re: Windows 2003 Client Backup errors
From: Bill Boyer <bill.boyer AT VERIZON DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 30 Sep 2003 09:05:19 -0400
I just started a thread like this a couple weeks ago. Seems that the 5.2
client on Win2k3 uses a new interface to backup the System Object, and this
caused them to make a change to the protocol with the TSM server. To fully
backup a Win2k3 server with the TSM 5.2 client, you need a TSM 5.2 server
also. It's actually buried deep in the client manual if you do a search on
systemobject.

As I was informed by Andy Raibeck, you can use the 5.1.6.7 client to backup
Win2k3 servers to a pre-5.2 TSM server with full recoverability. You just
don't get some of the bells and whistles that come with the 5.2 version.

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Bruce Lowrie
Sent: Tuesday, September 30, 2003 7:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Windows 2003 Client Backup errors


All,
Receiving a strange error on the TSM Server (Solaris 2.8, TSM Server 5.1.63)
activity log referencing a Windows 2003 client (Version 5.2.03) :

09/29/03   20:14:10 ANR9999D smnode.c(18984): ThreadId<66> Session 73736 for
node FPRTCMD01 : Invalid filespace for backup group member: 2.

We receive several of these every night, yet the backups complete
successfully. Under client version 5.2.00 I did not see this error, only
after moving to 5.2.03. If anyone has any insight, please let me know.

Regards,

Bruce E. Lowrie
Sr. Systems Analyst
Information Technology Services
Storage, Output, Legacy
*E-Mail: b.e.lowrie AT dowcorning DOT com
*Voice: (989) 496-6404
7 Fax: (989) 496-6437
*Post: 2200 W. Salzburg Rd.
*Post: Mail: CO2111
*Post: Midland, MI 48686-0994
This e-mail transmission and any files that accompany it may contain
sensitive information belonging to the sender. The information is intended
only for the use of the individual or entity named. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the contents of
this information is strictly prohibited. Dow Corning's practice statement
for digitally signed messages may be found at
http://www.dowcorning.com/dcps. If you have received this e-mail
transmission in error, please immediately notify the Security Administrator
at <mailto:Security.Administrator AT dowcorning DOT com>

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