Problem

STATUS CODE 185: A "tar did not find all the files to be restored" occurs on restore.

Error
<16> tar_restore::OVReadHeader: ERR - tar file boundary error: needed=512, bpos=0, size=0

Solution
Overview: A status 185 "tar did not find all the files to be restored" occurs on restore. Troubleshooting: This error can occur when buffer tuning is performed on the UNIX media server via one of the following files: /usr/openv/netbackup/NET_BUFFER_SZ /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS The UNIX media server can sustain higher buffer settings which a Windows client might reject. Log Files: The tar log on the client will show the errors:
<2> tar_base::V_vTarMsgW: INF - TAR STARTED <4> VTCP_ReadInit: TCP - will be using 16 65536 byte buffers <16> tar_restore::OVReadHeader: ERR - tar file boundary error: needed=512, bpos=0, size=0 <2> tar_base::V_vTarMsgW: INF - TAR EXITING WITH STATUS = 5

The bptm log on the media server will show the errors.
<2> io_init: using 131072 data buffer size <2> io_set_sendbuf: setting send network buffer to 131072 bytes <2> io_init: using 128 data buffers <2> get_next_file: [3498186] received string: (42878 6130092 128 0 0 0 12 /C/temp/mac.txt) <2> get_next_file: [3498186] received string: (EXIT STATUS 0) <2> child_wait: SIGCLD: exit=174, signo=0 core=no, pid=3391614 <2> send_brm_msg: EXIT testmachine_1102129353 174 <4> mpx_read_backup: successfully restored 0 of 1 requests, read total of 128 Kbytes at 33.800 Kbytes/sec

The bpbrm log on the media server will show the errors:
<2> bpbrm handle_restore: from client testmachine: INF - TAR KEPT 0 EXISTING FILES <2> bpbrm handle_restore: from client testmachine: INF - TAR EXITING WITH STATUS = 185 - tar did not find all the files to be restored <2> bpbrm handle_restore: from client testmachine: INF - TAR PARTIALLY

RESTORED 0 FILES <2> bpbrm process_media_msg: media manager for backup id testmachine_1102129353 exited with status 174: media manager - system error occurred

Resolution: If the above mentioned buffer config files exist on the UNIX media server, create its restore counterpart: /usr/openv/netbackup/NET_BUFFER_SZ Restore Counter Part: /usr/openv/netbackup/NET_BUFFER_SZ_RESTORE /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS Restore Counter Part: /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_RESTORE In the touch file NET_BUFFER_SZ_RESTORE, input the value found in the tar log. In this example, the tar log above shows the network buffers will be 65536. In the touch file NUMBER_DATA_BUFFERS_RESTORE, input the value found in the tar log. In this example, the tar log above shows 16 as the number data buffers. After performing the restore, it is important that the touch files are removed as some clients may not be compatible with the new buffer settings.

Problem
STATUS CODE 185: Attempts to restore an Exchange database to a recovery storage group fails with a NetBackup Status Code 185 (tar did not find all the files to be restored) when there are mismatched versions of NetBackup on the master server and the Exchange server.

Error
BEDS 0xFFFFFE30

Solution

Overview: Attempts to restore an Exchange database to a recovery storage group fails with mismatched versions of NetBackup on the master server and the Exchange server. Troubleshooting: Confirm the NetBackup versions of the master server as well as the Exchange server. Log Files: Review the tar log file on the Exchange server for errors similar to the following:
BEDS 0xFFFFFE30: A communications failure has occurred BEDS 0xFFFFFE30: Unable to create object for restore

Resolution: When recovering an Exchange mailbox store to a recovery storage group (RSG), the restore fails with a NetBackup Status Code 185 (tar did not find all the files to be restored). Further review of the NetBackup environment shows the following versions of the NetBackup software installed on the following computers: NetBackup 5.1 Master Server: NetBackup 5.1 MP6 or later. Exchange Server: NetBackup 5.1 MP5 or earlier. NetBackup 6.0 Master Server: NetBackup 6.0 MP4 or later. Exchange Server: NetBackup 6.0 MP3 or earlier By upgrading the Exchange client to the same MP as the master server, the restore finishes successfully.