Greetings!
To those of you using Digital's PolyCenter Network Save and Restore (NSR)
either single server or full server, I ask the following:
Have you gotten NSR to obey directives not to backup certain *local* mount
points?
I'm running Networker_V3.2A-06/07 Single Server, but these exact results can
be seen on Networker_V3.2-03/29 (full server).
What I've got is a CDROM mounted at /cdrom, and /misc as its own mounted
temporary partition, which gets used a lot. I don't want to backup /misc.
my /.nsr file contains:
null: cdrom
null: misc
This fails, NSR ignores this and backs up my CDROM each time I get a full save,
and /misc files are always getting backed up as incremental or full depending on
the file creation/modification.
To keep /misc files from getting backed up, I had to place a /misc/.nsr file
with:
null: .*
null: *
since the /.nsr entry for misc was ignored. This appears broken...
Now, since /cdrom is the mount point for a CDROM, I can't add a
/cdrom/.nsr file. I have also tried editing the Unix standard directives
to include:
<< /cdrom >>
+skip: .?* *
but this fails to be obeyed also.
So, how does one get NSR to *really* understand that I don't want to backup
CDROMs or other mount points as it should? I don't consider the necessity
of creating .nsr files with null: .* and null: * in each mount point directory
a reasonable solution when I interpret the documentation to mean I simply
need a .nsr file up one level with the null: <mount-point> to exclude
all files under that mount point.
Also, can anybody explain the following:
When the Unix standard directive has:
<< /tmp >>
+skip: .?* *
and there is no /tmp/.nsr file, I get files backed up (in this case a single):
--- Successful Save Sets ---
...
icefog.sois.alaska.edu: /tmp level=incr, 1 KB 00:00:14 1 file
...
But, when the Unix standard directive has:
<< /tmp >>
+skip: .?* *
and there is a /tmp/.nsr file containing:
null: .*
null: *
I get 0 files, 0 KB backed up:
--- Successful Save Sets ---
...
icefog.sois.alaska.edu: /tmp level=incr, 0 KB 00:00:57 0 files
...
and, yes, there was a file in /tmp created minutes before this backup ran.
Any ideas, comments, fixes? I think this is broken, but I may be mistaken.
Summary will follow.
Randy M. Hayman
haymanr_at_icefog.alaska.edu
Received on Wed Nov 13 1996 - 20:30:27 NZDT