Dianne,
The ability to control expiration processing was added to ADSM Version
1 at some early PTF level. Check the release notes that came with the
latest PTF you've applied to your ADSM server (ANR1110 in SYS1.SAMPLIB)
Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From: Dianne Sharp[SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent: Wednesday, March 19, 1997 5:16 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: FW: database keeps growing??
>
>>
>>I had this response from Dwight regarding checking the Expire Interval
>>setting on my MVS Server running ADSM V1. I can do the query option command
>>and it shows me that the interval is 1 (I think this means 1 hour as it
>>appears to happen every hour). However, in the V1 Admin Guide under Server
>>Options, ExpInterval is not one of the options listed.
>>
>>Does anyone know if or how I can change this option?
>>
>>Dianne Sharp
>>Operations Analyst
>>CLEAR Communications, Auckland, New Zealand
>>dsharp AT clear.co DOT nz
>>----------
>>From: decook AT amoco DOT com[SMTP:decook AT amoco DOT com]
>>Sent: Thursday, 20 March, 1997 2:03AM
>>To: Dianne Sharp
>>Subject: Re: FW: database keeps growing??
>>
>> Dianne, I've never been exposed to a V1 environment. What I can tell
>> you about V2 is that if you do a "query option" in a dsmadmc session
>> there is a field "expinterval" and that is how often expires run. I
>> believe they also (and this might be how it is done in V1) when
>> backups run. The expinterval might be to help get rid of files on
>> nodes that only backup once a month (or so)...?
>> One other thing you could try is (from an administrative session)
>> issue an "EXPIRE INVENTORY" and if it tells you that it is unknown
>> that would indicate it came to exist in V2.
>> Hope this helps.
>> later
>> Dwight
>>
>>
>>
>>______________________________ Reply Separator
>>_________________________________
>>Subject: FW: database keeps growing??
>>Author: DSHARP (DSHARP AT clear.co DOT nz) at unix,mime
>>Date: 3/17/97 11:27 PM
>>
>>
>>I kept this EMail that you sent ages ago because I wanted to ask you a
>>question, that I've only just got round to.
>>
>>You mention checking the expire interval on the ADSM server. I can't
>>find anything in the manuals about this. Is this a function of ADSM
>>Server V2? We are currently running V1 on MVS but are updating to V2
>>soon.
>>
>>Dianne Sharp
>>Operations Analyst
>>CLEAR Communications, Auckland, New Zealand
>>dsharp AT clear.co DOT nz
>>>----------
>>>From: Dwight Cook[SMTP:decook AT AMOCO DOT COM]
>>>Sent: Wednesday, 04 December, 1996 1:03PM
>>>To: Multiple recipients of list ADSM-L
>>>Subject: Re: database keeps growing??
>>>
>>>Item Subject: database keeps growing??
>>> Well, I haven't read the other messages but...
>>> each backup/archive copy of a file takes 100+bytes (I forget the exact
>>> number) so that is your growth...
>>> Check your expire interval on your server... if it is 0 (zero) then
>>> you will have to manually trigger file expiration (which is best
>>> because then you controll when it happens) if it is 0 and you haven't
>>> triggered file expiration it doesn't matter how you have your policy
>>> domains set up because you are never deleting obsolete files...
>>> Could also be like I was doing at first... the expiration process was
>>> starting at poor times so I would just cancel the process... same
>>> thing, I wasn't trashing old old copies...
>>> I've got two servers rolling in a third currently and assembling a
>>> forth and fifth... but on the existing two one has a 2GB db and has
>>> 6Terabytes of backup/archive's and the other has a 10GBdb and only
>>> 4Terabytes of data that is due to the first backing up SAP
>>> environments of large databases only(/mainly) and the second is
>>> backing up novell servers with A-BUH-ZILLION small, changing daily,
>>> multiply'n like mice, files on them... and ADSM being the fair backup
>>> system that it is uses just as much space keeping track of the 400
>>> byte file as it does tracking the 2GB file....
>>> Also how long are you keeping your activity log... ? If you are
>>> keeping more than 7 days it would be better to dump it out to a flat
>>> file and archive it away on tape...
>>> Anyway, if I'm forgetting anything I sure someone else will catch it
>>> but I'm betting it is either the cold/hard/facts of the number of
>>> files being backed up OR the lack of housekeeping...
>>> GOOD LUCK :-)
>>> later
>>> Dwight
>>>
>>>
>>>
>>>______________________________ Reply Separator
>>>_________________________________
>>>Subject: database keeps growing??
>>>Author: ADSM-L at unix,sh/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
>>>Date: 12/3/96 5:09 PM
>>>
>>>
>>>First thank you all the response mails to me. They give me lots of help.
>>>Our ADSM database is growing repidly. My question is the growing will
>>>stop on certain size or will grow unlimited? Is there some way to reduce
>>>the database size, or only add more space?
>>>
>>>We have sp2/aix 4.1 server and 23 nodes which is most OS/2s and unixs.
>>>
>>>Any comments will be appreciated.
>>>
>>>Regards
>>>
>>>
>>>Julie Xu
>>>04/12/96
>>>
>>
>>
>>
>
|
