Lee Hanel wrote:

Actually, you can back up indexes remotely.  We are currently doing that
in 5 different locations.  This is done by updating the storage nodes
field for the networker server itself to have the storagenode you wish
to use to save the indexes listed, then nsrserverhost.  About the only
gotcha on this is that the bootstrap has to be saved localy.  In our

We have a pool defined for the index and bootstrap (with "save sets: bootstrap, 
index" as suggested in the Adminitrator's Guide)
and all the indexes and the bootstrap go to that pool. So they all go to the 
same place instead of being backed up along with other
savesets (hence spread over all the tapes/pools).
I can't verify if it works with a pool bound to a storage node since it is on a 
library connected to server in our case. But I
remember I read something about bootstrap being restricted
with the server, so I guess you are right, you can not backup the bootstrap on 
a storage node.

environments, the networker servers have no tape drives, just an
adv_file type device for bootstrap saves only that are then staged off
to tape.

--
Lee Hanel
Backup Engineer
Rackspace Managed Hosting(TM)
Office: 210-892-4025 x1233
Mobile: 512-393-9250


On Tue, 2004-10-19 at 10:20 +0200, Grohal Klaus wrote:

Hi Michael

No you can't. The indexes will always be saved by the NetWorkerserver itself. Also, you 
can't remove the value "nsrserverhost" at the storage node field in the client 
recource for the NetWorker server.

regards
Klasu

-----Ursprüngliche Nachricht-----
Von: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] Im Auftrag von
Ballinger, John M
Gesendet: Montag, 18. Oktober 2004 23:39
An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Betreff: [Networker] Can we direct client-file indexes saved
to a tape on a storage node other than networker server


Can we configure to have the client-file indexes save to a
storage node
other than NetWorker server.
Do we just change the target storage node for the networker
server to be
some other storage node ?

Thanks - John

-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Michael Coxe
Sent: Monday, October 18, 2004 2:28 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] What's wrong with my SKIP directive?


I have a 1.4TB filesystem with several large subdirectories
and lots of smaller subdirectories. I split off the 4 large
subdirectories into their own client/group, and in the top level
directory backup placed the following directive to ignore the 4 large
subdirectories.

The root directory is /vol/vol0/home/buildusr:

I first tried the following, per the NW documentation, which
didn't work
- i.e., everything was backed up:

  directive:\
  "<< /vol/vol0/home/buildusr >>
        skip: builds
        skip: distributions
        skip: distributions-test
        skip: shipments";

Then, after reading suggestions from the Networker archives I tried
this, which doesn't appear to work either:

  directive:\
  "<< /vol/vol0/home/buildusr/builds >>
        skip:  * .?*
  << /vol/vol0/home/buildusr/distributions >>
        skip:  * .?*
  << /vol/vol0/home/buildusr/distributions-test >>
        skip:  * .?*
  << /vol/vol0/home/buildusr/shipments >>
        skip   * .?*";


What am I doing wrong? What's the right way to ignore/skip backing up
these 4 directories?


 - michael

--
  Michael Coxe, IT
  <mcoxe AT opsware DOT com>
  work (408) 744-7582
  cell (408) 898-7011

--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list. Questions regarding this
list should
be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker"
command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Yuri Pismerov, Sr. System Administrator,
TUCOWS.COM INC. (416) 535-0123  ext. 1352

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=