• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Client Option Set: Exclude System State Globally

paschumacher

ADSM.ORG Member
Joined
Feb 7, 2008
Messages
52
Reaction score
0
Points
0
Location
Bismarck, ND
Hello,

I have about 1200 TSM clients mostly ranging from 5.5 to 6.1.X. on TSM Server 6.1.4.2. I'd like to begin excluding the system state object, except on the Domain Controllers. (which will have a different optionset) I am running into some trouble and would like to ask your help.

I am trying to exclude the systemstate by using a client option set rather than manually changing all of the dsm.opt file to:

DOMAIN ALL-LOCAL -SYSTEMSTATE

Does anyone know if this can be accomplished using a client option set, or am I just wasting my time with fooling around with changing it from the Client Option Set.

Thank you in advance.
 

GregE

ADSM.ORG Senior Member
Joined
May 12, 2006
Messages
2,100
Reaction score
31
Points
0
Website
Visit site
Setup a test option set and try it on a test client.

def clientopt <option set> domain -systemstate
 

paschumacher

ADSM.ORG Member
Joined
Feb 7, 2008
Messages
52
Reaction score
0
Points
0
Location
Bismarck, ND
def clientopt <option set> domain -systemstate
I tried "def cliento <option set> inclexcl exclude.domain all-local -systemstate" and it didnt work.

mostly i'm just tired of beating my head against the wall and was wondering if anyone else has gotten it to work or knows how to exclude the systemstate backup through a client option set
 

paschumacher

ADSM.ORG Member
Joined
Feb 7, 2008
Messages
52
Reaction score
0
Points
0
Location
Bismarck, ND
you're right. i havent tried that one yet. i thought that everything after an INCLEXCL had to have a ".command" like exclude.dir or exclude.image. i'll give it a shot!

thanks!
 

GregE

ADSM.ORG Senior Member
Joined
May 12, 2006
Messages
2,100
Reaction score
31
Points
0
Website
Visit site
i thought that everything after an INCLEXCL had to have a ".command" like exclude.dir or exclude.image."
For INCLEXCL, it does. But DOMAIN is a different option.

Let us know your test results.
 
Last edited:

paschumacher

ADSM.ORG Member
Joined
Feb 7, 2008
Messages
52
Reaction score
0
Points
0
Location
Bismarck, ND
Thanks GregE, that did work well for the system state data. I am no longer backing up the system state data on my test servers. I do however, seem to still be capturing the 'system object' and 'asr'. I was under the impression that system state included those objects. I have tried to create the same statement in my client option set that removed the system state:

Option: DOMAIN
Sequence number: 1
Use Option Set Value (FORCE): Yes
Option Value: -systemstate

Option: DOMAIN
Sequence number: 2
Use Option Set Value (FORCE): Yes
Option Value: -systemservices

Option: DOMAIN
Sequence number: 3
Use Option Set Value (FORCE): Yes
Option Value: -systemobject

Option: DOMAIN
Sequence number: 4
Use Option Set Value (FORCE): Yes
Option Value: -asr

I have them all set to force: yes, so I am wondering if I did this correctly to exclude the asr and system object items.
 

GregE

ADSM.ORG Senior Member
Joined
May 12, 2006
Messages
2,100
Reaction score
31
Points
0
Website
Visit site
Windows2000 and XP have SYSTEMOBJECT, not SYSTEMSTATE
Windows2003, VISTA, and 2008 have SYSTEMSTATE, not SYSTEMOBJECT

To exclude systemobject, use "inclexcl exclude.systemobject"
To exclude systemservices, use "inclexcl exclude.systemservice"

I've found no way to exclude ASR. It's part of systemstate and systemobject and I've tried in the past.
 

nahmad

ADSM.ORG Member
Joined
Mar 27, 2011
Messages
65
Reaction score
0
Points
0
Location
Sydney
Hi paschumacher
I tried making same cloptset but it there was a error "no file system etc in domain"

Thanks

Nahmad
 

wuestenfuchs

ADSM.ORG Member
Joined
Feb 12, 2009
Messages
22
Reaction score
0
Points
0
Windows2000 and XP have SYSTEMOBJECT, not SYSTEMSTATE
Windows2003, VISTA, and 2008 have SYSTEMSTATE, not SYSTEMOBJECT

To exclude systemobject, use "inclexcl exclude.systemobject"
To exclude systemservices, use "inclexcl exclude.systemservice"

I've found no way to exclude ASR. It's part of systemstate and systemobject and I've tried in the past.
I know, very ancient thread. But just for the record.

TESTFLAG SKIPVSSASR
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 60 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.2%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Threads
31,732
Messages
135,270
Members
21,730
Latest member
fahim
Top