Daily , Weekly and Monthly Check list and To Do Guide for the Cluster-infrastructure - NIIT Tobacco Project

Daily , Weekly and Monthly Check list and To Do Guide for the Cluster-infrastructure

Shashank Kumar Singh

Tetra Information Services

Table of Contents

[#__RefHeading__40745_1672326576 Checking for cluster-infrastructure3]

[#__RefHeading__40747_1672326576 Database Backup3]

[#__RefHeading__40749_1672326576 Run Call Procedure4]

[#__RefHeading__40751_1672326576 Ping Check for each Server4]

[#__RefHeading__40753_1672326576 Mount Windows Partition 4]

[#__RefHeading__40755_1672326576 Check Ping From remote machine4]

[#__RefHeading__40757_1672326576 Check Date and time5]

[#__RefHeading__40759_1672326576 Moniter the Cluster-infrastructure5]

[#__RefHeading__40761_1672326576 Moniter nad managing the Cluster-infrastructure via Command line7]

[#__RefHeading__40763_1672326576 Weekly task 7]

[#__RefHeading__40765_1672326576 Monthly task 7]== Checking for cluster-infrastructure == Check whether the cluster is running properly or not. For this go to

Computer >> Yast >> Pacemaker connect with username hacluster and password linux and check that all services should be running properly.[[Image:]]

1. == Database Backup ==

Chcek the database backup is run in the last night or not if not please run it manually.
Computer >> places >> file system >> root >> backup
and check the date wise backup
[[Image:]]For command line go through following steps
The output should be showing like this if the backup are not present then take backup manually through below command

[[Image:]]

Run Call Procedure

Chcek for the data call procedure process and if it is not run in night the run through given launcher or from the command line through following steps

cd /opt/scripts

./ call_tb_proc_daily_configuration.sh

Ping Check for each Server

Check that both server ping from each other and accessable from each other. For this ping from both Server to each other and make sure they are pinging to each other and accessible from each other== Mount Windows Partition == Check that windows partition is mounted on the server and if it is not mount the go through launcher or follownig steps to check mounting and mount the partition.

[[Image:]]It shows like this if it now showing any output it means the barcode printer is unmounted from the server then rum following command to mount barcode printer on the server again

[[Image:]]

Now it has been done if any error occur the please check on the windows machine if there is sharing of printer folder has been done correctly or not also check for the windows user name and password.

Check Ping From remote machine

Check ther servers and cluster are ping from local and remote machines .For this ping gate way and cluster machine from other machine.

Check Date and time

Check the date and time on each server and make sure both should be same.

Moniter the Cluster-infrastructure

For monitoring the cluster from the Local network we can use hawk web interface for this follow belo given step

Step 1: Login the hawk webinterface https://clusterip:7630 with username hacluster

and password linux[[Image:]]

Step 2: Click the table view on the right corner for easy view this would be shown like this

[[Image:]]

Now you can mange resource, services and constraints or stop, start cluster services from here

[[Image:]]

Moniter nad managing the Cluster-infrastructure via Command line

Management of Cluster through CLI:-

1:- For monitoring cluster-infrastructure

crm_mon

2:- To see the resource list

crm resource list

3:- To start a resource-only

• Log in as root and start the crm tool:
  # crm configure
• Switch to the resource level:
  crm(live)# resource
• Start the resource with start and press the →| key to show all known resources:

crm(live)resource# start start ID

4:-To cleanup resource

• Get a list of all your resources:
  # crm resource list
• Remove the resource:
  # crm resource cleanup resource [node]

if you leave node option it will be clean for all nodes.

5:- To stop a resource-only

• Get a list of all your resources:
  # crm resource list
• Stop the resource:
  # crm resource stop resourcename [node]

Where clvm is the resource name

Weekly task

1. Supportconfig Report ( Refer to Automatic Report creation document )
2. HB_Report execution ( Refer to Automatic Report creation document )

Monthly task

1. Image creation for the Systems
2. Shareing of Supportconfig Report ( Refer to Automatic Report creation document ) to all stakeholders
3. Shareing of HB_Report execution ( Refer to Automatic Report creation document ) to all Stakeholders