# US 2004/0083245 A1 · Real time backup system

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

- Number: US 2004/0083245 A1
- Document ID: US20040083245A1
- Status: Published application
- Kind: A1
- Application number: 10/729,284
- Filed: 2003-12-04
- Published: 2004-04-29
- Earliest claimed: 1995-10-16
- Assignees: Network Specialists, Inc.
- Inventors: Donald E. Beeler JR.
- Web page: https://patentgrep.com/patent/US20040083245A1

## CPC

- G06F 11/2071: {using a plurality of controllers}
- G06F 11/2066: {Optimisation of the communication load}
- G06F 11/2082: {Data synchronisation}
- Y10S 707/99953: Recoverability
- Y10S 707/99955: Archiving or backup
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

In a computer network system, a user-defined file modification request is communicated to a primary server, which communicates the request to a secondary server. The file modification request is saved in a non-volatile storage media associated with the primary server, and the file modification request is executed and saved in a non-volatile storage media associated with the secondary server.

## Claims

### Claim 1

A real time backup system comprising:
at least one primary server having a non-volatile storage media where a file modification request for a file modification is saved;
at least one secondary server for executing said file modification request, each secondary server having a non-volatile storage media where said file modification is saved; and
a communication means for communicating said file modification request from said at least one primary server to said at least one secondary server.

### Claim 2

A method for real time backup comprising the steps of:
saving a file modification request for a file modification on at least one non-volatile storage media associated with at least one primary server;
executing said file modification request on at least one secondary server, each secondary server having a non-volatile storage media;
saving said file modification on said non-volatile storage media associated with said at least one secondary server; and
communicating said file modification request from said at least one primary server to said at least one secondary server.
