one thought...
for clients that require the monthly 4 year archives...
register alternate nodes by the name of <nodename>_exp
push any data required for long term retention (in the form of either
backups or archives or both) using the client <nodename>_exp
export that node
remove from environment...
doesn't take up space in the tsm database
doesn't take up space in the tsm ATL
personally I don't like to keep any archived data in an active TSM server
environment that has a retention value of more than 370 days
Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 925-8045
Mike Bantz
<[EMAIL PROTECTED]
> To
Sent by: "ADSM: [EMAIL PROTECTED]
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Thoughts on Monthly Archives
07/15/2004 04:00
PM
Please respond to
"ADSM: Dist Stor
Manager"
We are implementing the following:
Monthly FULL backups, saved for 4 years for document retention purposes.
Backupsets are not viable, as a restore would be a pain. So it looks like
we're going to do this with archives. My idea is to create another storage
pool with it's own media, another domain with it's own management class (we
really need only one: save 1 version of this file for 4 years), and remove
that media once the archive runs.
Anyone care to comment on if this is the best, easiest, way to do this? Or
comment on what to expect with things like tape usage and database size?
We're currently at 57% of a 12gig database.
Thanks in advance!!!
Mike Bantz
Systems Administrator
<<inline: graycol.gif>>
<<inline: pic32595.gif>>
<<inline: ecblank.gif>>
