EA005000B1 - Virtual tape storage system and method - Google Patents

Abstract

1. A virtual tape storage system, comprising: at least one user terminal located at a first location for generating a list of computer files, said computer files being within a first computer memory; a remote computer having a second writable stable computer memory, said second computer memory being located at a second location that is remote from said first location; and a long distance telecommunications line connectable to said user terminal and said remote computer; said list of files being transmitted in an extensible mark-up language from said user terminal via said long distance telecommunications line to said remote computer; and at least one file listed in said list being transmitted from said first computer memory to said second computer memory for stable archiving of said at least one file for subsequent access of said at least one file by a user. 2. The system of claim 1 wherein said list of files is part of a backup set specification; said backup set specification further comprising at least one scheduled time interval corresponding to a time when source computer files listed in said list are to be stably archived. 3. The system of claim 2 further comprising: a user application operable to run on said user terminal; and a server application operable to run on said remote computer; said user application and said server application being operable to communicate over said telecommunications line; said user application being configured to transmit said list; and said server application being configured to receive said list. 4. The system of claim 3 wherein said server application is configured to prevent alteration of stably archived files. 5. The system of claim 4 wherein said telecommunications line comprises an Internet connection. 6. The system of claim 5 wherein said user application includes an interface for displaying files and directories using a tree view structure; and said list is generated using said interface. 7. The system of claim 6 wherein said user application allows specifying a size of a backup space for storing files within said second memory; and wherein a user fee is charged according to said size specified. 8. The system of claim 7 further comprising an archival memory for off-line storage of at least one file stored in said second memory. 9. The system of claim 8 wherein said interface is further configured to allow a user to select files to be restored from said second memory; and said server application being configured to restore the selected files to the first memory from said second memory. 10. The system of claim 9 wherein said server application is further configured to allow a group user in a predefined group of users to restore files associated with any user in said predefined group of users. 11. The system of claim 10 wherein said server application is further configured to transmit to said user application an index file listing files stored in said second memory; and said index file is transmitted in an extensible mark-up language. 12. The system of claim 11 wherein: said user application is configured to transmit said list; and said server application is configured to receive said list. 13. The system of claim 1 wherein said telecommunications line comprises an Internet connection. 14. The system of claim 1 further including a user application operative to run on said user terminal; said application including an interface for displaying files and directories using a tree view structure; and wherein said list is generated using said interface. 15. The system of claim 1 wherein said user terminal is configured to allow a user to specify a size of a backup space within said second memory for stable archiving of files; and wherein a user fee is charged according to said size. 16. A method for stable archiving of computer files, comprising: defining a backup set comprising: a backup list comprising at least one source computer file name corresponding to a source computer file located in a first computer memory; and at least one scheduled time interval corresponding to a time when source computer files listed in said backup list are to be stably archived; determining when said at least one scheduled time interval has occurred; transmitting said backup list across a long distance telecommunications connection to a remote computer; reading said at least one source computer file name from said backup list; locating said source computer file corresponding to said source computer file name; after said determining, reading data from said source computer file; and writing said data into a destination computer file in a second writable stable computer memory connected to said remote computer. 17. The method of claim 16 wherein said telecommunications line comprises an Internet connection. 18. The method of claim 16 wherein said defining of said backup set is done using a user application including an interface for displaying files and directories using a tree view structure. 19. The method of claim 16 further comprising specifying a size of backup space within said second memory for writing said data; and charging a user a fee according to said size specified. 20. The method of claim 16 further comprising transmitting in an extensible mark-up language to a user application an index file listing files stored in said second memory for selecting files to be restored. 21. A system for stable archiving of computer files comprising: a user terminal having a first memory; a user application operable to run on said user terminal; a remote computer having a second memory; a server application operable to run on said remote computer; a third writable stable computer memory operable to communicate with said server application, said third memory being separate from said first memory and said second memory; and a long distance telecommunication connection operable to communicate with said client application and with said server application via a telecommunications line; said client application being furthered configured to transmit to said server application a predefined list of source computer files, the source computer files being located in said first memory; said server application being operable to receive said list; said server application being further configured to read data corresponding to the contents of at least one source computer file listed in said list; said server application being further configured to write said data into said third memory. 22. The system of claim 21 wherein said telecommunications connection comprises an Internet connection. 23. The system of claim 21 wherein said user application includes an interface for displaying files and directories using a tree view structure. 24. The system of claim 21 wherein said user application is further configured to allow a user to specify a size of backup space within said second memory for writing said data. 25. The system of claim 21 wherein said server application is further configured to transmit in an extensible mark-up language to said user application an index file listing files stored in said second memory that are available to be restored. 26. A method for stable archiving of computer files, the method comprising: defining at least one user space within a first writable stable computer memory connected to a remote computer; defining at least one backup space within said user space; defining at least one backup set definition comprising a list corresponding to at least one computer file located in a second computer memory accessible by a user terminal; copying said at least one computer file listed in said backup set definition to said at least one backup space; and preventing alteration of said computer files in said at least one backup space; wherein said user terminal is remote from said first writable stable computer memory. 27. The method of claim 26 wherein said defining of said backup set definition is done using a user application including an interface for displaying files and directories using a tree view structure. 28. The method of claim 26 further comprising: specifying a size of said backup space within said second memory for writing said data; and charging a user a fee according to said size specified. 29. The method of claim 26 further comprising transmitting in an extensible mark-up language to said user terminal an index file listing files stored in said second memory for selecting files to be restored.

