Solved

Backup Exec 2012 Error

Posted on 2013-11-14
4
1,571 Views
Last Modified: 2013-11-19
Received the following error when backing up the EX02. Exchange are running in DAG with EX01 & EX02. Backup Exec is installed on EX02 and backing the host name DAG. Any idea ?

Backup- EX01V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\exdag.ktl.com.hk\Microsoft Information Store\PublicFolder". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.

Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
0
Comment
Question by:AXISHK
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 1

Assisted Solution

by:mark_667
mark_667 earned 100 total points
ID: 39650675
Run a vssadmin list writers command on the affected machines to see if there's anything obviously wrong. I've had this intermittently for ages (and not just on Exchange machines) and haven't been able to get to the bottom of it, even the Symantec KB article suggests just rebooting the machine.
http://www.symantec.com/business/support/index?page=content&id=TECH42921
0
 
LVL 19

Assisted Solution

by:strivoli
strivoli earned 100 total points
ID: 39650680
I would restart ALL BE services on the BE Server and if the Exchange is hosted on another server, restart the Agent's service too.
0
 

Author Comment

by:AXISHK
ID: 39651101
Try both recommendations but don't help. Tks
0
 
LVL 9

Accepted Solution

by:
Sai Prasad Kinnera earned 300 total points
ID: 39659177
It is little difficult to troubleshoot VSS writer issues when suggested documents doesnt work.

I would suggest to follow below steps.

1) Check event viewer to confirm if you see any errors related to VSS
2) enable verbose Exchange VSS Writer Event logging via PowerShell.
To do this from a PowerShell commend:

C:\Windows\system32>get-eventloglevel *vss* | Set-EventLogLevel -Level expert
C:\Windows\system32>get-eventloglevel *vss*

Identity /   EventLevel
-----------------------------
MSExchange Repl\Exchange VSS Writer     /   Expert

To set this back to normal when it has captured the log, again from a PowerShell command:

get-eventloglevel *vss* | Set-EventLogLevel -Level lowest

3) In addition, it would be helpful to also collect the corresponding RAWS debug log with the event logs from the Exchange server for the failing backup job.  information on how to enable this level of logging can be found here:  http://www.symantec.com/business/support/index?page=content&id=TECH83408

4) Once done review the logs and see if any additional information can be found in them and then follow.

http://www.symantec.com/business/support/index?page=content&id=TECH125176
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Replication has always been one of those technologies that people run scared from. The main reason is usually cost. When you think of replication, your mind drifts to solutions that replicate from one disk frame to another using block level technolo…
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question