Wanda's comment: brilliant!  I've often advocated that saving stuff you
have not reasonable hope of actually being able to use is foolish. One
might as well send blank tapes to the vault and spare the read/write
head wear and tear from sending tape into a drive.

I've also gotta think that there are an equal number of folks in the
organization that DON'T want to see stuff hang around for 10 years.
Find some of those folks and get some help heading this bad idea off at
the pass.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Wanda Prather
Sent: Monday, April 28, 2008 1:13 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Retain All Existing TSM Backup / Archive Data for
10Yrs

Not necessary.

You can't rebind a file that has been archived to a different management
class, but if you change the RULE the file is bound to (i.e., the
archive
copy group retention setting), that change does indeed take effect, and
will
do what you ask.

That said, here's my plug for content management:

Will anybody be able to FIND anything in these archives 10 years from
now?
With TSM archiving, all you have to look at is file names.  If your mgmt
wants to be able to locate any INFORMATION 10 years from now, some sort
of
content management application is usually more appropriate.  You get
some
indexing and some organization and some search capabilities for the
data,
not just the host name and filenames for client nodes that no longer
exist...

W



On Mon, Apr 28, 2008 at 2:01 PM, Hart, Charles A <charles_hart AT uhc DOT com>
wrote:

> Ok, we have a requirements to retain all Backup / Archive data that
> exists in our TSM environment today for 10 years.  There's a few
"ugly"
> options, but would it be possible to do the following?
>
> Export node from Existing TSM servers to New TSM Server with Archive
And
> Backup Copy Groups set to 10 years retention.  I know that just
> increasing the Archive Copy group on the existing TSM Server's
Archives
> to 10YR will not re-bind those Archive objects, but what if you export
a
> node to a new TSM server with Longer retention Archive Copy Groups
will
> the Archives bind to the new Archive Copy groups on the new TSM
server?
> (I'm hoping so)
>
> Appreciate the input!
>
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail immediately.
>