Description

Prior art

The present invention relates generally to a system and method for archiving files. More specifically, the invention relates to such a system and method in which a user uses a local terminal to select files to be archived at a remote location connected to the local terminal via a long-distance link connection.

Various systems are known for allowing a user to archive computer files. The so-called near memory device uses memory media directly connected to the local system, such as a second local hard drive, internal memory, or other permanently connected device. The amount of memory for storing data is directly related to the total capacity of the connected device. Thus, the user may not have enough physical memory available to support his needs. In addition, a substantial level of knowledge is required to connect such a device, its format and prepare it for general use. In addition, the cost of the storage device and the cost of its maintenance can be high.

Some so-called distant (or remote) storage systems allow the user to back up files on the other side of the network in a physical environment for an offline storage device. In such a system, access to archived data is a relatively slow process. In addition, multiple users cannot simultaneously access data.

Accordingly, there is a need for a system that would allow a user to archive large amounts of data in a secure remote location, especially a system that would allow relatively quick access to archived data and that would allow multiple users to access the same archived data . In addition, there is a need for such a system with a relatively user-friendly user interface. In the present invention, such a system is implemented.

SUMMARY OF THE INVENTION

The present invention provides a system and method for archiving files at a location remote from the terminal, which is used to select files to be archived. The remote location at least includes rewritable stable memory and a computer. The user terminal at least has access to memory from which you can select files to be archived. The terminal and the computer are connected via a long-distance line connection, such as an Internet connection. It should be noted that such features may or may not be included in a specific embodiment of the invention, which is summarized here, while the present invention is set forth in the claims.

The objective of the invention is to perform an improved method and system for archiving files.

Brief Description of the Drawings

The accompanying drawings are used to describe the present invention, in which FIG. 1 depicts a block diagram of one embodiment of the invention;

FIG. 2 is a block diagram of one embodiment of the invention;

FIG. 3 is a block diagram of one embodiment of the invention;

FIG. 3A is a more detailed view of the memory shown in FIG. 3;

FIG. 4 is an example of a computer application interface used in the present invention.

Detailed Description of Preferred Embodiments

In order to increase understanding of the principles of the present invention, reference is made to the drawings, and a specific language is used to describe them. However, it should be understood that limiting the scope of the invention in this way is not implied, and changes and modifications of the illustrated systems and methods and other applications of the principles of the invention depicted in it are obvious to those skilled in the art.

In FIG. 1 is a block diagram of a virtual tape drive system 100 according to the present invention. The user terminal 102 allows the user to select stably archived files. Terminal 102 is connected via a long-distance link 109 to a remote computer 110. Computer 110 is connected to a memory 112 for stable file archiving. Computer 110 is further connected to memory 130 for storing stably archived files. In addition, the computer 110 is additionally connected to the archive memory 140 for copying files that have been stably archived in the memory 112.

