[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

390.0. " how to create 2 pools for manual saves" by EVTAI1::POUSSARD () Fri Feb 07 1997 05:27

	Hi,


	I tried to configure 2 differents pools for manual saves on a 
NetWorker 4.2A server.

	So I, first configure 1 pool ressource 'pool1' with a specific group 
of PC clients attached to this pool and only the manual level selected.
	When I run a manual backup on one PC client belonging to this group, 
NSR asks me for the Default pool instead of 'pool1'


	I then configured a new pool 'pool2'  with a group of UNIX clients, 
and the manual level selected. When I do a manual backup from an UNIX  client,
with nwbackup, NSR asks me also for the Default pool.
	I then have the message in daemon.log

nsrd: inconsistency in mmd 1 authorization structure, state MM_MODE_WRITING 
(1), number of authorized and active sessions is zero, initialization 
structure.


	If I type on the client:
	
	# save -s server -b pool2 /etc/hosts , then NSR asks me correctly 
for pool2, so I have no problem in this case.

	But on the PC client, I can't force the -b parameter.



	If, now, I create a unique pool resource 'pool3' And I don't select 
any group or clients or savesets, but only the 'manual' level, and then ask 
a manual backup from a PC or a UNIX client, then it works correctly and NSR 
asks me pool3 correctly


	My question is:

	- how can I create 2 differents pools ressources, each pool being 
allocated for manula saves of on specific group of clients ?

	

	Thanks for your reply

	

					Gilles.


T.RTitleUserPersonal
Name
DateLines
390.1DECWET::FARLEEInsufficient Virtual um...er....Fri Feb 07 1997 09:5318
This is a common misconception about the purpose and function of
the 'group' parameter of pools.

Many people think that if they check 'Group Foo' on the pool setup, that
this will cause ANY backup from any client which belongs to group 'Foo'
to go to this pool.

THIS IS INCORRECT.

Actually, the group parameter causes the pool to ONLY accept saves which
are CURRENTLY RUNNING as part of group 'Foo'.

If you desire that any backup which is run from any of the clients in group
'Foo' will go to a given pool, whether or not that backup is run as part
of a savegroup, then you must set it up as follows:

1) Remove the specification for the group.
2) Add a list containing each client in the group to the pool definition
390.2thanxHGOVC::XFMV01::SUDHIRBWed Feb 26 1997 04:3813
    hi ,
    
    .1 is a very useful note. 
    this is one fact that i grossly overlooked while
    configuring pools.
    
    thanx and keep the info coming...
    
    regds
    
    sudhir