EXCHANGE 2010 DAG

pramod1
pramod1 used Ask the Experts™
on
we are experiencing vss backup failures on exchange servers which are having passive copies of databases.

attached errors.

but when we rebooted the server, backups were successful but the errors )attached still shows

any clue how rebooting got it corrected even if the error shows
vss1.png
Capture2.png
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Event ID and Source of the posted info, please.
What version of Exchange server you're trying to backup?
Post the results of:
Get-Command ExSetup | ForEach {$_.FileVersionInfo} 

Open in new window

Author

Commented:
exchange 2010 sp3, cu18
Event ID and Source of the posted EVENT ENTRY, please.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
As per error reported in event viewer.( attached-capture2.png)

I ran following on EMS:

Didn’t find any issue with vssadmin list writers . In our case, the VSS writers were fine.

Typed: vssadmin list providers . This will show the VSS writers capable of taking a system snapshot when backing.
Next typed: disk shadow  . Once that comes up typed:  list providers .  one will now see the hardware ID for each VSS writer that you have.

Took note of what VSS error said in your event log. For mine I noticed that a VSS writer with the ID of { 819e044d3..} was giving lots of errors. I matched up the ID number of the event log to the ID number of command prompt output. I noticed that the HW Provider was the culprit

My question is do we really require that writer from Commvault perspective?
Senior Systems Admin
Top Expert 2010
Commented:
It helps to have the Event ID numbers as well as the error message so we can look that up.

At any rate, base on the errors you posted, it looks like you have a service running with bad credentials somewhere. Check the commvault service/agent on the server to make sure it has the correct credentials to access the server's Volume Shadow Service. Also make sure VSS is configured to run with the correct creds (Should be local system or network service).

Author

Commented:
event ID 13 and event ID 12292

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial