Computer network server backup with posted write cache disk controllers

Claim 2

A storage system controller for use with a computer and a mass storage subsystem, the storage system controller comprising: a microcontroller for executing code; microcontroller executable code that when executed by said microcontroller determines whether the mass storage subsystem has been written to since a most recent writing of data to the mass storage subsystem; and a posted write cache for holding data from the computer for intended storage in the mass storage subsystem, the posted write cache including cache flush logic that flushes the cache in response to said microcontroller executable code determining that the mass storage subsystem has been written to.

Claim 3

The controller of claim 1, wherein said posted write cache further includes a battery backed-up variable indicating the number of mass storage subsystem updates since reset, wherein the mass storage subsystem includes a value indicating the number of updates since reset, and wherein said microcontroller executable code further comprises: reading code that when executed reads from the mass storage subsystem said storage subsystem number of updates since reset; and comparison code that when executed compares the battery backed-up variable with the number of updates since reset with the storage subsystem number of updates since reset, and if the battery backed-up variable is less, determines that the mass storage subsystem has been written to since the most recent writing of data to the mass storage subsystem.

Claim 4

The controller of claim 2, wherein said reading code reads from redundant information sectors (RIS) of the mass storage subsystem.

Claim 5

The controller of claim 2, wherein said reading code reads from redundant array of inexpensive disks (RAID) of the mass storage subsystem.

Claim 8

The system of claim 5, wherein said first server further includes a battery backed-up variable indicating the number of mass storage subsystem updates since reset, wherein the mass storage subsystem includes a value indicating the number of updates since reset, and wherein said microcontroller executable code further comprises. reading code that when executed reads from the mass storage subsystem said storage subsystem number of updates since reset; and comparison code that when executed compares the battery backed-up variable with the number of updates since reset with the storage subsystem number of updates since reset, and if the battery backed-up variable is less, determines that the mass storage subsystem has been written to since the most recent writing of data to the mass storage subsystem.

Claim 9

The system of claim 6, wherein said reading code reads from redundant information sectors (RIS) of the mass storage subsystem.

Claim 10

The system of claim 6, wherein said reading code reads from redundant array of inexpensive disks (RAID) of the mass storage subsystem.

Claim 11

The system of claim 5, wherein said mass storage subsystem includes an internal bus, a first port, and a second port, said mass storage subsystem including relays for coupling the internal bus to the second port in response to a predetermined in-band signal being received by said mass storage subsystem over the second port.

Claim 12

The system of claim 9, wherein said first server is coupled to the first port of said mass storage subsystem and provides an indication that is has failed; wherein said second server is coupled to the second port of said mass storage subsystem and to said first server; and wherein said second server provides the predetermined in-band signal to the second port upon receiving the indication that said first server has failed.

Claim 13

The system of claim 5, wherein said first server is a primary server and wherein said second server is a backup server.

Claim 14

The system of claim 5, wherein said first server is a primary server and wherein said second server is a primary server.

Claim 15

A server for use with a mass storage subsystem, the server comprising: a processor for running an operating system; a video subsystem coupled to said processor; memory coupled to said processor for storing data and code; and a storage system controller coupled to said processor and said memory, the storage system controller comprising: a microcontroller for executing code; microcontroller executable code that when executed by said microcontroller determines whether the mass storage subsystem has been written to since a most recent writing of data to the mass storage subsystem; and a posted write cache for holding data from the computer for intended storage in the mass storage subsystem, the posted write cache including cache flush logic that flushes the cache in response to said microcontroller executable code determining that the mass storage subsystem has been written to.

Claim 16

A server for use with a mass storage subsystem, the server comprising: a processor for running an operating system; a video subsystem coupled to said processor; memory coupled to said processor for storing data and code; and a storage system controller coupled to said processor and said memory, the storage system controller comprising: a microcontroller for executing code; microcontroller executable code that when executed by said microcontroller determines whether the mass storage subsystem has been written to since a most recent writing of data to the mass storage subsystem; and a posted write cache for holding data from the computer for intended storage in the mass storage subsystem, the posted write cache including cache flush logic that flushes the cache in response to said microcontroller executable code determining that the mass storage subsystem has been written to.

Claim 17

The server of claim 13, wherein said posted write cache further includes a battery backed-up variable indicating the number of mass storage subsystem updates since reset, wherein the mass storage subsystem includes a value indicating the number of updates since reset, and wherein said microcontroller executable code further comprises: reading code that when executed reads from the mass storage subsystem said storage subsystem number of updates since reset; and comparison code that when executed compares the battery backed-up variable with the number of updates since reset with the storage subsystem number of updates since reset, and if the battery backed-up variable is less, determines that the mass storage subsystem has been written to since the most recent writing of data to the mass storage subsystem.

Claim 18

The server of claim 14, wherein said reading code reads from redundant information sectors (RIS) of the mass storage subsystem.

Claim 19

The server of claim 14, wherein said reading code reads from redundant array of inexpensive disks (RAID) of the mass storage subsystem.

Claim 20

The server of claim 14, wherein said mass storage subsystem includes an internal bus, a first port, and a second port, said mass storage subsystem including relays for coupling the internal bus to the second port in response to a predetermined in-band signal being received by said mass storage subsystem over the second port.

Claim 21

A server for use with a mass storage subsystem, the server comprising: a processor for running an operating system; a Basic Input/Output System (BIOS) for handling communications involving said processor; memory coupled to said processor for storing data and code; and a storage system controller coupled to said processor and said memory, the storage system controller comprising: a microcontroller for executing code; microcontroller executable code that when executed by said microcontroller determines whether the mass storage subsystem has been written to since a most recent writing of data to the mass storage subsystem; and a posted write cache for holding data from the computer for intended storage in the mass storage subsystem the posted write cache including cache flush logic that flushes the cache in response to said microcontroller executable code determining that the mass storage subsystem has been written to.

Claim 22

A server for use with a mass storage subsystem, the server comprising: a processor for running an operating system; a Basic Input/Output System (BIOS) for handling communications involving said processor; memory coupled to said processor for storing data and code; and a storage system controller coupled to said processor and said memory, the storage system controller comprising: a microcontroller for executing code; microcontroller executable code that when executed by said microcontroller determines whether the mass storage subsystem has been written to since a most recent writing of data to the mass storage subsystem; and a posted write cache for holding data from the computer for intended storage in the mass storage subsystem the posted write cache including cache flush logic that flushes the cache in response to said microcontroller executable code determining that the mass storage subsystem has been written to.

Claim 23

The server of claim 18, wherein said posted write cache further includes a battery backed-up variable indicating the number of mass storage subsystem updates since reset, wherein the mass storage subsystem includes a value indicating the number of updates since reset, and wherein said microcontroller executable code further comprises: reading code that when executed reads from the mass storage subsystem said storage subsystem number of updates since reset; and comparison code that when executed compares the battery backed-up variable with the number of updates since reset with the storage subsystem number of updates since reset, and if the battery backed-up variable is less, determines that the mass storage subsystem has been written to since the most recent writing of data to the mass storage subsystem.

Claim 24

The server of claim 19, wherein said reading code reads from redundant information sectors (RIS) of the mass storage subsystem.

Claim 25

The server of claim 19, wherein said reading code reads from redundant array of inexpensive disks (RAID) of the mass storage subsystem.

Claim 26

The server of claim 19, wherein said mass storage subsystem includes an internal bus, a first port, and a second port, said mass storage subsystem including relays for coupling the internal bus to the second port in response to a predetermined in-band signal being received by said mass storage subsystem over the second port.