This past weekend starting Friday, we migrated our data off of an XP512 to a
VA7110.  HP came in and performed the migration.  Today was the first day we
have been up since (excluding the few hours we were up before each crash).
It appears that the channel on the VA needs the Queue length set to 10 times
the number of luns or 750 whichever is greater.  Ours was set to 45 (UNIX
setting).  Whenever we stressed the I/O, the system would slow to a snails
pace and/or crash due to this problem.  Now that this problem is solved I am
wondering if there are any other gotcha's I should be looking out for.  I've
been going through dbgenrl repairs so long I'm not even sure what day it is.
I would like to avoid any additional problems.  Has anyone else experienced
any problems using the fiber connected VA on an N-Class?

Tim

>  -----Original Message-----
> From:         Tim Cummings
> Sent: Monday, February 21, 2005 2:45 PM
> To:   HP3000-L (E-mail)
> Subject:      Moving from XP512 to VA71xx
>
>
> We are moving from an XP512 to a VA71xx.  Hp wants us to do a tape
> store/restore to move the data (19 hours to backup, restore?).
>
> If we added 2 more fiber cards to hookup the new VA,  couldn't we use
> VOLUTIL's  COPYSET or COPYVOL to move our data?
>
> Our current config looks like:
>
> MPEXL_SYSTEM_VOLUME_SET
>  drive 1  (internal mirrored drive)
>
> XP01_SET
>  drives 101/119 (all on fiber card 1)
>  drives 221/239 (all on fiber card 2)
>
> volutil: showset
>
> Volume-set name: MPEXL_SYSTEM_VOLUME_SET
> Creation date: WED, JUN 11, 2003,  8:07 PM
> Generation number: 0
> Number of volumes in set: 1
> Number of classes in set: 1
>
> volutil: showset XP01_SET
>
> Volume-set name: XP01_SET
> Creation date: TUE, JUL  8, 2003,  1:39 PM
> Generation number: 0
> Number of volumes in set: 38
> Number of classes in set: 1
>
>
> Tim Cummings
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *