UNSOLVED

missyang

updated

19 years ago

M

missyang

32 Posts

0

539

October 19th, 2007 02:00

Does anyone have successful experience of upgrading from 7.2.2 to 7.3.3

Hi,

Recently I had two upgrade cases, both are from 7.2.2 build 494 to 7.3.3 in HP-UX. After the upgrade, both have quite similar issues with media. The error messsage is like "Invalid Resource Data" and stuff. NetWorker attempted to load tapes into one or two drives for forever and couldn't succeed, so the whole backup just suspended there. When tried to check on the hardware, there was some problems with a few tape drives (either damaged or unavailable). My questions are:

1. Is it because 7.3.3 is very very sensitive to hardware issues?
2. Even there're bad drives, there're still available ones, why must 7.3.3 stick on the bad ones and try like forever (at least 12hrs in my case)?
3. Does anyone have successful experience of upgrading from 7.2.2 to 7.3.3 by far?

Thanks in advance for your help.
  • dpinink_silva

    2 Intern

    •

    724 Posts

    174

    0

    Posted October 19th, 2007 03:00

    But did all the tapes drive you find damaged are the ones where Networker was trying to save?

    Nw will put the tape in service mode if it finds problems when trying to write to tape, I/O errors and stuff, maybe this "Invalid Resource Data" is not enough to put the tape in service mode, may be some other problem.

    I used to have that error message and tape drive behaviour in 7.3.2, when removing and installing again my library (STK Silo), but it was just a matter of stoping and starting Nw until it works (bad solution, I know). So, I would assume this is something related to your library also. Have you tried to reinstall it after the upgrade and see what happens?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    174

    0

    Posted October 19th, 2007 03:00

    I do, but in my case everything works and in case something is broken it is immediately removed. If you know something is broken why do you mark it so (eg. service mode).
  • missyang

    32 Posts

    174

    0

    Posted October 21st, 2007 18:00

    I didn't re-configure the whole tape library, coz the backup system has dozens of storage nodes, it'll be a big job to do so. But if it didn't work next time, I'd just try that.

    I guess now my question is: the NW seems to know which drives are damaged and go to try them directly and then just keep trying and trying, never marking them as service mode (after trying 12 hours, it should've reached the maximum of consecutive errors I believe). How does it happen?

    Thank you all (both in this case :P) for your reply.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    174

    0

    Posted October 22nd, 2007 07:00

    The problem is that when NW gets an error state on device it won't automatically mark it in service mode, but after some time (consecutive errors I assume). I believe this is a field when engineering could work a bit more, but at the same time it is not that easy either.