JP6013957B2 - File management method and file management system - Google Patents

Description

  The present invention relates to a file management system that performs backup storage of files (data files).

  Conventionally, as a file backup method, a differential backup method that backs up each file that has been changed since the last full backup (full backup), or a file that has changed since the last backup process each time backup processing is performed Incremental backup methods are known.

  For example, in Patent Literature 1, when a file operation by a user terminal is creation or update of a file, a link is created and stored with the target file to be created or updated as an entity file, and the file based on this link is updated A differential backup type file management system for storing a file in a backup device is disclosed.

JP 2012-208699 A (released on October 25, 2012)

  However, in the conventional file management system, when a large number of files are stored in one folder of the file system of the user terminal, the file configuration cannot be uploaded to the file server as it is, or the folder cannot be uploaded even if it can be uploaded. It may take time to display and browse.

  The present invention has been made in view of the above problems, and an object of the present invention is a file management system that performs backup storage of files, and allows a user to easily and quickly find a file to be browsed when browsing a file. It is to provide a file management system that can be used.

  A file management system according to an aspect of the present invention is a file management system including a terminal device and a server device that backs up and saves a file stored in the terminal device, and the backup source provided in the terminal device A file management unit that stores a file stored in the folder in a first folder in a backup destination folder provided in the server device in association with the backup source folder, and the first folder includes the first folder An upper limit value of the number of files that can be stored in the folder is set in advance, and when the file management unit stores a file in the backup source folder, the number of files stored in the first folder is the upper limit. If it is less than the value, the above file saved in the backup source folder When backup is saved in the first folder and the number of files saved in the first folder has reached the upper limit, among the files already saved in the first folder, based on a predetermined priority order. The selected file is moved to an archive folder provided in the backup destination folder, and the file saved in the backup source folder is saved in the first folder.

  According to the above configuration, the number of files stored in the first folder provided in the upload destination folder of the server device is limited to a preset upper limit value or less, and the files are stored in the backup source folder of the terminal device. In this case, the file can be preferentially saved in the first folder. As a result, a file desired by the user can be easily and quickly found when browsing the backed up file.

It is explanatory drawing which shows the structure of the file management system concerning one Embodiment of this invention. It is explanatory drawing which shows an example of the setting screen of the backup method displayed on the display part of a terminal device in the file management system of FIG. It is explanatory drawing which shows the structure of the file management server setting table used in the file management system of FIG. It is explanatory drawing which shows the structure of the upper limit setting table used in the file management system of FIG. It is explanatory drawing which shows the structure of the setting management table used in the file management system of FIG. It is a flowchart which shows the flow of a process in the file management system shown in FIG. 1, and has shown the process which uploads the file newly preserve | saved to the upload source folder of a terminal device to a file management server. It is explanatory drawing which shows the structure of the upload file management table used in the file management system of FIG. It is explanatory drawing which shows an example of the folder structure of the upload destination folder in the file management system shown in FIG. It is a flowchart which shows the flow of a process in the file management system shown in FIG. 1, and when the file preserve | saved at the upload source folder of a terminal device is updated, the process which uploads the said file to a file management server automatically is shown. Yes.

  An embodiment of the present invention will be described.

