03-28-2021 03:27 AM
03-28-2021 04:35 AM
@mikeviennaDo you have any specific objective for this testing ? Please share it with us so that we can help you better.
You may be already knowing it but we stopped support LTO2 drives since NBU 8.0 or 773. So not really sure if 9.0 can detect it.
Have you tried updating device mapping file ? Try it if not done already and then try using different buffer settings than default.
03-28-2021 04:36 AM
03-28-2021 07:19 AM
03-29-2021 03:34 AM - edited 03-29-2021 06:39 AM
Add VERBOSE = 5 to bp.conf. Crete directory /usr/openv/netbackup/logs/bptm
Re-run backup. There should now be a de-bug log in directory create above.
Looks for lines with <4> <8> <16>. Hopefully this gives a better indication of why block size of 256 is rejected.
Update: after a bit of searching, due to age of this SCSI controller, it may lack support for 256K block size.
PS: I wish you a speedy recovery
03-30-2021 03:45 PM
I will add the VERBOSE to my bp.conf file...
As I stated that the bptm log file is writing "block size of 256k but xxK were written" I have the bptm log directory
already...Or do you mean that after adding the verbose setting I have to re-create the bptm directory ?
Right, the HBA is old, but the "newest" with an PCI-X 133Mhz slot that I can find..
Will maybe try getting a FC drive or an pci-express SCSI HBA, but my test server only has two PCI-X slots (Sun Fire X4100M2),,
Will report , maybe I can tune the driver a little bit.
Thank you very much!
03-31-2021 12:16 AM
Just add VERBOSE = 5 to bp.conf and re-run backup. No need to recreate the bptm directory.
Adding VERBOSE = 5 to bp.conf will increase the logging from bptm in the bptm debug log.