Creating a mksysb without mirroring


Creating a mksysb without mirroring

If the ability to retrun the mksysb is available, the following procedure will allow you to create a mksysb without preserving mirroring.

 To create a new image.data file, run the following command:

 mkszfile

 Change into the / directory and vi the image.data file. Enter:

cd /

vi image.data

 The following examples show an lv_data stanza of an image.data file. The first example is with mirroring, while the second example shows the edited version without mirroring. The lines that need changes are marked by --> and are boldfaced. In the second example, the changes are made to those lines.

       To view and edit the file,enter:

 vi image.data

Example 1

    lv_data:
                VOLUME_GROUP= rootvg
                LV_SOURCE_DISK_LIST= hdisk0
                LV_IDENTIFIER= 00000001113f3c62.5
                LOGICAL_VOLUME= hd2
                VG_STAT= active/complete
                TYPE= jfs
                MAX_LPS= 512
        -->  COPIES = 2
               LPs = 70
               STALE_PPs= 0
               INTER_POLICY= minimum
               INTRA_POLICY= center
               MOUNT_POINT= /usr
               MIRROR_WRITE_CONSISTENCY= on
               LV_SEPARATE_PV= yes
               PERMISSION= read/write
               LV_STATE= opened/syncd
               WRITE_VERIFY= off
               PP_SIZE= 4
               SCHED_POLICY= parallel
        --> PP = 140
              BB_POLICY= relocatable
              RELOCATABLE= yes
              UPPER_BOUND= 32
              LABEL= /usr
              MAPFILE=
              LV_MIN_LPS= 68

Example 2

 lv_data:
              VOLUME_GROUP= rootvg
               LV_SOURCE_DISK_LIST= hdisk0
               LV_IDENTIFIER= 00000001113f3c62.5
               LOGICAL_VOLUME= hd2
              VG_STAT= active/complete
              TYPE= jfs MAX_LPS= 512
       --> COPIES = 1 LPs = 70
             STALE_PPs= 0
             INTER_POLICY= minimum
             INTRA_POLICY= center
             MOUNT_POINT= /usr
             MIRROR_WRITE_CONSISTENCY= on
             LV_SEPARATE_PV= yes
             PERMISSION= read/write
             LV_STATE= opened/syncd
             WRITE_VERIFY= off
             PP_SIZE= 4
             SCHED_POLICY= parallel
      --> PP = 70
            BB_POLICY= relocatable
            RELOCATABLE= yes
            UPPER_BOUND= 32
            LABEL= /usr
            MAPFILE=
            LV_MIN_LPS= 68

In Example 2 the COPIES value has been changed to 1 and the PP value is set equal to the LPs value. Make these changes to each of the lv_data stanzas in the image.data file. Once the changes are made, save the file and exit.

Run another mksysb from the command line that will utilize your edited image.data file. mksysb /dev/rmtX (where X is the number of your tape drive)

 WARNINGS:

Do not run the mksysb in SMIT because this will update the image.data file and overwrite any changes made.

Do not run the mksysb with the -i flag because this will update the image.data file as well.

Comments

Post a Comment

Popular posts from this blog

Installing and configuring the storage agent (AIX)

The storage agent must be installed on a client system that has connections to storage resources on the SAN. Before beginning this procedure: Verify that your system meets the hardware and software requirements. Be sure that you have the information recorded in the configuration-information work sheets. Close all existing Tivoli® Storage Manager products prior to installing the storage agent. Installation will stop if an active Tivoli Storage Manager process is detected. If this occurs, close all active Tivoli Storage Manager products and retry installing the storage agent. The storage agent honors the Tivoli Storage Manager server environment variables DSMSERV_CONFIG. The instructions in this section are shown using the Software Management and Installation Tool (SMIT). You can also use the Install and Update Software Manager (installm). To reduce workload and processing time and to optimize LAN-free performance, do not install the storage agent and the Tivoli Storag...
Read more

Move a file system to another volume group

How to move FS to anotherVG UNMOUNT fs Copy the source logical volume to the desired volume group with the cplv command. For example, where myvg is the new volume group and mylv is the name of the user's logical volume, enter:        cplv -v myvg mylv This will return the name of the new logical volume, such as lv00. 2- To make a new JFS log, enter the following command, where myvg is the name of the new volume group, enter:        mklv -t jfslog  myvg 1 To make a new JFS2 log, enter:      mklv -t jfs2log  myvg 1 ** This new logical volume will need to be formatted with the logform command in order to function properly as either a JFS or JFS2 log. For example:        logform /dev/loglv00 Answer yes to destroy. 3-Change the filesystem to reference a log device that exists in the new volume group and the new logical volume with the chfs command. For example, where ...
Read more

Xclock does not work after switch to another user

suppose that user1 can run xclock and after switch to user2 xclock does not work does not matter if user1 or user2 is root you need to import the following values from user1 to user2 For KSH Shell $user1:/> xclock $user1:/>su - user2 $user2:/> xclock Error: Can't open display: $user2:/>exit  $user1:/>xauth list hostname/unix:10  MIT-MAGIC-COOKIE-1  630b2e7a7a794022834b0783b6f471fa hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69b9b3002484c4ea1e29a2ad5 hostname/unix:12  MIT-MAGIC-COOKIE-1  745ca626d4ef81101ef744589b4cfb09 $user1:/>echo $DISPLAY localhost: 11.0   (Hint : choose the matching values)  $user1:/>su - user2  $user2:/>xauth add hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69b9b3002484c4ea1e29a2ad5   $user2:/>export DISPLAY=localhost:11.0 $user2:/> xclock For CSH Shell $user2:/>xauth add hostname/unix:11  MIT-MAGIC-COOKIE-1  dbdcd6d69...
Read more