Real time backup system for computer users

A media identifier comprising:

• a first, media identifier module interprets what form of media a person used to perform a function;
• a second module to tell the difference between a command or a data generation identification, wherein after the data is sent through the first module, the data are sent to the second module where the commands are interpreted, and wherein if the data are identified as data that generates new data, the data are labeled in a third, data labeler module;
• wherein the data labeler labels data according to whether they have a link or not;
• if the data has a link, the data are processed as a link data;
• a fourth, link module for connecting commands with data. For example, if certain data was found using a link;
• and
• a fifth module for listing the addresses of the links that need to be used to get data.

A procedure for command vs. data generation identification, comprising:

• receiving input labels;
• interpreting media used by a user;
• representing the form of media that the data are in when the data are received into a backup server;
• if data are gesture generated, then determining if the data are related or unrelated to data generation;
• verifying text to be a command or not, including the steps of
• i) sending the text through a command verifier, and
• ii) determining if the text is a command or not;
• separating data that is a command from data that is not a command;
• if the data is a command, interpreting the data;
• and
• if the data is not a command, storing the data.

A method for handling data in a real-time back up system, comprising:

• performing a regular back up;
• and
• determining whether data should be removed or not by the following circumstances:
• how old the data are, if there are newer versions of this data, and how often the data are being used;
• wherein the only condition where a file
• cannot be removed is where another database has a link to a file that another database needs.

A method of establishing a database of programs, comprising the steps:

• listing in a first column the programs used;
• listing in a second column the names of the users for each program;
• using a third column for keeping track of the time for generation of data and changes;
• also using the third column for keeping track of data history;
• listing in a fourth column commands used to control programs;
• listing in a fifth column the operating system used to hold data;
• listing in a sixth column the devices that were used by programs;
• listing in a seventh column the sources that were used to obtain data;
• and
• using an eighth column as an index showing where data is to be stored.

A method of using a database to explain the history of user's actions, comprising the steps:

• using a first column to records the actions that are inputted to control a program, wherein each action fits under a designated class;
• showing in a second column the class in which each action is placed;
• using a third column to keep a count of how often a class is formed by similar actions;
• if the actions fall into a class, automatically withdrawing the actions from the input column;
• using a fourth column to create a tree of the order of actions that took place when a program was being used;
• and
• using a fifth column for placing an index to a file from the tree index.

A method of operating a real-time data backup system, comprising the steps:

• recording a user's actions;
• identifying the actions;
• interpreting the user actions are interpreted in a user media recognizor;
• labeling actions as commands or data generators;
• labeling commands that are related to data generation;
• storing data;
• storing links to data programs and commands that generate data;
• and
• removing data and links if predefined conditions are satisfied.

A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for operating a real-time data backup system, the method steps comprising:

• recording a user's actions;
• identifying the actions;
• interpreting the user actions are interpreted in a user media recognizor;
• labeling actions as commands or data generators;
• labeling commands that are related to data generation;
• storing data;
• storing links to data programs and commands that generate data;
• and
• removing data and links if predefined conditions are satisfied.