Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

NetBackup 7.5.0.4 Exchange 2003 GRT backup failed status 20

Created: 10 Dec 2012 • Updated: 10 Dec 2012 | 10 comments

Hi,

This was working before upgrade however I'm now getting this error, I've seen this discussion https://www-secure.symantec.com/connect/forums/net... and understand that VSS is now a pre req, I have tried using VSS but my exchange environment freezes for up to 30 mins during the snapshot phase and then NBFSD fails to mount the NFS share and GRT fails anyway.

I've done numerous tests with manually mounting NFS and have done "System State" and AD backups of the particular server with GRT enabled and they all work fine.

Virtual Exchange server is 2003 SP2 running on Windows Server 2003 R2 SP2 using vmdk's on VMFS datastore on NetApp SAN

NBU is 5220 with puredisk

Any help with why VSS is causing Exchange to freeze ( not the server ) ?

GRT did work a couple of times with VSS but it ran for 14 hrs ( stream backup takes 1.5 hrs ) so I dont see any performance improvements

Thanks,

Dec

Comments 10 CommentsJump to latest comment

Dyneshia's picture

According to the Database compadibilty guide http://www.symantec.com/docs/TECH126904  exchange 2003 service pack 2 is not one of the listed compadable versions.  Exchange 2003 SP 1 has been tested and supported with a note that it will nto be supported after 7.5.x.x

Create the bpfis in the netbackup\logs directory on the exchange server and nbfsd on the media server to look for errors.  Also the application event viewer will show any errors regarding VSS / ESE.

Vm exchange backups in 7.5 still require the same configuration for GRT in previous versions.  An excellent technote to review is :

http://www.symantec.com/docs/HOWTO73076 - Everything you need to know to get Exchange Granular backups to work.

http://www.symantec.com/docs/TECH187917 - Disk Storage Types supported for Granular Recovery Technology (GRT)

I have seen where an upgrade will reset the services to the local account.

 

 

kml's picture

Hi,

did you find a way to fix it ? I have exactly the same issue;

Thanks in advance

captain jack sparrow's picture

Decky

How may VSS providers do you see in server

run from cmd (admin) vssadmin list providers

How is your backup policy configured?

What events are logged under event viewer during snapshots and nbfsd failure

if VSS is culprit , it must log events

Is OS updated with VSS patches?

Does backup works without GRT?

Is Shadow copy enabled on volumes where database and logs reside?

 

 Cheers !!!

CJS

 

DecKy's picture

I recreated the policy and GRT is working ok, however I'm still getting Performance events 510 and 509 during the process which I never had before VSS

Dyneshia's picture

Do you have multiple VSS providers ?

 

Reply back with :  vssadmin list providers

DecKy's picture

 

C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
 
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
 
C:\>
Dyneshia's picture

sorry the correct command it : vssadmin list writers

Dyneshia's picture

Make sure all writers are stable and have no errors or waiting for completion :

 

ssadmin list writers

DecKy's picture

All writers are stable

 

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {ec0c8e39-8a4c-4294-b835-666768c7b7ad}
   State: [1] Stable
   Last error: No error
 
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {babceea4-ce3e-4f07-8c00-a679c077f515}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {3506dd39-23ba-49cd-ac67-736910b8f6bd}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {4ad6820d-7e3a-40da-bc3d-a2d1daf45973}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {db8814bc-3aaf-459d-a2cc-931777c07a63}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {2e0f4558-c7f6-4b5e-b78f-ca4f06bd2a98}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {c40d9d19-ed69-42f1-a645-f3e082fed1ca}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {2ef0946c-fb3b-40c6-af06-3953037dae36}
   State: [1] Stable
   Last error: No error