• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2208
  • Last Modified:

Exchange Backups Suddenly Failing with resources not found

Everything has been working great with our Backup until three nights ago. Our full backup ran without a problem, but the next day (differential backups), I suddenly start getting the following error on all of our Exchange 2007 storage groups:

V-79-57344-65055 - AOFO: Initialization failure on: "\\[servername]\Microsoft Information Store\Default Storage Group". Advanced Open File Option used: No.
Snapshot provider error (0xE000FE1F): The device cannot be found.

Same error on all three storage groups and they no longer show up when creating selection lists in BE.

Nothing was changed on that server between the the two backups, so I'm pretty confused as to why the storage groups would suddenly be invisible to BE. I've restarted both the Exchange and BE services and checked the logs for anything that might hint at the problem. No luck. Exchange itself seems to be running perfectly normal.

Any help would be greatly appreciated:

Environment:
Server 1 - Mail Server: Exchange 2007 SP1 on Server 2003 R2 x64
Server 2 - Management:  Backup Exec 12.5 on Server 2003 R2 x86 (Also a GC server)
Server 3 - File Server: Server 2008 R2 x64 (Primary DC/DNS, etc.)
0
Danoklas
Asked:
Danoklas
  • 9
  • 5
  • 2
  • +3
1 Solution
 
mrbrain646Commented:
Did you try restarting the VSS service?
0
 
David WallCommented:
It may be worth reinstalling the remote agent on the exchange server.

0
 
hunartCommented:
Hi Danoklas,

I had this same error before.  Reconfigure your Exchange backup using "Backup from the active copy only (job fails if not available)" seemed to work for me.

Here is an article from Symantec http://seer.entsupport.symantec.com/docs/305815.htm.

Good luck...
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Shreedhar EtteCommented:
Hi,

Go to the comamnd prompt and execute the below command and post results:
vssadmin list writers


Also observed that Exchange 2007 is not updated with latest service pack.

Hope this helps,
Shree
0
 
DanoklasAuthor Commented:
mrbain646 - VSS service is running
WallD - I updated the BE agent.... no effect (did not reinstall completely though)
hunart - all BE options and settings have been working fine, so it's unlikely to be a setting.
shreedhar - see below.

Interestingly, I've also just discovered that Remote Desktop won't respond to connections and is throwing out errors about RAS not being a valid win32 application. It's starting to sound like one of those odd random things. I'm going to try and reboot the server this evening when there aren't many users connected.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {23ecc6b0-1ddf-4b43-b31e-84474253280a}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {683ebb2f-31ea-4193-abc5-a8f770fc9e0a}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {3ac35291-67ff-4cf9-9d09-ea75eb227fd9}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {4fccb8d5-b1f0-4437-8b3a-c5a137a4d4f0}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {b87a8a8d-0752-4d4b-9a4b-c1bd841f8a49}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {cb881267-167b-4fc2-8941-e477966d3fab}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {80a201df-ccd3-4cde-a613-f4c80ea28ed7}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e25bf1d6-91fa-448c-92b0-372e453369c4}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {d542d9d0-844b-41e6-b223-649a57ac3d9f}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {69b54a7d-b296-4ef4-bbf1-d751cacb752b}
   State: [1] Stable
   Last error: No error

0
 
DanoklasAuthor Commented:
Okay... been a long morning. Just realized I posted the vssadmin output from the wrong server. The server in question is just sitting there with a message saying

Waiting for responses:
These may be delayed if a shadow copy is being prepared.
0
 
DanoklasAuthor Commented:
Here's the correct list of VSS writers (eventually completed, but took awhile).

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {b3bdf6a8-a800-472e-8616-60fafb3a285d}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {d78b6aef-7313-4d61-88e0-2a283135fe7f}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {1976bd26-1a55-4eb6-bc72-2325c901c7ce}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0cd75d97-fffa-4a8a-9e05-541a761ebdfb}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {ec1e1a6e-ba14-4b2c-991d-244919a0ac52}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {027d03e2-3569-425b-9e3d-9b95378279cb}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {746025e0-564a-4fb2-bf3d-816e7c635fbd}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ea9183b8-4e15-40a4-93b7-9c8fad39304e}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {cb21ba6a-d89b-4d89-ab5c-293cd95466f9}
   State: [1] Stable
   Last error: No error
0
 
sunnyc7Commented:
Check if BE remote service is running on Exchange Server.
See if Exchange database and logs are browsable from the Backup Exec Server.

VSS Writer looks ok @ for exchange.

thanks
0
 
DanoklasAuthor Commented:
sunnyc7,

Yes the BE Remote Agent is running on the Exchange server.

As for the database and logs being browseable, not sure what you're asking there. If I load the Exchange Admin console on the BE server, I can see everything normally. However, in BE when you go to the selections list for the Exch server, it does not list the storage groups.... thus my problem. Everything was fine until 3 days ago, and nothing has changed to my knowlege.
0
 
sunnyc7Commented:
check if any Windows updates got installed on Exchange / Windows Security updates

Open IE > Tools > Windows Updates
On the left tab there is a history

my question was
- Exchange EDB path
- Exchange log path

Are these 2 shared and browsable

from BEX server, can you do this

start > run > 
type
\\exchange\Exchange.log\
and browse the logs ?

Will post back if I find something.
0
 
DanoklasAuthor Commented:
I've never seen any share with that name on this server.

Only Exchange-related shares are
\addresses
\ExchangeOAB
\Resources$

All of which are browseable

DK
0
 
sunnyc7Commented:
DK
Can you verify this
Is Backup Exec 12.5 Hotfix 329071  installed ?

or the Backup Exec 12.5 Service Pack 3 installed ?

Check here
http://seer.entsupport.symantec.com/docs/337276.htm

Discussion here.
http://www.symantec.com/connect/forums/backup-exec-125-exchange-information-store-missing
0
 
DanoklasAuthor Commented:
Currently at SP4.

Additionally, neither server is CCR or Server 2008. We do have a 2008 server, but both the Exchange server and the BE Media server are 2003 R2.
0
 
sunnyc7Commented:
Open a Case with Symantec ?
I am out of ideas @ will post back if i figure out something.
0
 
David WallCommented:
I would tryuninstalling and reinstalling the BE agent, just to be certain.
0
 
DanoklasAuthor Commented:
I'm hoping to come back this evening and do three things: Reboot server, Reinstall BE Agent (if still having trouble) and upgrade the NIC Drivers.

Will report back tomorrow.
0
 
DanoklasAuthor Commented:
Well, I hate to say it, but this appears to be one of those "Just reboot the server" things. Rebooted the machine and everything is just fine. Thanks for the help, though.
0
 
DanoklasAuthor Commented:
Followup:

Suddenly had the same error appear out of the blue. This time found the following article on Symantec's site. The solutions seems to have worked.

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH136306
0
 
sunnyc7Commented:
thanks for posting back your solution here.

0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 9
  • 5
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now