Dennis,
Networker will start at the top of the 'storage node' list and
then, if it can't satisfy the request from that one it goes to the next.
So, if you had a location A machine with the following in the storage
node field
Storage node B
Storage node A
Nsrserverhost
It would try to find a suitable tape in storage node B, failing that it
would go to storage node A and failing that it would go to the Networker
server.
You could, of course, just have an entry for where you want the data to
go and leave no choices. Or variations on above (i.e. one storage node
then back to the Networker server).
Now, the indexes, these actually belong to the Networker server. If you
specify a pool for a group then the indexes will be pointed to that pool
as well (the pool will have data from the Networker server and so will
take on Networker browse and retention if greater than the original).
If, however, you specify the client to the pool, the indexes will go to
the default pool and just the client data to the specified pool.
Hope it make a bit of sense.
Bob
-----Original Message-----
From: Voetelink D. [mailto:voetelink AT ECN DOT NL]
Sent: 03 March 2003 14:22
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Best way to configure storage node
Networkers,
I'm having some difficulty configuring networker in using our storage
node. I hope someone might be able to shed some light.
Our configuration:
Server : Tru64 UNIX, networker 6.1.3 at location A
Storage node: Linux, networker 6.1.3 at location B
All networker clients on location A are being backupped on the storage
node at location B, and all networker clients on location B are being
backupped on the server at location A. I've created 2 groups, each
containing the clients of one of the locations. ( Grp A -> all clients
at location A, Grp B -> all clients at location B )
First, I put the tapes on both the server and the storage node in the
same pool, and allowed all groups to write to that pool. Now I had the
problem that the server was asking for writable tapes, but wouldn't load
a tape in the drive ( while there were enough writable/recyclable tapes
available. ). I was however able to manually relabel or mount a tape,
which would be accepted for writing....
As this is nog an acceptable situation, I decided to create seperate
pools for the server and the storage node. This works with only one
problem: the indexes of the clients at location A are not backupped.
(index save: error, no matching devices; check storage nodes, devices or
pools) I looked in the list archived, and found that the solution was to
enter all clients in the 'clients' field of the pool. As I have about 50
clients to backup at location A, I'm afraid it's not an acceptable
situation either.
Can anyone tell me how to solve the problems mentioned above? Are we
using the storage node functionality incorrect? Can the first problem be
a flaw in 6.1.3 ???
Also, I would like to hear some stories on how people ARE using storage
nodes in a correctly working situation....
Please help.
greetings,
Dennis
--
*******************************************************************
D. Voetelink
UNIX Systems Administrator
Netherlands Energy Research Foundation,
Facilities Department
Petten, Netherlands
email : voetelink AT ecn DOT nl
phone : (+31) 224 564738
*******************************************************************
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
------------------------------------------------------------------------------
This note is to advise you, as required by United Kingdom legislation, namely
The Telecommunications (Lawful Business Practice)(Interception of
Communications) Regulations 2000, that any email messages generated, received,
or stored on the email systems of ChevronTexaco may be intercepted by
ChevronTexaco, as the system controller.
==============================================================================
------------------------------------------------------------------------------
This note is to advise you, as required by United Kingdom legislation, namely
The Telecommunications (Lawful Business Practice)(Interception of
Communications) Regulations 2000, that any email messages generated, received,
or stored on the email systems of ChevronTexaco may be intercepted by
ChevronTexaco, as the system controller.
==============================================================================
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
