We have actually used option 1 below on more than 1 occasion for similar
reasons.
Kyle
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Thomas A. La Porte
Sent: Friday, September 21, 2001 17:32
To: [EMAIL PROTECTED]
Subject: Re: Expiration
On Sat, 22 Sep 2001 07:32:19 -0400, it was written:
>>We now have a Law Enforcement organization interested in some "unusual
>>activities" that occurred in one of sixty databases that resides on one of
>>the servers. The "request" they placed was to retain the oldest copy that
>>we had of this da
0% of big box storage.
To find the needed dbspaces use "onarchive list /database=".
Zlatko Krastev
IT Consultant
"Prose, Fred" <[EMAIL PROTECTED]> on 21.09.2001 23:52:37
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL
>We now have a Law Enforcement organization interested in some "unusual
>activities" that occurred in one of sixty databases that resides on one of
>the servers. The "request" they placed was to retain the oldest copy that
>we had of this database until they were through with their investigation.
It might be feasable to export that node, depending on how big it is. Then
you can let regular backups on the node expire normally.
Alex
-Original Message-
From: Prose, Fred [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 1:53 PM
To: [EMAIL PROTECTED]
Subject: Expiration
I can think of two options.
1) Save an additional backup of your (ADSM) database, and take
measures to ensure that the tapes upon which your (Informix)
database reside do not get reused.
This will allow you to restore the ADSM database at some stage
in the future, and the tapes that
We run Tivoli 4.2 on AIX (4.3.3) with a primary emphasis on backing up
Informix databases using the Informix TDP. We defined a "database"
management class for the database backups, with "retain extra versions" set
to 30 days. All database servers (13) go to this same class. This has
always prov
