Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

UNSET, UNSET_ALL directives?

Created: 06 Aug 2013 • Updated: 06 Aug 2013 | 1 comment
This issue has been solved. See solution.

Hi All,

I was reading the Multistreaming configuration part and came accross with the below Unset and Unset_All Directives in Admin Guide which I didnot understand.

Could somebody pls make me understand in simple words what is this Unset and Unset_All, its work with an example? Admin Guide is sometimes too difficult to grasp the concept :(

UNSET, UNSET_ALL directives, and multiple data streams
All policy-specific directives that are passed to a client in a stream are passed in all subsequent streams. The UNSET and UNSET_ALL directives change this behavior. These directives are recognized only if the Allow multiple data streams option is set for the policy. For more information, see “Directives for specific policy types” on page 184.
The UNSET directive interrupts a policy-specific directive so it is not passed with any additional streams. The directive that was unset can be defined again later in the backup selections list to be included in the current and the later streams.
UNSET_ALL has the same effect as UNSET but unsets all policy-specific directives in the backup selections list that have been defined up to this point.
UNSET example
In the following backup selections list, the set command is a client-specific directive that is passed to the first and all subsequent streams.
set destpath=/etc/home
For the set command to be passed to the first two streams only, use UNSETor UNSET_ALL at the beginning of the third stream. At this location, it prevents SET from being passed to the last stream.
190 Policies
Rules to indicate paths in the backup selections list
set destpath=/etc/home
UNSET_ALL [or UNSET set destpath=/etc/home]
Excluding files
Operating Systems:

Comments 1 CommentJump to latest comment

Andy Welburn's picture

Added this note to the original discussion just as it was relocated:

The SET directive is a way of setting environment variables as directives in a backup selection list.

Personally we've never used them & my only ever exposure to them was for NDMP backups.

I doubt very much that you need to know about them ..... but I could be wrong.

The following T/N (essentially part of the NDMP Admin Guide) may help (or may confuse more) but UNSET/UNSETALL could easily be incorporated into the example it gives to UNSET specific or UNSETALL the variables that had been previously SET.

e.g. how I would envisage UNSET/UNSETALL in the example given by the T/N:

UNSETALL (or UNSET set hist = n)
SET DEF = 20