Terminal 102 may be any type of computer processing device that allows you to connect to a long-distance line, including, but not limited to, personal computers, diskless workstations, devices that have access to a worldwide network (personal or smart television remotes, personal information devices (ΡΌΑ) or the like. Connection 109 may have any kind of long-distance communication line. A long-distance communication line or communication line refers to a non-local communication connection, including but not limited to, a modem or other automatic connection, an Internet connection or a wireless connection suitable for maintaining communication with ΡΌΑ, such as the Omni Sky service (from 8k). A line refers to such a connection in any form, whether present or not direct physical connection Thus, the communication line may include intermediate switching devices, satellite communication lines, wired or wireless radio relay lines and / or relays, and the like.

In operation, the system 100 allows the user to select files that need to be stably archived in the memory 112. Files are selected using the user in the user terminal 102. Files can be selected from any memory to which the terminal 102 has access. For example, depending on the shape of the selected terminal 102, files can be selected from local memory, such as a hard disk drive, memory of a local network, such as a hard disk drive, accessed through a local network, or memory, such as memory 130 accessed through computer 110 via connection 109. The user also selects one or more time periods when files need to be archived. Alternatively, you can use an event interval (rather than a time interval) corresponding, for example, to an event, such as a change or access to a file.

According to a further description of the operation of the system 100, upon the occurrence of a pre-selected time interval (or event) (for example, hourly, daily, weekly, monthly, annual or other), the terminal 102 starts the process of stable archiving of files that the user has previously selected for archiving. Alternatively, the user can start the archiving process manually at any time. Terminal 102 sends a list of files to remote computer 110 via connection 109. For each file, computer 110 receives data corresponding to the contents of the file. If computer 110 has access to the file through terminal 102 (for example, to a file located in a memory locally connected to terminal 102), then computer 110 instructs terminal 102 to access the file and transfer its contents via connection 109. If computer 110 has direct access to the file (for example, to a file located in the memory 130), then the computer 110 reads the contents of the file. After receiving data for the file, computer 110 creates the file in rewritable stable memory 112. Computer 110 repeats the above steps until all files are stably archived. Files stably archived in memory 112 can be further backed up in separate archive memory 140 for offline storage.

After the files are archived, the user can then restore any or all of the archived files. When the user needs to perform a restore operation, the terminal 102 sends a request to the computer 110 to obtain a list of archived files. Terminal 102 then provides the user with a listing of the archived files. The user selects which files to restore. Terminal 102 sends a request for each file that needs to be restored in computer 110. Computer 110 then restores the contents of each file that needs to be restored from rewritable stable memory 112. Computer 110 then restores the files to their original location, for example, a memory location from which they were originally read for archiving. In the case of memory to which computer 110 has direct access (e.g., memory 130), files are directly restored. In the case of storage devices that are accessed via connection 109 (for example, a hard disk drive connected to terminal 102), the contents of the file are transferred to terminal 102 from which the files are recovered.

The original location used in this application refers to a location associated with a specific memory that is accessed by any computer system having access to that memory. In many computer systems, computer memory is accessed using a designation consisting of a single alphanumeric character, for example, drive C. However, this designation may change, for example, if other storage devices are added or removed from the computer system. In addition, the physical storage medium itself may change in the case of removable media such as removable hard drives, disks with a capacity of 100 megabytes or more (ΖΙΡ-disks) or the like. Thus, it should be noted that the initial location means what the system is accessing, and usually the application software (for example, word processing, spreadsheet, database or other) that directly accesses the memory. Therefore, the original location refers to a logical location, not a physical location. Although in some cases, the logical and physical location may coincide.

Used in this application, the terms memory or computer memory refers to any non-paper media readable electronically by a machine that allows you to store computer data, including but not limited to, hard disks, hard disk arrays, ΖΙΡ-disks, floppy disks, CDs and the like. Archive memory refers to any memory having a storage medium that is designed so that it can be physically removed from a computer system, or any storage media in a system that is not intended for online user access, including (but not limited to) computer tapes, CDs, hard drives, and the like. Thus, for example, the memory on a computer’s hard disk or a network of computers is archived if the user does not access the files directly, but rather has access to the files after they have been copied to other memory, such as memory 112. Stable archiving refers to storing data in non-volatile computer memory, and non-volatile computer memory refers to computer memory, which does not require external power in order to save any data contained in it. Stable memory or rewritable stable memory refers to non-volatile computer memory into which data can be recorded at least once.

In FIG. 2 shows a block diagram of a virtual tape drive system 200 according to the present invention. System 200 is similar to system 100 (FIG. 1), but may include various additional features. The user terminal 202 allows the user to create a backup set specification 204 that includes a list of files that need to be stably archived. Terminal 202 is additionally connected to memory 206 to save files that need to be stably archived. Terminal 202 is also additionally connected via an additional network connection 207 to memory 208 to save files that need to be stably archived. Terminal 202 is connected through a telecommunication connection 209 to a remote computer 210, which typically has standard RAM (CAM) or other memory to operate as a server. Computer 210 is connected to memory 212 for stable file archiving. Computer 210 is further connected to memory 230 to store files that need to be stably archived. Computer 210 is also further connected to archive memory 240 to copy files that have been stably archived in memory 212.

Terminal 202 may be a diskless workstation, a personal computer, a device connected to the World Wide Web, an intelligent television remote control, ΡΌΑ, or the like. The memory 206, 208 and 230 may be any type of computer memory, such as, for example, a hard disk. Connection 207 may be any type of network connection, such as a local area network (LAL), wide area network (EDAM), dial-up, or Internet connection. Connection 209 may take any form of long-distance connection.

In operation, system 200 allows the user to select files that need to be stably archived in memory 212. The user selects files in user terminal 202 and stores backup sets in specification 204. Files can be selected from any memory that terminal 202 has access to, such as memory 206, 208 or 230. The user is also preferably allowed to select entire directories (directories) and / or subdirectories (subdirectories) for archiving. Such directories or subdirectories are included in the term files in the set specification 204. In one preferred form, specification 204 is created using a computer application, such as application 303, described below with reference to FIG. 3. The user also selects one or more time periods when files listed in specification 204 need to be archived in memory 212. Any selected time periods (or intervals) may be single events or repeating events, for example, that are repeated daily , weekly, monthly, and so on. Other non-time intervals (or event intervals) can be used, for example, whenever a file is accessed or modified. The list of files and the selected intervals together form part of the backup set specification 204. The actions for selecting files and determining intervals should not be carried out in any particular order. The user also preferably defines a name for the backup set to be archived in the memory 212. This helps the user with the subsequent restoration of any required files, as described below. On the other hand, the name for the reservation set can be generated automatically. In addition, numerous set specifications can be created by the user using various and / or overlapping files and from different interval parameters.

Ί

With an additional description of the operation of the system 200, when a pre-selected interval took place (on a temporary or other basis), as defined in the backup set specification 204, the terminal 202 starts the process of automatic stable archiving of files included in the specification list 204. On the other hand, at any time can start the backup process manually. Predefined time intervals (for example, those that are pre-selected by the system administrator) can be used instead of or in addition to the intervals selected by the user. Terminal 202 sends the specification 204 to the remote computer 210 via connection 209. It is preferred that the specification be transmitted in an extensible markup language format such as XMB. For each file listed in specification 204, computer 210 then receives data corresponding to the contents of the file. If computer 210 has access to the file through connection 209 (for example, the file is located in memory 206 or memory 208), then computer 210 issues a command to terminal 202 to access the file and transfers its contents via connection 209. In addition, any file contents transmitted in this way via connection 209 can be represented in a compressed format and / or in the format of an extensible markup language. Any such compression can be performed using terminal 202 before transferring the file or on the fly. In addition, the files may have already been compressed. In a preferred form, the terminal 202 compresses the files before transmission in accordance with the compression algorithms that are available in the commercially available program ΡΚΖΙΡ. However, other compression methods are provided.

If computer 210 has direct access to the file (for example, when the file is located in memory 230), computer 210 reads the contents of the file. Any file read or transmitted to computer 210 can, if necessary, be checked for transmission errors in a known manner, for example, using a checksum, checking with a cyclic redundancy code (SNF), or the like. If transmission errors are detected in this way, then computer 210 may return the error code to terminal 202, for example, by instructing it to retransmit the file. Transferred files can also be checked for viruses if necessary.

In a preferred form, data is read from files in turn. However, it also provides for almost simultaneous reading from multiple files.

After receiving data for the file, computer 210 creates the file in rewritable stable memory 212. In a preferred form, files are recorded in a predetermined user space located within stable memory 212. Next, with reference to FIG. 3, a method for preliminarily defining user space is presented, suitable as it is. Preferably, the original file name and directory structure are retained, thereby allowing the file to be returned to its original location. Computer 210 repeats the above steps until all files listed in specification 204 are stably archived. In addition, any errors detected during the archiving process (for example, an error creating the file) are displayed in terminal 202 as an error code transmitted via connection 209. All files archived in this way are called a backup set.

After the files are created in the memory 212, the computer 210 preferably updates the index file (not shown) corresponding to the file name and location in the memory 212. The contents of the index file (if any) are preferably stored in an extensible markup language such as XME. If necessary, you can perform other operations with archived files or copy files using a computer 110, for example, virus detection or others, the results of which can be reported to the user of the terminal 202.

After the files are archived, the user can then restore any or all of the archived files. When a user needs to perform a restore operation, terminal 202 sends an electronic request to computer 210 to obtain a list of all backup sets previously created for that user and a list of any files, directories and / or subdirectories contained in these backup sets. In addition, other users in the predefined group may also have access to user reservation sets. In addition, backup sets can, if necessary, become available with the help of any user who has access to computer 210. Computer 210 sends a list of backup sets and files located in them when it performs such a request. If the index was used to create any backup sets, the index file can be transferred to terminal 202. Otherwise, terminal 210 can re-create such a list on the fly or transfer file and directory listings directly via connection 209. However, the index file is used in the preferred form. created (or updated, if it already exists) during the archiving process, while transferring a pre-existing index file minimizes the calculation time and bandwidth, especially in large beam on the directory structure and file list.

Terminal 202 then provides the user with a listing of the available backup sets and the files contained therein. This information is preferably presented as a tree structure, such as that made by listing the selective snapshot of the screen shown in FIG. 4 and described with reference to it. However, other forms of presenting this information are provided, such as a network structure using nodes. The user then selects which files should be restored. Terminal 202 sends a request for each file that will be restored on computer 210. Such requests can be sent individually for each file that will be restored or grouped in a package listing. Computer 210 then restores the contents of each recoverable file from rewritable stable memory 212. Files can be restored in this way one at a time, or multiple files can be restored almost simultaneously. Computer 210 then restores the files to the location of the memory from which they were originally read for archiving. In the case of a memory (e.g., memory 212) that is directly accessed by computer 210, files are directly restored. In the case of storage devices accessed via connection 209 (e.g., memory 206 and / or 208), the contents of the file are transferred to terminal 202 from which the files are restored. If the files were additionally compressed during archiving, then you can expand the files before restoring.

As shown in FIG. 2, files stably archived in the memory 212 can be further reserved in the archive memory 240 for offline storage. Such a backup in the memory 240 can be performed automatically (for example, at predetermined intervals), it can be requested by the user in the terminal 202, or it can be performed using an operator who has access to the computer 210. When files are restored as described above, if any errors are detected or if the restored file is no longer in memory 212, then instead of accessing the file, you can perform it from memory 240. In addition, if stably archived files were reserved in memory 240, then these files can if necessary, copy to removable storage media (such as a computer tape or CD), which can be physically sent to the user (for example, by mail) when such a request is made or at periodic intervals.

In FIG. 3 is a block diagram of a virtual system of a tape drive 300 according to the present invention. System 300 is similar to systems 100 and 200 (FIGS. 1 and 2, respectively), but may include various additional features. The user terminal 302 comprises a user application 303 launched within the memory 305. In addition, the terminal 302 includes a memory 306 for storing files. The backup set specification 304 is created by the user and includes a list of archived files (including directories, subdirectories, and so on). In addition, the computer can be connected to computer memory 308 via a network connection 307. Terminal 302 is connected to a remote computer 310 via a long-distance connection 309.

As shown in FIG. 3, the remote computer 310 comprises a server application 311 that runs within the memory 313. The computer 310 also includes a rewritable stable memory 312, which is shown in detail in FIG. 3A. The user space 314 is a subset of the memory area in the memory 312. The backup space 316 is a subset of the memory area in the user space 314. The backup set space 318 is a subset of the memory area in the backup space 316. As will be described in more detail below, files that are listed in specifications 304 are stably archived in the reservation set space 318 through the system and method of the present invention. In addition, the computer 310 includes a memory 330 for storing files. Computer 310 also further includes an archive memory 340, which can be used to archive data contained in memory 312 for offline storage of typically the same data.

Terminal 302 may be any type of processing device that allows a connection to a long-distance line, such as a diskless workstation, personal computer, a device connected to a worldwide network, an intelligent television remote control, ΡΌΑ, or the like. The memory 306, 308 and / or 330, if selected, can be any type of computer memory, such as hard drives. Connection 307 may be a type of network connection, such as ΕΑΝ, νΑΝ, dial-up, or Internet connection. Connection 309 may be a form of long-distance connection. Files stably archived in memory 312 can be further backed up in archive memory 340 for offline storage.

The user application 303 is a computer program executed within the memory 305 of the terminal 302. Among other functions, the application 303 allows the user to select computer files that need to be stably archived, to determine the time interval and / or interval of the event when the computer files need to be stably archived, and restore files, which were previously stably archived. Files that need to be archived in this way can be selected from any computer memory that the application 303 can access, including the memory 306, 308 and / or 330, if selected. In a preferred form, the user application 303 has access to local memory, such as memory 306, although in some forms the terminal does not contain memory 306 for storing computer files. For example, terminal 302 may be selected as a diskless workstation, in which case the user will select files that need to be stably archived from one or more computer memories available to the diskless workstation through a connection, such as a network connection 307 or a telecommunication connection 309. In another form, the terminal 302 may be selected as an intelligent television device having a telecommunication connection 309 to maintain communication with the server 310, but not having about local memory 306 or network connection 307. In this form, the user can select files that need to be stably archived from memory, such as memory 330, to which computer 310 has access. For files stably archived in memory, you can, if necessary, create backups in the archive memory 340 for offline storage.

The following is an example of the operation of the present invention. Before archiving the files, the user first determines through the user application 303 the information that is required to create the backup space 316 inside the user space 314. In a preferred form, the user determines the size and name for the backup space 316. The size is preferably selected from a list of discrete sizes of computer memory (for example, 2 gigabytes, 4 gigabytes and so on). On the other hand, the user can be allowed to determine any size for the backup space 316. If the system according to the present invention is used as part of a commercial service (for example, a service providing users with stable file archiving on a remote server accessed via the Internet), a fee may be charged depending on the size (volume) of the selected backup space. For example, an initial creation fee of $ 30 can be charged for creating a backup space of any size. In addition, fees may apply for sequential storage. For example, a fee of $ 8 per month may be charged for 4 gigabytes of backup space, and for 2 gigabytes of space a lower fee may be charged.

In addition, such a commercial service allows users to provide access to a memory having access to the Internet (such as memory 330), from which you can select files to be archived. In addition, such a commercial service would allow only subscribed users to have access to archiving services. For example, a commercial service may provide limited functionality for free clients, such as access to 25 megabytes of a memory area (eg, memory, such as memory 330), but without access to archiving services. In addition, for subscription customers (for whom a subscription fee is, for example, $ 10 per month), you can provide, for example, 100 megabytes of storage space and access to archiving services. Alternative business models are also possible for generating revenue from a commercial service using the system of the present invention.

As shown by the example of the operation of the present invention, in addition to determining the size for the backup space, the user can also determine the name for the backup space 316. On the other hand, the name for the backup space 316 can be created automatically, for example, as a time / date stamp function. In a preferred form, the backup space name must be unique within user space 314. In addition, the user can define other parameters for the backup space 316, such as a group designation showing other users who will have permission to access the backup space. In addition, the date / time stamp can be included (for example, add) in the name specified by the user. In general, the information defining the backup space is referred to herein as the backup space specification. The user application 303 sends the backup space specification to the server application 311, which creates the backup space as described below.

The specification is accepted by application 311, which then creates data structures within user space 314 for backup space 316. If the user does not already have user space 314 allocated to him (for example, the user has not created a backup space beforehand), application 311 first creates user space 314 in memory 312. Application 311 preferably returns a code to application 302 indicating a successful outcome or failure to create a backup space and / or user one space.

Once the backup space 314 has been created for the user, the user can then create the backup set definition 304 through an application 303 that defines the files to be stably archived. The user is preferably provided with a list of files in a tree format displaying the names and directory structures of files to which the application 303 has access. There are other forms of presenting this information to the user, for example, you can apply a network structure that uses nodes, rather than a tree structure. The user can define the set definition using other parameters, such as the date the file was created, the number of the project or group associated with the file, the author of the file, or the like. The user selects one or more files to be archived. The user preferably also selects one or more periods during which archiving is to be performed. The user preferably also has the option to select a recurring time interval (for example, daily, weekly, monthly and so on) or an event interval. In addition, the user can preferably select a name for the reservation set, which should be archived in the space 316 reservation set. Alternatively, a name for a reservation set can be created automatically.

If the reservation space 316 already exists for the user, the user can choose to overwrite the existing reservation set in it or add it to the backup space, in which case a new reservation set will be created in it. In addition, the user can be allowed to select a range of reservation set spaces in case there are more than one. For example, if a user selects files that will occupy more space than is available in one backup space, then some files can be archived in one backup space, although other files can be archived in another backup space. If such overlapping of backup spaces is acceptable, it is preferable that the user is warned about the possibility that the selected files cannot fit inside one backup space and then provide the opportunity to move to another backup space or create additional backup spaces. On the other hand, overlapping can be done automatically if the user has any other backup available spaces.

It should be noted that there is no need for a specific order with respect to actions to select files, to accurately determine the time interval or to assign a name to a backup set. For example, a user may first select a time interval, and then select files or vice versa. In addition, there are numerous actions for selecting files and / or determining time periods. For example, a user may first select files, then select a time interval, then select additional files and / or delete already selected files from the list, then add additional time intervals and / or delete already defined time intervals.

After the reservation set definition 304 is created, application 303 periodically determines if any of the time intervals specified in definition 304 have taken place; if so, the archiving process begins. In addition, the user can start the archiving process manually through application 303. Application 303 sends the specification 304 to the remote computer 310 via connection 309. It is preferred, but not necessary, that the specification is transmitted in an extensible markup language such as XMB.

For each file listed in specification 304, application 311 then receives data corresponding to the contents of the file. If the file is accessed using application 311 via connection 309 (for example, the file is located in memory 306 or memory 308), application 311 instructs application 303 to access the file and transfer its contents via connection 309. In addition, any contents of the file transmitted in this way via connection 309 may be in a compressed format and / or in an extensible markup language format. Any such compression can be performed using application 303 before transferring the file or on the fly. In addition, files may already be compressed. In a preferred form, application 303 compresses the files before transmission in accordance with compression algorithms, which are available under the name of the available for purchase program ΡΚΖΙΡ. However, other compression methods are provided.

If the file is directly accessible by computer 311 (for example, the file is located in memory 330), then the application 311 reads the contents of the file. Any file read using or transferred to application 311 can, if necessary, be checked for transmission errors in a known manner, such as a checksum, SCS or the like. If transmission errors are detected in this way, application 311 may return the error code to application 302, for example, by instructing it to retransmit the file. In a preferred form, the data is read in turn from the files. However, it also provides for almost simultaneous reading from multiple files.

After receiving data for the file, the application 311 creates the file in the space 318 of the redundant stable memory rewriting set 312. It is preferable that the original file name and directory structure be saved, thereby allowing the file to be restored back to its original location. Application 311 repeats the above steps until all files listed in specification 304 are stably archived in backup set space 318. Application 311 preferably prevents any further modification of any files in the backup set space 318 unless the user subsequently wants to rewrite the backup set with the new backup set. In addition, any errors detected during the archiving process (for example, as an error creating the file) are shown in application 303 as an error code transmitted through connection 309.

When files are created in the memory reservation set space 318, the application 311 preferably updates the index file (not shown) corresponding to the file name and location in the reservation set space. The contents of the index file (if any) are preferably stored in an extensible markup language format such as XMB.

After the files are archived, the user can then restore any or all of the archived files. When a user wishes to perform a restore operation, application 303 sends a request to application 311 for a list of all backup sets previously created for that user, and a list of any files contained in these backup sets. In addition, other users in a predefined group may also have access to user reservation sets. In addition, backup sets can be accessed by any user who has access to computer 310. Application 311 sends a list of backup sets and the files contained in them when requested. If an index was used to create any backup sets, the index file can be transferred to application 303. Otherwise, application 313 can re-create such a list on the fly or transfer the file and directory lists directly via connection 309. However, in the preferred form during The archiving process uses the created index file (or updated, if it already exists), while the transfer of the previously existing index file reduces the calculation time and bandwidth, especially This is especially true for large directory structures and file lists.

Application 303 then provides the user with a listing of the available backup sets and the files contained in them. Preferably, this information is presented in the form of a tree structure represented by the example of the listing shown in FIG. 4. However, other forms of presenting this information are provided, such as those described previously. The user selects which files should be restored. Application 303 sends a request to application 311 for each file to be recovered. Such requests can be sent individually for each file that needs to be restored, or as a group listing. Application 311 then restores the contents of each file to be restored from the space 318 of the backup set. Files can be restored this way one at a time, or multiple files can be restored almost simultaneously. Application 311 then restores the files in the memory location from which they were originally read for archiving. In the case where the application 311 provides direct access to the memory (for example, to the memory 312), the files are directly restored. In the case where access to the storage devices is via connection 309 (for example, memory 306 and / or 308), the contents of the file are transferred to the application 303 from which the files are restored. If the files were further compressed during archiving, the files can be expanded before recovery.

In FIG. 4 illustrates an exemplary user interface 400 used with various forms of the present invention. The interface 400 launches a user terminal (e.g., terminals 102, 202 and / or 302 in FIGS. 1, 2, and 3, respectively) and provides the user with a list of files to be archived and a list of files (if any) that have been archived previously. The interface presents the file and directory listing in a tree format, although other formats are provided for presenting such information.

In FIG. 4, a tree listing is shown in more detail on the left side of the interface 400. At the top level of the tree listing, the Desktop icon is displayed. Any terms shown in FIG. 4, enclosed in quotation marks, hereinafter it should be understood as related to specific icons that are displayed on interface 400. Two desktop sublevels are shown: My computer, the sublevels of which are files that the user can access directly through the user terminal and Server Simdesk (Ytbekk), the sublevels of which are the existing user areas in stable rewritable memory (for example, memory 112, 212 and 312, respectively, in Figs. 1, 2 and 3).

A tape library is a user area, such as user space 314 in FIG. 3A. The library sublevels on tapes represent the backup space, such as the backup space 316 in FIG. 3A. A 2 gigabyte tape represents one such backup space. Its sublevels (three shown) are separate reservation set spaces, such as reservation set space 318 (FIG. 3A). Two such reservation set spaces are called Ebeei beto 12-11-2000 14:51 and Eeyeei beto 12-11-2000 14:52). The names of the reservation set space include a date / time stamp, it should be noted that the date / time stamp in the two names mentioned differs by one minute, indicating that they were created at different times.

