HP3000-L Archives

February 2005, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Walt McCullough <[log in to unmask]>
Reply To:
Walt McCullough <[log in to unmask]>
Date:
Tue, 22 Feb 2005 11:17:07 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (137 lines)
 To Tim (et al)

When we developed Volutil and the COPY set of commands (way back in the mid
80s) many
(not me) envisioned a world that didn't have removable or swappable drives
(remember the 7933 &7935) and those people were rewarded by HP and the
industry doing away with disk drives with  removable drive packs
(contamination by dust).

As usual, those commands were popular among those with older storage (much
of the 3000 base) while much of the 90s was barren of removable disk packs.

Then in the mid to late 90s, HP and others started introducing racks with
sealed disk mechs that when used as JBOD allowed for removable/swappable
media and used as raw material for the advent of storage array technology.

There was a comment made in an earlier message about FC used as a platform
to move data from one disk to another without the server being involved,
well the technology to do that existed back in the SCSI days but no one was
really interested until FC came along.

The FC messaging hit a whole new group of (naive) decision makers promising
that the move to FC automatically gave them data migration capabilities and
serverless backup (not hardly, at the time).

Now there are a number of third party companies out there that provide the
means to migrate data from array or storage technology to a new or different
one while every storage vender already has serverless copy features used to
copy from one part of the array to another part within the (same) array.

The trick is to weigh the cost of deciding whether this is a single
migration effort where money is no object and data availability is the
highest concern over the cost (and simplicity) of just doing a
STORE/RESTORE.

Walt

Walter McCullough
SR. HA&Storage Technologist
TCSD, MPE/iX R&D Lab
Hewlett-Packard Company



"Tim Cummings" <[log in to unmask]> wrote in message
news:B4Gdnd-_f_Ah0YbfRVn-sA@fidnet.com...
> I find it amazing that HP creates a utility (VOLUTIL) for one
> and only one OS (MPE) that will copy everything BUT MPE native mode
> volumes.
>
> Tim
>
> -----Original Message-----
> From: Denys Beauchemin [mailto:[log in to unmask]]
> Sent: Monday, February 21, 2005 3:57 PM
> To: 'Tim Cummings'; [log in to unmask]
> Subject: RE: [HP3000-L] Moving from XP512 to VA71xx
>
>
> That's a nice thought but I don't think you can make it work.  Beyond the
> connectivity problem, (and you did not mention what type of system these
> lovely gadgets are connected to, but I suspect some type of N-class,) the
> documentation of VOLTUTIL is quite specific.  The volumes must be in a
> non-mounted state.  The source volume must be in a LONER, SCRATCH or
UNKNOWN
> state and the target volume must be in a SCRATCH or UNKNOWN state.  This
> means you will need to somehow corrupt your volumes before trying this.
>
> The COPYSET command wants the source to be in a LONER state and the target
> to be in a SCRATCH or UNKBOWN state.
>
> All in all, it would be interesting to try, especially on a small
volumeset.
> I am not one to condone testing such things with production data.
>
> An alternative would be to create a new volumeset with the VA71xx attached
> to it and then start copying groups from one volumeset to another.  You
> could do this at the group level and take your time doing it, a phased
> implementation if you will.  You will have to deal with issues of
> nomenclature for duplicate accounts, but if you could get by those
problems,
> this could be a great way of doing things.  (Provided you have the
> connectivity above.)
>
> Denys
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
> Of Tim Cummings
> Sent: Monday, February 21, 2005 1:45 PM
> To: [log in to unmask]
> Subject: [HP3000-L] 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 *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

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

ATOM RSS1 RSS2