HP 3000 Manuals HP 3000 Manuals
Using VOLUTIL to Complete Private Volume Migration Discussed below is the method of migrating MPE V/E private volume environments using VOLUTIL command files built by DIRMIG, and the MPE/iX volume management utility VOLUTIL. The discussion below is divided into the following sections: * Customizing PVSUMARY.PUB.SYS * Performing the Migration * Demonstrating a Volume Set Migration Read and understand "Customizing PVSUMARY.PUB.SYS" before attempting to complete private volume migration. It is assumed that the reader has already used the Private Volumes Migration Menu of DIRMIG to create VOLUTIL command files.
NOTE For more information concerning the VOLUTIL utility and volume management on MPE/iX, refer to Volume Management (32650-90045).
Customizing PVSUMARY.PUB.SYS The command file PVSUMARY.PUB.SYS contains VOLUTIL commands to generate the MPE V/E private volume environment on MPE/iX. However, alphanumeric tokens are used in lieu of logical device numbers for VOLUTIL command parameters. You are responsible for editing PVSUMARY.PUB.SYS and substituting logical device numbers for the place holders in every VOLUTIL command. PVSUMARY.PUB.SYS is organized by volume sets. For every volume set contained in PVSUMARY.PUB.SYS, the pattern of VOLUTIL commands remains the same, as in the following example. _________________________________________ | | | | | . | | . | | . | | SCRATCHVOL XX1 | | NEWSET volume set name VSET1 XX1 | | SETDEFAULTSET volume set name | | . | | . | | . | | SCRATCHVOL XX2 | | NEWVOL XX2 | | . | | . | | . | | SCRATCHVOL XXn | | NEWVOL XXn | | . | | . | | . | | | | | _________________________________________ Using an EDIT/V compatible editor, edit PVSUMARY keeping the following rules in mind: * You must replace token XX1 with the logical device number of the disk drive upon which the master volume is to be mounted. This value can not be zero. * You must replace token XX2 through XXn with the logical device numbers of disk drives upon which member volumes are to be mounted. Logical device numbers in the range 1...255 are allowed. The logical device number associated with a member volume cannot be the logical device number associated with the master volume. More than one member volume can be associated with the same logical device number. * Tokens XX2 through XXn can be zero only if the those volumes will be logically initialized on the master volume. You can physically initialize these volumes with VOLUTIL's command, :INITVOL, at a later time. * Any VOLUTIL command or MPE/iX command can be modified, added, or deleted at your discretion. However, this is only recommended for those users who are intimately knowledgeable with VOLUTIL and MPE/iX's mountable volumes. * All of the above changes should be made for each volume set definition in PVSUMARY.PUB.SYS. The preceding comments identify which place holders should be replaced by logical device numbers within a particular volume set. Once you make these replacements, PVSUMARY.PUB.SYS is ready for use by VOLUTIL. Performing the Migration Once the VOLUTIL command files are ready (customized), the MPE V/E private volume environment can be migrated. The process is broken into three main steps: * Prepare to Migrate Private Volumes * Migrate Private Volumes with VOLUTIL * Verify the Migration Read "Performing the Migration" entirely before proceeding. Once the process is well understood, follow the steps described in "Prepare to Migrate Private Volumes" and continue through "Verify the Migration". These steps may be repeated as necessary. Prepare to Migrate Private Volumes. During the migration, it is recommended that you perform the migration on the physical Console. If this is not possible, perform the migration at a logical Console where the physical Console is in sight, as volume mount and dismount messages are posted to the physical Console (even if the logical Console has been relocated). Below are the necessary steps to take to prepare for private volume migration: 1. Enter the command :SHOWVAR HPTIMEOUT If the HPTIMEOUT value is less than 15 minutes but greater than 0, issue the MPE/iX command, :SETVAR HPTIMEOUT 15. This will set the Command Interpreter read timeout value to 15 minutes. If the :SETVAR fails, use SYSGEN to configure the maximum Command Interpreter read timeout value to at least 15. Reboot the system. A value of 0 indicates that there is no read timeout in effect and no HPTIMEOUT changes are necessary. The 15-minute timeout is the approximate time to place HP 7933/35 disk drives online and offline. The command files built by DIRMIG use the 15-minute timer to wait for the Operator to place the volumes online and offline. 2. Identify those disk packs that will be used for the migration. The volumes should be new or unused. Don't use a volume if it is suspected that it is used for something else (for example, a system pack). 3. Mount the available volume media into the disk drives. Messages of the following type are posted to the Console: LONER VOLUME MOUNTED ON LDEV 4. (AVR 11) or, UNKNOWN VOLUME MOUNTED ON LDEV 14. (AVR 9) _________________________________________________________________ NOTE Do not proceed to the next step until the system posts AVR messages to the Console for each volume media mounted. _________________________________________________________________ 4. Enter the command :DSTAT ALL The status for each of the newly mounted volumes should be one of the following: UNKNOWN, SCRATCH, or LONER. If the status is MASTER or MEMBER, enter the MPE/iX command :VSCLOSE for each unique volume set definition associated with the logical device. :VSCLOSE closes the volume sets, and the volumes' status will become LONER. The DIRMIG command files will fail if the status is not UNKNOWN, LONER, or SCRATCH. 5. Verify the command files to be used by VOLUTIL. Ensure that the following is correct, and modify the file if necessary: * The member and class information * The logical device numbers * The accounting structure that will be built Migrate Private Volumes with VOLUTIL. Below are the necessary steps you take to migrate private volumes with the MPE iX VOLUTIL utility: Enter the command :RUN VOLUTIL.PUB.SYS VOLUTIL drives the private volume migration. The VOLUTIL utility is command driven and provides a HELP facility. You may enter commands by hand to configure volume sets, however, the command files built by DIRMIG may be input to VOLUTIL to migrate specific volume set environments.
NOTE Some of the actions described below are timed by the CI variable HPTIMEOUT to allow dismounting and mounting of volume media. Follow each directive in a timely fashion. If the media is not mounted by the time VOLUTIL continues, VOLUTIL will wait until the appropriate volumes are mounted.
Below is the procedure for using the command files. Read all the :COMMENT messages posted to the Console. The input is entered in response to VOLUTIL prompts: 1. USE cmdfile Enter the name of the VOLUTIL script file, cmdfile, via the VOLUTIL USE command. cmdfile may either be the user-modified copy of PVSUMARY.PUB.SYS, or one of the individual command files for a specific volume set. 2. Enter Y or YES in response to any SCRATCHVOL prompts of the following: SCRATCH VOLUME ON LDEV (Y/N)? An error may occur if the volume is not a LONER volume, however the error will not effect the subsequent NEWSET or NEWVOL commands from executing. The SCRATCHVOL command is included since any type of volume may be mounted. 3. Enter Y or YES in response to any CONTINUE OPERATION message of the following: VOLUME ON LDEV n IS A LONER VOLUME. CONTINUE WITH TRANSACTION (Y/N)? CONTINUE WITH DISC INITIALIZATION ON LDEV (Y/N)? 4. Press Return in response to an INPUT command. If the user is requested to dismount and subsequently mount another volume, the user should do so in a timely fashion and press Return , ONLY after an AVR message is posted to the Console after a volume is mounted. If Return is pressed prematurely, then VOLUTIL will wait until the volume is mounted, and then prompt the user for a response. Respond as necessary. * Continue responding and mounting/dismounting separate disk packs into the specified disk drives as directed by VOLUTIL. * After the volume set information is migrated to the new volumes, accounts and groups will be built on the volume set. Verify the Migration. Several commands are used to verify the proper migration: * Run the VOLUTIL utility by entering the command :RUN VOLUTIL.PUB.SYS. Use the VOLUTIL command, :SHOWSET. The output should indicate the results of the most currently migrated volume set. * Use the MPE/iX :LISTACCT command with the ONVS keyword to verify the span of acctname to vsetname. Enter: :LISTACCT acctname ; ONVS=vsetname * Use the MPE/iX :LISTGROUP command with the ONVS keyword to verify the span of groups and accounts to vsetname. Enter: :LISTGROUP grpname [acctname] ; ONVS=vsetname At least the master of each volume set must be mounted and on-line before these commands can be used to verify the success of the private volume migration. Demonstrating a Volume Set Migration The following sections illustrate the migration of a volume set with a volume set command file created by DIRMIG. The discussion is divided into two parts: * Creating the Volume Set Command File * Using a Volume Set Command File with VOLUTIL Creating the Volume Set Command File. The following screens illustrate a DIRMIG execution to create a volume set command file named VSET1CMD. It is assumed that the file PVASSIST.PUB.SYS exists from a previous execution of DIRMIG. __________________________________________________________________________ | | | | | CTRL A | | =LOGOFF #S1222 | | :RUN DIRMIG.PUB.SYS | | | | ============================================================ | | DIRMIG.PUB.SYS HP30362A.00.00 (c) HEWLETT PACKARD CO.,1986. | | MPE/iX Migration Utility. MON, MAR 23, 1987, 4:44 PM | | ============================================================ | | Current Log File: DIRLOG01.PUB.SYS. | | | | CHOOSE FROM MIGRATION OPTIONS BELOW: | | | | 0 - EXIT | | 1 - HELP | | 2 - COMPLETE MIGRATION (No Dialog) | | 3 - COMPLETE MIGRATION (With Dialog) | | 4 - RINS | | 5 - USER LOGGING ID'S | | 6 - DIRECTORY | | 7 - PRIVATE VOLUME ENVIRONMENT | | | | ENTER MIGRATION OPTION(S) | | >> 7 | | | | PRIVATE VOLUME MIGRATION | | ------------------------ | | CHOOSE FROM PRIVATE VOLUME OPTIONS BELOW: | | | | 0 - EXIT/(No Volume Set Migration) | | 1 - HELP | | 2 - LIST VOLUME SETS | | 3 - VISIT VOLUME SETS/ (Specified Accounts) | | 4 - GENERATE PVSUMARY COMMAND FILE/ (Specified Accounts) | | | | ENTER PRIVATE VOLUME OPTION | | >> 3 | | | | | __________________________________________________________________________ _______________________________________________________________________________ | | | | | ENTER ACCOUNT SUBSETS | | >> PVACCT1 | | ========= BEGINNING PRIVATE VOLUME MIGRATION =============== | | | | VOLUME SET MIGRATION FOR VSET1.PVGROUP1.PVACCT1. | | | | CHOOSE VOLUME SET OPTION BELOW: | | | | 0 - EXIT/(No Volume Set Migration) | | 1 - HELP | | 2 - LIST VOLUME SET DEFINITION | | 3 - GENERATE A COMMAND FILE | | 4 - DELETE VOLUME SET DEFINITION | | 5 - NEXT VOLUME SET DEFINITION | | | | ENTER VOLUME SET OPTION | | >> 3 | | | | ENTER COMMAND FILE NAME | | >> VSETICMD | | | | ENTER LOGICAL DEVICE NUMBER FOR INITIALIZING MASTER VSET1 | | >> 3 | | | | ENTER LOGICAL DEVICE NUMBER FOR INITIALIZING MEMBER MEMBER2 | | >> 4 | | | | ENTER LOGICAL DEVICE NUMBER FOR INITIALIZING MEMBER MEMBER3 | | >> 4 | | | | ENTER LOGICAL DEVICE NUMBER FOR INITIALIZING MEMBER MEMBER4 | | >> 4 | | | | SPAN PVGROUP2.PVACCT2 TO VOLUME SET VSET1.PVGROUP1.PVACCT1 (YES/[NO])? | | >> YES | | | | SPAN PVGROUP1.PVACCT2 TO VOLUME SET VSET1.PVGROUP1.PVACCT1 (YES/[NO])? | | >> YES | | | | GENERATING COMMAND FILE VSET1CMD.PUB.SYS... | | | | COMMAND FILE VSET1CMD.PUB.SYS SAVED. | | | | VOLUME SET MIGRATION FOR VSET1.PVGROUP1.PVACCT1. | | | _______________________________________________________________________________ __________________________________________________________________________ | | | | | CHOOSE VOLUME SET OPTION BELOW: | | | | 0 - EXIT/(No Volume Set Migration) | | 1 - HELP | | 2 - LIST VOLUME SET DEFINITION | | 3 - GENERATE A COMMAND FILE | | 4 - DELETE VOLUME SET DEFINITION | | 5 - NEXT VOLUME SET DEFINITION ENTER VOLUME SET OPTION | | >> 0 | | NO MORE VOLUME SETS TO PROCESS. | | =========== END OF PRIVATE VOLUME MIGRATION ================ | | | | PRIVATE VOLUME MIGRATION | | ------------------------ | | CHOOSE FROM PRIVATE VOLUME OPTIONS BELOW: | | | | 0 - EXIT/(No Volume Set Migration) | | 1 - HELP | | 2 - LIST VOLUME SETS | | 3 - VISIT VOLUME SETS/ (Specified Accounts) | | 4 - GENERATE PVSUMARY COMMAND FILE/ (Specified Accounts) | | | | ENTER PRIVATE VOLUME OPTION | | >> 0 | | | | END OF PROGRAM | | : | | | __________________________________________________________________________ VSET1CMD is now ready for use by VOLUTIL. Using a Volume Set Command File with VOLUTIL. The following screens demonstrates how to use a volume set command file with VOLUTIL. In the example, two disk drives are configured for the private volume usage. The migration is performed on the System Console. The mount and dismount messages are shown. The following routine uses the command file VSET1CMD created in the previous routine. (PVSUMARY could also have been used.) Note these points in the following routine: * The user must issue a :VSCLOSE on VSET2.GROUP1.ACCOUNT on ldev 3 before continuing with VOLUTIL. * The error issued by :SCRATCHVOL on ldev 14 for the UNKNOWN volume does not affect the subsequent :NEWVOL command. * The user will dismount and mount two additional volumes on ldev 14 when prompted by VOLUTIL. _______________________________________________________________________________________ | | | | | :SHOWVAR HPTIMEOUT | | HPTIMEOUT = 0 | | :SETVAR HPTIMEOUT 15 | | : | | VSET2.GROUP1.ACCOUNT VOLUME MOUNTED ON LDEV 3 (AVR 7) | | UNKNOWN VOLUME MOUNTED ON LDEV 14 (AVR 9) | | :DSTAT ALL | | | | LDEV-TYPE STATUS VOLUME (VOLUME SET - GEN) | | ----------- --------- --------------------------- | | 1-079350 MASTER MEMBER1 (MPEiX_SYSTEM_VOLUME_SET) | | 2-079350 MEMBER MEMBER2 (MPEiX_SYSTEM_VOLUME_SET) | | 3-079350 MASTER VSET2 (VSET2.GROUP1.ACCOUNT) | | 14-079350 UNKNOWN | | | | :VSCLOSE VSET2.GROUP1.ACCOUNT | | :RUN VOLUTIL.PUB.SYS | | | | Volume Utility 8.30.01 (C) Hewlett-Packard Co., 1986 | | volutil:USE VSET1CMD | | | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :COMMENT MPE/iX Directory Migration Tool | | volutil: :COMMENT Command File : VSET1CMD.PUB.SYS | | volutil: :COMMENT Created On : MON, MAR 23, 1987, 4:45 PM | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :COMMENT | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :COMMENT VOLUME SET COMMANDS FOR VSET1.PVGROUP1.PVACCT1 | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: SCRATCHVOL 3 | | | | SCRATCH VOLUME ON LDEV 3 (Y/N)? Y | | | | SCRATCH VOLUME MOUNTED ON LDEV 3 (AVR 8) | | volutil: NEWSET VSET1.PVGROUP1.PVACCT1 VSET1 3 | | | | UNRECOGNIZABLE MPE/iX DISC VOLUME | | CONTINUE WITH DISC INITIALIZATION ON LDEV 3 (Y/N)? Y | | | | volutil: SETDEFAULTSET VSET1.PVGROUP1.PVACCT1 | | volutil: SCRATCHVOL 14 | | *ERROR: MOUNTED VOLUME ON LDEV IS OF WRONG TYPE (SCRATCH VOLUME). | | volutil: NEWVOL MEMBER2 14 | | VOLUME ON LDEV 14 IS UNKNOWN VOLUME. CONTINUE WITH TRANSACTION (Y/N)? Y | | | | | _______________________________________________________________________________________ ________________________________________________________________________________________ | | | | | UNRECOGNIZABLE MPE/iX DISC VOLUME | | CONTINUE WITH DISC INITIALIZATION ON LDEV 14 (Y/N)? Y | | | | volutil: :COMMENT | | volutil: :COMMENT ------------------------------------------------------------- | | volutil: :COMMENT The following sequence of commands enables the user | | volutil: :COMMENT to dismount a volume set member in order to initialize | | volutil: :COMMENT a new member on the same ldev. | | volutil: :COMMENT ------------------------------------------------------------- | | volutil: :VSCLOSE VSET1.PVGROUP1.PVACCT1 | | volutil: :COMMENT ********************************************************** | | volutil: :COMMENT * CURRENT VOLUME ON LDEV 14 MUST BE DISMOUNTED TO * | | volutil: :COMMENT * INITIALIZE VOLUME SET MEMBER MEMBER3 ON LDEV 14 . * | | volutil: :COMMENT * MOUNT VOLUME SET MEMBER TO BE INITIALIZED ON LDEV 14 .* | | volutil: :COMMENT ********************************************************** | | volutil: :INPUT HPWAITVOL,"ENTER <RETURN> WHEN VOLUME IS ON-LINE:";WAIT=900 | | | | ENTER <RETURN> WHEN VOLUME IS ON-LINE: | | DISMOUNT REQUEST FOR LDEV 14 GRANTED (AVR 12) | | LONER VOLUME MOUNTED ON LDEV 14 (AVR 11) | | | | Return | | | | volutil: :VSOPEN VSET1.PVGROUP1.PVACCT1 | | VSET1.PVGROUP1.PVACCT1 VOLUME MOUNTED ON LDEV 3 (AVR 7) | | volutil: SCRATCHVOL 14 | | SCRATCH VOLUME ON LDEV 14 (Y/N)? Y | | | | SCRATCH VOLUME MOUNTED ON LDEV 14 (AVR 8) | | volutil: NEWVOL MEMBER3 14 | | UNRECOGNIZABLE MPE/iX DISC VOLUME | | CONTINUE WITH DISC INITIALIZATION ON LDEV 14 (Y/N)? Y | | | | volutil: :COMMENT | | volutil: :COMMENT ------------------------------------------------------------- | | volutil: :COMMENT The following sequence of commands enables the user | | volutil: :COMMENT to dismount a volume set member in order to initialize | | volutil: :COMMENT a new member on the same ldev. | | volutil: :COMMENT ------------------------------------------------------------- | | volutil: :VSCLOSE VSET1.PVGROUP1.PVACCT1 | | volutil: :COMMENT ********************************************************** | | volutil: :COMMENT * CURRENT VOLUME ON LDEV 14 MUST BE DISMOUNTED TO * | | volutil: :COMMENT * INITIALIZE VOLUME SET MEMBER MEMBER4 ON LDEV 14 . * | | volutil: :COMMENT * MOUNT VOLUME SET MEMBER TO BE INITIALIZED ON LDEV 14 .* | | volutil: :COMMENT ********************************************************** | | volutil: :INPUT HPWAITVOL,"ENTER <RETURN> WHEN VOLUME IS ON-LINE:";WAIT=900 | | | | | ________________________________________________________________________________________ _______________________________________________________________________________________ | | | | | ENTER <RETURN> WHEN VOLUME IS ON-LINE: | | DISMOUNT REQUEST FOR LDEV 14 GRANTED (AVR 12) | | LONER VOLUME MOUNTED ON LDEV 14 (AVR 11) | | | | Return | | | | volutil: :VSOPEN VSET1.PVGROUP1.PVACCT1 | | VSET1.PVGROUP1.PVACCT1 VOLUME MOUNTED ON LDEV 3 (AVR 7) | | volutil: SCRATCHVOL 14 | | SCRATCH VOLUME ON LDEV 14 (Y/N)? Y | | SCRATCH VOLUME MOUNTED ON LDEV 14 (AVR 8) | | volutil: NEWVOL MEMBER4 14 | | UNRECOGNIZABLE MPE/iX DISC VOLUME | | | | CONTINUE WITH DISC INITIALIZATION ON LDEV 14 (Y/N)? Y | | | | volutil: :COMMENT | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :COMMENT CLASS INFORMATION FOR VSET1.PVGROUP1.PVACCT1. | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: NEWCLASS CLASS1 VOLUMES= (VSET1, MEMBER2, MEMBER3, MEMBER4) | | volutil: NEWCLASS CLASS2 VOLUMES= (VSET1, MEMBER2, MEMBER3, MEMBER4) | | volutil: NEWCLASS CLASS3 VOLUMES= (VSET1, MEMBER2, MEMBER3, MEMBER4) | | volutil: NEWCLASS CLASS4 VOLUMES= (VSET1, MEMBER2, MEMBER3, MEMBER4) | | volutil: NEWCLASS CLASS5 VOLUMES= (VSET1, MEMBER2, MEMBER3, MEMBER4) | | volutil: :COMMENT | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :COMMENT SPANNING INFORMATION FOR VSET1.PVGROUP1.PVACCT1. | | volutil: :COMMENT ------------------------------------------------------------ | | volutil: :NEWACCT PVACCT2,MGR; ONVS= VSET1.PVGROUP1.PVACCT1 | | volutil: :NEWGROUP PVGROUP2.PVACCT2;ONVS= VSET1.PVGROUP1.PVACCT1 | | volutil: :NEWGROUP PVGROUP1.PVACCT2;ONVS= VSET1.PVGROUP1.PVACCT1 | | volutil: EXIT | | | | END OF PROGRAM | | : | | | _______________________________________________________________________________________ Private Volume Migration Checklist Below is a checklist of the major steps of private volume migration. * Migrate private volume accounts to MPE/iX with DIRMIG.PUB.SYS. * Create PVSUMARY.PUB.SYS and/or volume set command files with DIRMIG. * Customize PVSUMARY.PUB.SYS. * Identify all necessary volume media. * Ensure that HPTIMEOUT is configured to at least 15 minutes. * Verify the VOLUTIL command files for correctness. * Run VOLUTIL.PUB.SYS and use the appropriate command files. * Label the disk packs as they are generated. * Verify the migration with VOLUTIL and :LISTxxxx commands.