Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Microsoft Exchange Writer will not reset itself....waiting for completion

Created: 11 Feb 2013 | 1 comment

Netbackup 7104, Windows 2008r2

Hello all.

I have another issue that is defeating me. One of my Exchange backups repeatedly fails with error 130. All writers are stable with no errors, with the exception of the Microsoft Exchange Writer below. 

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {50f76caf-49cc-4313-ae82-602927be4831}
   State: [5] Waiting for completion
   Last error: No error
    <--------or sometimes shows "retryable eror"

Most of the time, the Exchange backups complete fine, but if for any reason the backup fails, or hangs up and has to be killed, the Writer hangs in the state above and will never clear. Sometime it shows "no error" and sometimes it shows "retryable error". Our VIP c-level executive mailboxes reside on this server, and we cant keep creating work requests and waiting for approval to reboot this server over and over. It looks really bad. Ive been researching this, and keep either coming across older suggestions, or technotes that lead nowhere or have been removed. Are there any new developments around this issue? Below are the job details, which of course show that the microsoft information stores are not frozen. I know that reboooting the server clears the issues, and have read that restarting the Exchange Information Store service can clear this as well, but that will still likely interupt exchange services to those databases. I cant really even tell if this is an issue specific to Symantec products, or to Microsoft. This behaviors seems to have started within the past couple weeks, and I dont know of any changes to cause this.

2/10/2013 2:41:43 PM - awaiting resource PDC_SG_TLD_0 - No drives are available
2/10/2013 2:42:19 PM - granted resource pdc00nbua801w.ohlogistics.com.NBU_CLIENT.MAXJOBS.PDC00EXCA501W
2/10/2013 2:42:19 PM - granted resource pdc00nbua801w.ohlogistics.com.NBU_POLICY.MAXJOBS.Exchange_2010_DAG
2/10/2013 2:42:19 PM - granted resource 2288L3
2/10/2013 2:42:19 PM - granted resource IBM.ULTRIUM-TD3.008
2/10/2013 2:42:19 PM - granted resource pdc00nbua804w-hcart3-robot-tld-0
2/10/2013 2:42:19 PM - estimated 0 Kbytes needed
2/10/2013 2:42:19 PM - begin Parent Job
2/10/2013 2:42:19 PM - begin Unknown Type, Step By Condition
Status 0
2/10/2013 2:42:19 PM - end Unknown Type, Step By Condition; elapsed time: 00:00:00
2/10/2013 2:42:19 PM - begin Unknown Type, Read File List
Status 0
2/10/2013 2:42:19 PM - end Unknown Type, Read File List; elapsed time: 00:00:00
2/10/2013 2:42:19 PM - begin Unknown Type, Create Snapshot
2/10/2013 2:42:19 PM - started
2/10/2013 2:42:21 PM - started process bpbrm (1013812)
2/10/2013 2:42:29 PM - Info bpbrm(pid=1013812) PDC00EXCA501W is the host to backup data from    
2/10/2013 2:42:29 PM - Info bpbrm(pid=1013812) reading file list from client       
2/10/2013 2:42:29 PM - Info bpbrm(pid=1013812) start bpfis on client        
2/10/2013 2:42:29 PM - begin Create Snapshot
2/10/2013 2:42:31 PM - Info bpfis(pid=8652) Backup started          
2/10/2013 2:42:55 PM - Info bpbrm(pid=1013812) from client PDC00EXCA501W: TRV - snapshot preparation successful    
2/10/2013 3:38:24 PM - Critical bpbrm(pid=1013812) from client PDC00EXCA501W: FTL - snapshot creation failed - Error attempting to gather metadata., status 130
2/10/2013 3:38:24 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:24 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:25 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:25 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:25 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:26 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:26 PM - Info bpbrm(pid=1013812) DB_BACKUP_STATUS is 156         
2/10/2013 3:38:27 PM - Critical bpbrm(pid=1013812) from client PDC00EXCA501W: FTL - snapshot creation failed, status 130  
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - NEW_STREAM0 is not frozen   
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\EXCH-DAG-1 is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\EXCH-DAG-2 is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\EXCH-DAG-3 is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\EXCH-DAG-4 is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\EXCH-DAG-VIP is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\Test-Database-PDC501W-DDC501W is not frozen 
2/10/2013 3:38:27 PM - Warning bpbrm(pid=1013812) from client PDC00EXCA501W: WRN - Microsoft Information Store:\Public Folder 501 is not frozen
2/10/2013 3:38:41 PM - Info bpfis(pid=8652) done. status: 130         
2/10/2013 3:38:41 PM - end Create Snapshot; elapsed time: 00:56:12
2/10/2013 3:38:41 PM - end writing
Status 130
2/10/2013 3:38:41 PM - end Unknown Type, Create Snapshot; elapsed time: 00:56:22
2/10/2013 3:38:41 PM - begin Unknown Type, Stop On Error
Status 0
2/10/2013 3:38:41 PM - end Unknown Type, Stop On Error; elapsed time: 00:00:00
2/10/2013 3:38:41 PM - begin Unknown Type, Delete Snapshot On Exit
2/10/2013 3:38:41 PM - begin Unknown Type, Delete Snapshot On Exit
2/10/2013 3:38:42 PM - started process bpbrm (1014768)
2/10/2013 3:38:58 PM - end writing
Status 0
2/10/2013 3:38:58 PM - end Unknown Type, Delete Snapshot On Exit; elapsed time: 00:00:17
Status 130
2/10/2013 3:38:58 PM - end Unknown Type, Delete Snapshot On Exit; elapsed time: 00:00:17
system error occurred(130)

Thanks all,

Todd

Comments 1 CommentJump to latest comment

RamNagalla's picture

after all your investigation ,  i would suggest you to make sure that the issue is not with Microsoft before we go and look into netbackup.

below discussion suggest some hotfix, so please check if that applies to you..

http://social.technet.microsoft.com/Forums/en-US/w...

<<<copy from above link>>>>

As R.Alikhani said, please apply the hotfix to have a try.

In additional, please try to apply the hotfix in this article.

http://support.microsoft.com/kb/833167

Then, please refer to this article.

Event ID 8194 — Volume Shadow Copy Service Operations

http://technet.microsoft.com/en-us/library/cc734235(v=ws.10).aspx

At last, if the issue persists, please try to re-register the VSS Writers.

How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.

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

Jeff Ren TechNet Community Support beneficial to other community members reading the thread.