NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Enterprise Vault (EV) database backup fails with status 130 on a SQL server with Dell EqualLogic VSS provider

Enterprise Vault (EV) database backup fails with status 130 on a SQL server with Dell EqualLogic VSS provider
TECH214401 | 2014-05-08
Technical Solutions | CMS-XML

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump
TECH214512 | 2014-05-08
Technical Solutions | CMS-XML

VMware Instant Recovery fails with Status 130 due to network connectivity failure between ESX host and Restore Host

VMware Instant Recovery fails with Status 130 due to network connectivity failure between ESX host and Restore Host
TECH216312 | 2014-04-02
Technical Solutions | CMS-XML

STATUS 130, Backups of a FreeBSD 8.2 and MacOS 10 clients fail with error code 130

STATUS 130 , Backups of a FreeBSD 8.2 and MacOS 10 clients fail with error code 130
TECH195922 | 2014-02-18
Technical Solutions | CMS-XML

Exchange 2010 backup fails with status code 130 system error occurred

Backup fails with status 130 14:42:21.838 [12496.11760] 2 log_fs_dev_rec: INF - mnt_flag=0 14:42:21.838 [12496.11760] 2 log_fs_dev_rec: INF - fi_flag=1
TECH181190 | 2014-01-21
Technical Solutions | CMS-XML

Windows backups fail with status 130

Windows backups fail with status 130
TECH173378 | 2014-01-02
Technical Solutions | CMS-XML

Extended status = 130:1:VSS volume was not prepared for snap.

Unable to backup Exchange 2010 Databases Status 130
TECH174489 | 2013-11-27
Technical Solutions | CMS-XML

Backup of Microsoft Exchange 2007/2010 backup fails with an error "snapshot creation failed, status 130"

Backup of Microsoft Exchange 2007/2010 backup fails with an error "snapshot creation failed, status 130 "
TECH191596 | 2013-11-12
Technical Solutions | CMS-XML

NetBackup Exchange 2013 snapshots will fail, reporting status code 130, if any database is dismounted.

Exchange 2013 snapshot will fail with status 130 (system error occured ) reported if any of the databases are dismounted.
TECH209272 | 2013-10-30
Technical Solutions | CMS-XML

Exchange snapshot backup completes with a status code 130

If so, ensure no backups are occurring and delete all of those files. When logging is turned on, this folder does not clear out. Delete the files to ensure the folder is not full and causing our status 130 because it has no room to add the new files for the backup.
TECH191343 | 2013-10-29
Technical Solutions | CMS-XML

BUG REPORT: SAP backups on Linux exit with status 130.

BUG REPORT: SAP backups on Linux exit with status 130 .
TECH53930 | 2013-10-24
Technical Solutions | CMS-XML

How to disable circular logging in Microsoft Exchange 2003/2007/2010 to avoid a differential or incremental backup failure with error "snapshot preparation failed, status 130".

How to disable circular logging in Microsoft Exchange 2003/2007/2010 to avoid a differential or incremental backup failure with error "snapshot preparation failed, status 130 ".
TECH192178 | 2013-10-26
Technical Solutions | CMS-XML

Status code: 130 "Backup image size limit has been exceeded"

1/31/2005 6:24:11 AM server_name Critical Backup from client client_name: FTL - Backup image size limit has been exceeded. 1/31/2005 6:24:16 AM server_name Error Backup backup of client client_name exited with status 130 (system error occurred) Resolution:
TECH17988 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE 13 or 130: Lotus Notes backups running on Linux fail with either a NetBackup Status Code 130 (system error occurred) or a NetBackup Status Code 13 (file read failed).

130
TECH48782 | 2013-10-23
Technical Solutions | CMS-XML

Status code 130 when attempting to backup through the passive node an exchange 2007 CCR cluster

hkey_local_machine\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Enable Remote Streaming Backup (DWORD) set to 1 (This is true for any Exchange 2007 cluster configuration with Exchange SP1). Ensure that all nodes of the cluster have the Enable Remote Streaming Backup set to a value of 1. A status 130 may result if the above value is not set.
TECH62589 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?