Re: System Object won't rebind to new mgt class
The syntax for include is below. We only allow ALL right now, meaning all system objects are bound to the same mgmt class. include.systemobject ALL mgmtclass Regards deleting filespaces: 1) from the client - issue del fi, a list of filespaces are prompted and you can enter 1, 2, or whatever the system object filespace is. 2) from the server - the syntax is: del fi nodename filespace name nametype=unicode filespace name must match exactly what you see. Use , if there are spaces and is case sensitive. Issue q fi nodename and you'll see all the filespaces. For the system object filespace, it should be: del fi nodename SYSTEM OBJECT nametype=unicode Hope this helps! Joanne Nguyen TSM Client Development Thach, Kevin [EMAIL PROTECTED]@VM.MARIST.EDU on 11/14/2002 10:34:34 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: System Object won't rebind to new mgt class It is being backed up, just not to the proper mgt class. I think I will try Mark's suggestion to delete the filespace and see if it works correctly next time it gets backed up. Stupid question... What is the proper syntax to delete a System Object filespace? I have tried: del fi nodename 'System Object' and that doesn't work. -Original Message- From: Remeta, Mark [mailto:MRemeta;SELIGMANDATA.COM] Sent: Thursday, November 14, 2002 1:25 PM To: [EMAIL PROTECTED] Subject: 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? -Original Message- From: Mark Stapleton [mailto:stapleto;BERBEE.COM] Sent: Thursday, November 14, 2002 1:14 PM To: [EMAIL PROTECTED] Subject: Re: System Object won't rebind to new mgt class From: ADSM: Dist Stor Manager [mailto:ADSM-L;VM.MARIST.EDU]On Behalf Of Thach, Kevin 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 5.1.0.1 (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 ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE 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. This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
System Object won't rebind to new mgt class
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 5.1.0.1 (same as all the others that have worked correctly) Any ideas I might try? This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: System Object won't rebind to new mgt class
From: ADSM: Dist Stor Manager [mailto:ADSM-L;VM.MARIST.EDU]On Behalf Of Thach, Kevin 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 5.1.0.1 (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 ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
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? -Original Message- From: Mark Stapleton [mailto:stapleto;BERBEE.COM] Sent: Thursday, November 14, 2002 1:14 PM To: [EMAIL PROTECTED] Subject: Re: System Object won't rebind to new mgt class From: ADSM: Dist Stor Manager [mailto:ADSM-L;VM.MARIST.EDU]On Behalf Of Thach, Kevin 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 5.1.0.1 (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 ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE 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.
Re: System Object won't rebind to new mgt class
It is being backed up, just not to the proper mgt class. I think I will try Mark's suggestion to delete the filespace and see if it works correctly next time it gets backed up. Stupid question... What is the proper syntax to delete a System Object filespace? I have tried: del fi nodename 'System Object' and that doesn't work. -Original Message- From: Remeta, Mark [mailto:MRemeta;SELIGMANDATA.COM] Sent: Thursday, November 14, 2002 1:25 PM To: [EMAIL PROTECTED] Subject: 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? -Original Message- From: Mark Stapleton [mailto:stapleto;BERBEE.COM] Sent: Thursday, November 14, 2002 1:14 PM To: [EMAIL PROTECTED] Subject: Re: System Object won't rebind to new mgt class From: ADSM: Dist Stor Manager [mailto:ADSM-L;VM.MARIST.EDU]On Behalf Of Thach, Kevin 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 5.1.0.1 (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 ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE 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. This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: System Object won't rebind to new mgt class
ahh del fi nodename SYSTEM OBJECT namet=uni -Original Message- From: Thach, Kevin [mailto:KThach;COVHLTH.COM] Sent: Thursday, November 14, 2002 1:35 PM To: [EMAIL PROTECTED] Subject: Re: System Object won't rebind to new mgt class It is being backed up, just not to the proper mgt class. I think I will try Mark's suggestion to delete the filespace and see if it works correctly next time it gets backed up. Stupid question... What is the proper syntax to delete a System Object filespace? I have tried: del fi nodename 'System Object' and that doesn't work. -Original Message- From: Remeta, Mark [mailto:MRemeta;SELIGMANDATA.COM] Sent: Thursday, November 14, 2002 1:25 PM To: [EMAIL PROTECTED] Subject: 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? -Original Message- From: Mark Stapleton [mailto:stapleto;BERBEE.COM] Sent: Thursday, November 14, 2002 1:14 PM To: [EMAIL PROTECTED] Subject: Re: System Object won't rebind to new mgt class From: ADSM: Dist Stor Manager [mailto:ADSM-L;VM.MARIST.EDU]On Behalf Of Thach, Kevin 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 5.1.0.1 (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 ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE 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. This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] 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.
