This fix worked for me.  I couldnt find this fix documented anywhere on the Veritas support site or anywhere else for that matter.  I tried updating Veritas 10d to SP2 first but that did nto fix the problem.  

You must add the registry key to both servers like the post says.  I missed that at first and only applied it to the BE server.  It worked after I applied to the Exchange server and restarted the BE Remote service.

Thanks for the post!!!!!

The fix worked for me for a full restore of DBs after a server crash. Like Jeff I only applied to the BE server at first. After calling Symantec and applying the fix to the Exchange server the restore (and automatic roll forward) worked perfectly.

Result - happy(ish) customer.

Lesson 2 - Always RAID1 your tranaction logs and RAID5 your edbs/stms, backup correctly and it actually works ;-)

Cheers Brian if I had read the blog correctly it wold have saved me a couple of hours in the early hours!!

with regard to lesson 2, this is fine for many deployments however RAID10 is often a more appropriate choice for or both databases and logs in higher volume environments.

Hi

Unfortunately the fix didn't work for me. I have a feeling the snapshot used MS VSS which looks to be the problem.

The error  is shown below. I checked the KB's and ran all the tests with no errors. your help would be appreciated.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: 0x800423f3, State: 0013.  Consult your Microsoft documentation for details. Check the Windows Event Viewer for corresponding application or system errors.

V-79-57344-65233 - A failure occurred querying the Writer status.

V-79-57344-65233 - A failure occurred querying the Writer status.

V-79-57344-65072 - Connection to the restore target has been lost.  Operation canceled.

Excellent Find - We've only recently come into this problem and found that we could easily restore our Storage Group in the first IS, but when it came to restoring any other SG's from different IS's the problem showed up (we've just never had to restore for any other IS before).

Lucky we didn't wait for Veritas/Symantec to get back to us - it's been a week with no word from them...

This was the answer to an annoying problem I had.  Thanks since this saved me hours or days of work in trying to figure this out.

re: Backup Exec Exchange 2003 Bug Workaround

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183

apparantly the vss writer is switched off by default and needs to be switched on for image restore (Exchange 2003) to work. This is for Windows Small Buiness Server but its prob the same for 2003 server as the platform is the same. back up exec v11d has notes on this problem

I ran into the same problem after upgrading Backup Exec from 9.x to 10.0 - The upgrade was necessary because of a new LTO library we bought. But a colleque forgot to upgrade the remote agents so restoring to the RSG continued to work fine. After I upgraded the remote agents to 10 I got the error regarding mounted stores.

I am not sure whether modifying the registry is too risky. Does anyone know whether Symantec corrected the bug?

Thanks, Rosario

Didn't work for me on 9.1 Backup Exec.

I was, however trying to restore into a new domain/server (SBS 2k3). I suspect this was part of my problem with it not working.

After screwing around with options, reg hax etc. for a couple of hours

I ended up copying the files over manually and using legacydn to hack it into mounting. Created some users, attached the old mailboxes and made some PST's - all is good.

So when I add the reg entries to both servers, it will restore to the "Recovery" storage group, correct?

Yes, its working correct (on my v12)

Regards and thx for this

AGG

Worked great with Backup Exec 11d and 2003 Enterprise server.

Here is the updated key for it:

[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\ESE]

"Ignore Mount State"=dword:00000001

Thanks!

-Rob

Slightly unrelated, but I've recently started using Exclaimer to manage our <a ref="http://www.exclaimer.com/products/exchange-email-disclaimers.aspx" title="exchange email disclaimers">email disclaimers</a> - so far I have been really impressed with this tool - I highly recommend it.

I think the word here is saviour.

Just remember to change BOTH the backup exec soyurce machine and the remote machine.

The tip also applies if you are using Ontrack PowerControls Extract wizard or similar

This worked for our Backup Exec 12.5 SP2 on our Exchange 2003 server.

Thanks!!!

This worked for our Backup Exec 12.5 SP2 on our Exchange 2003 server.

Thanks!!!

This worked also for Backup Exec 12.5 SP3, thanks.

Will Symantec ever fix this problem?

(it seems, that they test the software only with one storagegroup - but maybe more than one SG is a "unusual" configuration *lol*)

PingBack from http://mgonzalez.wordpress.com/2007/04/21/exchange-2003-mailbox-restore-and-backup-exec-10d-issue/

PingBack from http://frankthefrank.info/entry.php?id=kwws%3d22euldqghvprqg1frp2eorj2dufklyh253392432492Edfnxs0H%7bhf0H%7bfkdqjh053360Exj0Zrundurxqg1dvs%7b

Pingback from unix86.org » Configure AutoArchive In Outlook 2007