Bill and Denys,
Thanks for such a quick response. I concurr with John, it is good for you
to be back...
Chuck
----- Original Message -----
From: "Bill Lancaster" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, February 21, 2005 6:08 PM
Subject: Re: [HP3000-L] Moving from XP512 to VA71xx
Denys is right. Clonedisc (a part of our De-Frag/X product) is intended
to allow a user to do a complete copy of an ailing disk to another,
identical disk in the chain.
I've always believed that if you want to move data from one volume set
to another volume set it's easier and faster to simply back it up and
restore it.
Bill
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Denys Beauchemin
Sent: Monday, February 21, 2005 2:56 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Moving from XP512 to VA71xx
So, I went to the Lund site. I finally found CLONEDISC as a command in
their De-Frag/X Disk Manager product. "CLONEDISC allows you to perform
a
bit-by-bit copy of a failing disc drive to another disc drive of the
same or
greater size."
I don't think that is what Tim needs.
Denys
-----Original Message-----
From: Chuck Ciesinski [mailto:[log in to unmask]]
Sent: Monday, February 21, 2005 4:49 PM
To: [log in to unmask]; [log in to unmask]
Subject: Re: Re: [HP3000-L] Moving from XP512 to VA71xx
Denys and everyone,
Has anyone inquired with the folks at Lund. As I recall, they had a
product
called 'CLONEDISK' which might fit the bill for copying disc volumes. I
know
that James Reynolds published some history on that product to the -L
several
years ago.
Bill Lancaster can you address this?
Chuck Ciesinski
----- Original Message -----
From: "Denys Beauchemin" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, February 21, 2005 5:30 PM
Subject: Re: [HP3000-L] Moving from XP512 to VA71xx
> This sounds promising. Not having MPEX, I can't tell you if
everything
> would work but that is easily tested.
>
>
>
> You will need to issue the command
>
> :NEWACCT MYACCT,MGR;ONVS=VASET_01
>
>
>
> The you can create all the groups you want with:
>
>
>
> :NEWGROUP XXX;ONVS=VASET_01
>
> :NEWGROUP XXX;HOMEVS=VASET_01
>
>
>
> When the source group is empty, make sure you purge it with BOTH a
standard
> PUIRGEGROUP and then a PURGEGROUP with ONVS.
>
>
>
> Once all the groups have been copied and removed from the source
volumeset
> you can do a final PURGEACCT with ONVS=. This will remove the
structure
> from the source volumeset.
>
>
>
> However, if you do not intend to use the XP512 or you can reformat in
> another way, you may dispense with the PURGExxx ;ONVS=xxx.
>
>
>
>
>
>
>
> Denys
>
> _____
>
> From: Tim Cummings [mailto:[log in to unmask]]
> Sent: Monday, February 21, 2005 3:42 PM
> To: [log in to unmask]; Tim Cummings; [log in to unmask]
> Subject: RE: [HP3000-L] Moving from XP512 to VA71xx
>
>
>
> I'm thinking that at the least, I could do the following:
>
>
>
> create new volume set VASET_01
>
> create new groups for my existing account on the new volume set.
> (SOURCE1, DATA1,PUB1,STREAMS1 ...)
>
> Use MPEX to copy existing groups one by one to the new volume set.
(COPY
> @.SOURCE TO @.SOURCE1 ...)
>
> Purge group SOURCE.
>
> Create SOURCE group on new volume set.
>
> Use MPEX to rename files back to original group names.
> (RENAME @.SOURCE1 TO @.SOURCE)
>
>
>
> I will need to create the new groups with the same characteristics as
they
> exist today. (BUILDACCT? might be a good start)
>
>
>
> Does anyone see any holes in this theory.
>
>
>
> Tim
>
>
>
> -----Original Message-----
> From: Denys Beauchemin [mailto:[log in to unmask]]
> Sent: Monday, February 21, 2005 4:11 PM
> To: 'Tim Cummings'; [log in to unmask]; [log in to unmask]
> Subject: RE: [HP3000-L] Moving from XP512 to VA71xx
>
> I apologize for not being more explicit. Now, you cannot have
accounts
with
> the same name on a single system even if they are in separate
volumesets.
> When I mentioned issues with account nomenclature what I meant to say
was
> that if you could change the account name for the new volumeset (and
you
> could keep the all the groups the same,) you would be home free. So,
if
> your account names are hard-coded and too difficult to change, then
it's
> store/restore time.
>
>
>
> On the other hand if you could manage an account name change, the
> possibilities that open up for you are legions.
>
>
>
> Denys
>
>
> _____
>
>
> From: Tim Cummings [mailto:[log in to unmask]]
> Sent: Monday, February 21, 2005 3:04 PM
> To: [log in to unmask]; Tim Cummings; [log in to unmask]
> Subject: RE: [HP3000-L] Moving from XP512 to VA71xx
>
>
>
> Yes, these gadgets are on an N-class.
>
> Can you have 2 volume sets with the same account structures on them?
> If so, how would the copy be done?
> I would like to do the transition in a phased implementation.
>
> 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 *
* 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 *
|
