In addition to setting up a pool (or using an existing pool), the more important thing is to set up an archive copy group with the desired retention. The key here is that an archive is a distinctly different function than backup. The stuff that is archived is managed per the archive copy group. You may choose to point the archive copygroup destination at a new pool or at an existing pool. More about that later.
In your case you will need to use the backup/archive client to archive the exchange/sql data. To do this, those databases must be down (you can choose to do this at 3:00 am on Sunday morning). I don't believe the TDPs allow archiving, but I may be wrong on that point and I'm sure someone else will correct me if necessary. So operationally, you will continue to do daily TDP backups of this stuff and add a once-a-month db shutdown/archive to capture the data for long term retention. As for which pool should the data go to. Two choices: existing backup pool or new archive pool. Pros and cons? Separate pool, separates the data and allows you to remove the full tapes to the vault if you would like. Same pool allows reclamation to continue to move the data around on volumes thus "freshening" the data periodically. Your choice. Kelly J. Lipp STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 [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 Mark Bertrand Sent: Tuesday, October 15, 2002 9:43 AM To: [EMAIL PROTECTED] Subject: Archive\Long Term Storage Question I have been working with TSM for about a year now but have no experience with archiving. Recently I have been asked to look into archiving for long term storage of our Exchange, SQL and Oracle database backups. We are currently using TDP for our normally backup schedules and would like to retain an annual\monthly copy of those databases. I know this list has an overwhelming amount of information about how TSM is not designed for retention settings of this type, but they can be achieved with copy group retention settings and second management classes. My particular server has an archivepool but it doesn't have any space allocated to it, so I am unable to use the archive feature. My question is, what benefits would I have setting up an archivepool correctly to be able to use the archive feature over setting up new management classes with the required retention settings. Even if my archivepool was setup correctly, wouldn't it act like my existing diskpool, as in migrations to an archivetape pool with reclamations and expirations. Am I correct in assuming that we could not identify/remove a particular tape volume with a particular archived database on it. My understanding is that backupsets are the only way to accomplish that except for the fact that backupsets do not work for databases. I understand that archiving is used for backing up data with plans for deletion, but we have no plans to delete any of these databases. Please excuse my ignorance on this subject, I have done a lot of reading (including the FAQ) on this list but could not really find a particular answer on the benefits. Server W2K TSM 4.2.2.13, clients (most) W2K TDP 2.2 Mark B.