Just know that you can cause corruption and potentially double your
customers database size with those backups. They should be used in a
disaster recovery situation only and in a lab at best. Explain to me why you
wish to change your mapisvc.inf to use mspst32.dll forthe Outlook service.?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Dgoldman
http://blogs.msdn.com/dgoldman
Download OABInteg
(http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD)
Post by rvangeldropHi Dgoldman,
Is there any chance you can tell me what problems I can encounter when I do
this?
Your comment that brick level backups are not recommended is already known
to us. However we still think this is good alternative option to offer to our
customers, who are often certified partners themselves.
Regards,
rvangeldrop
Post by Dgoldman [MSFT]No this is not a safe change. Also brick level backups are not recommended.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Dgoldman
http://blogs.msdn.com/dgoldman
Download OABInteg
(http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD)
Post by rvangeldropIn Exchange 2003 sp2, I wish to change my mapisvc.inf to use
mspst32.dll
for
the Outlook service.
With this I want to accomplish that our self-developed brick-level backup
module will support unicode and large pst's.
Is this a safe change. What other components or functions in Exchange use
Outlook Service and what risks do I run in changing this?