Well, we changed nothing about how we were doing the restores, except for that option, and all of our backups are legacy. We do a full on weekends via a cmd file, and incrs. Each day.
Now, if the TDP is doing a vss backup when we do the full on Sunday, it's doing so of its own accord. Here's the Sunday command that kicks off the full backup: start /B tdpexcc backup * full /tsmoptfile=dsm.exch.opt /logfile=excsch.log /excserver=svrname >> excfull.log Here's the daily command that kicks off the incremental backup: start /B tdpexcc backup * incr /tsmoptfile=dsm.exch.opt /logfile=excsch.log /excserver=svrname >> excincr.log See Ya' Howard > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Thursday, April 10, 2008 10:09 AM > To: [email protected] > Subject: Re: [ADSM-L] ACN5798SE error Restoring Exchange > > Howard, > > If you are performing legacy restores the "Disable VSS Instant Restore" > will have no effect on what you are doing. > And so... I think it must have been your run recovery settings > or the way in which you were performing the restores. > > As far as applying legacy incremental restore on top of VSS full > restores, > that is not supported by Microsoft for Exchange. > > Thanks, > > Del > > ---------------------------------------------------- > > "ADSM: Dist Stor Manager" <[email protected]> wrote on 04/10/2008 > 10:55:47 AM: > > > Right after I sent this message I asked the Exchange guy to disable > "vss > > instant restore" and see if that worked, and viola, its working. > > > > Not sure what the vss instant does, but it obviously doesn't like > > incrementals from a legacy backup, :-D. > > > > No, I don't think I'm running 5.3.3.0.1 I have never downloaded it. > > > > The backup was legacy, which I believe had something to do with it, > > actually. > > > > See Ya' > > Howard
