Re: verexist & verdelete information ignored on 3.1.2.1
1999-01-14 11:35:57
Subject: |
Re: verexist & verdelete information ignored on 3.1.2.1 |
From: |
Bill Colwell <bcolwell AT DRAPER DOT COM> |
Date: |
Thu, 14 Jan 1999 11:35:57 -0500 |
I noticed that fewer files were being expired after moving up to 3.1.2.1 on
the os/390 server. I called it in to IBM, which already knew of the
problem. For os/390 the apar is pq22256. I think all 3.1.2.1 servers have
this problem.
Even though the apar is marked severity 1, IBM isn't rushing out a fix. I
was told the next server level will come out at the end of 1Q99. But Level
2 did say that a fix test would be available soon, it might be available
now.
OS/390 users of 3.1.2.1 can call the support center and get the fix test if
this is a big problem for them.
--
-----------------------------------------------------------
-----------------------------------------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
-----------------------------------------------------------
In <3.0.2.32.19990114110319.00d59bc8 AT postoffice3.mail.cornell DOT edu>, on
01/14/99
In <3.0.2.32.19990114110319.00d59bc8 AT postoffice3.mail.cornell DOT edu>, on
01/14/99
at 11:03 AM, Paul Zarnowski <vkm AT CORNELLC.CIT.CORNELL DOT EDU> said:
>Gareth,
>Thank you for posting this e-mail. I did some checking, and it looks like
>we also have the same problem. We are running 3.1.2.1 on AIX. This
>explains why our database growth has accelerated since upgrading to
>3.1.2.1.
>I'd advise others on 3.1.2.1 to check this out too.
>..Paul
>--
>At 12:43 PM 1/14/99 -0000, you wrote:
>>We have recently noticed that after upgrading to 3.1.2.1 on AIX and NT
>>platforms, more versions of changed files are kept than the parameters in
>>the ACTIVE copygroups stipulate.
>>
>>For example:
>>
>>If policies are set so that:
>>
>>3 copies are kept if the data exists
>>1 copy is kept if the data is deleted
>>
>>If a file then changes and is backed up 5 times, 5 copies are kept! Even if
>>the data is then deleted from the client and another backup is performed. We
>>have also run expire inventory with no change.
>>
>>Has anyone else out there found this?
>>
>>The time based expiration for these versions still seems to work ok.
>>
|
|
|