Problem

STATUS CODE 43: Backup jobs using the FlashBackup policy type are failing with status code 43 (unexpected message received) reported.

Error
db_FLISTsend failed: unexpected message received (43)

Solution
Overview: FlashBackups fail during the attempt to send file list information to the NetBackup database manager (bpdbm). The error is caused when the master server ran out of network buffer space. Media Server log files: The bpbrm log contains entries similar to the following:
09:28:43.453 [5696.5784] <2> logconnections: BPDBM CONNECT FROM 10.255.30.85.4671 TO 10.81.5.140.13724 09:28:44.140 [5696.5784] <2> db_end_sts: no DONE from db_getreply(): unexpected message received 09:28:44.140 [5696.5784] <16> bpbrm main: db_FLISTsend failed: unexpected message received (43) 09:28:44.328 [5696.5784] <2> set_job_details: LOG 1196436524 16 bpbrm 5696 db_FLISTsend failed: unexpected message received (43) ... 09:29:02.484 [5696.5784] <2> inform_client_of_status: INF - Server status = 43 ... 09:29:07.796 [5696.5784] <2> bpbrm Exit: client backup EXIT STATUS 43: unexpected message received

Master Server log files: The bpdbm log contains entries similar to the following:
09:30:52.448 [5972.8440] <2> bytes from socket 09:30:52.480 [5972.8440] <2> No buffer space available. 09:30:52.480 [5972.8440] <2> 09:30:52.480 [5972.8440] <2> 09:30:52.480 [5972.8440] <2> message received (43) 09:30:52.605 [5972.8440] <2> unexpected message received get_adaptable_string: read 1100362 of 6496331 get_adaptable_string: (4) network read() error: db_FLISTreceive: expected 18, got -1 db_FLISTreceive: image_db: db_FLISTreceive() failed: unexpected bpdbm: request complete: exit status 43

Resolution: Check the boot.ini on the master and verify that the /3GB switch is not used. What the /3GB

switch does is allocate 1GB of address space to the Windows operating system and 3GB of address space to user mode processes. This allows Windows to better accommodate demanding applications such as Exchange and SQL Servers. By only allowing the operating system to allocate 1GB of address space, a limit is also placed on the amount of network buffers your operating system can use. Remove the /3GB entry from your boot.ini and the "No buffer space available" error from the operating system should not reappear.