Actually I wouldn't say  the  that the Notes API was "awful" or "poorly
written" (although users of that API are of course entitled to their own
opinion). The real problem was that the Notes API wasn't really intended
as a backup API. As a result, while the Notes Agent did function, it was
very slow, especially for large Notes databases. Starting with Domino (if
I remember my history correctly), the Notes developers added function
specifically for backup to the product. Thus we developed a TDP that used
this new API, not the old API.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Stapleton, Mark" <stapleto AT BERBEE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/15/2003 09:52
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM Agent for Lotus Notes


From: John Stephens [mailto:jws AT stephens DOT net]
>Is there still an agent or TDP for Lotus Notes version 4.x
I am aware of the TDP for Domino, but what about Notes user's what do
they use for TSM backups?<

The backup API included with Notes up to and including version 4 was *so
awful* that Tivoli had to withdraw support and sales for the TDP for
Notes version 4 package pretty quickly. There's not much an backup
application can do when the API it has to reference is poorly written.

You'll just have to replicate the data onto another Notes box, or shut
down the Notes service long enough to do a backup of the cold files.

--
Mark Stapleton (stapleton AT berbee DOT com)