2.10.2 Create a Copy of an Image (:area e:)

1.
Open SWU Boot-Devices: System > SWU Boot-Devices
2.
In SWU Boot-Devices page: Insert second boot device "hicom_second_harddisk.img" with Insert VHD2.
Figure 33
System > SWU boot devices
3.
Confirm message (PopUp) with OK.
Afterwards the second boot device is linked successfully and ready for usage.
4.
Further steps via AMO interface (ComWin)
Initiate the second boot device :a1h61: via AMO INIT
STA-INIT:UNIT=A1,DEVNAME=A1H61;
H500: AMO INIT STARTED
H04: IT WILL BE TRIED TO WRITE UPON A NOT FORMATTED MANAGEMENT AREA
H05: MANAGEMENT AREA WRITTEN
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6E:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6F:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6G:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6H:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6I:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6J:> COMPLETED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H6K:> COMPLETED
H03: INIT FINISHED
STATUS  =  H'0000
AMO-INIT -111       HARD DISK AREA INITIALIZING            
START COMPLETED;
Verify status of boot device :a1h61: via AMO DDSM
DISPLAY-DDSM:UNIT=A1,TYPE=C,CNO=6;
H500:  AMO DDSM  STARTED
CONTROLLER: 6           
         TYPE: HD  SS-NO : <STDH6>  SIZE :  2860 MB (  45775*64KB) GRAN : 512
AREA: A  NAME     : A1H6A       STATUS    : P R E S E N T               
         AREA-SZ: 0     MB  (2    *64KB)        A-GRAN: 512  
AREA: E  NAME     : A1H6E       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :PDS:                                                  
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 450   MB  (7200 *64KB)        A-GRAN: 4096 
AREA: F  NAME     : A1H6F       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :DBDA:,:DBD:,:TMD:,:PAS:,:AMD:,:DMP:                   
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 100   MB  (1600 *64KB)        A-GRAN: 4096 
AREA: G  NAME     : A1H6G       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :CGD:                                                  
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 150   MB  (2400 *64KB)        A-GRAN: 4096 
AREA: H  NAME     : A1H6H       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :DMS:,:DSY:                                            
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 70    MB  (1120 *64KB)        A-GRAN: 4096 
AREA: I  NAME     : A1H6I       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :SCR:                                                  
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 1024  MB  (16384*64KB)        A-GRAN: 4096 
AREA: J  NAME     : A1H6J       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :GLA:                                                  
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 450   MB  (7200 *64KB)        A-GRAN: 4096 
AREA: K  NAME     : A1H6K       STATUS    : B L O C K E D  B Y  A M O   
         AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
         CONFIGURED LOGICAL NAMES:
            :DIAG:                                                 
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 616   MB  (9868 *64KB)        A-GRAN: 4096 
AMO-DDSM -111       DISK STATUS                                                 
DISPLAY COMPLETED;
Copy :area e: via AMO DDRSM
COPY-DDRSM:UNIT=A1,MASTERID=1,MASTERAR=E,SLAVEID=6,SLAVEAR=E;
H500:  AMO DDRSM STARTED
H01: WARNING: YOU ARE GOING TO OVERWRITE THE AREA/DEVICE <:A1H6E:>              
     DO YOU REALLY WANT THIS (Y/N)?
  *y
AMO-DDRSM-111       DEVICE DOUBLE RECORDING SERVER MODULE                       
COPY COMPLETED;
Now second RMX boot device "hicom_second_hardisk.img" is created and could be used for RMX startup.
5.
Unlink second boot device again in OpenScape 4000 Platform Administration.
System > SWU Boot-Devices > Take out VHD2
6.
Confirm message (PopUp) with OK.
Now, the the second boot device is unlinked successfully.
7.
Further steps on LINUX shell in case image is needed for further analysis by GVS.
•
Display existing OpenScape 4000 images (/opt/ecosrv/share/)
•
Compress existing "hicom_second_harddisk.img" using bzip2 and nice.
# nice -n 10 ionice -c 3 bzip2 -c /opt/ecosrv/share/hicom_second_harddisk.img > /tmp/hicom_second_harddisk.img.bz2
•
Transfer/copy compressed image (hicom_second_harddisk.img.bz2) via WinSCP and escalate to GVS/DEV using GVS SFTP.
NOTE:  Please delete the software images that are not needed anymore.
Platform Administration (Portal), ID: P31003-H31A0-M101-03-76A9
Copyright © Unify Software and Solutions GmbH & Co. KG 07/2020  -  All rights reserved.