Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Networker vs TSM
- Thread starter ericobp
- Start date
*predicts no replies*
Networker has its share of problems, some in its design, some in its implementation. When I hit the pub on friday to ***** about my job with my friends who use TSM, they keep telling me "TSM doesn't have that problem, why don't you switch?"
Networker has its share of problems, some in its design, some in its implementation. When I hit the pub on friday to ***** about my job with my friends who use TSM, they keep telling me "TSM doesn't have that problem, why don't you switch?"
Serbtastic
Vendor
What problem in particular are you referring to? We use Legato NetWorker software and find it to be very good.
Reneburema
MIS
Hi,
Networker and TSM have roughly the same capabilities. But the main difference is in the way TSM approaches backups.
TSM is designed to run incremental backups for ever.
With Networker you can design your backup schedules, so if you want to backup incremental for ever you can implement it.
Working with the TSM environment is done from one of the 3 user interfaces (web, asci and gui). Things like scheduing error reporting are all in the application and database.
For the Networker environment you have 2 interfaces gui and asci. Things like reporting scheduling, reconfguring the clients can be integrated into unix shell scripts and ran from cron etc, etc.
TSM has fixed ways of moving data
backup ---> disk ---> tape
+--large files--> tape
Networker must be configured to do such things. You can make backups to disks. And then use staging and clonening to move the data onto the next device
In short TSM has more a standard way of working and Networker is more customisable to your needs. But it takes
a specialist to do so....
Networker has given me some nightmares especialy with netware clients not being backupped without any error messages..
I don't know off such issues with TSM...
Oh just one last thing TSM has a nice feature when you make a backup you can write simultanious to a second device.. I would like to have that in networker too..
Hopes this helps
Cheers Rene
Networker and TSM have roughly the same capabilities. But the main difference is in the way TSM approaches backups.
TSM is designed to run incremental backups for ever.
With Networker you can design your backup schedules, so if you want to backup incremental for ever you can implement it.
Working with the TSM environment is done from one of the 3 user interfaces (web, asci and gui). Things like scheduing error reporting are all in the application and database.
For the Networker environment you have 2 interfaces gui and asci. Things like reporting scheduling, reconfguring the clients can be integrated into unix shell scripts and ran from cron etc, etc.
TSM has fixed ways of moving data
backup ---> disk ---> tape
+--large files--> tape
Networker must be configured to do such things. You can make backups to disks. And then use staging and clonening to move the data onto the next device
In short TSM has more a standard way of working and Networker is more customisable to your needs. But it takes
a specialist to do so....
Networker has given me some nightmares especialy with netware clients not being backupped without any error messages..
I don't know off such issues with TSM...
Oh just one last thing TSM has a nice feature when you make a backup you can write simultanious to a second device.. I would like to have that in networker too..
Hopes this helps
Cheers Rene
- Status
Similar threads