Re: System Object won't rebind to new mgt class
I think of you have a DOMAIN statement in the DSM.OPT that does not include
the system object it will not be backed up. That is how we excluded the
system objects on our Win2k servers. Most have a DOMAIN C: D: etc... in
their DSM.OPT. Maybe this server has the DOMAIN statement therefore the
system object is not being backed up?
From: Mark Stapleton [mailto:stapleto AT BERBEE DOT COM]
Sent: Thursday, November 14, 2002 1:14 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: System Object won't rebind to new mgt class
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> On all of our Win2K servers, we've recently added the following
> line to the client dsm.opt files:
> include.systemobject ALL win_sysobj
> All but 1 client's System Object filespaces have properly rebound
> to the new
> mgt class. One however, is still bound to the default mgt class
> and I can't
> figure out why. It HAS backed up since the change, so I know
> that's not it.
> Server is 4.2.3 on AIX 4.3.3 and Win2K client is 126.96.36.199 (same as all the
> others that have worked correctly)
> Any ideas I might try?
Delete the filespace, and let the next client backup take care of it.
Mark Stapleton (stapleton AT berbee DOT com)
Certified TSM consultant
Certified AIX system engineer
Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.