StoreEver Tape Storage
1752800 Members
5776 Online
108789 Solutions
New Discussion юеВ

Re: fbackup and DLT8000

 
Procnus
Frequent Advisor

fbackup and DLT8000

We recently had our dlt8000 drive replaced with a drive with v80 firmware. Since then the fbackup script we were running, which took 4 hours, now is taking an insane length of time. By insane I mean that after 8 hours it wasn't even half way through. The filesystems being backed up are Oracle, the command line being used is :
/usr/sbin/fbackup -0 -c /var/adm/fbackupfiles/config -f /dev/rmt/0m -i /d04 -i /d03 -v > /archive/oracle.logs/fbackup

the contents of the config file are :
blocksperrecord 128
records 64
readerprocesses 4
checkpointfreq 1024

I have checked out other post on the same subject, to no avail. Does anyone have any other suggestions?

Cheers
Steven
3 REPLIES 3
Michael Tully
Honored Contributor

Re: fbackup and DLT8000

Hi,

Check out the latest patches for your version of the OS.

For HPUX 11
PHNE_25484
PHKL_27212
PHCO_23436
PHCO_25875
PHCO_25424

11.11 (11i)
PHKL_27121
PHCO_23914

HTH
~Michael~
Anyone for a Mutiny ?
Vincent Farrugia
Honored Contributor

Re: fbackup and DLT8000

Hello,

First, make sure that your DLT8000 drive is connected to an HVD or LVD interface, not a SE interface. Recently one of our guys connected a VS80 to a SE controller, and, while it worked, the backups were taking ages to complete, since VS80 requires an LVD interface. DLT8000 can be HVD or LVD, check that from the symbol on it.

If that is all ok, check the firmware. I think the v80 firmware has issues, cuz it's not the first time that this question was asked on ITRC.

Try to backtrack the firmware to v59. All the DLT8000 drives we have have v59 firmware installed.

Get an HP engineer to do that for you, cuz if you screw the firmware downgrade, you'll have a nice dead drive.

HTH,
Vince
Tape Drives RULE!!!
Procnus
Frequent Advisor

Re: fbackup and DLT8000

Thanks for the help, but I've just found out that the drive removed was on v80 firmware. So there is no reason for this happening.

Time to do a microsoft and reboot to see if it helps :(

Cheers
Steven