From: Tom Leffingwell (tom@miami.edu)
Date: Mon Oct 27 2003 - 12:07:04 EST
I only received one response, so I'll include here. My question was
whether anyone had ever attempted to upgrade from RA3000 to an RA7000 by
simply moving the disks from enclosure to the other and reentering the
configuration. I was trying to avoid doing a vdump/vrestore type
operation.
-Tom
---------- Forwarded message ----------
Date: Thu, 23 Oct 2003 09:57:22 -0600
From: Alan Rollow - Dr. File System's Home for Wayward Inodes.
<alan@desdra.cxo.cpqcorp.net>
To: Tom Leffingwell <tom@miami.edu>
Subject: Re: RA3000/HSZ22 to RA7000/HSZ70 upgrade
It might be worth trying with a single disk (properly
backed up of course) to find out. The HSZ22, HSZ40
and HSZ50 are sufficiently similar that they have a
common fault management model (events, data structures,
etc). Since the whole HSZ family from 40 up to 80 are
closely related, the on-disk metadata may be common
enough to allow doing what you want. I wouldn't expect
that it is supported or even formally tested though.
Even if it did seem to work, I would try to migrate the
data to locally initialized disks instead of keeping it
on the moved ones.
Other choices:
o It is possible to have both storage systems connected
to the system at the same time? Then you could migrate
data with dump/restore or vdump/vrestore across a pipe.
If you're using AdvFS and have the appropriate license
you can migrate most of the data with addvol/rmvol.
o If you're using AdvFS, have the spare disks, and enough
single disk domains, you could migrate the data to
Transportable disks, move those over, and migrate the
data to HSZ70 local non-transportable disks. It may
take longer than the restore, but with addvol/rmvol
it can be done online.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:40 EDT