I am researching this but in the mean time Backup Exec 2012 revision 1798 Service pack 2 http://www.symantec.com/docs/TECH208600 resolves the error. This can be installed through running Live Updates (make sure the agent is pushed out to any remote servers afterwards).
what error ?
my backup is fine.
just asking what is this remsrv.exe and why it's talking to mapi32.dll
started process monitor during exchange restore from tape and noticed that remsrv.exe is doing some acions on/via mapi32.dll why and for what is my question
As far as I know remsrv is used by the GRT capability so yes it does touch MAPI and possibly EWS components as part of expected behaviour. It is possible it is used more by the GRT to Tape process than the GRT to disk as we do perform slightly different processes for the two backup types even though the data is the same.
do i need to have it on both server's ?
so it's not required on both ? if yes, why ? because be uses EWS ? if yes, is MAPI still somehowe involved in the bcakup restore process ?
actualy i do have a exch 2003 in our domain. is mapi cdo req for be ?
so if mapi is not used, but EWS can you guys give me some info about how the backup and restore process is working ?
To answer your inquiry, Backup Exec consists of components that work together to provide a complete backup and restore functionality. The components are:
Below link explains "How Backup Exec Works"
With regards to Backup Exec backing up Exchange Server, Backup Exec calls and interact with VSS. Below is the link that describes "How Backup Exec Exchange Agent interacts with VSS to snapshot and backup Exchange Server"