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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
tsm vs netbackup?
- Thread starter kat115
- Start date
So why should you go with Veritas Netbackup versus IBM/Tivoli TSM.
1. Ease of installation and use, YOU can install and configure Netbackup out of the box without any consulting required (single master, no fancy configs).
2. If your NetBackup DB starts to out grow your file system, all you need to do is auto-grow that file system (if you have that capability) or tar up your db directory, grow it and tar it back to the newly sized file system.
With TSM, it requires a lot more work...since it is a relational DB, (proprietary nonetheless) you have to resize the DB and the filesystem and from what I remember it wasn't pretty.
3. NetBackup uses the traditional method of backup...Full and Incrm and these can have varying retention levels. By default NBU will not co-locate data of differing retention periods on the tape media. This is a good thing, because you don't want to end up with 'holes' in your tapes after
some images have expired. With TSM paradigm, they will co-locate files on the same media. The claim is that it is faster to do it that way. What you aren't told is when it the the reclamation process, no backup jobs may run.
So if your reclamation takes longer than normal and runs into your backup window, you might just miss a day of backups for some systems.
You may want to check out this link:
In terms of reporting, there is a free application called Operational Reporter. Ths sad thing this application is in its infancy and this application only runs on Windows.
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/server/NT/5.2.2.2/
The file that you want to download is called TSMCON522_WIN.EXE
In terms of management, regardless of the software.
If you do not understand how the software works or do not read any of the manuals/white papers/forum discussion or take a training class, management of the software is not simple.
From this FTP site under server you can down load the TSM Server and try it for 60 days.
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/
From the same ftp site there is a directory called client, this is where you download the client.
TSM is on the pricey side.
If cost is an issue, do check out NetBackup.
Also there is another product called Sysback.
I do not know how expensive is Sysback, may want to look into this product.
If price is really a BIG issue. Why bother to get a backup application. What about using mksysb, savevg, tar, dd or cpio?
Sorry for the mini novel.
Good Luck,
Sias
1. Ease of installation and use, YOU can install and configure Netbackup out of the box without any consulting required (single master, no fancy configs).
2. If your NetBackup DB starts to out grow your file system, all you need to do is auto-grow that file system (if you have that capability) or tar up your db directory, grow it and tar it back to the newly sized file system.
With TSM, it requires a lot more work...since it is a relational DB, (proprietary nonetheless) you have to resize the DB and the filesystem and from what I remember it wasn't pretty.
3. NetBackup uses the traditional method of backup...Full and Incrm and these can have varying retention levels. By default NBU will not co-locate data of differing retention periods on the tape media. This is a good thing, because you don't want to end up with 'holes' in your tapes after
some images have expired. With TSM paradigm, they will co-locate files on the same media. The claim is that it is faster to do it that way. What you aren't told is when it the the reclamation process, no backup jobs may run.
So if your reclamation takes longer than normal and runs into your backup window, you might just miss a day of backups for some systems.
You may want to check out this link:
In terms of reporting, there is a free application called Operational Reporter. Ths sad thing this application is in its infancy and this application only runs on Windows.
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/server/NT/5.2.2.2/
The file that you want to download is called TSMCON522_WIN.EXE
In terms of management, regardless of the software.
If you do not understand how the software works or do not read any of the manuals/white papers/forum discussion or take a training class, management of the software is not simple.
From this FTP site under server you can down load the TSM Server and try it for 60 days.
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/
From the same ftp site there is a directory called client, this is where you download the client.
TSM is on the pricey side.
If cost is an issue, do check out NetBackup.
Also there is another product called Sysback.
I do not know how expensive is Sysback, may want to look into this product.
If price is really a BIG issue. Why bother to get a backup application. What about using mksysb, savevg, tar, dd or cpio?
Sorry for the mini novel.
Good Luck,
Sias
LED888: with respect I disagree with some of your points here.
Point 1. I have no obhjection: TSM's not the easiest thing in the world.
Point 2. it takes two commands to make a TSM DB (or log)bigger (a) define dbvol [or logvol if that's what 's needed], (b) extend db.
It's painless, not painful. You can build the TSM DB on either raw logical volumes or as files in a filesystem - either way is plain simple.
Point 3. backup jobs *can* run while reclamation is running, I've no idea why you think they can't...
A common misconception is that TSM's always-incremental backup policy is in some way inferior. It's just the default - check out setting the backup method to absolute (which means "take a full backup").
As for cost - well, that comes down to where you buy!
Craigy (TSM Certified Consultant @ TSM5.2)
Point 1. I have no obhjection: TSM's not the easiest thing in the world.
Point 2. it takes two commands to make a TSM DB (or log)bigger (a) define dbvol [or logvol if that's what 's needed], (b) extend db.
It's painless, not painful. You can build the TSM DB on either raw logical volumes or as files in a filesystem - either way is plain simple.
Point 3. backup jobs *can* run while reclamation is running, I've no idea why you think they can't...
A common misconception is that TSM's always-incremental backup policy is in some way inferior. It's just the default - check out setting the backup method to absolute (which means "take a full backup").
As for cost - well, that comes down to where you buy!
Craigy (TSM Certified Consultant @ TSM5.2)
- Status
Similar threads
