VMware Cloud Community
John_Molnar
Contributor
Contributor

Explaining the "aging processes" of event and task history

I'm trying to clarify some vagueness between various .pdf articles and

this forum post. The admin guide ( vi3_35_25_admin_guide.pdf ) on

page 54 says:

When an object is removed from the inventory, its log and event history

remains until urged through the aging processes. Data is kept for a

specified window of time. As the time window shifts, older data is purged.

Similarly, the older VC v1.3 Users Manual (vc_users13.pdf)[2] on page 418 says:

When an object is removed from the VirtualCenter inventory, its log and event history

remains until purged through the normal processes.

This forum thread (http://communities.vmware.com/message/935150), however, indicates that the

'normal aging process' is, in fact, a manual, interactive maintenance procedure. Am I reading

understanding this correctly?

If there is no configurable or automated mechanism for deleting from these tables, what is the

"specified window of time" that the admin guide refers to? Is there a difference in the 'aging

process' between ESX 3.0.x, ESX 3.5, ESX 3i/e, and/or Virtual Center 2.x deployments? If there

is an automatic purging process, does anyone know how the SDK EventHistoryCollector and/or

TaskHistoryCollector objects are supposed to behave when faced with modifications to the

underlying persisted history?

Thanks for any clarification anyone can offer.

-john molnar

0 Kudos
1 Reply
John_Molnar
Contributor
Contributor

oh, i forgot to include this link:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100012...

which also indicates data purging is manual processes. Is this some

difference between VC and a standalone ESX? If data purging is a

purely manual process, then what's this "specified window of time"

jibberjabber all about? Something as simple as tech writers getting

ahead of the developers, perhaps, or is there some double-secret

functionality that i'm missing somewhere?

thanks for any feedback,

--john molnar

0 Kudos