David,

Many Years ago when i first took over networker from my colleague (networker 5
had just arrived), the first i did was read the admin manual. It explains
concepts and steps of each individual resource so i then knew where to look
for in case a resource attribute was unclear. How frustrating it was then
that creating clients and groups was not so easy as I thought. It seemed
intuitive but the practice turned out much more difficult. Restrictions that
popped up when doing something that seemed at first counter intuitive. The
misunderstanding of the interwoven-ness of things in networker is what bites
each time

Different companies have different strategies and complexities and Networker
is an excellent tool to use for complex solutions. the more easy scenarios
seem more difficult.

What I have allways missed in the documentation of networker is a few
scenarios based on real world cases and how to get there.

A few case studies in growing complexity would give beginners a headstart into
understanding what is possible with networker and actually how to get there,
step by step. Later versions of that document could then be expanded with
variations if that seem needed.

e.g.

take our environment:

We have one server and approx 300 clients. 70 servers 180 desktops 80 laptops.
3 lto2 libraries of 10 slots (but licenses are 8 or 9) . 3 months retention
for desktops and laptops , 6 months retention for servers. We have 3 major
pools Desktop, Server, ServerClone and some archiving pools.
automatic cloning for the server pool + some scripts.
(currently some 275 lto2 tapes used.)
Laptops backup to Disk (pool Default ) and are staged to Desktop pool after 6
hours max. No san , no drive sharing. In my opinion a simple scenario. We are
mainly a development environment with sales and tech support.

Maarten


On Wednesday 03 November 2004 00:19, David Geddes wrote:
> Hi,
>
> We are trying to plan a better doc set for NetWorker and would like your
> opinion. Assume that you are new to the NetWorker product but are now
> responsible for its successful implementation. Would you open the NetWorker
> Admin Guide (pdf or printed) and read a conceptual overview? Suppose the
> overview explained, without going into much detail, how the features in
> this product could be used to help you achieve your goals, i.e., implement
> a backup and recover solution across your enterprise. Additionally, the
> overview explained how, again without going into much detail, you could
> optimize your backup and recovery operations. Is this the sort of thing
> that would be useful to a NetWorker Administrator. Is it something that an
> Administrator might read or is it a safer bet to assume that Administrators
> are only going to read the docs if they're in a jam. Thanks for any help on
> this!
>
> - dg
>
> --
> 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
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Maarten Boot,
Compuware Europe B.V.
Hoogoorddreef 5
1101 BA Amsterdam

--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=