In particular, on Ebeei, on 12-11-2000 14:51, the sublevel C: is shown. C: contains sublevels corresponding to files archived from memory corresponding to C: (Eeeer Tyoid-C) shown under My computer. Accordingly, any files recovered from C :, will be restored to C: (Eeeer Tyoid-C). The icon representing a folder is a display next to C:, indicating that it contains subdirectories or files. VBU is a subdirectory of C: containing the Vaskir subdirectory (“Backup”), which directly contains the Documents subdirectory. Documents are highlighted, indicating that they and any files and subdirectories in them were selected for recovery. Any files, directories and subdirectories in them restored in this way will be restored to their respective locations inside C: (Eeeer Tyoid-S). Such file recovery can be performed as described above with reference to FIG. 1, 2 or 3.

Although the present invention has been depicted and described in detail in the above description with reference to the drawings, which should be considered in nature as illustrative and not restrictive, it should be understood that only preferred forms are shown and described, and that all changes and modifications that are in Within the scope of the invention, it is desirable to protect.

Claims (29)

CLAIM 1. A virtual tape drive system comprising at least one user terminal located at a first location, configured to generate a list of computer files, the computer files being located inside the first computer memory, a remote computer having a second rewritable stable computer memory, the second computer the memory is located in a second location that is remote from the first location, and a long-distance line connected to the user the terminal and the remote computer, while the list of files is transmitted in an expandable markup language from the user terminal via the long-distance line to the remote computer, and at least one file listed is transferred from the first computer memory to the second computer memory for stable archiving via at least one file for subsequent user access to at least one file. 2. The system according to claim 1, characterized in that the list of files is part of the specification of the backup set, and the specification of the backup set additionally contains at least one scheduled time interval corresponding to the time when the source computer files included in the list must be archived. 3. The system according to claim 2, characterized in that it further comprises a user application designed to operate on a user terminal, and a server application designed to operate on a remote computer, wherein the user application and the server application are configured to communicate over a communication line, wherein the user application is configured to transmit the list, and the server application is configured to receive the list. 4. The system according to claim 3, characterized in that the server application is configured to prevent changes to stably archived files. 5. The system according to claim 4, characterized in that the communication line contains an Internet connection. 6. The system according to claim 5, characterized in that the user application includes an interface for displaying files and directories using the tree structure, and the list is generated using the interface. 7. The system according to claim 6, characterized in that the user application allows you to determine the size of the backup space for saving files inside the second memory, and the board is charged from the user according to the specified size. 8. The system according to claim 7, characterized in that it further comprises an archive memory for offline storage of at least one file stored in the second memory. 9. The system of claim 8, wherein the interface is further configured to allow the user to select files to be recovered from the second memory, and the server application is configured to restore the selected files to the first memory from the second memory. 10. The system according to claim 9, characterized in that the server application is additionally configured to allow a group user located in a predefined user group to recover files associated with any user in a predefined user group. 11. The system of claim 10, wherein the server application is further configured to transfer files listing the index files stored in the second memory to the user application, and the index file is transmitted in an expandable markup language. 12. The system of claim 11, wherein the user application is configured to transmit the list, and the server application is configured to receive the list. 13. The system according to claim 1, characterized in that the communication line contains an Internet connection. 14. The system according to claim 1, characterized in that it further includes a user application designed to operate on a user terminal, wherein the application includes an interface for displaying files and directories using a tree structure, and the list is generated using the interface. 15. The system according to claim 1, characterized in that the user terminal is configured to allow the user to determine the size of the backup space inside the second memory for stable file archiving, and the user board is charged according to the specified size. 16. A method for stably archiving computer files, comprising the steps of defining a backup set containing a backup list containing at least one name of the source computer file corresponding to the source computer file located in the first computer memory and at least one the planned time interval corresponding to the time when the source computer files included in the reservation list should be archived, determine when at least one scheduled time interval, transmit the reservation list via the long-distance connection to the remote computer, read at least one name of the source computer file from the reservation list, place the source computer file corresponding to the name of the source computer file, after determining read the data from the source computer file , and write data to the target computer file in a second rewritable stable computer memory connected to the remote computer y. 17. The method according to clause 16, wherein the communication line contains an Internet connection. 18. The method according to clause 16, wherein the definition of the backup set is done using a user application that includes an interface for displaying files and directories using a tree structure. 19. The method according to p. 16, characterized in that it further comprises the steps according to which determine the size of the backup space inside the second memory for recording data and charge a fee from the user according to the specified size. 20. The method according to clause 16, characterized in that it further comprises the step of transferring, in an extensible markup language, to the user application, the listing files of the index files that are stored in the second memory for selecting files to be restored. 21. A system for stable archiving of computer files, comprising a user terminal having a first memory, a user application designed to work on a user terminal, a remote computer having a second memory, a server application designed to work on a remote computer, a third rewritable stable computer memory, designed to maintain communication with the server application, and the third memory is located separately from the first memory and the second memory, and the connection to the line more communication, designed to maintain communication with the client application and the server application through the communication line, while the client application is additionally configured to transfer the server application to a predetermined list of source computer files, the source computer files being located in the first memory, the server application is configured to receiving the list, the server application is further configured to read data corresponding to the contents of at least one source computer Of the file included in the list, the server application is further configured to write data to the third memory. 22. The system according to item 21, wherein the communication connection contains an Internet connection. 23. The system according to item 21, wherein the user application includes an interface for displaying files and directories using a tree structure. 24. The system according to item 21, wherein the user application is additionally configured to allow the user to determine the size of the backup space inside the second memory for recording data. 25. The system according to item 21, wherein the server application is further configured to transmit in an extensible markup language to the user application listing files listing of index files that are stored in the second memory and which are available for recovery. 26. A method for stably archiving computer files, a method comprising the steps of determining at least one user space inside a first rewritable stable computer memory connected to a remote computer, determining at least one backup space within the user space, determining at least at least one backup set definition containing a list corresponding to at least one computer file located in the second to the computer memory accessed by the user terminal, copy at least one computer file listed in the definition of the backup set, at least one backup space, and prevent the change of computer files in at least one backup space, when this, the user terminal is removed from the first rewritable stable computer memory. 27. The method according to p. 26, characterized in that the determination of the backup set is made using a user application that includes an interface for displaying files and directories, and using the tree structure. 28. The method according to p. 26, characterized in that it further comprises the steps according to which determine the size of the backup space inside the second memory for recording data and charge a fee from the user according to the specified size. 29. The method according to p. 26, characterized in that it further comprises transmitting in an extensible markup language to the user terminal the listing files of the index files stored in the second memory, for selecting files that will be restored.