hidden:Starting and Stopping HPSS: Difference between revisions

From Lsdf
Jump to navigationJump to search
No edit summary
 
(52 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Activate/deactivate HPSS on either hpsscr04 or hpsscr05==
==Stopping the HPSS services==
1.'''Activate HPSS'''
run: /hat/core_manual/bin/hpss_activate_node.ksh
This script:
- activates hpss volume groups (see '''Miscellaneous''' for details)
- mounts hpss file systems
- sets IPs of the productive HPSS core
- starts hpss and DB2
- copies /hat/core_manual/etc/root_active_crontab over /var/spool/cron/root
2.'''Deactivate HPSS active core'''
run: /hat/core_manual/bin/hpss_deactivate_node.ksh
This script:
- stops HPSS and DB2
- umounts all HPSS file systems
- deactivates all HPSS volume groups
- takes away all HPSS productive IPs
- deletes /var/spool/cron/root
'''Please note:'''
- if you solely want to stop HPSS and DB2 but have access to HPSS file systems
please see below how only stop hpss
- if you want to set a cronjob on the active core, write it in
/hat/core_manual/etc/root_active_crontab
to be activeted at the next run of
/hat/core_manual/bin/hpss_activate_node.ksh
'''Beware:'''
''keep /hat/core_manual synchronized on both hpsscr04 and hpsscr05''


'''Stop HPSS using the hpss command line'''
==Stop/Start HPSS and DB2 on the active core without deactivating it==

1.'''Start the command line on the core server and stop all server'''
1.'''Stop all HPSS processes and DB2 in one step'''
/opt/hpss/bin/rc.hpss stop
1.1. [root@hpsstcr03 scripts]# /opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
2.'''Alternatively, stop HPSS and DB2 in more steps for a better overview'''
2.1.'''Start the command line on the core server and stop all server'''
/opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
hpssadm> server shutdown -all
hpssadm> server shutdown -all
hpssadm> server list -all
hpssadm> server list -all
List
ID Status Type Subtype Subsystem Op State Server Name Host Execute Host UUID
0 Connected SSMSM Enabled SSM System Manager hpsstcr03.lsdf.kit.edu hpsstcr03 264216ec-0752-11e4-9b61-40f2e9724ad2
1 Connected SUD Enabled Startup Daemon (hpsstcr03) hpsstcr03.lsdf.kit.edu hpsstcr03 58cea534-0767-11e4-8c5a-40f2e9724ad2
hpssadm> quit
hpssadm> quit
1.2.'''Stop startup daemon'''
2.2.'''Stop startup daemon'''
root@hpsstcr03 scripts]# /opt/hpss/bin/rc.hpss -d stop
/opt/hpss/bin/rc.hpss -d stop
1.3.'''Stop system manager'''
2.3.'''Stop system manager'''
root@hpsstcr03 scripts]# /opt/hpss/bin/rc.hpss -m stop
/opt/hpss/bin/rc.hpss -m stop
2.'''Stop the database'''
2.4.'''Stop DB2'''
2.1.[root@hpsstcr03 scripts]# /opt/hpss/bin/rc.hpss stop
2.5.'''Stop DB2 using rc.hpss:'''
/opt/hpss/bin/rc.hpss stop
SQL1064N DB2STOP processing was successful.
'''Please note:'''

rc.hpss will try to stop all hpss processes

rc.hpss will find all hpss processes stopped (had been stopped in step 2.3)
'''Start HPSS and the database'''
rc.hpss will only stop DB2
'''as user root on the core server'''
'''DB2 can also be stopped using DB2 manager'''

