On 2008-12-18 20:24, NetWorker revealed:

N> NetWorker does an outstanding job of fully utilizing the configured backup
N> resources to protect the configured clients, in an automated way. It
N> intelligently allocates backup streams to available devices on the fly
N> allowing you to configure how many parallel streams each device should
N> accept, which is a powerful paradigm and in my experience with the same
N> environment will run faster and use less production resources than any other
N> enterprise tape backup product. You're welcome to disagree but I've seen
N> some compelling bake-offs.

I wouldn't go as far as claiming this is bullshit, but its pretty close. 
In our experience, commvault (the only other backup product I have real 
experience of except for networker) is really much better at distributing 
jobs, and moving them as resource availability changes.


N> The drawback has been that it has a steep learning curve on how to configure
N> it properly and the GUI was pretty ugly and lacked functionality. In the
N> past it also had major reliability issues but it is much more stable and
N> reliable now and the architecture/database structure is well-designed and
N> robust. Once it is configured correctly it does the job very well. And the
N> GUI issues in my opinion have been largely addressed.

Oh really? Do you define "in the past" as more than six months ago or 
what? :P

//Oscar

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER