JP2011192241A - Backup program, method, and computer - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automatically back up a file naturally by a user, excepting initial setting. <P>SOLUTION: This method includes a process for detecting writing the file by an application, a process for determining whether identification information of the application under execution is registered as an backup object, in a storage part registered with identification information of backup-objective application, or not, a process for determining whether an extension in a file name of a writing-objective file is registered as an backup object, in an extension storage part registered with an extension in a file name of a backup-objective file, or not, when identification information of an application program is stored as the backup object in the storage part, and a process for storing a copy of the writing-objective file into a backup area, when the extension in the file name of the writing-objective file is registered as the backup object in the extension storage part. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a file backup technology.

  For example, software that automatically backs up personal computer files has existed for some time. However, in the conventional method, the location (that is, the directory) where the backup target file is stored must be specified, so the user has to be aware that the file is always stored in a predetermined location. In such a case, the user needs to specify the location where the file to be backed up is saved in advance, but if the file is saved in a location other than this location, the backup will not be performed, resulting in the file May disappear.

  Japanese Patent Laid-Open No. 2000-82004 discloses a system that performs backup and recovery by software in a plurality of procedures only for a file designated by a user. Specifically, the name of the operation target file is associated with the backup procedure and the recovery procedure and is made resident in the management table, and according to the associated procedure, the copy control process performs the specified file backup and recovery triggers. The occurrence of an event or a request for backup or recovery execution for the management table from the application program via the request notification unit is monitored, and when an event or request occurs, the copy process is started to perform backup or recovery. Make a copy of In such a system, since a file name must be specified, there are many burdens on users who handle various files.

  Also, currently available word processors, spreadsheet applications, etc., write temporary files such as snapshots to the disk even when the user does not instruct. Such a temporary file including a snapshot is provided only in the case where an application program crashes, and there is no meaning to prevent data loss by duplicating data.

JP 2000-82004 A

  Accordingly, an object of the present invention is to provide a technique for enabling a user to automatically back up a file without being particularly conscious of other than the initial setting.

  In the backup method according to one aspect of the present invention, (A) a step of detecting writing of a file by an executing application program, and (B) identification information (for example, a file name) of the executing application program includes: Determining whether the identification information of the backup target application program is registered as a backup target in the registered application identification information storage unit; and (C) the identification information of the application program being executed is the application identification information storage unit If the file name extension of the file to be written is registered as a backup target in the extension storage unit in which the file name extension of the file to be backed up is registered And (D) if the extension in the file name of the file to be written is registered as a backup target in the extension storage unit, a copy of the file to be written is stored in advance. And saving to a predetermined backup area (for example, a spare disk device or a network drive).

  In this way, if the application program identification information and the file name extension indicating the file type are registered in advance, they are automatically backed up, so the user intends without being aware during normal work. The file will be saved. If such a method is adopted, files intended by the user can be backed up without performing useless backups, compared to setting only the extension or setting only the application program. .

  In the backup method described above, (E) when the extension of the file name of the file to be written is not registered as a backup target in the extension storage unit, it is retained in the operating system. In addition, from the extension association data storage unit in which the identification information of the application program and the extension in the file name of the file processed by the application program are associated, the extension in the file name of the file to be written is changed. A step of reading the identification information of the associated application program, and (F) determining whether the identification information of the read application program is registered as a backup target in the application identification information storage unit And (G) when the identification information of the read application program is registered as a backup target in the application identification information storage unit, a copy of the file to be written is determined in advance. And a step of saving in a backup area.

  Many users are not concerned about the types of files that application programs process. For example, there are cases where the types of files processed by application programs are expanded due to version upgrades, etc., but the number of types may increase, but the user may not have noticed and forgot to register for the extension storage unit. There may be. Even in such a case, even if the application program is registered and the OS (Operating System) automatically associates the file type with the application program at the time of installation, as described above, automatic backup is performed. Done. That is, it is possible to follow the forgotten backup of important files by reducing the user's registration effort.

  The method according to the present invention may be implemented by a combination of computer hardware and a program. The program according to the present invention is stored in, for example, a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, a hard disk, or the like. Stored in a medium or storage device. The intermediate processing result is temporarily stored in a storage device such as a main memory.

  According to the present invention, a file can be automatically backed up without any particular attention except for the initial setting.

FIG. 1 is a system outline diagram in the embodiment of the present invention. FIG. 2 is a diagram schematically illustrating an example of data stored in the extension association DB. FIG. 3 is a functional block diagram of the backup processing program. FIG. 4 is a diagram illustrating a processing flow of initial setting. FIG. 5 is a diagram illustrating an example of a backup instruction screen. FIG. 6 is a diagram illustrating an example of data stored in the application DB. FIG. 7 is a diagram illustrating an example of data stored in the extension DB. FIG. 8 is a diagram showing a processing flow during backup processing. FIG. 9 is a functional block diagram of the computer.

  FIG. 1 shows a schematic diagram of a system according to an embodiment of the present invention. For example, a computer 3 that is a personal computer is connected to a network 1 such as the Internet or a LAN (Local Area Network). A file server 5 related to the present embodiment is also connected to the network 1, and the file server 5 manages a backup data storage unit 51.

  The computer 3 executes various application programs, and FIG. 1 shows an example in which the application A, the application B, and the application X are executed. Further, like a normal computer, the computer 3 executes an operating system OS101. A normal application such as applications A, B, and X writes data such as a file to the storage device 31 or the backup data storage unit 33 that is, for example, a hard disk drive, or a file from the storage device 31 or the backup data storage unit 33 by the OS 101. And so on. Further, the applications A, B, and X perform data communication with other computers connected to the network 1 by controlling the communication processing unit 35 using the OS 101.

  When the application program is installed in the computer 3, the OS 101 stores data for associating identification information (for example, a file name) of the application program with an extension indicating the type of file processed or handled by the application program. The extension-related DB 103 is maintained and managed. An example of data held in the extension association DB 103 is schematically shown in FIG. In the example of FIG. 2, the file name of an application program that preferentially processes a file having a file name including the extension is registered in association with the extension. Note that the file name of the application program is also treated as a process name when the process is specified by the file name in the OS 101, and is therefore also described as a process name in FIG.

  Returning to the description of FIG. 1, the computer 3 also executes a backup processing program 301 that performs the main processing in the present embodiment. The backup processing program 301 uses the setting data storage unit 311, the application DB 313, and the extension DB 315 to detect a file write event from the application program, and stores the backup data for specifying the file related to the appropriate event Processing to be stored in the unit 33 or the like is performed. At this time, the extension association DB 103 held in the OS 101 is also used.

  Next, functions of the backup processing program 301 will be described with reference to FIG. The backup processing program 301 causes the computer to implement a write monitoring unit 3011, a setting unit 3012, and a storage processing unit 3013. The write monitoring unit 3011 detects a file write event from the application program and performs the processing described below. At this time, the data stored in the application DB 313 and the extension DB 315 are used, and the extension association DB 103 is also used. In addition, the setting unit 3012 stores data about the backup storage destination of the file in the setting data storage unit 311 in accordance with an instruction from the user. Furthermore, the setting unit 3012 stores data in the application DB 313 and the extension DB 315 in accordance with an instruction from the user.

  Next, processing contents of the backup processing program 301 will be described with reference to FIGS. First, in response to an instruction from the user, the setting unit 3012 of the backup processing program 301 displays a backup designation screen on the display device of the computer 3 (step S1). For example, a screen as shown in FIG. 5 is displayed.

  In the example of FIG. 5, an input field for a storage destination of a file determined to be backed up (referred to as a backup file), a reference button for designating the storage destination with reference to the directory structure, an application for backup, A check box group and application name list for specifying programs, a check box group and extension name list for specifying file types to be backed up, a save button for saving settings, and a cancel button are provided. It has been. The application name list of the backup target application is extracted from, for example, application program data (application name and application program file name) installed in the computer 3 and managed by the OS 101 and displayed. Similarly, the extension in the file name of the file managed by the OS 101 is extracted and displayed from the extension list of the file type to be backed up. The extension may be extracted from the extension-related DB 103 in some cases. The user clicks the save button after checking the check boxes of the applications A and B after checking such a display screen, and further checking the check boxes of the extensions doc and csv. And

  Then, the setting unit 3012 receives designation of the backup file storage destination and stores it in the setting data storage unit 311 (step S3). For example, a directory name as shown in the input field of FIG. 5 is registered. As described above, the data may be stored in a specific area of the backup data storage unit 51 managed by the file server 5.

  Further, the setting unit 3012 receives designation of an application program to be backed up, and stores identification information (for example, a file name) of the application program in the application DB 313 (step S5). For example, data as illustrated in FIG. 6 is stored in the application DB 313.

  In the example of FIG. 6, the file name (= process name) of the application program, the application name, and the backup flag are registered. An application program whose backup flag is set to “1” is a backup target application. Note that only the application program data designated as the backup target application may be registered without using the backup flag. That is, only the file name of the backup target application may be registered. Similarly, the application name need not be registered.

  Further, the setting unit 3012 receives designation of the backup target file type, and stores an extension corresponding to the backup target file type in the extension DB 315 (step S7). For example, data as shown in FIG. 7 is stored in the extension DB 315.

  In the example of FIG. 7, an extension and a backup flag are registered. The file type corresponding to the extension whose backup flag is set to “1” becomes the backup target file type. Note that only the extension corresponding to the backup target file type may be registered without using the backup flag.

  As described above, the setting as the preprocessing is completed.

  Then, a process when the user actually operates the computer 3 will be described with reference to FIG. The write monitoring unit 3011 of the backup processing program 301 detects a file write event by the application program (FIG. 9: Step S11). For example, it is realized by hooking a system call by an application program. In the file writing event, identification information (process name, file name) of the writing application program, file data to be written, and the file name of the file are specified.

  Then, the write monitoring unit 3011 confirms whether or not the write application program is an application program registered in the application DB 313 as a backup target (step S13). That is, the application DB 313 is searched with the identifier of the writing application program, and the search result is obtained.

  If the writing application program is not registered as a backup target in the application DB 313 (step S15: No route), the process ends without performing the automatic backup process. The file is stored in, for example, the storage device 31 as usual.

  On the other hand, when the writing application program is an application program registered as a backup target in the application DB 313 (step S15: Yes route), the writing monitoring unit 3011 indicates that the extension in the file name of the file to be written is an extension. It is confirmed whether or not the extension is registered as a backup target in the DB 315 (step S17). That is, the extension DB 315 is searched with the extension in the file name of the file to be written, and the search result is obtained.

  When the extension in the file name of the file to be written is registered as a backup target in the extension DB 315 (step S19: Yes route), the write monitoring unit 3011 sends the data of the file to be written to the storage processing unit 3013. When receiving the data of the file to be written, the storage processing unit 3013 stores the data in the storage destination registered in the setting data storage unit 311 (step S25). For example, the data is stored in the backup data storage unit 33 in the computer 3 or stored in a predetermined area of the backup data storage unit 51 managed by the file server 5 via the communication processing unit 35 and the network 1. In the case of storing in the backup data storage unit 51 managed by the file server 5, there is a case where the data is stored after being authenticated.

  As described above, when the process proceeds to step S25 in the Yes route in step S19, the application program and the extension can be specified according to the user instruction registered in the application DB 313 and the extension DB 315. Files are backed up as expected.

  Note that when determining whether to back up only with an application program, various temporary files are generated depending on the application program, so many meaningless files are subject to automatic backup processing. There is a problem. There is also a problem in determining whether to back up by just the extension. For example, if you are using a dedicated application program or an editor, etc. to perform work that generates HTML (Hyper Text Markup Language) files, register the extensions html and html. If you decide whether or not to back up only by the extension, the HTML file is written even when the web browser writes to the cache, so even in such a case, useless files are subject to automatic backup processing. .

  As described above, the determination is made based on the combination of the application program and the extension, so that the backup is automatically performed in a form according to the user's intention. Even in this case, as long as the initial settings are made, the backup is performed without being aware of the save destination directory, so the file can be read from the backup destination even in the event of a disk crash. It becomes like this.

  On the other hand, when the extension in the file name of the file to be written is not registered as a backup target in the extension DB 315 (step S19: No route), the write monitoring unit 3011 writes in the extension association DB 103 of the OS 101. It is confirmed whether or not the application program associated with the extension in the file name of the file is an application program registered in the application DB 313 as a backup target (step S21). That is, when the extension association DB 103 is searched with the extension in the file name of the file to be written and an identifier of some application program is obtained as a search result, the application DB 313 is further updated with the identifier of the application program. Search to obtain a second search result.

  In the extension association DB 103, when the application program associated with the extension in the file name of the file to be written is an application program registered as a backup target in the application DB 313 (step S23: Yes route). Then, the process proceeds to step S25 to perform backup.

  For example, it is assumed that the user has upgraded the application A after registering the application A and the extension “.doc” in the file name of the file handled by the application A. At this time, it is assumed that the file with the extension “.docx” is newly processed even though the identification information (for example, the file name) of the application A does not change. If the user notices “.docx” and registers it in the extension DB 315 as a backup target, there is no particular problem. However, if the user has forgotten registration, the extension “.docx” will not be executed unless step S21 is performed. Files with are excluded from backup. However, since it is highly likely that the user basically considers the file created by application A to be important, if the conditions described above are satisfied, automatic backup processing should be performed. Yes.

  If step S21 is not performed, the application B normally processes A. When the file “txt” is processed by the application A and stored with the file name “A.txt” as it is, if the extension “.txt” is not registered in the extension DB 315, the target of automatic backup processing is set. Must not. However, if the application B to be backed up is associated with the extension “.txt” in the extension association DB 103, it is confirmed in step S21 that it is a target for automatic backup. In this way, it is possible to detect a file write event that is considered safer from the viewpoint of the application, and to perform backup.

  On the other hand, when the application program associated with the extension in the file name of the file to be written in the extension association DB 103 is not an application program registered as a backup target in the application DB 313 (step S23: No route). ), The process for this file write event is terminated.

  As described above, file write events can be monitored, and backups can be automatically performed for appropriate file write events. Therefore, the user can save the file separately in a form in accordance with the intention, without being aware of anything other than the initial setting.

  Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the functional block diagram shown in FIG. 3 is an example, and does not necessarily match the actual program module configuration.

  Further, the screen configuration of FIG. 5 is an example, and for example, an input screen may be displayed for each file storage destination, application / program, and extension. Furthermore, the input screen may be configured by a combination of arbitrary elements.

  Further, the file storage destination may be set in more detail. That is, the storage destination may be set in association with the application DB 313 or the extension DB 315. In other words, in the case of the application A, settings may be made such that it is stored in the directory A, and if the extension is “.doc”, it is stored in the directory B.

  In addition, as long as the same result can be obtained for the processing flow, the processing order may be changed or the processing flow may be performed in parallel.

  The computer 3 and the file server 5 are computer devices, and as shown in FIG. 9, a memory 2501, a CPU 2503, a hard disk drive (HDD) 2505, a display control unit 2507 connected to the display device 2509, a removable A drive device 2513 for the disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. An operating system (OS) and an application program for executing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above, the OS, and necessary application programs.

