STATUS CODE 249: When performing a backup of a client with NetBackup, the backup job completes with Status 249.
Problem
STATUS CODE 249: When performing a backup of a client with NetBackup, the backup job completes with Status 249.
Error Message
Master BPDBM Log -- ( Wait for client to produce and send TIR file" - 8 minutes )
23:42:01.000 [662] <2> logconnections: BPDBM ACCEPT FROM xxxxxxxxx TO yyyyyyyy.13721 fd = 9
23:42:01.051 [662] <2> ImageReadFilesFile::check_tir_state: Need to wait for tir to finish
.
.
23:50:21.233 [662] <2> ImageReadFilesFile::check_tir_state: Need to wait for tir to finish
23:50:21.233 [662] <16> ImageReadFilesFile::executeQuery: Exceeded retries waiting for image record completion
23:50:21.239 [662] <2> process_request: request complete: exit status 249 the file list is incomplete; query type: 60
Overview:
The backup of a client performed with Veritas NetBackup (tm) completes with Status 249: "The server timed out while waiting for the client to finish sending the file list, or a sequencing problem occurred." This can happen for Windows or UNIX backup jobs.
A delay can occur when backing up clients using TIR (True Image Restore) With (or without) Move Detection.
The client process does not backup what are referred to as "socket special files". It makes a note of each socket special file which it skips.
The client process passes the full list of socket special files to bpbrm on the media server - which in-turn passes the list to bpdbm.
bpbrm log example:
<2> logconnections: BPDBM CONNECT FROM xxxxxxxxxxxx TO yyyyyyy.13724
<2> db_end: Need to collect reply
<4> bpbrm main: from client appserver.domain.com: TRV - /var/mqm/ipc/FILE/@qmpersist/spipe/pmpipe is a socket special file. Skipping.
bpbkar from client
<4> bpbkar: INF - bpbkar exit normal
<4> bpbkar: INF - EXIT STATUS 0: the requested operation was successfully completed
<16> bpbkar: ERR - read server exit status = 249: the file list is incomplete
<4> bpbkar: INF - setenv FINISHED=1
The issue involves contention for the bpdbm process between bpbrm and bptm . The result of this contention is that bpdbm is processing a long request from bpbrm and the request made by bptm times out before it is fulfilled.
In the example above, a quick search through the bpbkar log shows a list of 28,662 'socket special files'. It takes bpbkar about 2 minutes to pass the list of files to bpbrm over the single established socket.
However, In the bpbrm log, it can be seen that after 5 minutes, it only transfers a list of 9,321 files to bpdbm before the timeout is exceeded and the Status 249 is generated. The bpbrm process needs to open a unique socket to bpdbm for each 'socket special file' notification. This takes significantly more time then bpbkar takes, which uses the single established socket.
SOLUTION:
The location of the FFREADtries:
Once the file has been created, values can be added to adjust the default settings. For instance 20 60 can be added to make it have 20 tries with a sleep interval of 60 seconds.
Example:
A cycling of the Master Server services may be necessary to activate the timeout threshold introduced by the FFREADtries file.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. 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. You may also refer to the English Version of this knowledge base article for up-to-date information.