NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


Show Me
Status
Information Resources
Product(s)
Most Popular Subjects
Downloads
   

Symantec Suggests

  Next 

Long client hostname causes backup to fail with status 12 setting up shared memory

Long client hostname causes backup to fail with status 12 setting up shared memory
TECH224941 | 2014-09-25
Technical Solutions | CMS-XML

If the total length of client name and backup policy name exceeds a certain limit on Windows master servers, backups may fail with error status code 12

Detailed Status in Activity Monitor will show: 1/21/2014 6:44:02 AM - begin writing 1/21/2014 6:44:14 AM - Error bpbrm(pid=2516) db_flistsend failed: file open failed (12)
TECH214234 | 2014-01-23
Technical Solutions | CMS-XML

Any backups using a newly installed media server fail with Status Code: 12 : File open Failed

14:04:32.397 [4194386] 2 bpbrm main: client myClien EXIT STATUS = 12: file open failed 14:04:38.105 [4194386] 2 bpbrm Exit: client backup EXIT STATUS 12 : file open failed bpbkar log shows the following:
TECH145797 | 2014-01-26
Technical Solutions | CMS-XML

A master-initiated NetBackup for Lotus Notes restore with full or point-in-time recovery fails with Status Code 12

A Lotus Domino transaction log recovery may fail with status 12 if the restore of the logged Lotus Notes database was initiated from the NetBackup master server, or other remote host whose operating system is different from the client s (i.e., Unix vs. Windows), or if NetBackup is installed in different paths on either system.
TECH21193 | 2013-12-11
Technical Solutions | CMS-XML

Oracle automatic backup job fails with status 6 or status 29 after the application job fails with status 12.

Oracle automatic backup job fails with status 6 or status 29 after the application job fails with status 12 .
TECH60963 | 2013-11-07
Technical Solutions | CMS-XML

STATUS CODE: 12 "file open failed" occurs during a MS SQL or Oracle database agent backup.

2 bpcd_remote_write: couldn t open remote file /usr/openv/netbackup/logs/mssql_backup_failures/012405.rpt on client , error = 2
TECH37192 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR : Status 10 on AIX client, the bpbkar process produces "bpbkar read_and_sort_dir_entries: FTL - dir_list_rec malloc failed. Errno = 12:" messages in the log when backing up a file system that contains too many small files

GENERAL ERROR : Status 10 on AIX client, the bpbkar process produces "bpbkar read_and_sort_dir_entries: FTL - dir_list_rec malloc failed. Errno = 12:" messages in the log when backing up a file system that contains too many small files
TECH76719 | 2013-10-17
Technical Solutions | CMS-XML

GENERAL ERROR: NetBackup Exchange backups of Exchange 2000/2003 exit with Status Code 12. The <install_path>\netbackup\logs\bpbkar log shows errors that would indicate the Exchange services are not running.

GENERAL ERROR: NetBackup Exchange backups of Exchange 2000/2003 exit with Status Code 12. The &lt;install_path&gt;\netbackup\logs\bpbkar log shows errors that would indicate the Exchange services are not running.
TECH16593 | 2013-10-23
Technical Solutions | CMS-XML

Robot Error status code 12

Message: Usage error in creating child process Explanation:
HOWTO91271 | 2013-10-02
How To | CMS-XML

Device management status code 12

This error is an unexpected internal error . Stop and restart ltid
HOWTO91141 | 2013-10-02
How To | CMS-XML

Media Manager status code 12

Examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide Specify a robot type that supports the volume s media type.
HOWTO90897 | 2013-10-02
How To | CMS-XML

NetBackup status code: 12

Check the NetBackup Problems report. Try to determine the file and why the error occurred. A possible cause is a permission problem with the file.
HOWTO90441 | 2013-10-02
How To | CMS-XML

Alternate path restore of a Windows client fails with status 12: Couldn't open /usr/openv/netbackup/.rename.xxx on client MyClient, status: 2

A restore of a Windows client fails with status 12 . The Job Details show this is due to being unable to create the rename file on the destination client. Status 2 Status 12
TECH174179 | 2013-09-03
Technical Solutions | CMS-XML

VMware Backups of Linux Servers using EXT4 may fail with Status 12 (db_flistsend failed: file open failed (12))

VMware Backups of Linux Servers using EXT4 may fail with Status 12 (db_flistsend failed: file open failed ( 12 ))
TECH199924 | 2013-07-01
Technical Solutions | CMS-XML

BUG REPORT: The bptm write process may attempt to access a non existent shared memory file if job database cleanup runs longer then 5 minutes resulting in a status 12

BUG REPORT: The bptm write process may attempt to access a non existent shared memory file if job database cleanup runs longer then 5 minutes resulting in a status 12
TECH66236 | 2013-03-02
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?