| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 141.1 | Pre/post processing is a feature | DECWET::KOWALSKI | Time's not for saving | Wed Nov 13 1996 07:40 | 3 |
| 141.2 | | CRONIC::LEMONS | And we thank you for your support. | Wed Nov 13 1996 09:40 | 4 |
| 141.3 | | DECWET::MORRIS | This mind left intentionally blank | Wed Nov 13 1996 10:15 | 18 |
| 141.4 | | DECWET::ONO | The Wrong Stuff | Wed Nov 13 1996 12:11 | 16 |
| 141.5 | Questions about pre/post | ALFSS2::ZURIK_E | | Fri Feb 21 1997 08:14 | 13 |
| I have a question about the previous note.
In the script - the command save $*
Where does the save command get its arguments?
Can savefs or savegrp be used in the script?
The note says to put the script name in the saveset field. Don't you
mean backup command field?
Gene
NSR Support
|
| 141.6 | | DECWET::RANDALL | | Fri Feb 21 1997 12:26 | 29 |
| RE .-1
> In the script - the command save $*
>
> Where does the save command get its arguments?
Networker sends argument for save to the script when it is run. These
arguments get passed on to save via:
save $*
in the script.
> Can savefs or savegrp be used in the script?
Don't use savegrp or savefs. This is not what Networker is expecting.
Networker starts the script for each filesystem on the client that needs saving,
so using savefs or savegrp will not work. Actually savegrp is what starts your
script anyway.
> The note says to put the script name in the saveset field. Don't you
> mean backup command field?
The backup command field is correct.
For another good example of pre-post processing look on page 51 of the Admin
Guide.
-- Rich Randall
|