[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

487.0. "Problems with cross mountpoint backups (save -x)" by LUX06::GLOESENER () Fri Mar 14 1997 01:25

I have a Unix system configured as Networker client (4.2A), on this client I
execute the following command:

	save -q -s servernam -b poolname -W 80 -x -l full /

A file /.nsr exists:

	+skip: core
	+compressasm: .

I believed that the -x should make the save cross mount points such as
/usr and /var but it doesn't for me. Of course no .nsr file exists in 
/usr or /var skipping these directories. Even the mount points themself,
/usr and /var directories, are not backuped.

Any hints are welcome,
Gast.

Note: Please do not tell me to use savegrp or automatic sheduled backups
      because this isn't possible due to security reasons on the client.
	nsrexecd is not running !

T.RTitleUserPersonal
Name
DateLines
487.1first guess, some minor researchDECWET::EVANSNSR EngineeringMon Mar 17 1997 12:1921
My first cut at this would be to simply make multiple save's do this job.
  save /usr
  save /var
  ...

sounds like you are firing them up via cron.  That's OK. just remember to save
 those indexes too... Also, you will need to "load balance" the number of
 saves running simultaneously - NetWorker usually defaults to 4 (settable in
 the GUI)

save -x tells save (actually walk function in save) to cross mount points
 if a file crosses a mount point. The only way I know of to do this is a 
 softlink. walk saves a hidden directory (to mark the crossing), then walks on
 down that crossed mount point (at least, my cursory research seems to
 indicate that to me). I guess this would work if the softlink was to a
 directory.

The default behaviour is to not cross mount points, because usually, save is
 operating within savefs, which has already told the server (savegroup) a
 list of "local" mount points to operate upon - ergo, one save is run
 against one mount point.