THis subject has been heavily discussed already. Just search ADSM-L for details.
By the way, if I have Oracle database mydb on sever MYNODE and dedicated TSM
node MYNODE_ORA for TDPO backups then:
1) on TSM Server:
PolicyPolicy Mgmt Copy
Lipp
> Sent: Thursday, January 21, 2010 1:31 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Data retention period 60days
>
> Figure out which management class is governing your Oracle backups. Q
> node nodename where nodename is the name the client uses to identify
> itself. Check
Kelly Lipp
Sent: Thursday, January 21, 2010 1:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Data retention period 60days
Figure out which management class is governing your Oracle backups. Q
node nodename where nodename is the name the client uses to identify
itself. Check to see which policy domain
Figure out which management class is governing your Oracle backups. Q node
nodename where nodename is the name the client uses to identify itself. Check
to see which policy domain the node is in.
Q copy domainname f=d
You'll probably see verexists=2, verdel=1 retextra=30 retonly=60.
The most
Boy, it sure looks like you'll have three versions forever on this one.
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick
La
On May 3, 2008, at 12:30 PM, David Hensley wrote:
I am using an Oracle TDP. I have 6TB of old Oracle data on both the
onsite
and offsite tapecopy pools. I need to delete the vast majority of
data in
both pools. As the data is spread over several tapes is there any
way of
deleting the data from t
On Fri, 15 Mar 2002 16:11:12 -0500, "Ward, Stuart" <[EMAIL PROTECTED]>
wrote:
>In the very near future I will need to put together a software and hardware
>proposal for data retention of approximately 50 years due to FDA
>regulations encompassing the medical industry.
>
>My main question would be
To provide you a direct answer to your question:
I have found good experience with the IBM 3995 Optical Jukebox. I
believe the shelf life on optical media is 100 years.
--
Joshua S. Bassi
Sr. Solutions Architect @ rs-unix.com
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- A
I had to do something similar a couple of years back. But after exhaustive
research the best practices are very expensive and require additional
personnel to make sure all the steps are followed.
First: You need a starting media, 12 years ago it was 9-track tape, which
under the best conditions h
This is the beauty of TSM. It can move the data from one set of volumes to
another over time. You just have to ask it to do so. Meaning you do not
have to worry about the media problem. What you have to worry about is the
application that reads the data, the OS that the data was created on, et
Hot Diggety! Ward, Stuart was rumored to have written:
>
> In the very near future I will need to put together a software and hardware
> proposal for data retention of approximately 50 years due to FDA
> regulations encompassing the medical industry.
Look at NASA. I've talked with various of the
For a quick Friday afternoon response:
There has been some discussion on this from time to time.
In one respect it boils down to this:
You can do the research on media and how long it lasts etc.etc.
But, the main point of having long term stuff is being able at some
future point, to retrieve and
01 04:02
Sent by:Zlatko Krastev/ACIT<[EMAIL PROTECTED]>
To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
cc:
Subject:RE: Data Retention
TSM v4.1 for AIX, Administrator's Guide, Table 27 (Table 22 in Windows
guide, Table 26 for Solaris)
"NOLIM
Gerald Wichmann <[EMAIL PROTECTED]> schrieb:
> So there is no reason to ever set retain only to less then retain extra
> right?
hmm - perhaps to prevent this MC to apply to directory backups (when
DIRMC is not specified) ???
--
Reinhard MerschWestfaelische Wilhelms-Univer
PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject:Re: Re: Data Retention
Based on how the original question was worded, both Mark's and Bill's
answers below are incorrect.
The last version expires 21 days after it went _inactive_, not after
it became the the only version
Agreed! Helps to read the question thoroughly.
_
William Mansfield
Senior Consultant
Solution Technology, Inc
David Bronder
cc:
Sent by: "ADSM:Subject: Re: Re: Data Rete
13, 2001 12:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Data Retention
Agreed! Helps to read the question thoroughly.
_
William Mansfield
Senior Consultant
Solution Technology, Inc
David Bronder
cc
Based on how the original question was worded, both Mark's and Bill's
answers below are incorrect.
The last version expires 21 days after it went _inactive_, not after
it became the the only version. In the original question, 14 days
have passed since the file was deleted (and went inactive), le
21 days. According to Table 17 in the admin guide, the RETONLY clock
starts ticking when the file goes inactive, which happens during the first
backup after the file is deleted from server storage.
_
William Mansfield
Senior Consultant
Solution Technology, Inc
630 7
On Tue, 13 Nov 2001 10:14:31 -0800, it was written:
>Versions data exists - nolimit
>Versions data deleted - nolimit
>Retain extra versions - 14
>Retain only versions - 21
>
>When a version is deleted from the server and after 14 days have passed,
>is the "only" version retained for 7 more days or
20 matches
Mail list logo