Routine O & M procedures and specifications for linux

Objective: to ensure the normal operation of the operating server on a 7x24 basis

Workflow:

1. Monitor the current connection status of the server load, web, and image servers on the nginxstatus page. nagios monitors the indicators of all items on each server .. if the light is red. indicates that the relevant server must be handled immediately when a fault occurs .. if the light is yellow. indicates that the relevant server must handle exceptions as soon as possible. if the light is green. indicates that the current service is normal.

2. view the CPU, memory, load, user logon, and network card Traffic of related servers on the CACTI page, if the value of any item is significantly different from the value at the same time last week, you need to check the system log to find out the cause.

3. We recommend that you change the password of all server users every three months.

4. Submit the server system status table every month, such as memory usage and hard disk usage.

5. Check the server hardware every three months.

6. Security Updates: major vulnerabilities are immediately tested and updated. Other vulnerabilities are updated every 1-3 months.

Troubleshooting

1. Confirm the fault

2. Inform the supervisor of the Fault Level

3. notify Customer Service and relevant departments and Release relevant announcements

4. Put forward a fault handling plan for implementation after approval by the supervisor

5. Record the handling process after each fault is handled. The format is as follows:

Fault time detected. fault details

The Troubleshooting process summarizes the Fault Causes and preventive measures.

Disaster recovery

1. Establish a Disaster Recovery Solution

2. regularly check the disaster recovery server to ensure 100% availability.

3. Conduct regular disaster recovery drills to cope with emergencies

Daily Management

1. Create management and usage documents.

2. Update relevant management documents in a timely manner.

3. Stick to the special plane concept.

4. Timely patch updates and vulnerability blocking measures