Re: Exchange2003 backup folder limits at 2GB

Thanks Ben,
I've a dedicated backup server that do only backup another servers to
its HDD for quick backup and then copy everything to tape later. (Legato
call this method 'staging')

Anyway it requires an agent to be installed on each server. I'm not
sure what it does and where does it call the MAPI, if it calls MAPI on
Exchange Server then we cannot fix it but if it calls MAPI on the Backup
Server, this could be a good idea to fix it.

I'll get back to my Legato's support guy. Anybody here have more info?

Regards,
Tony.

"Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom> wrote
in message news:%23CT2OSqIGHA.524@xxxxxxxxxxxxxxxxxxxxxxx
> Not exactly. That's not it. There isn't a *new* version of MAPI that
> Exchange is going to use. As Scott mentioned, there are two versions of
> mapi32.dll. One for Exchange, and one for Outlook.
>
> Can you not install the backup product on a dedicated backup server
> instead of on your Exchange server? That would potentially fix the
> problem you are seeing with their software because you could install
> Outlook 2003 (with unicode PST support) on the backup server.
>
> BTW - not all Brick-level backup mechanisms export to PST first. At least
> not as far as I am aware...but then again, I don't use Brick-level backups
> and never will.
>
> --
> Ben Winzenz
> Exchange MVP
> MessageOne
> Read my blog!
> http://winzenz.blogspot.com
> http://feeds.feedburner.com/winzenz (RSS Feed)
>
>
> "Tony" <tony@xxxxxxxxxxxxxx> wrote in message
> news:eJwzaPiIGHA.1388@xxxxxxxxxxxxxxxxxxxxxxx
>> Thanks Scott, you make it super clear.
>> So right now, I cannot do anything but reduce the folders size or split
>> it to keep each folder smaller than 2GB then the backup can be done
>> successfully. Until the new version of MAPI.
>>
>> Thanks,
>> Tony.
>>
>> "_SBL" <none@xxxxxxxx> wrote in message
>> news:%23e$kepeIGHA.516@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hello Tony, Ben, et al,
>>>
>>> The information in this thread is correct, but an important fact has
>>> been left out: this software is running on an Exchange Server system,
>>> and Microsoft very strongly cautions against installing Outlook onto
>>> Exchange Server systems.
>>>
>>> Access to .PST files is accomplished via MAPI. As you are all aware,
>>> there are two distinct versions of MAPI within Microsoft. The Exchange
>>> Server version of MAPI is simple in terms of features, but has been made
>>> very robust over the years. The Outlook version is very rich in
>>> features, but is considered (by the Exchange Server people) to be much
>>> less stable, and thus we have all been effectively prohibited from
>>> installing Outlook (and its MAPI) onto Exchange Server systems.
>>>
>>> We would love to be able to use the new MAPI in our brick-level
>>> backup -- in addition to solving the PST size problems, it would solve
>>> the problem wherein the old .PST format mangles data whenever the
>>> character sets do not match (i.e. one gets email with Japanese
>>> characters) as the new format uses Unicode. But we cannot, since we are
>>> restricted to using the version of MAPI that comes with Exchange Server.
>>>
>>> Does this get us off of the hook? Of course not. But since we cannot use
>>> the new .PST file format, we will be forced to use multiples of .PST
>>> files in the old format -- when one file gets full, create another. We
>>> are hoping to provide this for a future release.
>>>
>>> Ben writes: "If your backup software has to export everything in a
>>> mailbox to a PST file ... That is just kludgy!"
>>>
>>> True, but brick-level backups are kludgy by their very nature.
>>> Brick-level is offered in our products in addition to other, more
>>> efficient, more modern, and more reliable backup mechanisms, ranging
>>> from the traditional streaming API to modern snapshot technologies to
>>> moving data near-line and off-line. Most Exchange experts, including
>>> most Exchange MVPs in fora like this one, recommend against brick-level
>>> backups entirely. Microsoft has never embraced it, either, and none of
>>> the newer interfaces (ExOLEDB through MONAD) can do it even as well as
>>> MAPI.
>>>
>>> So why do we offer a brick-layer solution at all? Because our customers
>>> demand it. It is easy for people to understand and easy for them to
>>> implement, trivially easy to do restores, and all of the backup vendors
>>> have it. Some vendors hide it under different names, some have solutions
>>> that do not involve .PST files, but it is still MAPI, and still a kludgy
>>> approach.
>>>
>>> We will continue to address the most severe problems in our brick-level
>>> method, but most of our R&D is dedicated to more future-oriented
>>> solutions.
>>>
>>> Thanks,
>>>
>>> _Scott
>>>
>>> Scott Bingham (sfbing)
>>>
>>> RDC Engineering
>>>
>>> EMC Corporation
>>>
>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Exchange2003 backup folder limits at 2GB
    ... Until the new version of MAPI. ... > Access to .PST files is accomplished via MAPI. ... The Exchange Server ... "If your backup software has to export everything in a mailbox ...
    (microsoft.public.exchange.admin)
  • RE: Reinstalling Exchange Database
    ... I understand that you have a SBS 2k3 server, and you want to know what the ... There are several methods we can used to backup the Exchange server, ... Expand the Microsoft Exchange Server branch in the left pane, ...
    (microsoft.public.windows.server.sbs)
  • Re: Force user to use outlook and custom organizational form
    ... You can get the server name of the Exchange server, ... You need to use CDO 1.21, EX MAPI or Redemption for that. ... If you don't use custom forms any custom properties won't stay intact ...
    (microsoft.public.exchange.development)
  • Re: Mapi Session 9175
    ... attendant needs to create its profile when it needs to connect to the system ... need to also ensure you do not disable the the Exchange Server itself, ... MAPI version of the server, and may cause problems if the registry key is ... The attempt to log on to the Microsoft Exchange Server computer has ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 backup
    ... >me what their backup/disaster recovery plan is should ... >their exchange server fail to function or the server that ... Restore from backup. ... >good backup plan should be from the exchange server side ...
    (microsoft.public.exchange.admin)
Loading