cancel
Showing results for 
Search instead for 
Did you mean: 

System Error Occured(130)

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Environment

Netbackup = 7.5

Netbackup Client = 7.5.0.7

Exchange Server = 2010

Exchange Server OS = 2008R2

Exchange Policy Attributes (Database backup source) = passive copy only

 

Query

I am facing ERROR 130 while Differential backup. Although my Full backups are running fine. I also disable the Circular Logging from Exchange Database. Furthermore see the below result:

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Administrator.COMPANY.COM>vssadmin list providers
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
 
 
C:\Users\Administrator.COMPANY.COM>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
No items found that satisfy the query.
 
C:\Users\Administrator.COMPANY.COM>vssadmin list writers
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: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {71680e71-4b1c-489b-8da0-88f00b0272a6}
   State: [7] Failed
   Last error: Retryable error

 
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {196bccc2-6766-420a-9517-49cb75cde471}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {936298ca-dfb5-4621-b15b-2b1f17f4743d}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {92ca7d39-0ee5-40ae-bf82-6baa72f77d73}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {3db3fb75-3258-4c88-8bb9-2e5247513cbd}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {ff2a2752-b5b7-4fbf-a0ec-86cc324fbe7f}
   State: [1] Stable
   Last error: No error
 
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {3ddb9312-c867-421c-9ba8-9d5493077645}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {6236179a-94fd-4175-85c2-852e32928932}
   State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {96f775b6-5f57-422b-a4a9-d55c9ef638ba}
   State: [1] Stable
   Last error: No error
 
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {f239011a-8187-4567-9116-72759a7fd05e}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {b7c2656d-ee4e-4f3a-a9a9-c96f840958be}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {8b79246c-7fbf-479a-b635-dc083ef2bb94}
   State: [1] Stable
   Last error: No error


 
 As per the Symantec TECHNOTE TECH181190 I restarted the Passive Exchange node and found  'Microsoft Exchange Replica Writer' state stable but after triggering the differential backup the Netbackup again failed with ERROR CODE 130. After the Netbackup policy failed I again triggered the command vssadmin list writers  it again shows below result:

 

Writer name: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {71680e71-4b1c-489b-8da0-88f00b0272a6}
   State: [7] Failed
   Last error: Retryable error

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

This is why NBU is failing with status 130.

Changes that the writer made to the writer components while handling the event will not be available to the requester

Requester is in this case Netbackup. This is Windows OS issue, its not something you can fix within Netbackup. You may find useful in this general VSS troubleshooting advice:

http://www.symantec.com/docs/TECH200584

View solution in original post

11 REPLIES 11

Marianne
Level 6
Partner    VIP    Accredited Certified

Have you checked Event Viewer Application log on passive node for errors?

And bpbkar log?

Please post all text in Details tab of failed job.

Nicolai
Moderator
Moderator
Partner    VIP   

Status 130 is system error.

VSS is called by Netbackup, so Netbackup may provoke/initiate the error but do not cause it. So to say :)

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi Zahid,

 

Fix the replicator writer issue. If its not working your passive copies are not in a good state. Even if you might get a backup to succeed it will then not clear the logs. As Marianne suggested, check the event viewer, I'm sure you'll find many messages telling you there is some issue with some or all database syncrhonizations.

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited
EVENT VIEWER
 
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
PrepareForBackup event

Context:
Execution Context: Writer
Writer Class Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Name: Microsoft Exchange Replica Writer
Writer Instance Name: Exchange Replication Service
Writer Instance ID: {48509177-848d-417f-abac-dbab1e7c4907}
Command Line: "C:\Program Files\Microsoft\Exchange Server\V14\bin\msexchangerepl.exe"
Process ID: 3400
 
===================
 
bpbkar logs are not creating
 
======================
 
ACTIVITY MONITOR
 
