of Contract Employees
(P.A.C.E. -- www.pacepros.com)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
bbullock
Sent: Thursday, August 15, 2002 1:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
True, t
Hi All,
I've just come back from two weeks working on something else and caught up with the
list, and I can't help jumping in with this one even if it's late.
How about
backup TSM DB and shutdown current TSM instance (henceforth this is TSM-A)
create second TSM instance on same physical machi
.
Nick Cassimatis
[EMAIL PROTECTED]
Today is the tomorrow of yesterday.
bbullock
cc:
Sent by: "ADSM: Subject: Re: Eternal Data retention
brainstorming.
Dist Stor
, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 16, 2002 10:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
That will work for the active data in the old (renamed) filespaces, but I
believe the inactive data in the renamed filespaces will continue to expire
#x27;ve done the task and covered your aZZ :)
Zlatko Krastev
IT Consultant
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject:Re: Eternal
he scope of the request and the volume
of data involved.
Thanks,
Ben
-Original Message-
From: Nicholas Cassimatis [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 16, 2002 8:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
What kind of shelf life are you exp
-Original Message-
From: Slag, Jerry B. [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
If they tell you the hosts/filespaces just do a rename of the existing
filespaces.
-Original Message-
lto:[EMAIL PROTECTED]]
Sent: Friday, August 16, 2002 9:09 AM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
How about a backupset of every node on that day? Of course, it would have
to be "today" I guess...
Robin Sharpe
Berlex Labs
What kind of shelf life are you expecting for your media? Since they've
discovered that optical has data decay, it's not even "forever"! I've seen
some others on the list point at it, but how will you restore this data in
10 years?
Here's what I'd look at doing:
1. Take about 5 dbbackups (or
Wanda... or anyone... one question. When changing retention settings for a
management class, are they immediately processed by TSM or does the next
backup have to run to rebind all the files to the new class settings ?
If it is the latter, the files that no longer exist on the client, but are
sti
e old copypool tapes into the
library during the restore.
That's my theory at this point.
Ben
-Original Message-
From: Ramnarayan, Sean A [EDS] [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 16, 2002 4:09 AM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming...
"ADSM: Dist Re: Eternal Data retention brainstorming.
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
08/16/02 07:09
AM
Please respon
Tell the legal department you want a complete duplicate of you TSM
environment !!!
People make so many unrealistic request with absolutely no thought as to
what they are asking for.
The only way to do that is to make a handful of tsm db backups (to protect
against loss due to media failur
Have you considdered using archiving to store the data that needs to be
kept forever? I've very sure no government org is really intrested in
your /etc/passwd file for over 1o years back. Find out what you need to
keep and set up archiving
On donderdag, augustus 15, 2002, at 09:30 , bbullock
]
Subject: Re: Eternal Data retention brainstorming.
Dang, my mails are long-winded. Forgive me if I'm boring those of
you who are not interested. Fell free to use the "delete" button. :-)
There's been a lot of good suggestions sent to me. The real kicker
is
Dang, my mails are long-winded. Forgive me if I'm boring those of
you who are not interested. Fell free to use the "delete" button. :-)
There's been a lot of good suggestions sent to me. The real kicker
is that with the volume of data involved (460TB as of today), some of the
solu
Ben,
I've had to do "permanent" retention only twice so far.
The first time we did the "keep forever" change to the management class
associated with our Lotus Notes files. As predicted, data and tape usage
grew unbounded. That helped us decide to migrate from 3570 technology to
LTO.
After tha
with the same
retention settings, right ?
Duane Ochs
Systems Administration
Quad/Graphics Inc.
414.566.2375
-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 3:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainsto
,
Ben
-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
Well, this is an interesting "what-if" scenario for discussion!
I'll take a crack at it.
As a refinement to Wanda's final suggestion, couldn't you alter
your policies for 'del volhist type=dbb' (or simply retain the
current copy of your database backup exclusive of the volume
history), and then modify your storage pool's reusedelay
parameter appropriately?
The drawback that I see is
Do you use DRM and if so, do you copy all primary pools?
If so, snapshot a DB backup and have your offsite people box up all your
current offsite tapes plus this snapshot. Very carefully mark those boxes!
Back at the TSM server, mark all these volumes as "destroyed" and let them
be re-created as y
If they tell you the hosts/filespaces just do a rename of the existing
filespaces.
-Original Message-
From: bbullock [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:31 PM
To: [EMAIL PROTECTED]
Subject: Eternal Data retention brainstorming.
Folks,
I have
We have only done this with our exchange servers (not the basic node but the
data from the exchange TDP). On these systems we have three nodes
base_node, base_nodeA, and base_nodeM. The base_node is for the operation
system. The "A" is the current exchange node. If told to lock, we will
change
-Original Message-
From: Doug Thorneycroft [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 2:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Eternal Data retention brainstorming.
how about renaming the filespace, This will keep your active versions.
-Original Message-
From
how about renaming the filespace, This will keep your active versions.
-Original Message-
From: bbullock [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, August 15, 2002 12:31 PM
To: [EMAIL PROTECTED]
Subject:Eternal Data retention brainstorming.
Folks,
I have
Well, this is an interesting "what-if" scenario for discussion!
I'll take a crack at it...
1) Painful, but may be the best solution overall.
2) I don't think that will work. Turning off EXPIRE INVENTORY will prevent
your tapes from reclaiming, but if you have a mgmt class set to 5 versions,
I t
26 matches
Mail list logo
