Del,

  The information you provide below seems to be contradicted by the
capabilities of Backup Exec.  It treats the Directory and Information Store
as separate entities.  In fact, you are not supposed to be able to restore
an Exchange Directory to another machine with a different name, with any
product.  I am all but positive that Backup Exec uses documented Exchange
APIs.

I stand somewhat confused,
Dan T.


----------
> From: Del Hoobler <hoobler AT US.IBM DOT COM>
> From: Del Hoobler <hoobler AT US.IBM DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: MS_Exchange backupt
> Date: Friday, January 16, 1998 11:35 AM
>
> Tom,
>
> I cannot comment on the Seagate solution but I do know
> that the Microsoft Exchange Server backup API's give you access
> to both Exchange Databases (Directory and Information Store)
> as ONE LARGE OBJECT.  Any application that uses the documented
> Exchange backup and restore API's to do backups, must deal
> with them as one large object.
> But, when doing incremental backups, only the log files are
> backed up and not the entire database itself.
> I hope this helps.
>
> Del Hoobler
> IBM ADSM Agent Development
>
> >> We're looking at using ADSM for our MS-Exchange backups, with either
the
> >> Seagate BackupExec software or the as-of-yet-unavailable IBM agent.
How
> >> do (will) these work? Is the datastore treated as one large object? Or
> >> do the agents do backup of the datastore content?
>
> >> We're trying to get a feel for how long the process will take with a
> >> five-gig datastore over our 100 Mbit ethernet.
>
> >> TIA
>
> >> Tom Kauffman
> >> Sr. Technical Analyst
> >> NIBCO Inc.