###########################################################################
Fail-over and Switch-over from primary to standby on IBM Netezza System
############################################################################
1. Login to active Node.
Please run the following command as root on the active host to monitor resources status.
Make sure all disk and other hardware is ok,
crm_resource -U -r nps
crm_mon
2. Then run the following to migrate nps on the standby node host to swith all NPS services to standby host.
Before doing this ask all user to use VIP address to connect Netezza system, Otherwise they would be disconnect.
$/nzlocal/scripts/heartbeat_admin.sh --migrate
3. Wait for few minute and open another session( new active server) and run below command several time to check status.
nzstate
nzstats
crm_mon
crm_resource -U -r nps
Output of nzstate should be online.
Check log file
tail -f /nz/kit/log/sysmgr/sysmgr.log
Fail-over and Switch-over from primary to standby on IBM Netezza System
############################################################################
1. Login to active Node.
Please run the following command as root on the active host to monitor resources status.
Make sure all disk and other hardware is ok,
crm_resource -U -r nps
crm_mon
2. Then run the following to migrate nps on the standby node host to swith all NPS services to standby host.
Before doing this ask all user to use VIP address to connect Netezza system, Otherwise they would be disconnect.
$/nzlocal/scripts/heartbeat_admin.sh --migrate
3. Wait for few minute and open another session( new active server) and run below command several time to check status.
nzstate
nzstats
crm_mon
crm_resource -U -r nps
Output of nzstate should be online.
Check log file
tail -f /nz/kit/log/sysmgr/sysmgr.log
No comments:
Post a Comment