Hi John


Some of the top stories are:
Using versioning on TSM will remove "point in time recover" back in
time, because files that changes many times will not be available for
very long.

TSM writes backup to disc(Which has to be big and expensive), and while
it's on disc it can't be recoverd(easyly). And it can take all day
before the file has been moved to tape. There for its very difficult to
restore a file which a user deleted yesterday, and that is one off the
most used functions in networker.

The Collocation function stores all the backed up data for a client on
one set of media to reduce media mounts required for a restore.  Means
more media is required to backup your clients as there will be one set
of media for each client.

-----End off Mudtrowing ---------

Maybee you sold try to lower the number of backupservers(if possible) to
uptain a better information and configuration flow.

Henrik Grevelund


-----Oprindelig meddelelse-----
Fra: Ballinger, John M [mailto:john.ballinger AT PNL DOT GOV] 
Sendt: 18. marts 2003 00:47
Til: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Emne: [Networker] IBM Tivoli Storage Manager vs NetWorker


Does anyone have any comments on "IBM Tivoli Storage Manager"  vs Legato
NetWorker.

We are currently using Legato NetWorker with at least 7 NetWorker
servers and maybe 20+ storage-nodes to backup Solaris, Windows, LINUX.

thanks - John

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

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