# US 2014/0207938 A1 · Server restart management via stability time

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0207938 A1
- Document ID: US20140207938A1
- Status: Published application
- Kind: A1
- Application number: 13/747,887
- Filed: 2013-01-23
- Published: 2014-07-24
- Earliest claimed: 2013-01-23
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Robert M. Abrams; Nicholas C. Matsakis; Daniel Nieves; Anthony T. Sofia
- Web page: https://patentgrep.com/patent/US20140207938A1

## CPC

- H04L 43/0811: by checking connectivity
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/3031: {where the computing system component is a motherboard or an expansion card}
- G06F 11/3051: {Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs (verification or detection of system hardware configuration G06F11/2247)}
- H04L 67/025: for remote control or remote monitoring of applications
- G06F 11/3409: {for performance assessment}
- G06F 11/3419: {by assessing time}
- G06F 2201/815: Virtual
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The stability and availability status of a server is determined by monitoring the stability time specification of the server. The stability time is set for the server and defined as a time between a starting state of the server and a stability point of the server. The server activity is monitored by an availability manager to determine an availability status of the server. Responsive to the server activity progressing to the stability point within the stability time, an embodiment determines that the server is stable. Responsive to the server activity failing to progress to the stability point within the stability time, an embodiment determines that the server is unreliable.

## Claims

### Claim 1

A computer-implemented method, comprising:
specifying, by a processing device, a stability time for a server, the stability time defining a time between a starting state of the server and a stability point of the server;
monitoring, by an availability manager, server activity to determine an availability status of the server;
determining that the server is stable in response to the server activity progressing to the stability point within the stability time; and
determining that the server is unreliable in response to the server activity failing to progress to the stability point within the stability time.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the server is marked as unreliable in response to the server being restarted prior to progressing to the stability point.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the availability manager prevents the server from restarting until the stability time has expired to prevent thrashing.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising an agent of the server, the agent evaluating and reporting the server activity to the availability manager.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the stability time is specified during server configuration and is based on a determination of server functionality over a historical period of time.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the availability status of the server is selected from a group comprising an available state, an exposed state, a critical state, a not available state, and an unreliable state.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the exposed state is defined as a time between an operating state of the server to the stability point of the server.

### Claim 8

A computer system, comprising:
a processor, a system memory, and a bus that couples various system components including the system memory to the processor, the system configured to perform a method comprising:
specifying, by a processing device, a stability time for a server, the stability time defining a time between a starting state of the server and a stability point of the server;
monitoring, by an availability manager, server activity to determine an availability status of the server;
determining that the server is stable in response to the server activity progressing to the stability point within the stability time; and
determining that the server is unreliable in response to the server activity failing to progress to the stability point within the stability time.

### Claim 9 (depends on 8)

The computer system of claim 8, wherein the server is marked as unreliable in response to the server being restarted prior to progressing to the stability point.

### Claim 10 (depends on 8)

The computer system of claim 8, wherein the availability manager prevents the server from restarting until the stability time has expired to prevent thrashing.

### Claim 11 (depends on 8)

The computer system of claim 8, further comprising an agent of the server, the agent evaluating and reporting the server activity to the availability manager.

### Claim 12 (depends on 8)

The computer system of claim 8, wherein the stability time is specified during server configuration and is based on a determination of server functionality over a historical period of time.

### Claim 13 (depends on 8)

The computer system of claim 8, wherein the availability status of the server is selected from a group comprising an available state, an exposed state, a critical state, a not available state, and an unreliable state.

### Claim 14 (depends on 13)

The computer system of claim 13, wherein the exposed state is defined as a time between an operating state of the server to the stability point of the server.

### Claim 15

A computer program product, comprising:
a computer readable storage medium having computer readable program code stored thereon that, when executed, performs a method, the method comprising:
specifying, by a processing device, a stability time for a server, the stability time defining a time between a starting state of the server and a stability point of the server;
monitoring, by an availability manager, server activity to determine an availability status of the server;
determining that the server is stable in response to the server activity progressing to the stability point within the stability time; and
determining that the server is unreliable in response to the server activity failing to progress to the stability point within the stability time.

### Claim 16 (depends on 15)

The computer program product of claim 15, wherein the server is marked as unreliable in response to the server being restarted prior to progressing to the stability point.

### Claim 17 (depends on 15)

The computer program product of claim 15, wherein the availability manager prevents the server from restarting until the stability time has expired to prevent thrashing.

### Claim 18 (depends on 15)

The computer program product of claim 15, further comprising an agent of the server, the agent evaluating and reporting the server activity to the availability manager.

### Claim 19 (depends on 15)

The computer program product of claim 15, wherein the stability time is specified during server configuration and is based on a determination of server functionality over a historical period of time.

### Claim 20 (depends on 15)

The computer program product of claim 15, wherein the availability status of the server is selected from a group comprising an available state, an exposed state, a critical state, a not available state, and an unreliable state.