su - hpssdb
db2stop
exit
3. '''Start HPSS and DB2'''
'''as user root on the core server'''
rc.hpss starts all hpss processes and DB2 as well
/opt/hpss/bin/rc.hpss start
/opt/hpss/bin/rc.hpss start
'''check if all servers are running'''
'''start hpss admin tool'''
/opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
/opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
'''check if all servers are running'''
hpssadm>server start -all
hpssadm>server list -all
hpssadm>server list -all
''a list of servers will be showed please note:''
Execute flag not set (SSM_ESTART_NO_EXEC) (Server = STK_02 PVR) (server 18)
''"status: connected" and "op state: enabled"''
Servers
'''close hpss admin tool'''
Time Created by System Manager Aug 4, 2016 1:51:33 PM
Time Updated by System Manager Aug 24, 2016 5:13:02 PM
Time Received by Client Aug 24, 2016 5:13:04 PM
List
ID Status Type Subtype Subsystem Op State Server Name Host Execute Host UUID
0 Connected SSMSM Enabled SSM System Manager hpsscr.lsdf.kit.edu hpsscr d05ca280-bef7-11e3-a434-40f2e9722522
1 Connected SUD Enabled Startup Daemon (hpsscr) hpsscr.lsdf.kit.edu hpsscr ec6ae47e-bf19-11e3-9061-40f2e9722522
2 Connected LS Enabled Location Server hpsscr.lsdf.kit.edu hpsscr 0e9dbfd0-bf1a-11e3-9061-40f2e9722522
3 Connected CORE Subsystem #1 Enabled Core Server hpsscr.lsdf.kit.edu hpsscr 1f000e32-bf1a-11e3-9061-40f2e9722522
4 Connected LOGD Enabled Log Daemon hpsscr.lsdf.kit.edu hpsscr 6f338618-bf1a-11e3-9061-40f2e9722522
5 Connected LOGC Enabled Log Client (hpsscr) hpsscr.lsdf.kit.edu hpsscr d9358ed0-bf1a-11e3-9061-40f2e9722522
6 Connected MPS Subsystem #1 Enabled Migration/Purge Server hpsscr.lsdf.kit.edu hpsscr 5c228a3c-bf1b-11e3-9061-40f2e9722522
7 Connected PVL Enabled PVL hpsscr.lsdf.kit.edu hpsscr b668344c-bf1b-11e3-9061-40f2e9722522
8 Connected PVR STK Enabled STK_01_GridKa hpsscr.lsdf.kit.edu hpsscr b6a93d86-29a2-11e6-832b-40f2e9722522
9 Connected PVR STK Enabled STK_01 PVR hpsscr.lsdf.kit.edu hpsscr b6eb3b56-bf1d-11e3-9061-40f2e9722522
10 Connected MOVER Enabled Mover Tape MVR01 hpsscr.lsdf.kit.edu hpsscr 2f1588ce-bf1f-11e3-9061-40f2e9722522
11 Connected MOVER Enabled Mover Disk MVR01 hpsscr.lsdf.kit.edu hpsscr a0b80d36-bf1e-11e3-9061-40f2e9722522
12 Connected MOVER Enabled Mover Disk MVR02 hpsscr.lsdf.kit.edu hpsscr c9a13cf0-bf22-11e3-9061-40f2e9722522
13 Connected MOVER Enabled Mover Tape MVR02 hpsscr.lsdf.kit.edu hpsscr ec39acc0-bf22-11e3-9061-40f2e9722522
14 Connected MOVER Enabled Mover Disk MVR03 hpsscr.lsdf.kit.edu hpsscr 05b92c52-bf23-11e3-9061-40f2e9722522
15 Connected MOVER Enabled Mover Tape MVR03 hpsscr.lsdf.kit.edu hpsscr 20bd053c-bf23-11e3-9061-40f2e9722522
16 Connected MOVER Enabled Mover Disk MVR04 hpsscr.lsdf.kit.edu hpsscr 34c9ea7c-bf23-11e3-9061-40f2e9722522
17 Connected MOVER Enabled Mover Tape MVR04 hpsscr.lsdf.kit.edu hpsscr 497424d8-bf23-11e3-9061-40f2e9722522
19 Connected MOVER Enabled Mover Disk MVR01-2 hpsscr.lsdf.kit.edu hpsscr ed3ee018-1742-11e4-9ee4-40f2e9722522
20 Connected MOVER Enabled Mover Disk MVR02-2 hpsscr.lsdf.kit.edu hpsscr b473a2c6-1744-11e4-9ee4-40f2e9722522
21 Connected MOVER Enabled Mover Disk MVR03-2 hpsscr.lsdf.kit.edu hpsscr 56fb561a-1745-11e4-9ee4-40f2e9722522
22 Connected PVR SCSI Enabled IBM_IU1_01 PVR hpsscr.lsdf.kit.edu hpsscr be446d0e-b6a8-11e4-bad8-40f2e9722522
hpssadm> quit
hpssadm> quit


