That's what I thought. There was a suggestion of using one client definition
and putting it in multiple groups. That is where you have the single
browse/renetion policy issue. If you ahve separate clients, then that
resolve sthat issue - but creates another... if you change the saveset
definition, you now have to change it as many times as you have a copy of
that client. Either way, the management starts to become onerous. 
 
Siobhan Ellis
Senior Technology Consultant
Enstor
Level 10, 118 Alfed St
Milsons Point
NSW 2061
Australia
 
Mobile: +61 424 750 544
Phone: +61 2 9900 2100
Fax: +61 2 9900 2199
e-mail: siobhan.ellis AT enstor.com DOT au

>>> "Rohrich, James" <James.Rohrich AT uop DOT com> 2/16/2005 9:57:23 AM >>>

Actually the case you mentiondoes work by using different pools with
different retention and browse policieson different tapes.

 _____
From: Legato NetWorker discussion on behalf ofSiobhan Ellis Sent: Tue

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=