1 Network 3 Computer 5 File Server 51 Backup Data Storage Unit 311 Setting Data Storage Unit 313 Application DB
315 Extension DB 301 Backup processing program 101 OS 103 Extension-related DB
31 Storage Device 33 Backup Data Storage Unit 35 Communication Processing Unit 3011 Write Monitoring Unit 3012 Setting Unit 3013 Storage Processing Unit

Claims (4)

Detecting the writing of a file by a running application program;
Determining whether the identification information of the application program being executed is registered as a backup target in the application identification information storage unit in which the identification information of the backup target application program is registered;
When the identification information of the application program being executed is registered as a backup target in the application identification information storage unit, the extension in the file name of the file to be written is the file name of the backup target file. Determining whether the extension is registered as a backup target in the extension storage unit in which the extension is registered;
When an extension in the file name of the file to be written is registered as a backup target in the extension storage unit, a copy of the file to be written is stored in a predetermined backup area. Saving step;
A backup program that allows a computer to execute When the extension in the file name of the file to be written is not registered as a backup target in the extension storage unit, it is held in the operating system and the application program identification information and the application The application program associated with the extension in the file name of the file to be written from the extension association data storage unit associated with the extension in the file name of the file processed by the program Reading the identification information of
Determining whether the read identification information of the application program is registered as a backup target in the application identification information storage unit;
When the identification information of the read application program is registered as a backup target in the application identification information storage unit, a copy of the file to be written is stored in a predetermined backup area. Saving step;
The backup program according to claim 1, further causing the computer to execute. Detecting the writing of a file by a running application program;
Determining whether the identification information of the application program being executed is registered as a backup target in the application identification information storage unit in which the identification information of the backup target application program is registered;
When the identification information of the application program being executed is registered as a backup target in the application identification information storage unit, the extension in the file name of the file to be written is the file name of the backup target file. Determining whether the extension is registered as a backup target in the extension storage unit in which the extension is registered;
When an extension in the file name of the file to be written is registered as a backup target in the extension storage unit, a copy of the file to be written is stored in a predetermined backup area. Saving step;
A backup method executed by a computer. Means for detecting writing of a file by a running application program;
Means for determining whether the identification information of the application program being executed is registered as a backup target in the application identification information storage unit in which the identification information of the backup target application program is registered;
When the identification information of the application program being executed is registered as a backup target in the application identification information storage unit, the extension in the file name of the file to be written is the file name of the backup target file. Means for determining whether the extension is registered as a backup target in the extension storage unit in which the extension is registered;
When an extension in the file name of the file to be written is registered as a backup target in the extension storage unit, a copy of the file to be written is stored in a predetermined backup area. Means for storing;
Having a computer.

Images