The expiration time and load mainly depend on number of objects and not on
their total size. If you have to expire several thousands Domino databases
it will go pretty quick. But when the time comes to the mountain of
transaction logs of the Domino server, things may get worse.

For that reason TSM is having the CANcel EXPiration command. You can
schedule EXPire INVentory to start say at 15:00 and schedule at 19:00
expiration cancellation. Thus expiration would have only four hours each
day and when everything got expired it should finish before being
cancelled.
Put your own periods and schedules!

Be aware that if your expiration needs outgrow your expiration window, you
will sonner or later run out of scratches!!! Usual expiration should
finish on time and should not need to be cancelled.

Zlatko Krastev
IT Consultant






Douglas Currell <dlcurrell AT YAHOO DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
17.11.2003 11:00
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        TDP Policy Change


Currently, Domino data is being kept longer than is required by our SLA
and TDP is in use. I hope to update the domain and copygroups to reflect
our lesser needs. This would then allow terabytes of data to be expired.
Is it necessary to control the expiration? My fear is that expiration
could carry on for a very long time and have performance implications. Any
ideas on how to approach this would be appreciated.



---------------------------------
Post your free ad now! Yahoo! Canada Personals