ianG
16 years agoLevel 5
bpimmedia - file read failed
Hey folks,
Following an upgrade from 6.5.3.1 to 6.5.4 we're getting an error when doing bpimmedia queries:
C:\>bpimmedia -mediaid 05261S
file read failed
Now this is a frozen tape, that may or may not be blank, so initially I thought it was blank, and just returning a non-specific error... however, same command on a pooled tape:
C:\>bpimmedia -mediaid 05812S | findstr /i image
IMAGE headora008s 8 headora008s_1259374475 headora008s-sap 17 Default-Application-Backup-weekly 2 3 10 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374436 headora008s-sap 17 Default-Application-Backup-weekly 2 3 11 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374247 headora008s-sap 17 Default-Application-Backup-weekly 2 3 11 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374246 headora008s-sap 17 Default-Application-Backup-weekly 2 3 10 1290988800 0 0
IMAGE headora008s 8 headora008s_1259373855 headora008s-sap 17 Default-Application-Backup-weekly 2 3 8 1290988800 0 0
IMAGE headora008s 8 headora008s_1259370699 headora008s-sap 17 Default-Application-Backup-weekly 2 3 176 1290988800 0 0
IMAGE headora008s 8 headora008s_1259367612 headora008s-sap 17 Default-Application-Backup-weekly 2 3 86 1290988800 0 0
IMAGE headora008s 8 headora008s_1259367611 headora008s-sap 17 Default-Application-Backup-weekly 2 3 85 1290988800 0 0
file read failed
So at a bit of a loss..
Found this but no real discussion on it, so am wary - that and I've not mucked with NBCC or the db before
Following an upgrade from 6.5.3.1 to 6.5.4 we're getting an error when doing bpimmedia queries:
C:\>bpimmedia -mediaid 05261S
file read failed
Now this is a frozen tape, that may or may not be blank, so initially I thought it was blank, and just returning a non-specific error... however, same command on a pooled tape:
C:\>bpimmedia -mediaid 05812S | findstr /i image
IMAGE headora008s 8 headora008s_1259374475 headora008s-sap 17 Default-Application-Backup-weekly 2 3 10 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374436 headora008s-sap 17 Default-Application-Backup-weekly 2 3 11 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374247 headora008s-sap 17 Default-Application-Backup-weekly 2 3 11 1290988800 0 0
IMAGE headora008s 8 headora008s_1259374246 headora008s-sap 17 Default-Application-Backup-weekly 2 3 10 1290988800 0 0
IMAGE headora008s 8 headora008s_1259373855 headora008s-sap 17 Default-Application-Backup-weekly 2 3 8 1290988800 0 0
IMAGE headora008s 8 headora008s_1259370699 headora008s-sap 17 Default-Application-Backup-weekly 2 3 176 1290988800 0 0
IMAGE headora008s 8 headora008s_1259367612 headora008s-sap 17 Default-Application-Backup-weekly 2 3 86 1290988800 0 0
IMAGE headora008s 8 headora008s_1259367611 headora008s-sap 17 Default-Application-Backup-weekly 2 3 85 1290988800 0 0
file read failed
So at a bit of a loss..
Found this but no real discussion on it, so am wary - that and I've not mucked with NBCC or the db before
- bpdbm is timing out due to the size of the image database. Have a look at this TechNote: seer.entsupport.symantec.com/docs/273884.htm
Please remember to stop/start NBU afte creating/modifying DBMto file.
You do realize that bpimmedia will only query the NBU catalogs and not verify actual data on tape?
To list the actual contents on tape, you need 'media contents report' (might have to add media server hostname as well):
bpmedialist -U -mcontents -m <media_id> [-h <hostname>]
You may also want to have a look at bpverify.