==Alternatively you can stop/start HPSS servers using HPSS GUI==
In this case stopping is done in two steps.
First in the GUI all hpss servers are to be stopped and then the database is to be stopped.
1. open the HPSS GUI on the active Core-Server
/opt/hpss/bin/hpssgui.pl &
2. click on Operations --> Shutdown --> All Non-SSM Servers
3. then Operations --> Shutdown --> System Manager
4. stop DB2:
''either using rc.hpss''
/opt/hpss/bin/rc.hpss stop
''or DB2 manager''
su - hpssdb
db2stop
exit
Starting also in two steps:
''start DB2:''
su - hpssdb
db2start
exit
start HPSS GUI and start all HPSS servers


==Miscellaneous==
Stopping is done in two steps. First in the GUI all activity is to be stopped. Then run the
1.'''HPSS volumes groups:'''
''hpss_deactivate_node'' script.
''at the OS level HPSS and DB2 is using the following volume groups:''

db2_backup1_vg : used for DB2 backups
- 1 open the HPSS GUI on the active Core-Server (hpsscr)
db2_backup2_vg : also used for DB2 backups

db2_log_vg : used for storing active DB2 redologs
[root@hpsscr ~]# /opt/hpss/bin/hpssgui.pl &
db2_logarch1_vg : used for DB2 redologs archived path 1

db2_logarch2_vg : used for DB2 redologs archived path 2
- 2 click on Operations --> Shutdown --> All Non-SSM Servers
db2_logmirror_vg : used for mirrored redologs
- 3 then Operations --> Shutdown --> System Manager
hpss_tbspc1_vg : used for DB2 tablespaces

hpss_tbspc2_vg : also used for DB2 tablespaces
Then stop the daemons and database:
hpss_vg : used for HPSS specific files

'''Please note:'''
/ha/bin/hpss_deactivate_node.ksh
''DB2 active logs (redologs) cannot be backuped; they have to be actively mirrored''

'''Please also take a look at scripts in /root/software'''
==Starting the HPSS services==
'''Please use these scripts with CAUTION:'''

''they are intended to be used by a skilled administrator to manually
activate/deactivate/export/import/mount/umount hpss vg/fs''
activate_hpss_vg.sh
deactivate_hpss_vg.sh
export_hpss_vg.sh
import_hpss_vg.sh
mount_hpss_fs.sh
umount_hpss_fs.sh


Run the ''hpss_activate_node'' script, then start the processes in the GUI.


[root@hpsscr ~]# /opt/hpss/bin/hpssgui.pl &
/ha/bin/hpss_activate_node.ksh


----[[ hidden:HPSS|<small>back to HPPS main page</small>]]
----[[ hidden:HPSS|<small>back to HPPS main page</small>]]

Latest revision as of 17:30, 27 May 2021

Activate/deactivate HPSS on either hpsscr04 or hpsscr05

1.Activate HPSS 
run: /hat/core_manual/bin/hpss_activate_node.ksh
This script:
- activates hpss volume groups (see Miscellaneous for details)
- mounts hpss file systems
- sets IPs of the productive HPSS core
- starts hpss and DB2
- copies /hat/core_manual/etc/root_active_crontab over /var/spool/cron/root
2.Deactivate HPSS active core 
run: /hat/core_manual/bin/hpss_deactivate_node.ksh
This script:
- stops HPSS and DB2
- umounts all HPSS file systems
- deactivates all HPSS volume groups
- takes away all HPSS productive IPs
- deletes /var/spool/cron/root

