Error 13 Netbackup
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing netbackup status 13 Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange netbackup file read failed(13) Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español netbackup 6.5 error 13 USA Site: Veritas Veritas PartnerNet Error status - backup error 13 file read failed. Job details show 'socket read failed: errno = 62 - Timer expired' Article:000009238 netbackup error code 13 Publish: Article URL:http://www.veritas.com/docs/000009238 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to
Netbackup Error 58
this Article Manage your Subscriptions Problem A file system backup (Standard or Windows policy) fails with Exit Status 13 Error Message The bpbrm debug log and Job Details show the following error: 15:24:07.908 [31147] <2> bpbrm mm_sig: received ready signal from media manager15:29:07.908 [31147] <16> bpbrm readline: socket read failed: errno = 62 - Timer expired15:29:30.716 [31147] <2> bpbrm Exit: client backup EXIT STATUS 13: file read failed Cause The NetBackup Backup and Restore Manager (bpbrm) has not received any progress updates from the client host in recent minutes. In the example above, after exactly 5 minutes. Which is the default CLIENT_READ_TIMEOUT as configured under the host properties of the media server; host properties > media servers > mymediaserver > Timeouts > Client Read Timeout(default: 300 seconds) Solution Some clients may experience this problem when backing up very large file systems, very active file systems, or file systems with many small seldom-changing files. In those cases, the client may spend more
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile
Netbackup Error 156
Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us netbackup error 41 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 13: netbackup error 24 Backups fail with status code 13 (file read failed) reported Article:000090900 Publish: Article URL:http://www.veritas.com/docs/000090900 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create https://www.veritas.com/support/en_US/article.000009238 a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 13: Backups fail with status code 13 (file read failed) reported Error Message bpbrm handle_backup: db_FLISTsend failed: https://www.veritas.com/support/en_US/article.000090900 file read failed (13) Solution The exact error message above indicates there may be an issue updating the images database with the backup file list information. Troubleshooting:Create the following touch file:On a Windows master server:
failed. This can also occur for Flash Backup or Advanced Client backups. Table of Contents 1 Flash Backup and the Advanced Client options. 3 1.1 Offhost backup method or Third-Party Copy Device. 3 1.2 Snapshot mount point is present but http://all-about-symantec-netbackup.blogspot.com/2015/08/status-code-13-file-read-failed.html not mounted. 3 2 Network issues. 4 3 Search. 4 1 Flash Backup and the Advanced Client options For a Status 13 encountered on a Flash Backup, or any policy backup using the Advanced Client options it is recommended to http://www.sqlserverf1.com/symantec-netbackup-status-code-13/ check the OS logs (messages or syslog). Example UNIX /var/adm/messages log showing a full snapshot partition. unix: WARNING: sn_alloccache: cach/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable. This indicates that the cache partition is not large enough. If netbackup error possible, increase the size of the cache partition. If multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them, or reschedule the entire backup to a time when the file system is less active. Status code 13 may appear in the bpbkar log file for Flash Backup and Advanced client backups and can indicate the following: 1.1 Offhost backup method or Third-Party Copy Device When using the offhost backup, the disk containing the error 13 netbackup client files must be a SCSI or Fibre Channel device. A status 13 can occur if the files to back up reside on an IDE drive as opposed to SCSI, and the offhost backup method was set to either NetBackup Media Server or Third-Party Copy Device. These two options are not supported on IDE drives. If the disk is an IDE drive, you may see the following: Example from the UNIX /usr/openv/netbackup/logs/online_util/log.
Symantec NetBackup status code 13 December 15, 2014 SQLServerF1 Leave a comment Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features. Below are some of the NetBackup status error code Status Code 13 which may be received while using the Symantec NetBackup tool. NetBackup status code: 13 Message: file read failed Explanation: A read of a file or socket failed. The possible causes include the following: ■ Anetwork communication problem that occurred on the master server, media server, or one of the clients. ■ An I/O error that occurred during a read from the file system. ■ Read of an incomplete file or a corrupt file. ■ A socket read failure caused by a network problem or a problem with the process that writes to the socket. ■ A problem specific to NetBackup Snapshot Client (see recommended actions). ■ The first EV-SQL backup after a NetBackup installation failed. See the Troubleshooting section of the NetBackup for Enterprise Vault Agent Administrator’s Guide. ■ On Windows, the file list that NetBackup generates for the snapshot copy operation does not have enough information to restore from the tar32 copy. For example, block number information is not correct because the tar32 copy is not yet created. Recommended Action: Do the following, as appropriate: ■ Check the NetBackup Problems report for clues on where andwhythe problem occurred. ■ Check that network communication works properly. See "Resolving network communication problems" in the Troubleshooting Guide. ■ For a FlashBackup client, check the /var/adm/messages log for errors like the following: Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable This error indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups use the same NetBackup status codes NetBackup status codes 46 cache, reduce the number of concurrent backups. To reduce the number, reschedule some of them or reschedule the entire backup to a time when the file system is less active. ■ For detailed troubleshooting information, create a debug log directory for the process that returned this status code. Then retry the operation and check the resulting debug log. ■ Ensure that the latest service packs for all products and components (SQL, Exchange, Notes, etc.) have been installed. ■ En