The "bpexpdate -deassignempty" command fails with "Could not update media list, file read failed" due to bad image headers in the NetBackup catalog.
Exact Error Message
<16> compare_list_to_fragments: unexpected return value from db_IMAGEreceive: file read failed 13
<16> check_for_empty_media: Could not update media list, file read failed
<16> bpexpdate: file read failed
<16> compare_list_to_fragments: unexpected return value from db_IMAGEreceive: file read failed 13
<16> check_for_empty_media: Could not update media list, file read failed
<16> bpexpdate: file read failed
Details:
Overview:
The bpexpdate command will check the NetBackup (tm) image database for images to expire. If a bad image header file exists, this can cause the bpdbm daemon to return a "status 13, file read failed" to the bpexpdate command. To resolve this error, the NetBackup images database needs to be checked for bad image headers.
Troubleshooting:
This Problems report may appear with messages like:
05/29/05 16:41:40 nbmaster1 - cleaning image DB
05/29/05 16:41:42 nbmaster1 - Bad image header: Unix_1114295338_INCR
05/29/05 16:41:44 nbmaster1 - Bad image header: Unix_1114295341_INCR
05/29/05 16:42:01 nbmaster1 - Bad image header: Unix_1114704580_INCR
Master Server Log Files:
The /usr/openv/netbackup/logs/admin/log.
<2> logconnections: BPDBM CONNECT FROM x.x.x.x.34611 TO x.x.x.x.13721
<16> compare_list_to_fragments: unexpected return value from db_IMAGEreceive: file read failed 13
<16> check_for_empty_media: Could not update media list, file read failed
<16> bpexpdate: file read failed
<2> bpexpdate: EXIT status = 13
The /usr/openv/netbackup/logs/bpdbm/log.
<16> db_get_image_info: fopen(D:\VERITAS\NetBackup\db\images\client\1114000000\Unix_1114704580_FULL): Permission denied (13)
<16> list_client_images: cannot get image info...client Unix_1114704580_FULL
<4> bpdbm: request complete: exit status 13 file read failed
Media Server Log Files: n/a
Client Log Files: n/a
Resolution:
The bpexpdate command will check the NetBackup image database for images to expire. If a bad image header file exists, this can cause the bpdbm daemon to return a "status 13, file read failed" to the bpexpdate command. To resolve this error, the NetBackup images database needs to be checked for bad image headers.
1. Run a consistency check of the NetBackup database. This will help find bad image header and zero byte header files.
# /usr/openv/netbackup/bin/bpdbm -consistency > /tmp/filename.txt
Note: The consistency check should be run when there are no backups or restores running. False errors will appear for any current backup since the .f files file will not be completely written until the backup completes. In a 24X7 environment, this can be run while backups are running. Special care will need to be taken to check the timestamp of any image with errors, to ensure it was not an active backup.
2. Review the output file /tmp/filename.txt that was created for any images listed with a "Bad image header" error
3. Remove the image files that correspond to the "Bad image header" errors listed in the consistency output
4. Run the bpexpdate again
The bpexpdate command will check the NetBackup (tm) image database for images to expire. If a bad image header file exists, this can cause the bpdbm daemon to return a "status 13, file read failed" to the bpexpdate command. To resolve this error, the NetBackup images database needs to be checked for bad image headers.
Troubleshooting:
This Problems report may appear with messages like:
05/29/05 16:41:40 nbmaster1 - cleaning image DB
05/29/05 16:41:42 nbmaster1 - Bad image header: Unix_1114295338_INCR
05/29/05 16:41:44 nbmaster1 - Bad image header: Unix_1114295341_INCR
05/29/05 16:42:01 nbmaster1 - Bad image header: Unix_1114704580_INCR
Master Server Log Files:
The /usr/openv/netbackup/logs/admin/log.
<2> logconnections: BPDBM CONNECT FROM x.x.x.x.34611 TO x.x.x.x.13721
<16> compare_list_to_fragments: unexpected return value from db_IMAGEreceive: file read failed 13
<16> check_for_empty_media: Could not update media list, file read failed
<16> bpexpdate: file read failed
<2> bpexpdate: EXIT status = 13
The /usr/openv/netbackup/logs/bpdbm/log.
<16> db_get_image_info: fopen(D:\VERITAS\NetBackup\db\images\client\1114000000\Unix_1114704580_FULL): Permission denied (13)
<16> list_client_images: cannot get image info...client Unix_1114704580_FULL
<4> bpdbm: request complete: exit status 13 file read failed
Media Server Log Files: n/a
Client Log Files: n/a
Resolution:
The bpexpdate command will check the NetBackup image database for images to expire. If a bad image header file exists, this can cause the bpdbm daemon to return a "status 13, file read failed" to the bpexpdate command. To resolve this error, the NetBackup images database needs to be checked for bad image headers.
1. Run a consistency check of the NetBackup database. This will help find bad image header and zero byte header files.
# /usr/openv/netbackup/bin/bpdbm -consistency > /tmp/filename.txt
Note: The consistency check should be run when there are no backups or restores running. False errors will appear for any current backup since the .f files file will not be completely written until the backup completes. In a 24X7 environment, this can be run while backups are running. Special care will need to be taken to check the timestamp of any image with errors, to ensure it was not an active backup.
2. Review the output file /tmp/filename.txt that was created for any images listed with a "Bad image header" error
3. Remove the image files that correspond to the "Bad image header" errors listed in the consistency output
4. Run the bpexpdate again
No comments:
Post a Comment