Backupsets aren't stored in pools so no to the question about pools!

Yes, this is a good idea but only if you have the time at the end of the
month to get it done.  To generate the set TSM will read data from whatever
tapes the client data is stored on.  If there are lots of tapes, this means
lots of mounts.  I have not done this myself but I've done some TSM health
checks on systems where they were trying to.  Notice I said trying to.  They
weren't having luck getting the work done in a timely fashion.  So, that's
one negative.

The other negative is that the backupset tape is tracked in the volhist
table rather than in the volume table.  Therefore it is a little easier to
lose track of the tapes that contain backupsets.  Not a real downer but
something to consider.

Finally, generate backupset creates a tape from the client's active files.

You are right having the client move all the data to the server for an
archive can be problematic.  I like the approach of using a targeted archive
rather than a general archive: only archive the stuff you really need to
archive, not the entire client. That should help to cut down on the amount
of data you need to move.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Joe Cascanette
Sent: Thursday, November 22, 2001 7:06 AM
To: [EMAIL PROTECTED]
Subject: Archives vrs Backup Sets


Has anyone been using backup sets?. I have been looking into using
backup sets on a monthly bases instead of archives. I am using DLT 40/80
gig drives/tapes (10 of them). TSM 4.2.1.6 on Windows 2000, and 4.2.0
clients on about 98% of the machines.

>From what I am reading I am able to perform this operation at the TSM
server and it directs the output to scratch tapes. The GREAT thing about
this is it does NOT touch the serves to retransmit all the data to the
archive storage pool, and then to tape (which is alot of traffic!). The
Backups sets would use more tapes (kind of like collocation turned on
right?!). So after the daily incremental running at night, I will be
able to create the backup sets ( for a monthly archive) using the
current data just backed up from that node. (right?!)

One question is when doing a backup set, does it also save all the
inactive files? or just the active ones?

Is there a way to direct all the backup sets to another copy pool to
utilize tape consumption and to keep the tapes separate from the other
copypools for easier search? (just a thought - but this would be a lot
of extra work.


Any thoughts would be greatly appreciated.


Thank you

Joe Cascanette
The Cumis Group

Reply via email to