Please note:
- if you solely want to stop HPSS and DB2 but have access to HPSS file systems
please see below how only stop hpss
- if you want to set a cronjob on the active core, write it in 
/hat/core_manual/etc/root_active_crontab
to be activeted at the next run of 
/hat/core_manual/bin/hpss_activate_node.ksh
Beware:
keep /hat/core_manual synchronized on both hpsscr04 and hpsscr05

Stop/Start HPSS and DB2 on the active core without deactivating it

1.Stop all HPSS processes and DB2 in one step
/opt/hpss/bin/rc.hpss stop

2.Alternatively, stop HPSS and DB2 in more steps for a better overview 

2.1.Start the command line on the core server and stop all server 
/opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
hpssadm> server shutdown -all
hpssadm> server list -all  
hpssadm> quit
2.2.Stop startup daemon
/opt/hpss/bin/rc.hpss -d stop
2.3.Stop system manager
/opt/hpss/bin/rc.hpss -m stop
2.4.Stop DB2
2.5.Stop DB2 using rc.hpss:
/opt/hpss/bin/rc.hpss stop
Please note:
rc.hpss will try to stop all hpss processes
rc.hpss will find all hpss processes stopped (had been stopped in step 2.3)
rc.hpss will only stop DB2
DB2 can also be stopped using DB2 manager
su - hpssdb
db2stop
exit
3. Start HPSS and DB2
as user root on the core server
rc.hpss starts all hpss processes and DB2 as well
/opt/hpss/bin/rc.hpss start
check if all servers are running
start hpss admin tool
/opt/hpss/bin/hpssadm.pl -U hpssssm -a /var/hpss/etc/hpss.unix.keytab
check if all servers are running
hpssadm>server list -all  
a list of servers will be showed please note:
"status: connected" and "op state: enabled"  
close hpss admin tool
hpssadm> quit

Alternatively you can stop/start HPSS servers using HPSS GUI

In this case stopping is done in two steps. 
First in the GUI all hpss servers are to be stopped and then the database is to be stopped.

1. open the HPSS GUI on the active Core-Server
/opt/hpss/bin/hpssgui.pl &
2. click on Operations --> Shutdown --> All Non-SSM Servers
3. then Operations --> Shutdown --> System Manager
4. stop DB2:
either using rc.hpss 
/opt/hpss/bin/rc.hpss stop
or DB2 manager
su - hpssdb
db2stop
exit

Starting also in two steps:
start DB2:
su - hpssdb
db2start
exit

start HPSS GUI and start all HPSS servers

Miscellaneous

1.HPSS volumes groups:
at the OS level HPSS and DB2 is using the following volume groups:
db2_backup1_vg      : used for DB2 backups
db2_backup2_vg      : also used for DB2 backups
db2_log_vg          : used for storing active DB2 redologs
db2_logarch1_vg     : used for DB2 redologs archived path 1 
db2_logarch2_vg     : used for DB2 redologs archived path 2
db2_logmirror_vg    : used for mirrored redologs
hpss_tbspc1_vg      : used for DB2 tablespaces
hpss_tbspc2_vg      : also used for DB2 tablespaces
hpss_vg             : used for HPSS specific files
Please note:
DB2 active logs (redologs) cannot be backuped; they have to be actively mirrored
Please also take a look at scripts in /root/software
Please use these scripts with CAUTION:
they are intended to be used by a skilled administrator to manually
activate/deactivate/export/import/mount/umount hpss vg/fs

activate_hpss_vg.sh
deactivate_hpss_vg.sh
export_hpss_vg.sh
import_hpss_vg.sh
mount_hpss_fs.sh
umount_hpss_fs.sh





back to HPPS main page