(1-1. Configuration of File Management System 1)
FIG. 1 is an explanatory diagram showing a schematic configuration of a file management system 1 according to the present embodiment.

  As shown in FIG. 1, the file management system 1 includes a terminal device 100 and a file management server 300, and these devices are communicably connected via a network 200. In the example of FIG. 1, only one terminal device 100 and one file management server 300 are depicted, but the number of terminal devices 100 and file management servers 300 connected to the network 200 is not limited to this. There may be a plurality of each.

  The network 200 only needs to have a configuration that allows the terminal device 100 and the file management server 300 to be communicably connected. For example, the Internet, extranet, LAN, ISDN, VAN, CATV communication network, virtual private network (virtual private network) ), Telephone line networks, mobile communication networks, satellite communication networks, and the like. Also, the transmission medium constituting the communication network is not particularly limited. For example, even in the case of wired such as IEEE 1394, USB, power line carrier, cable TV line, telephone line, and ADSL line, infrared rays such as IrDA and remote control, Bluetooth (registration) Trademark), 802.11 wireless, HDR, mobile phone network, satellite line, terrestrial digital network, and the like.

  The terminal device 100 is a computer device that performs various types of information processing in accordance with user instructions. In addition, the terminal device 100 accesses the file management server 300 via the network 200 and performs various processing requests to the file management server 300, file uploads, and the like. The terminal device 100 may be, for example, a general-purpose personal computer or a mobile terminal such as a smartphone, a tablet terminal, or a mobile phone.

  As illustrated in FIG. 1, the terminal device 100 includes a display unit 101, an operation input unit 102, an application (application) storage unit 103, a terminal control unit 104, a file storage unit 105, a file information storage unit 106, and a communication unit 107. It has. The terminal control unit 104 includes a UI (user interface) control unit 111, an application (application) processing unit 112, a storage management unit 113, an upload management unit 114, and a communication control unit 115.

  The display unit 101 displays various information according to instructions from the UI control unit 111. As the display unit 101, for example, a liquid crystal display, a plasma display, an organic EL (electroluminescence) display, or the like can be used.

  The operation input unit 102 is an operation device for the user of the terminal device 100 to input various instructions. As the operation input unit 102, for example, a conventionally known operation device such as a keyboard or a mouse can be used. A touch panel having both the function of the display unit 101 and the function of the operation input unit 102 may be used.

  The application storage unit 103 stores various application programs executed by the application processing unit 112. The type of the application program is not particularly limited, and for example, word processor software, spreadsheet software, drawing software, image editing software, various game software, and the like can be used.

  The file storage unit 105 stores various files (data files) created or edited by the terminal device 100. As the file storage unit 105, for example, an HDD (Hard Disc Drive), an SSD (Solid State Drive), or the like can be used.

  The file information storage unit 106 includes various types of information such as setting information related to uploading (backup) of files to the file management server 300 (file management server setting table, upper limit setting table, setting management table, upload file management table, etc. described later). Remember.

  The communication unit 107 communicates with other devices (such as the file management server 300) that are communicably connected via the network 200.

  The UI control unit 111 controls the operation of the display unit 101 to display various information, various input screens, and the like. In addition, the UI control unit 111 receives an operation input input from the user via the operation input unit 102.

  The application processing unit 112 reads an application program corresponding to a user instruction from the application storage unit 103 and executes it. In addition, the application processing unit 112 performs processing for storing a file created by the application program in the file storage unit 105, processing for reading and editing a file stored in the file storage unit 105, and the like.

  The storage management unit 113 monitors access to the file storage unit 105 and notifies the upload management unit 114 of the contents when a file is added, deleted, updated, or the like. As a method for monitoring access to the file storage unit 105, for example, (i) API (application program interface) for file monitoring prepared in an OS (Operating System) such as Windows (registered trademark) or Linux (registered trademark) To receive a notification when a file is updated using, or (ii) periodically check the update date and time of all files in the monitoring folder, and check if there is a difference from the previous check For example, a confirmation method can be used. In this embodiment, the update information of the local file (file stored in the file storage unit 105) is monitored using the former OS standard API.

  The upload management unit 114 (i) uploads a file stored in the file storage unit 105 (local file storage) to the file management server 300, (ii) deletes, moves, or updates a file in the file management server 300. (Iii) Manage processing such as acquisition of file information in the folder of the file management server 300. For example, the upload management unit 114 stores the file in the root folder (first folder) of the upload destination folder based on the file information stored in the upload destination folder and the information stored in the file information storage unit 106. It is determined whether to upload or upload to an archive folder (second folder) provided in a lower hierarchy of the upload destination folder. Further, the upload management unit 114 exchanges files between the root folder and the archive folder as necessary. In this embodiment, an archive folder is a file that cannot be saved in the root folder in the group of files to be backed up (when the upper limit of the number of files that can be saved in the root folder is set, the root is exceeded. This is an area for storing files that could not be saved in the folder.

  In the present embodiment, the upload management unit 114 includes a file having a high possibility of being a user-desired file of the number of files equal to or less than a predetermined upper limit value that has been saved or updated most recently among files to be backed up. It is assumed that the backup folder is saved in the root folder, and the remaining files are saved in the archive folder. Therefore, it is preferable that the access speed (or the file reading speed) with respect to the root folder is the same as or faster than the archive folder. Details of processing in the upload management unit 114 will be described later.

  The communication control unit 115 controls the operation of the communication unit 107 in response to an instruction from the upload management unit 114 and performs communication with the file management server 300.

  As shown in FIG. 1, the file management server 300 includes a communication unit 301, a server control unit 302, and a file storage unit 303.

  The communication unit 301 communicates with other devices (such as the terminal device 100) that are communicably connected via the network 200.

  The server control unit 302 is a computer device that includes an arithmetic processing unit such as a CPU and a dedicated processor, and a storage unit (all not shown) such as a RAM, a ROM, and an HDD. The server control unit 302 implements an RDBMS (Relational Database Management System) function by reading and executing various information stored in the storage unit and a program for performing various controls. .

  For example, the server control unit 302 receives various processing requests from the terminal device 100 (file saving (backup saving), processing requests for deletion, movement, update, etc., file information acquisition request in a folder, etc.) and the processing requests Process according to the.

  The file storage unit 303 stores files according to instructions from the server control unit 302.

  The file management server may be a device having a file server function such as a CIFS (Common Internet File System) server or an NFS (Network File System) server.

  In the present embodiment, the configuration in which the upload management unit 114, the storage management unit 113, and the file information storage unit 106 are provided in the terminal device 100 has been described. Alternatively, all may be provided in the file management server 300 or another device that is communicably connected to the terminal device 100 via the network 200.

(102. Backup method setting process)
In this embodiment, when performing a file backup process, the user performs a backup method setting process prior to the execution of the backup process.

  Specifically, when the user inputs a backup method setting processing start instruction via the operation input unit 102, the UI control unit 111 causes the display unit 101 to display a backup method setting screen.

  FIG. 2 is an explanatory diagram showing an example of a backup method setting screen (UI dialog). In the example shown in this figure, the file management server account setting, the upper limit value of the number of files stored in the root folder, the upload folder setting, and the like are performed on the backup method setting screen.

  The account setting of the file management server is setting of access information for the file management server. In the example of FIG. 2, the file management server address, user name, and password are set. The file management server account setting result is stored in a file management server setting table stored in the file information storage unit 106 as shown in FIG. In the present embodiment, when the terminal device 100 accesses the file management server 300, the user information (user name and password) input by the user via the operation input unit 102 and the file management server setting table are displayed. User authentication processing is performed based on the stored user information (user name, password). However, since a known technique can be used as the user authentication processing method, the description thereof is omitted in the following description.

  In the setting of the upper limit value of the number of files stored in the root folder, the upper limit value of the number of files stored in the root folder of the upload destination folder is set. That is, when uploading a file to the file management server, an upper limit value of the number of files to be stored in the root folder of the folder is set for each upload destination folder. When saving files exceeding the upper limit, only the number of files corresponding to the upper limit is saved in the root folder in order from the latest update date and the remaining files are created in the lower hierarchy of the root folder. Upload to archive folder. The setting result of the upper limit value of the number of files is stored in an upper limit value setting table stored in the file information storage unit 106, as shown in FIG.

  In the upload folder setting, the correspondence between the path of the upload source folder, which is a folder for storing the target file for upload (backup) in the file storage unit 105, and the upload destination folder path is set. The setting result of the upload folder setting is stored in a setting management table stored in the file information storage unit 106 as shown in FIG. In the example of FIG. 2, only the correspondence between one set of upload source folder and upload destination folder is set. However, the present invention is not limited to this, and a plurality of sets of correspondence may be set.

(1-3. Processing when creating a new file)
FIG. 6 is a flowchart showing a processing flow when a file is newly saved in the upload source folder in the terminal device 100 and the file is automatically uploaded to the file management server 300.

  A file newly created by the user is stored in a folder (the folder and a lower-level folder of the folder) set as the upload source folder in the file storage unit 105, that is, the upload source folder registered in the setting management table. Then, the storage management unit 113 monitoring access to the file storage unit 105 detects it and notifies the upload management unit 114 (S1).

  Upon receiving the above notification, the upload management unit 114 acquires information indicating the upper limit value of the number of files to be stored in the root folder of the upload destination folder from the file information storage unit 106 (S2). Specifically, based on the setting management table stored in the file information storage unit 106, the upload destination folder corresponding to the folder (upload source folder) in which the newly created file is stored in the file storage unit 105 is stored. Get the path. Further, based on the upper limit setting table stored in the file information storage unit 106, the upper limit of the number of files stored in the root folder of the upload destination folder is acquired.

  Also, the upload management unit 114 causes the file management server 300 to transmit a folder information acquisition request for the upload destination folder via the communication control unit 115 and the communication unit 107, and acquires the folder information of the upload destination folder (S3). The folder information indicates information indicating the number of files stored in the root folder of the upload destination folder, information indicating the update date and time of each file stored in the root folder, and whether or not there is an archive folder Contains information.

  Next, the upload management unit 114 determines that the number of files stored in the root folder of the upload destination folder is based on the upload setting information acquired in S2 and the folder information of the upload destination folder acquired in S3. It is determined whether or not the upper limit set for is reached (S4).

  If it is determined in S4 that the number of files stored in the root folder of the upload destination folder has not reached the upper limit value (below the upper limit value), the upload management unit 114 determines that the newly created file is the upload destination folder. Is uploaded to the root folder (S5). That is, the upload management unit 114 sends the newly created file and a processing request for saving the file in the root folder of the upload destination folder to the file management server 300 via the communication control unit 115 and the communication unit 107. Send.

  On the other hand, when it is determined in S4 that the number of files stored in the root folder of the upload destination folder has reached the upper limit value (greater than the upper limit value), the upload management unit 114 has an archive folder in the upload destination folder. It is determined whether it has been created (S6).

  If the archive folder has not been created in S6, the upload management unit 114 sends a processing request for creating an archive folder in the lower hierarchy of the root folder of the upload destination folder via the communication control unit 115 and the communication unit 107. The file is transmitted to the file management server 300 (S7).

  When it is determined in S6 that an archive folder has been created, and after sending an archive folder creation processing request in S7, the upload management unit 114 selects the files stored in the root folder of the upload destination folder. Then, a processing request for moving the file with the oldest update date and time to the archive folder is transmitted to the file management server 300 via the communication control unit 115 and the communication unit 107 (S8).

  Thereafter, the upload management unit 114 uploads the newly created file to the archive folder in the upload destination folder (S9). That is, the upload management unit 114 sends the newly created file and a processing request for saving the file in the archive folder of the upload destination folder via the communication control unit 115 and the communication unit 107. Send to.

  After performing the processing of S5 or S9, the upload management unit 114 determines whether the file to be uploaded is stored (depending on whether it is stored in the root folder of the upload destination folder or in the archive folder). Then, the upload file management table (table in which the upload source file path and the upload destination folder path are associated) stored in the file information storage unit 106 is updated (S10).

  FIG. 7 is an explanatory diagram showing an example of an upload file management table. As shown in this figure, in the upload file management table, the file path of the upload source file (the storage destination path of the file in the terminal device 100) and the upload destination folder path of the file (the file in the file management server 300) Are stored in association with each other.

  Thereafter, the upload management unit 114 determines whether or not there is a next new file (S11), and when there is a next new file, the process returns to S1. If there is no next new file, the process is terminated.

  FIG. 8 is an explanatory diagram showing an example of the folder structure of the upload destination folder. In the example shown in this figure, a plurality of archive folders are created according to the update date and time. Note that a sequential number may be used as the folder name of each archive folder, or the update date and time of a file stored in the folder may be used.

  Further, when a file is moved from the root folder of the upload destination folder to the archive folder, it may be moved to the archive folder corresponding to the update date and time of the file to be moved. Further, when there is no archive folder corresponding to the update date and time of the file to be moved, an archive folder corresponding to the update date and time may be created and moved to the folder.

  In the present embodiment, the configuration has been described in which when the number of files to be saved in the root folder of the upload destination folder reaches the upper limit value, the file with the oldest update date / time is saved in the archive folder. Alternatively, a file to be stored in the archive folder may be determined based on other attribute information. Examples of the other attribute information include information indicating a keyword or priority set by the user.

(1-4. Processing when updating a file)
FIG. 9 is a flowchart showing a flow of processing when a file stored in the upload source folder in the terminal device 100 is updated and the file is automatically uploaded to the file management server 300.

  10 is a flowchart showing a processing flow when a newly created file (newly saved in the file storage unit 105) in the terminal device 100 is automatically uploaded to the file management server 300 and saved (backed up).

  Storage management that monitors access to the file storage unit 105 when a file stored in the folder set as the upload source folder in the file storage unit 105 (the folder and a lower-level folder of the folder) is updated. This is detected by the unit 113 and notified to the upload management unit 114 (S21).

  Upon receiving the above notification, the upload management unit 114 acquires information indicating the upload destination folder of the updated file from the upload file management table stored in the file information storage unit 106 (S22). It is determined whether it is a root folder (S23).

  If it is determined in S23 that the file is the root folder of the upload destination folder, the upload management unit 114 uploads the updated file to the root folder, and overwrites the file before update of the file stored in the root folder. (S24).

  On the other hand, if it is determined in S23 that it is not the root folder of the upload destination folder (is an archive folder), the upload management unit 114 selects a pre-update file corresponding to the updated file stored in the archive folder. It is deleted (S25).

  The upload management unit 114 moves the file with the oldest update date among the files stored in the root folder to the archive folder (S26), and uploads the updated file to the root folder (S27). .

  After performing the processing of S24 or S27, the upload management unit 114 updates the upload file management table stored in the file information storage unit 106 according to the processing results of S24 to S27 (S28).

  Thereafter, the upload management unit 114 determines whether or not there is a next update file (S29). If there is a next update file, the process returns to S21. If there is no next update file, the process ends.

  In the present embodiment, the first folder, which is a folder for saving a file that has been updated in the backup source folder and a file that has been updated in the backup source folder, is designated as the backup destination folder. The root folder is an archive folder that stores files that cannot be saved in the root folder when the number of files to be saved in the first folder reaches the upper limit. It is not limited to. For example, the first folder may be provided in the lower hierarchy of the root folder of the backup destination folder, and the archive folder may be provided in the lower hierarchy of the first folder or in the same hierarchy as the first folder.

(1-5. Summary)
A file management system 1 according to an aspect of the present invention includes a terminal device 100 and a file management server (server device) 300 that backs up and saves a file stored in the terminal device 100, and a backup provided in the terminal device 100. An upload management unit (file management unit) 114 that stores a file stored in the original folder in a first folder (root folder) in a backup destination folder provided in the file management server 300 in association with the backup source folder; The upper limit of the number of files that can be stored in the first folder is preset, and the upload management unit 114 stores the file in the first folder when the file is stored in the backup source folder. The number of saved files is less than the above upper limit In some cases, the files stored in the backup source folder are backed up and stored in the first folder. When the number of files stored in the first folder reaches the upper limit, the files are already stored in the first folder. Among the stored files, a file selected based on a predetermined priority order is moved to an archive folder provided in the backup destination folder, and the file stored in the backup source folder is moved to the first folder. Save.

  As a result, the number of files stored in the first folder of the upload destination folder of the file management server 300 is limited to a preset upper limit value or less, and when the file is stored in the backup source folder of the terminal device 100, The file can be preferentially saved in the first folder. Therefore, the file desired by the user can be easily and quickly found when browsing the backed up file.

  In addition, when the file stored in the backup source folder is updated, and the file before update corresponding to the updated file is stored in the archive folder, the upload management unit 114 deletes the file before update stored in the archive folder, and selects a file selected based on the predetermined priority among the files stored in the first folder. The updated file may be stored in the first folder.

  According to the above configuration, when a file that has been backed up is updated, regardless of whether the pre-update file of the file is stored in the first folder or the archive folder, The file can be saved in the first folder. As a result, a file desired by the user can be easily and quickly found when browsing the backed up file.

  The priority order is set based on the update date and time of the file. When the upload management unit moves the file from the first folder to the archive folder, A configuration may be adopted in which the file with the oldest update date is moved to the archive folder.

  According to the above configuration, a number of files equal to or less than the upper limit value are stored in the first folder in order from the file with the latest update date. As a result, a file desired by the user can be easily and quickly found when browsing the backed up file.

  In addition, the upload management unit 114 provides a plurality of the archive folders associated with different file attribute information, and moves the files stored in the first folder to the archive folder. It is good also as a structure which moves to the folder for archive corresponding to the file attribute information of the said file.

  According to the above configuration, the file to be moved to the archive folder can be stored in a different archive folder for each file attribute. Therefore, when browsing the backed up file, the user can easily and quickly find the desired file. Can be found.

  The first folder may be a root folder of the upload destination folder, and the archive folder may be a lower hierarchy folder of the root folder.

  According to the above configuration, the archive folder is provided in the lower hierarchy of the first folder. Therefore, even when the file desired by the user is stored in the archive file, the file desired by the user can be easily and easily stored. Can be found quickly.

  The present invention is not limited to the above-described embodiments, and various modifications can be made within the scope shown in the claims. That is, embodiments obtained by combining technical means appropriately modified within the scope of the claims are also included in the technical scope of the present invention.

  The present invention can be applied to a file management system that performs backup storage of files.

1 File Management System 100 Terminal Device 101 Display Unit 102 Operation Input Unit 103 Application Storage Unit 104 Terminal Control Unit 105 File Storage Unit 106 File Information Storage Unit 107 Communication Unit 111 UI Control Unit 112 Application Processing Unit 113 Storage Management Unit 114 Upload Management Unit 115 Communication Control Unit 200 Network 300 File Management Server (Server Device)
301 communication unit 302 server control unit 303 file storage unit

Claims (7)

A file management method of the terminal device for backing up and saving a file saved in the terminal device to a server device ,
Including a file management step of backing up and saving a file stored in a backup source folder provided in the terminal device in a first folder in a backup destination folder provided in the server device in association with the backup source folder ,
When the file stored in the backup source folder is updated, the file before update corresponding to the updated file is stored in the archive folder provided in the backup destination folder. If
It said file management step causes the delete the pre-update file stored in the archive folder, the file management method updated the file, characterized in Rukoto is stored in the first folder. The file management method according to claim 1, wherein an upper limit value of the number of files that can be stored in the first folder is set in advance in the first folder. When the file stored in the backup source folder has been updated, and the pre-update file corresponding to the updated file is stored in the archive folder,
The file management step,
Of the files stored in the first folder, the file management method according to the file that is selected based on Jo Tokoro priority to claim 1 or 2, characterized in that Before moving to the folder for the archival . The above priority is set based on the update date of the file,
In the file management step , when the file is moved from the first folder to the archive folder, the file having the oldest update date is moved to the archive folder among the files stored in the first folder. The file management method according to claim 3 . A plurality of the above-mentioned archive folders associated with different file attribute information are provided,
The file management step , when moving a file stored in the first folder to the archive folder, moves the file to an archive folder corresponding to file attribute information of the file. 5. The file management method according to any one of 1 to 4 . The first folder is the root folder of the backup destination folder, the file management method according to any one of claims 1 to 5 said archive folder which is a lower hierarchy folder of the root folder . A file management system comprising a terminal device and a server device that backs up and saves a file stored in the terminal device,
A file management unit that stores a file stored in a backup source folder provided in the terminal device in a first folder in a backup destination folder provided in the server device in association with the backup source folder;
When the file stored in the backup source folder is updated, the file before update corresponding to the updated file is stored in the archive folder provided in the backup destination folder. If
The file management system, wherein the file management unit deletes the pre-update file stored in the archive folder and stores the updated file in the first folder.

Images