Home > Error Code > Symantec Netbackup Error Code 130

Symantec Netbackup Error Code 130

Contents

No Yes How can we make this article more helpful? Resolution Snapshot options One of the possible solutions is found in this Veritas KB: Exchange backup Snapshot processing is failed Error 130 The symptoms described here are the system error 130 Bookmark the permalink. 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' http://allconverter.net/error-code/symantec-netbackup-error-code-84.html

The bpbkar log on the client will show the Status 130, but will not list any specific error messages to indicate the underlying cause of the failure. Email Address (Optional) Your feedback has been submitted successfully! For the name, type:PowerShellOptions, and hit Enter. Exchange 2013 CU11 to a newer CU This Veritas KB is very explicit: After upgrading Exchange 2013 to Cumulative Update 11 (CU11), Exchange backup may fail with either status code 69

Netbackup Status 4207 Could Not Fetch Snapshot Metadata Or State Files

status: 130 31/05/2016 15:40:14 - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 0:00:40 31/05/2016 15:40:14 - Info bpfis(pid=30648) done. If backing up the passive node in a cluster, please collect the logs from both active and passive nodes as we contact the active node to get the health of the It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation.

Zahid Haseeb. It is possible that updates have been made to the original version after this document was translated and published. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Ftl Terminated By Signal 11 C:\>vssadmin list providersvssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool(C) Copyright 2001-2005 Microsoft Corp.

We need to use VSS for our backups. The bpbkar log should show that the backup fails consistently when trying to back up a VxFS filesystem.  If this is seen in the logs, then check the filesystem that contains Create/Manage Case QUESTIONS? For best results, it is recommended to use No Limit.

Error Bpfis log INF - INF - StreamInfo Id:STAN FSAttrib:0x0 FSAttrib:0x0 CAlgor:0x0 Flags:0x0 Size:422 INF - ERR - EnumerateForLocalMetaData: Unable to match file name filestream.hdr INF - VSS_Writer_freeze_commit: snapshot create failed Snapshot Creation Failed - Snapshot_notification::postsnapshot Failed., Status 130 Double click PowerShellOptions and enter 1 as the value data. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. All rights reserved.

Snapshot Processing Failed Status 156 Exchange

No Yes Did this article save you the trouble of contacting technical support? If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Netbackup Status 4207 Could Not Fetch Snapshot Metadata Or State Files Thank You! Exchange Vss Writer Failed With Error Code 1295 When Processing The Post-snapshot Event. If a third party hardware provider is installed (vssadmin list providers), modify the backup policy to have our backup use system provider type:In the attributes tab, click on the “options” button

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? weblink Email Address (Optional) Your feedback has been submitted successfully! Microsoft Customer Support Microsoft Community Forums Windows Server TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 If GRT backups fail to catalog mailboxes with Exchange 2013 CU11 and you have archive mailboxes please upgrade to CU12. Snapshot Preparation Failed - Error Attempting To Find Volumes To Snap., Status 130

So it only fails when using the passive node, without knowing exactly when and what caused the problem. status: 130: system error occurred 31/05/2016 15:40:14 - end writing Status 130 31/05/2016 15:40:14 - end Parent Job; elapsed time: 0:00:41 31/05/2016 15:40:14 - begin Exchange 14 Snapshot, Stop On Error Thanks. navigate here 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.

The system returned: (22) Invalid argument The remote host or network may be down. Vfm_freeze_commit: Method: Vss_writer, Type: Fim, Function: Vss_writer_freeze_commit In case the MS Exchange  backup is being performed using the passive database copy, the “Microsoft Exchange Replica Writer” is used on the note which holds the pasive copy of the Setting PowerShellOptions to 1 forces monad (the NetBackup process responsible for running PowerShell queries) to connect to local Exchange Management Shell session, thereby bypassing the need to interact with mailbox anchoring.

If Use Limit must be set, please consult with Microsoft to get an accurate size for your drives. 2.

If a status code 130 is still observed after the following steps, we will need a verbose bpfis log and the application event logs from the Exchange Servers. Keeping the default value of 0 will result in the backups using a provider other than VSS to perform the backup.Netbackup uses VSS for an Exchange Snapshot backup, Instant Recovery, and All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: http://0.0.0.10/ Connection to 0.0.0.10 Microsoft Exchange Replica Writer Retryable Error Run the following commnad to reset the errors:bpclient -client -update -exdb For example:bpclient -client DAG_Name -update -exdb DAG_DB3:EXSRV1:0:0:0   If a status code 130 is still observed, we will

Solution 1.  On the Exchange server, run "vssadmin list writers", "vssadmin list providers" and “vssadmin list shadows” from the command prompt. Thank You! Both appear on the above logs. his comment is here CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical