There are a few things you can check:
Has Expire Inventory ran since you suspect \trends.nsf was removed?
Did you run the Notes agent against the trends.nsf database before the Notes
server issued a purge/compress/etc.. command. I have seen situations where
the Notes app has come in and dumped the deleted nsf file before the Notes
agent has had a chance to see the deletion stub from Notes and this has
caused the agent to lose it's knowledge about the particular nsf file's
documents.
What version of Notes are you running and what is the Agent version.
If you would like to discuss other situations that may be happening, please
feel free to contact me.
John Stephens
Storage Solutions Specialists, Inc.
Tivoli Certified Consultant - ADSM V3
IBM Certified Specialist - AIX
http://WWW.Storsol.com
Wk: 813-265-3707
Fax: 520-441-9829
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Terry Taylor
> Sent: Wednesday, April 12, 2000 10:19 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Lotus Notes Connect Agent
>
>
> Good morning all!
>
> First of all, thanks to all who responded regarding my query
> about when a file goes inactive. I still have not had a
> chance to test it, but I will later this week.
>
> Secondly, this subject may have been discussed before, but here
> it goes anyway. I have a group of Lotus Notes servers
> which I am backing up with both the normal ADSM client and the
> Notes Connect agent. We exclude the nsf files from the
> ADSM client, and then pick them all up with the Notes Agent. We
> have separate node names, as well as separate dsm.opts
> on each Notes server. We also have just ONE policy domain for
> ALL Notes data, both ADSM client and Notes agent.
>
> My problem is that the Notes agent does not seem to be using the
> retention policies correctly, if at all. Our "Retain
> Only Version" for Notes servers is set to 30 days. I have a
> particular file, TRENDS.NSF, that was deleted from a server
> back in February. This is obviously longer than 30 days. But
> when I query this node, I still see the following entry:
>
> $NOTESDIR\TRENDS.NSF
>
> and then it displays a number of files and physical storage
> amount. My question is: Why is this NSF file NOT dropping
> out of ADSM after the 30 day period?
>
> And after doing a little more digging, I have discovered that on
> at least two servers so far, ADSM is still maintaining
> as many as 250 more filespaces (NSF's) as actually exists on the
> server. I'm sure if I looked at the rest of my Notes
> servers, I would probably find the same thing. I know I can go
> in and delete each of these filespaces manually, but
> his could be a rather time consuming process. Not to mention
> dangerous if I delete the wronf file space. Better off
> left to an automated process.
> I am currently battling through ADSM database capacity problems,
> so any of you running Notes can appreciate what kind of
> D/B volume this agent can produce. If any of you can shed some
> light on this, I would apprecuiate it! Thanks!
>
|
