Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Exchange policy issue - 130 error code

Created: 10 Apr 2013 • Updated: 10 Apr 2013 | 5 comments
This issue has been solved. See solution.

I am attempting to test/config GRT feature set on a test server and am receiving 130 and 59 error codes.  I believe it also has a negative effect on my production netbackup server and policy.  I recieve inconsisdent 130 errors on my production server as well now.

I have been running around trying to resolve this and am coming up empty.  Assistance is apreciated.

Thanks,

Jason

Operating Systems:

Comments 5 CommentsJump to latest comment

Dyneshia's picture

A 130 is usally casue by either :

1) Circular logging is turned on and you are running a DIFF or INC

2) Issue with VSS ( snapshot )

   * from a command line run :

     vssadmin list writers

     vssadmin list providers

   * Check the application event viewer for any VSS ESE errors

   * upload the bpfis log for review.

inlikefletch's picture

I am running a Full.

I see no VSS errors logged.

And I do not see a bpfis log.  Is there somewhere this needs to be enabled?  On the client or master server?

Thanks,
Jason

Dyneshia's picture

Yes, on the client create folder : 

veritas\netbackup\logs\bpfis

veritas\netbackup\logs\bpbkar

veritas\netbackup\logs\bpresolver

Also, please run and reply back with the outpu from

     vssadmin list writers

     vssadmin list providers

( also ran from the cleint )

What version of exchange are you running ?

inlikefletch's picture

I am running version 7.5.0.4.

VSS output from client:

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

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

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: {6a39a1b6-681f-44aa-bffa-ec2dfef3263e}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {11b7e592-87c0-4fb4-8a07-5ea1a20bdeae}
   State: [7] Failed
   Last error: Retryable error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {709ab09f-dbdd-4f93-936a-7faec502e38c}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {768057a4-1686-4404-a614-8da303327c9f}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {563e0bb1-c31b-4243-9744-43cde4137314}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {3351c8ac-796a-426d-9af3-715d598b9f3b}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {10175746-fbae-4419-9f61-ebae8d104eb1}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {5e9cb90b-6be3-4a55-b212-7e38517ad8b8}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {35614f6a-d2d6-45c0-ae61-ae4ef45e61c9}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {6b33c769-8599-4982-a7d0-0f449e3c3fda}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {c2e453b7-66c2-4694-b324-516a669529f0}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {575ca157-80bf-46ee-be6d-26da2e1387f2}
   State: [1] Stable
   Last error: No error

then:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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

Dyneshia's picture

Writer name: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {11b7e592-87c0-4fb4-8a07-5ea1a20bdeae}
   State: [7] Failed
   Last error: Retryable error

This is your problem, the MS writer is failed.  A quick fix would be to reboot the server to clear our the writer.  To keep this from happening or to find a root cause, Microsoft would need to be contacted.

SOLUTION