There is no specific option that I know of on the save command that you can use to skip files. Your best bet is to use local directive files. You just need to create a text file called nsr.dir (Windows) or .nsr (UNIX) anywhere that you want to have NetWorker skip stuff. You can then run your save normally and this will be skipped. If you want at certain times to not have these files skipped, you just need to use the '-i' option on the save command and the directives will be ignored.
The syntax for the directive file is explained in the Administration Guide and here:
If you really want to do everything in one command, you could write a script which creates the directive file, then does the save and then deletes the directive file afterwards.
Skipping any file or ffolder during the client initiated backup can be done using Directives. In case you want to skip the /nsr (NetWorker) folder, then no worries as it contains the "skip" directive by default and will not be backed up.
The Client initiated backups do not use the directives specified on the backup server. These are the global directives
you will have to create the local directives on the client server. Create .nsr files and specify the files to be skipped in the file. This file will be checked whenever the Networker backs up the parent folder.
coganb
736 Posts
519
0
Posted April 19th, 2010 02:00
There is no specific option that I know of on the save command that you can use to skip files. Your best bet is to use
local directive files. You just need to create a text file called nsr.dir (Windows) or .nsr (UNIX) anywhere that
you want to have NetWorker skip stuff. You can then run your save normally and this will be skipped. If you want at certain times
to not have these files skipped, you just need to use the '-i' option on the save command and the directives will be ignored.
The syntax for the directive file is explained in the Administration Guide and here:
http://solutions.emc.com/EMCSolutionView.asp?id=esg53311&usertype=C
If you really want to do everything in one command, you could write a script which creates the directive file, then does
the save and then deletes the directive file afterwards.
-Bobby