See my original reply to your initial post on this subject (from 28
February).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Rob Hefty <R.Hefty AT LABSAFETY DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/03/2003 06:58
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Overriding Options File



Hello all,

TSM Server: 4.2.2
Clients: 4.2.X

Scenario:
We are trying out a new SLA and want to test weekly full backups including
system state objects.  Our current backups are all incremental and we have
excluded some application data (Program Files, Documents and Settings...),
thus a weekly full would need to override the options file.

Any ideas?

-----Original Message-----
From: Wu, Jialin [mailto:jialin_wu AT MERCK DOT COM]
Sent: Sunday, March 02, 2003 9:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Overriding Options File


Create a new option file that has your new include/exclude list. In your
scripted backup, specify the new opt file by adding -optfile=xxx at the
end
your backup command.

Jialin

-----Original Message-----
From: Len Boyle [mailto:SNOLEN AT VM.SAS DOT COM]
Sent: Sunday, March 02, 2003 10:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Overriding Options File


In article
<5ABBE878224C34468AEB19C6EDBC4BF30146D734 AT mailsrvr.labsafety DOT com>,
Rob Hefty <R.Hefty AT LABSAFETY DOT COM> says:
>
>Is there a way to override the options file on a scripted backup so as to
>backup all data whether or not it is usually?  I thought this was
considered
>in as Selective but tests prove otherwise.
>
Hello Rob

As others have pointed out, you can do this. But it is not normally done
as alternating excluding and then not excluding files can play havoc with
your
retention policys.

Can you tell the list group, what leads to your question? Maybe there is
another method of doing what you wish.

If not, another method might be to define two nodes for your server.
Backup the data normally excluded on node1 using node2.

len

----------------------------------------------------------------------------
--
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA)
that
may be confidential, proprietary copyrighted and/or legally privileged,
and
is intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please immediately return this by e-mail and then delete
it.

============================================================================
==