11/19/2014 12:21:34 PM - Info nbjm(pid=3056) starting backup job (jobid=2440) for client MBX02, policy NW-DB01, schedule Daily-Diff   
11/19/2014 12:21:34 PM - Info nbjm(pid=3056) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2440, request id:{B47EF910-8CA0-4F72-9017-35E33A7C9CFC})   
11/19/2014 12:21:34 PM - requesting resource Network
11/19/2014 12:21:34 PM - requesting resource fileserver-me.COMPANY.COM.NBU_CLIENT.MAXJOBS.MBX02
11/19/2014 12:21:34 PM - requesting resource fileserver-me.COMPANY.COM.NBU_POLICY.MAXJOBS.NW-DB01
11/19/2014 12:21:34 PM - granted resource fileserver-me.COMPANY.COM.NBU_CLIENT.MAXJOBS.MBX02
11/19/2014 12:21:34 PM - granted resource fileserver-me.COMPANY.COM.NBU_POLICY.MAXJOBS.NW-DB01
11/19/2014 12:21:34 PM - granted resource MediaID=@aaaay;Path=E:\Exchangeà€ Backups\Network;MediaServer=fileserver-me.COMPANY.COM
11/19/2014 12:21:34 PM - granted resource Network
11/19/2014 12:21:34 PM - estimated 0 Kbytes needed
11/19/2014 12:21:34 PM - begin Parent Job
11/19/2014 12:21:34 PM - begin Exchange 14 Snapshot, Step By Condition
Status 0
11/19/2014 12:21:34 PM - end Exchange 14 Snapshot, Step By Condition; elapsed time: 00:00:00
11/19/2014 12:21:34 PM - begin Exchange 14 Snapshot, Read File List
Status 0
11/19/2014 12:21:34 PM - end Exchange 14 Snapshot, Read File List; elapsed time: 00:00:00
11/19/2014 12:21:34 PM - begin Exchange 14 Snapshot, Create Snapshot
11/19/2014 12:21:34 PM - started process bpbrm (4264)
11/19/2014 12:21:34 PM - started
11/19/2014 12:21:39 PM - Info bpbrm(pid=4264) MBX02 is the host to backup data from      
11/19/2014 12:21:39 PM - Info bpbrm(pid=4264) reading file list from client         
11/19/2014 12:21:39 PM - Info bpbrm(pid=4264) start bpfis on client          
11/19/2014 12:21:39 PM - begin Create Snapshot
11/19/2014 12:21:41 PM - Info bpfis(pid=6944) Backup started            
11/19/2014 12:25:19 PM - Critical bpbrm(pid=4264) from client MBX02: FTL - snapshot processing failed, status 156    
11/19/2014 12:25:19 PM - Critical bpbrm(pid=4264) from client MBX02: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::SnapshotPrepare failed., status 130
11/19/2014 12:25:19 PM - Info bpbrm(pid=4264) DB_BACKUP_STATUS is 156           
11/19/2014 12:25:20 PM - Warning bpbrm(pid=4264) from client MBX02: WRN - NEW_STREAM0 is not frozen     
11/19/2014 12:25:20 PM - Warning bpbrm(pid=4264) from client MBX02: WRN - Microsoft Information Store:\NW-DB01 is not frozen   
11/19/2014 12:25:20 PM - Info bpfis(pid=6944) done. status: 130           
11/19/2014 12:25:20 PM - end Create Snapshot; elapsed time: 00:03:41
11/19/2014 12:25:20 PM - Info bpfis(pid=0) done. status: 130: system error occurred        
11/19/2014 12:25:20 PM - end writing
Status 130
11/19/2014 12:25:20 PM - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 00:03:46
11/19/2014 12:25:20 PM - begin Exchange 14 Snapshot, Stop On Error
Status 0
11/19/2014 12:25:20 PM - end Exchange 14 Snapshot, Stop On Error; elapsed time: 00:00:00
11/19/2014 12:25:20 PM - begin Exchange 14 Snapshot, Delete Snapshot
11/19/2014 12:25:20 PM - started process bpbrm (3996)
11/19/2014 12:25:25 PM - begin Delete Snapshot
11/19/2014 12:25:25 PM - Info bpfis(pid=0) Snapshot will not be deleted         
11/19/2014 12:25:28 PM - Info bpfis(pid=1632) Backup started            
11/19/2014 12:25:28 PM - Critical bpbrm(pid=3996) from client MBX02: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.dag01_1416385294.1.0       
11/19/2014 12:25:29 PM - Info bpfis(pid=1632) done. status: 1542           
11/19/2014 12:25:29 PM - end Delete Snapshot; elapsed time: 00:00:04
11/19/2014 12:25:29 PM - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
11/19/2014 12:25:29 PM - end writing
Status 1542
11/19/2014 12:25:29 PM - end Exchange 14 Snapshot, Delete Snapshot; elapsed time: 00:00:09
Status 130
11/19/2014 12:25:29 PM - end Parent Job; elapsed time: 00:03:55
system error occurred(130)

Marianne
Level 6
Partner    VIP    Accredited Certified

VSS error is Microsoft issue.  Log a call with Microsoft.

NBU backing is failing because of VSS issue.

Nothing can be done from NBU point of view to fix this.

Nicolai
Moderator
Moderator
Partner    VIP   

This is why NBU is failing with status 130.

Changes that the writer made to the writer components while handling the event will not be available to the requester

Requester is in this case Netbackup. This is Windows OS issue, its not something you can fix within Netbackup. You may find useful in this general VSS troubleshooting advice:

http://www.symantec.com/docs/TECH200584

sksujeet
Level 6
Partner Accredited Certified

Are you getting any exchange related error after that in event viewer. If i remember correctly I had seen this issue and the exchange database was not in the consistend state. I had to take help from my exchange guys to play the exchange logs to make it in consistend state.

Take help of exchange admin to see if your database shows fine, there are commands to check the exchange database if it is in consistent state( I don't remeber it).

 

 

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Today after sharing the states on my above post. My NBU admin triggered the full/diff backup and it got successful. My exchange admin did nothing. Even the Exchange is 24/7 means not restarted too

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Again Failed. Now doing google how to fix it

Marianne
Level 6
Partner    VIP    Accredited Certified

Or contact Microsoft since the issue is clearly with VSS.

We have often seen that a reboot is a tempory fix...

Moheeto
Not applicable
Employee Accredited Certified

C:\Users\Administrator.COMPANY.COM>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
 
No items found that satisfy the query.

 

Hi Zahid,

You can also give one try to configure shadow copies on the client. In my experience Correct configuration of shadow copies does fix a lot of VSS issues.


To configure them go to Disk Management on client. Right click any drive to select properties and then Shadow Copies tab.

Click on settings to configure Shadow copies on each drive. If a drive has less free space reconfigure its shadow copy to another drive which has enough free space.
Select No Limit and click ok. After clicking ok make sure you click disable tab (unless its not greyed out) on the previous window otherwise windows will keep accumulating shadow copies locally which will eat up. Once you have done this make sure all VSS writers are stable and do paste the output of vssadmin list shadows