JP2014238669A - Thin client terminal device and data backup control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To achieve both user convenience and data protection in a user's terminal.SOLUTION: Proposed is a thin client terminal device including: a first storage unit storing therein information indicating at least either a specific operation or a specific application; and a determination unit determining whether to transmit data relating to a write instruction to a server device on the basis of determining whether the write instruction to write data to a write-prohibited nonvolatile second storage unit is by execution of the specific operation or the specific application indicated by the information.

Description

  The present invention relates to a thin client terminal device and a data backup control program.

  The OS of the PC is provided with a storage unit (hereinafter referred to as a built-in disk) in which data relating to the user's operating environment (storage data) such as the background color of the PC screen is stored. In order to prevent such data leakage and the like, a method of saving data for storage has been proposed (see, for example, Patent Document 1).

  In addition, when data is written to the built-in disk, falsified data or virus-infected data may be stored in the built-in disk. In response to a write instruction to the internal disk, data relating to the write instruction is stored in a volatile memory instead of being written to the internal disk.

JP 2009-176001 A

  However, the data stored in the volatile memory is valid only from the startup to the shutdown of the PC, and is erased and invalidated at the time of restart. For this reason, the user cannot use the PC under the operating environment used at the time of the previous startup after the restart. On the other hand, the user may want to continue to use the same operating environment as at the previous activation even after rebooting.

  On the other hand, the data stored in the volatile memory is only used temporarily, such as Notepad, and is not required after restart, and it is also required after restart, such as the work file being created. There is something. If all the data stored in the volatile memory can be used even after the restart, there arises a problem that unnecessary data and data that is not intended by the administrator from the viewpoint of security are valid at the time of restart.

  Therefore, an object of one aspect is to enable both user convenience and data protection in a user terminal.

One idea is that
A first storage unit that stores information indicating at least one of a specific operation and a specific application;
In response to a write instruction to the nonvolatile second storage unit in which writing is prohibited, the write instruction is based on whether the write instruction is a specific operation indicated by the information or execution of a specific application. A determination unit that determines whether or not to transmit the data according to the server device;
A thin client terminal device is provided.

  According to one aspect, it is possible to achieve both user convenience and data protection in the user terminal.

1 is an overall configuration example of a system according to an embodiment. The figure for demonstrating an example of the storage place of data. 1 is a hardware configuration example of a thin client terminal device and a storage server device according to an embodiment. 1 is a functional configuration example of a thin client terminal device and a storage server device according to an embodiment. The figure which showed an example of the environment file which concerns on one Embodiment. The figure which showed the whole flow of the backup control process (at the time of restoration) of the data which concerns on one Embodiment. The figure which showed an example of the identification table which concerns on one Embodiment. The figure which showed the whole flow of the backup control process (at the time of backup) of the data which concerns on one Embodiment. The flowchart which showed operation | movement of the thin client terminal device which concerns on one Embodiment. The flowchart which showed the operation example (whole backup) of the preservation | save server apparatus which concerns on one Embodiment. The flowchart which showed the operation example (sequential backup) of the preservation | save server apparatus which concerns on one Embodiment. The flowchart which showed the operation example (at the time of a restore) of the preservation | save server apparatus which concerns on one Embodiment. The figure for demonstrating an example of the storage place of the data which concerns on one Embodiment.

  Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, the duplicate description is abbreviate | omitted by attaching | subjecting the same code | symbol.

[System overall configuration]
In a thin client system, a thin client terminal device requests a predetermined process (for example, a spreadsheet process or a screen generation process) from a virtual server device (thin client server device), and executes a process according to the request on the virtual server device side. However, the thin client terminal device is provided with the execution result (for example, a spreadsheet result or a generated screen).

A specific description will be given with reference to the overall configuration example of the system according to the embodiment shown in FIG. The thin client system is indicated by Sys1 in FIG. Taking screen generation processing as an example, in the thin client system, processing is executed in the following order of S1 to S4.
S1: The thin client terminal device 10 transfers the key code operated on the thin client terminal device 10 to the virtual server device 15, and requests generation of a screen corresponding to the key code.
S2: The virtual server device 15 operates an application on the virtual server device 15 based on the key code received from the thin client terminal device 10.
S3: The virtual server device 15 transfers the screen transition generated by executing the application on the virtual server device 15 to the thin client terminal device 10.
S4: The thin client terminal device 10 displays the screen image transmitted from the virtual server device 15 on the screen.

Here, in S <b> 5, the thin client terminal device 10 changes the data for setting the operation environment on the user terminal when the user changes the setting of the background color of the screen. Therefore, in the data backup control system Sys2 according to the present embodiment, the changed data is stored in the storage server device 20 in a predetermined case as shown in S6 and S7.
S6: When a change occurs in the data for setting the operation environment in the user's terminal due to the specific operation or the execution of the specific application, the thin client terminal device 10 instructs the storage server device 20 to store the changed data. . Specific operations or specific applications will be described later.
S7: The storage server device 20 stores the change data in the storage server device 20 in response to an instruction from the thin client terminal device 10.

  The storage server device 20 is an example of a server device that temporarily saves change data. In the present embodiment, the virtual server device 15 and the storage server device 20 may be the same server device. However, if the virtual server device 15 and the storage server device 20 are configured by different server devices, the processing load of each server device can be distributed.

  As described above, in the present embodiment, the change data is stored in the storage server device 20 as shown in S6 and S7. The change data shown in S6 and S7 is generated in response to a writing instruction from the software when the user changes the setting of the operating environment such as the background color of the PC screen or when a specific application is executed, for example. To do. Before describing the details of saving the change data shown in S6 and S7, an example of saving the change data will be described with reference to FIG. The left side of FIG. 2 shows modified data storage example 1, and the right side of FIG. 2 shows modified data storage example 2.

[Saved data example 1, 2]
The OS of a terminal device such as a PC is provided with a built-in disk in which initial data relating to the operating environment of the user's PC, such as the background color of the screen, is stored. The built-in disk is realized by, for example, a CF (Compact Flash) card, an SDD (Super Density Disc), and an HDD (Hard Disc Drive).

(Change data storage example 1)
In the case of the change data storage example 1, the data related to the user's operating environment is stored as follows at each time point A to D.

A. When the OS is started The OS of the terminal device reads data stored in the internal disk when it is started (logged in). At this time, the data stored in the internal disk is data in the initial state of the OS regarding the user's operating environment.

B. Write instruction from software by executing a specific operation or a specific application If a write instruction is received from software that accepts an input operation or executes an application program by executing a specific operation or a specific application, the write instruction Such data is stored in the internal disk. At this time, the data stored in the built-in disk is data in the initial state and change data related to the user's operating environment.

C. When the OS is terminated When the OS of the terminal device is terminated (logout), the data stored in the internal disk is retained as it is.

D. When the OS is restarted When the OS of the terminal device is restarted (at the time of re-login), the data stored in the internal disk is read. At this time, the data stored in the built-in disk is OS initial state data and change data related to the user's operating environment.

  In the case of the change data storage example 1, since the change data is written to the internal disk, there is a possibility that tampered data or virus-infected data is stored in the internal disk.

(Example 2 of saving change data)
Therefore, in change data saving example 2, in response to a write instruction to the internal disk, the data related to the write instruction is stored in the volatile main memory instead of being written to the internal disk. In the case of the change data storage example 2, the data related to the user's operating environment is stored as follows at each time point A to D.

A. When the OS is started The OS of the terminal device reads data stored in the built-in disk when the OS is started. At this time, the data stored in the internal disk is data in the initial state of the OS regarding the user's operating environment.

B. Write instruction from software by execution of specific operation or specific application When there is a write instruction from software by execution of specific operation or specific application, the data related to the write instruction is stored in volatile main memory . At this time, the data stored in the built-in disk is retained as the initial data regarding the user's operating environment.

C. When the OS is terminated When the OS of the terminal device is terminated, the data stored in the internal disk is held as it is. Data stored in the volatile main memory is erased.

D. When the OS is restarted When the OS of the terminal device is restarted, it reads the data stored in the internal disk. At this time, the data stored in the internal disk remains the data in the initial state of the OS related to the user's operating environment.

  In the case of the change data saving example 2, the change data stored in the volatile main memory can be used in the same manner as when the change data is saved in the built-in disk from the time of OS startup to the shutdown. In this case, data storage in the internal disk is suppressed, and the initial state data is retained in the internal disk. When the terminal device is turned off, the change data stored in the volatile main memory is erased. In other words, the data stored in the volatile main memory is valid from the time when the terminal device is activated until it is shut down, and all data is erased and invalidated at the time of restart. As a result, user operation errors, data that has been intentionally altered, data that has been tampered with, or data that has been infected with a virus that can be included in the volatile main memory cannot be used at the time of restart.

  In the thin client terminal device 10 equipped with the OS having the function of suppressing the writing to the internal disk as in the modified data storage example 2, the system change by the user, virus infection, data It can cope with prohibition of saving.

  However, there are cases where the user wants to use the terminal in the same operating environment as at the time of the previous activation even after the reboot. As an example, there is a case where it is desired to continue to use a temporary change of the operating environment, and there is no need for a permanent setting change of the environment by the administrator.

  On the other hand, the data stored in the volatile main memory is temporarily necessary data such as a memo pad, which is not required after restarting, and after restarting such as a document being created. There is also what you need. Therefore, if all data stored in the volatile main memory can be used after restarting, unnecessary data and data that is not intended by the administrator from the security point of view may be effective at restart. is there.

  Therefore, the thin client terminal device 10 according to the present embodiment temporarily stores data stored in the volatile main memory in the server device when the writing instruction from the software is a specific operation or execution of a specific application. Evacuate. When the OS is restarted, the temporarily saved data is transmitted from the storage server device 20 to the thin client terminal device 10 and restored to the volatile main memory. As a result, data that has been changed by execution of a specific operation or a specific application is used to realize the same operating environment as at the time of the previous startup after the restart, and before the terminal device is turned off. The state of is reproduced. Hereinafter, the thin client terminal device 10 and the data backup control method according to the present embodiment, which enable both user convenience and data protection in the user terminal, will be described.

[Thin client terminal]
The thin client terminal device 10 according to the present embodiment has a function of protecting writing to the internal disk. That is, in response to a write instruction from the software to the internal disk, the thin client terminal device 10 stores the data related to the write instruction in the volatile main memory instead of writing the data to the internal disk. This protects writing to the internal disk and prevents tampering with data in the internal disk.

  The writing instruction from the software is performed when data is saved, a function setting is changed, an application or a driver is installed, or the like. The application executed in the thin client terminal device 10 can use the data stored in the volatile main memory in the same manner as the data stored in the internal disk until the thin client terminal device 10 is shut down. When the thin client terminal device 10 is restarted or shut down, all data stored in the volatile main memory is erased. In the present embodiment, specific data among the data stored in the volatile main memory is temporarily saved in the storage server device 20, and the data saved from the storage server device 20 at the time of restart is acquired, and the main data is acquired. Restore to memory. Thereby, for example, even when the OS is restarted due to an unexpected power-off, the user can use the terminal in the same operating environment as at the time of the previous startup.

[Hardware configuration]
A hardware configuration example of a thin client terminal device and a storage server device according to an embodiment will be described with reference to FIG. The thin client terminal device 10 and the storage server device 20 are connected via a network 30.

  The thin client terminal device 10 includes a CPU (Central Processing Unit) 11, a network adapter 12, an input device 13, a display device 14, a main memory 15, and a storage 16. The CPU 11 is an arithmetic unit that performs overall control and data backup control by reading programs and data from the storage 16 to the volatile main memory 15 and executing various processes.

  The network adapter 12 is an interface connected to the network 30. The thin client terminal device 10 transmits / receives data to / from other devices such as the storage server device 20 using the network adapter 12.

  The input device 13 includes a keyboard, a mouse, and the like, and is operated when the user requests to change the operation environment such as the background color of the screen or to execute a desired application. The display device 14 includes a display and displays a desktop screen or the like.

  The main memory 15 is a volatile memory that temporarily stores programs and data, and is realized by a RAM (Random Access Memory) or the like. The main memory 15 stores data related to a write instruction instead of saving to the internal disk in response to a write instruction to the internal disk from software.

  The storage 16 is a non-volatile memory, and is realized by, for example, a CF card, an SDD, or an HDD. The storage 16 is provided with a built-in disk. The internal disk is realized by, for example, a CF card or an SDD, and stores initial state data regarding the user's operating environment such as the background color of the screen. The HDD stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the thin client terminal device 10 is activated.

  The storage server device 20 includes a CPU 21, a network adapter 22, a main storage unit 23, and an auxiliary storage unit 24. The CPU 21 is an arithmetic unit that implements control of the entire apparatus and data backup control by reading out programs and data stored in the auxiliary storage unit 24 to the main storage unit 23 and executing various processes, for example.

  The network adapter 22 is an interface connected to the network 30. Thereby, the storage server device 20 transmits / receives data to / from other devices such as the thin client terminal device 10 using the network adapter 22.

  The main memory unit 23 is a volatile memory that temporarily stores programs and data, and is realized by a RAM (Random Access Memory) or the like. The auxiliary storage unit 24 stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the storage server device 20 is activated. The auxiliary storage unit 24 temporarily stores change data transmitted from the thin client terminal device 10.

[Function configuration]
Next, a functional configuration example of a data backup control system according to an embodiment will be described with reference to FIG. In the backup control system according to the present embodiment, the thin client terminal device 10 includes a terminal-side control unit 31, a program execution unit 32, a first storage unit 33, a determination unit 34, a terminal-side transmission unit 35, and a terminal-side reception unit 36. , An input unit 37, a second storage unit 38, and a third storage unit 39.

  The terminal-side control unit 31 controls the entire thin client terminal device 10. The program execution unit 32 executes various application programs.

  The first storage unit 33 stores an environment file. The environment file stores information indicating a specific operation and / or a specific application.

  FIG. 5 shows an example of a specific operation and a specific application set in the environment file 45 stored in the first storage unit 33. In the environment file 45, information indicating a specific operation or a specific application is set by a user or an administrator on the server side. Examples of specific operations set in the environment file 45 include power management, screen wallpaper (background color) change, IP address setting, and specific file change. As an example of a change in a specific application set in the environment file 45, there are a setting, a work file, and a temporary file. In addition to these setting items, the administrator can newly set information indicating a specific operation and a specific application in the environment file 45, change the set information, or delete the set information.

  The second storage unit 38 has a built-in disk that stores data for which writing is prohibited. As described above, initial state data relating to the user's operating environment is stored in the internal disk.

  The data in the environment file 45 stored in the first storage unit 33 needs to be stored in a storage area where the data is not deleted even after restarting. For this reason, the data in the environment file 45 is stored in the internal disk in a state where the prohibition of writing to the internal disk is once canceled.

  The third storage unit 39 can be realized by the volatile main memory 15. The third storage unit 39 stores data relating to the write instruction instead of writing to the internal disk in response to the write instruction from the software to the internal disk. In the present embodiment, writing to the internal disk of the second storage unit 38 is prohibited.

  In response to the write instruction to the internal disk, the determination unit 34 determines whether to transmit the data related to the write instruction to the storage server device 20 based on whether the write instruction is a specific operation or execution of a specific application. judge.

  When the write instruction is a specific operation or execution of a specific application, the terminal-side transmission unit 35 transmits data (backup data) related to the write instruction to the storage server device 20. Thereby, even after restarting the thin client terminal device 10 like data for changing the wallpaper (background color) of the screen from the data stored in the third storage unit 39 or a work file being created. Necessary change data can be saved in the storage server device 20. When the thin client terminal device 10 is restarted, the saved data is acquired from the storage server device 20 and restored to the third storage unit 39, so that a specific operation environment that the user wants to use can be used even after the restart. Become.

  Further, among the data stored in the third storage unit 39, for example, data that is temporarily used, such as a memo pad, but is not required after restarting, is not saved in the storage server device 20, Those data are deleted when the thin client terminal device 10 is shut down so that it cannot be used when the thin client terminal device 10 is restarted. Thereby, it is possible to avoid unnecessary data and data not intended by the administrator from the viewpoint of security being valid at the time of restart.

  The terminal side receiving unit 36 receives the backup data saved in the storage server device 20. The input unit 37 receives a user's specific operation. For example, the input unit 37 accepts a change in the operating environment setting requested by the user in response to a user operation using a keyboard or a mouse.

  The storage server device 20 includes a server-side control unit 41, a server-side reception unit 42, a server-side transmission unit 43, and a data storage unit 44. The server-side control unit 41 controls the entire storage server device 20.

  The server-side receiving unit 42 receives backup data to be saved in the storage server device 20 from the thin client terminal device 10. The server side transmission unit 43 transmits the backup data to the thin client terminal device 10. The data storage unit 44 stores the backup data received by the server side receiving unit 42.

Backup control processing (during restoration)]
Next, the data backup control process at the time of restoration according to the present embodiment will be described with reference to FIG. 6, and then the data backup control process at the time of backup will be described. FIG. 6 is a diagram showing an overall flow of the data backup control process (during restoration) according to an embodiment. The left side of FIG. 6 shows the operation of the thin client terminal device 10, and the right side of FIG. 6 shows the operation of the storage server device 20.

  In the thin client terminal device 10, data storage in the internal disk is suppressed, and the data is temporarily stored in the storage server device 20 before the function of storing the changed data in the third storage unit 39 (main memory) is enabled. The backup data is restored to the third storage unit 39.

  The specific process will be described. When the power is turned on, the OS is started from the second storage unit 38 (step S10). The OS reads the data of the initial state of the OS related to the user's operation environment from the internal disk, and sets the user's operation environment. After starting the OS in step S10, the program execution unit 32 starts the agent (step S11). The agent is also activated in the storage server device 20 (step S51). The agent monitors the state of the OS and the state of the third storage unit (main memory) 39.

  Next, the terminal-side control unit 31 starts a connection with the storage server device 20 via the network 30 (step S12). Receiving this, the server side control part 41 performs a connection process with the thin client terminal device 10 (step S52). When the connection is established, the terminal-side control unit 31 accepts a user login operation (step S13). The terminal-side control unit 31 confirms whether or not the user who performed the login operation has joined the domain (step S14). When the user is participating in the domain, the terminal-side control unit 31 identifies the logged-in user with the domain name and the user name (Step S15).

  In that case, the terminal-side control unit 31 uses the data management table 50 stored in the data storage unit 44 of the storage server device 20. The data management table 50 in FIG. 7A stores a MAC address 51, a domain name 52, a user name 53, a changed file name 54, a path 55, and a backup data storage destination 56 to the storage server device 20. . In step S15, the terminal-side control unit 31 identifies the backup data storage destination 56 in the storage server device 20 from the domain name 52, the user name 53, and the login information in the data management table 50 shown in FIG. To do.

  On the other hand, when the user has not joined the domain, the terminal-side control unit 31 identifies the data by the MAC address (step S16). In that case, the data management table 50 shown in FIG. 7B is used. The data management table 50 in FIG. 7B stores a MAC address 51, a user name 53, a changed file name 54, a path 55, and a backup data storage destination 56 to the storage server device 20. In step S <b> 16, the terminal-side control unit 31 sets the backup data storage destination 56 in the storage server device 20 from the MAC address 51 of the data management table 50 shown in FIG. 7B and the identification information of the logged-in terminal device. Identify.

  Next, the terminal-side control unit 31 requests confirmation of whether the changed data (backup data) is stored in the backup data storage location 56 specified in step S15 or step S16 (step S17). In response to this, the server-side control unit 41 confirms whether the changed data (backup data) is stored in the specified backup data storage location 56, and notifies the thin client terminal device 10 of the result (step). S53).

  The terminal side transmission unit 35 determines whether the change data is stored in the storage server device 20 (step S18). When notified that the change data exists in the storage location 56, the terminal-side transmission unit 35 determines that the change data is stored, and transmits a transfer request for the change data of the specific storage location 56 to the storage server device 20. (Step S19). When receiving the transfer request, the server-side transmission unit 43 transfers the change data of the specific storage location 56 (step S54).

  The terminal-side receiving unit 36 receives the transferred change data, and the terminal-side control unit 31 overwrites the transferred storage data on the third storage unit 39 (main memory). As a result, the operating environment of the user is set by the OS at the next login based on the internal disk data of the second storage unit 38 and the change data of the third storage unit 39 (main memory). In this state, the UI is displayed, and the operation of the terminal device is started (step S21).

Backup control processing (during backup)]
Next, data backup control processing (during backup) according to the present embodiment will be described with reference to FIG. FIG. 8 is a diagram showing an overall flow of data backup control processing (during backup) according to an embodiment. The left side of FIG. 8 shows the operation of the thin client terminal device 10, and the right side of FIG. 8 shows the operation of the storage server device 20.

  When the thin client terminal device 10 starts UI display and operation (step S30), the thin client terminal device 10 is operated by the user (step S31). When a data change occurs according to the operation of the thin client terminal device 10, the program execution unit 32 instructs to write the generated changed data (step S32). On the other hand, in the present embodiment, the change data instructed to be written is written in the third storage unit (main memory) 39 by the function of protecting the data in the internal disk of the second storage unit 38 ( Step S33).

  Next, based on the environment file 45, the determination unit 34 determines whether the change data write instruction is due to a specific operation or execution of a specific application (step S34). If the write instruction is due to a specific operation or execution of a specific application, the terminal-side transmitting unit 35 transmits change data related to the write instruction to the storage server device 20 (step S35).

  The server-side receiving unit 42 receives change data related to a write instruction. The server-side control unit 41 stores the received change data (backup data) in the data storage unit 44 (step S61). The server side transmission unit 43 notifies the thin client terminal device 10 that the backup of the changed data has been completed (step S62).

  In the thin client terminal device 10, the terminal-side control unit 31 determines whether shutdown is requested (step S36). If shutdown is not requested, the process returns to step S31 and continues processing. When the shutdown is requested, the terminal side transmission unit 35 notifies the storage server device 20 of the end of the change data transmission process (step S37). Thereafter, the terminal side control unit 31 shuts down the OS (step S38).

  When the storage server device 20 receives the change data transmission processing end notification, the storage server device 20 ends the change data storage processing from the thin client terminal device 10 (step S63).

  By the data backup control process described above, necessary change data can be saved from the data stored in the third storage unit (main memory) 39 to the storage server device 20 even after rebooting. Examples of the change data necessary after the restart include data for changing the wallpaper (background color) of the screen and a work file being created. At the time of restart, the thin client terminal device 10 acquires the data saved from the storage server device 20 and restores it to the third storage unit 39, so that the user can use it at the previous start-up even after the restart. The operating environment that was being used can be used continuously.

[Operation of thin client terminal]
Next, the operation of the thin client terminal device will be described with reference to FIG. FIG. 9 is a flowchart showing the operation of the thin client terminal device according to the embodiment.

  When the OS of the thin client terminal device 10 is activated, the terminal-side control unit 31 determines whether the storage server device 20 is accessible (step S110). When it is determined that access is possible, the terminal-side control unit 31 determines whether a data change has occurred in the third storage unit (main memory) 39 (step S111). The terminal-side control unit 31 repeats step S111 until a data change occurs in the third storage unit 39. If a change occurs, the terminal-side control unit 31 determines whether the storage server device 20 is accessible (step S112). If it is determined that access is not possible at this point, the process proceeds to step S117. The processing after Step S117 is processing in the case of offline (impossible access to the storage server device), which will be described later. If it is determined that access is possible at this point, the process proceeds to step S113, and online processing (access to the storage server device is possible) is performed. In step S <b> 113, the terminal-side control unit 31 creates a backup file that stores the data stored in the third storage unit 39 as backup data, and transmits the backup file to the storage server device 20.

  Next, the terminal-side control unit 31 determines whether an OS shutdown and reboot operation has been performed (step S114). When there is no OS shutdown and reboot operation, the process returns to step S111, and the online processing of S111 to S114 is repeated. On the other hand, when there is an OS shutdown and reboot operation, the terminal-side transmission unit 35 notifies the storage server device 20 of the end of the data backup processing (step S115), and the terminal-side control unit 31 shuts down the OS ( Step S116).

  If it is determined in step S110 or step S112 that the storage server device 20 cannot be accessed, and if the OS shutdown and reboot operations match in step S117, the process proceeds to step S118, and the terminal-side control unit 31 Executes interrupt processing and temporarily stops OS shutdown processing. Next, the terminal side control unit 31 determines whether or not the storage server device 20 is accessible (step S119). If it is determined that access is possible at this point, the process proceeds to step S120, where the terminal-side transmission unit 35 creates a backup file of the data stored in the third storage unit 39 and transmits the backup file to the storage server device 20. Next, the terminal-side control unit 31 cancels the interrupt process and restarts the OS shutdown process (step S121).

  On the other hand, if it is determined in step S119 that the storage server device 20 cannot be accessed, the terminal-side control unit 31 initializes the third storage unit 39 by deleting the data stored in the third storage unit 39. It is determined whether or not it can be changed (step S124). When it is determined to initialize the third storage unit 39, the terminal-side control unit 31 proceeds to step S121, cancels the interrupt process, and restarts the OS shutdown process. On the other hand, if it is determined in step S124 that the third storage unit 39 is not initialized, the terminal-side control unit 31 cancels the OS shutdown process (step S125) and holds the OS startup (step S126). ).

  When the reboot operation and the OS startup are executed after the interruption is canceled in step S121 (step S122), the terminal-side control unit 31 executes the interruption process again and temporarily stops the OS startup process (step S122). S123). Next, the terminal side control unit 31 determines whether or not the storage server device 20 is accessible (step S127).

  If it is determined that the storage server device 20 is accessible at this time, the process proceeds to step S128, and the terminal side receiving unit 36 receives a backup file of the data stored in the storage server device 20. The terminal-side control unit 31 restores the received backup file data to the third storage unit 39 (step S128). Next, the terminal-side control unit 31 cancels the interrupt process, restarts the OS startup process (step S129), and starts the OS (step S130).

  When it is determined in step S127 that the storage server device 20 cannot be accessed, the terminal-side control unit 31 determines whether the third storage unit 39 may be initialized (step S131). When it is determined that the third storage unit 39 is to be initialized, the terminal-side control unit 31 proceeds to step S129, cancels the interrupt processing, and restarts the OS startup processing. On the other hand, if it is determined in step S131 that the third storage unit 39 is not initialized, the terminal-side control unit 31 cancels the OS restart process (step S132). As a result, the OS is shut down (step S133).

  When the backup file data is restored to the third storage unit 39, the backup file in the predetermined data storage location of the data storage unit 44 of the storage server device 20 is deleted.

  As described above, the thin client terminal device 10 according to the present embodiment transmits the change data to the storage server device 20 whenever there is a change in the data if the connection with the storage server device 20 is established. To do. On the other hand, if the connection with the storage server device 20 is not established, the thin client terminal device 10 cannot send the changed data to the storage server device 20 even if the data is changed. At that time, send the change data at once.

[Full backup]
Next, an example of the operation at the time of backup of the storage server device according to the embodiment will be described with reference to FIG. FIG. 10 is a flowchart illustrating an example of an operation (overall backup) at the time of backup performed by the storage server device according to the embodiment.

  The server side receiving unit 42 receives data of the first (first) backup file (first backup file) from the thin client terminal device 10 (step S140). The data of the first backup file is all of the data stored in the third storage unit 39 and is stored in the data storage unit 44.

  Next, the server-side receiving unit 42 sequentially receives the second and subsequent backup file data from the thin client terminal device 10 (step S141). Here, the n-th (n = 2, 3, 4...) Backup file is the n-th backup file. The data of the nth backup file is data (changed data) that is different from the data stored in the third storage unit 39 when the previous backup file was generated.

  The server-side control unit 41 synthesizes the difference data of the nth backup file with the entire data of the first backup file, generates the latest overall data, and stores it in the data storage unit 44.

  Next, the server-side receiving unit 42 determines whether or not the backup end is notified from the thin client terminal device 10 (step S143). The server-side control unit 41 repeats the processes of steps S141 to S143 until it is determined that the end of backup has been notified, and ends this process when it is determined that the end of backup has been notified.

[Sequential backup]
Next, another example of the operation at the time of backup of the storage server device according to the embodiment will be described with reference to FIG. FIG. 11 is a flowchart illustrating operations (sequential backup) at the time of backup performed by the storage server device according to the embodiment.

  The server side receiving unit 42 receives data of the first (first) backup file (first backup file) from the thin client terminal device 10 (step S140). The data of the first backup file is all of the data stored in the third storage unit 39 and is stored in the data storage unit 44.

  Next, the server-side receiving unit 42 sequentially receives the second and subsequent backup file data from the thin client terminal device 10 (step S141). The data of the n-th (n = 2, 3, 4...) Backup file is the difference data (change data) from the data stored in the third storage unit 39 when the previous backup file was generated. . Next, the server-side control unit 41 stores the n-th backup file in the data storage unit 44 as a separate file from the first backup file (step S150).

  Next, the server-side receiving unit 42 determines whether or not the backup end is notified from the thin client terminal device 10 (step S143). The server-side control unit 41 repeats the processes of steps S141 to S143 until it is determined that the end of backup has been notified, and ends this process when it is determined that the end of backup has been notified.

  In the case of the sequential backup method, the backup files are stored separately without being synthesized. Thereby, the processing load of the storage server device 20 can be reduced.

[restore]
Next, an operation example at the time of restoration of the storage server device according to the embodiment will be described. At the time of restoration, the backup method of the backup data stored in the storage server device 20 is checked to determine the restoration method.

  For example, in the overall backup method shown in FIG. 10, the storage server device 20 creates the latest backup data in which the difference data is combined with the entire data in step S142. Therefore, at the time of restoration, the server-side transmission unit 43 transmits the latest combined backup data to the thin client terminal device 10. The thin client terminal device 10 can restore the backup data to the third storage unit 39 at once.

  In the sequential backup method, the difference data (change data) of the n-th backup file is set to n = 2 with respect to the entire data of the first backup file in the order in which the backup data is created on the thin client terminal device 10 side. By overwriting in order 3, 4,..., The backup data can be restored to the third storage unit 39 in order.

  In the following, the operation performed by the storage server device 20 at the time of restoration in the sequential backup method shown in FIG. 11 will be described with reference to FIG. FIG. 12 is a flowchart illustrating an operation example of the storage server device according to an embodiment (processing at the time of restoration in the sequential backup method).

  At the time of restoration in the sequential backup method, first, the server side transmission unit 43 transmits the first backup data (whole data) to the thin client terminal device 10 (step S160). Next, the server side transmission unit 43 transmits the difference data of the nth (n = 2) th backup to the thin client terminal device 10 (step S161). The server-side control unit 41 determines whether all backup data has been transmitted (step S162). When it is determined that all backup data has not been transmitted, 1 is added to n (step S163), and the process returns to step S161, where the server-side transmission unit 43 determines the difference between the nth (n = 3) backups. Data is transmitted to the thin client terminal device 10.

  On the other hand, if the server-side control unit 41 determines in step S162 that all backup data has been transmitted, this process ends.

[Save changed data]
As described above, the thin client terminal device 10 stores the data stored in the third storage unit 39 when the writing instruction from the software is a specific operation or execution of a specific application. Back up to the device 20. When the OS is restarted, the thin client terminal device 10 acquires the temporarily saved data from the storage server device 20 and restores it to the third storage unit 39. Thereby, a part of the state before the power is turned off is restored.

  A data storage location according to the present embodiment will be described with reference to FIG. In the present embodiment, data related to the user's operating environment is stored as follows at each time point A to D.

A. When the OS is started The OS of the terminal device reads the data stored in the internal disk of the second storage unit 38 at the time of startup (login). At this time, the data stored in the internal disk is data in the initial state of the OS regarding the user's operating environment.

B. Write instruction from software by execution of specific operation or specific application When there is a write instruction from software by execution of a specific operation or specific application, the change data related to the write instruction is stored in the third storage unit 39 (volatile Sex main memory). As a result, the data stored in the built-in disk is retained as the initial data regarding the user's operating environment.

C. When the OS is terminated The OS of the terminal device retains the data stored in the built-in disk as it is when the OS is terminated (logout). Of the data stored in the third storage unit 39 (main memory), the change data relating to writing by execution of a specific operation or specific application set in the environment file 45 (see FIG. 5) is stored in the storage server. The data is saved in the data storage unit 44 (server disk) of the apparatus 20. On the other hand, change data relating to operations not set in the environment file 45 and writing due to execution of an application is stored only in the third storage unit 39 (main memory) and is not stored in the storage server device 20, so the power is shut off. Is erased by.

D. When the OS is restarted When the OS of the terminal device is restarted (at the time of re-login), the data stored in the internal disk is read. The saved backup data is transmitted from the storage server device 20 and restored to the third storage unit 39 (main memory). The storage server device 20 deletes the transmitted backup data from the data storage unit 44.

  As a result, for the data changed by the specific operation or the execution of the specific application, the same operation environment as the previous login can be continuously used even after the restart.

  On the other hand, data that is only temporarily used, such as a memo pad, but is not necessary after rebooting is not data that has been changed by a specific operation or execution of a specific application. Erased. Thereby, unnecessary data after restart can be invalidated at the time of restart. In addition, the administrator on the server side sets a specific application in the environment file 45 so that only the data changed by the execution of the specific application has the same operating environment as at the time of the previous start after the restart. To be able to use. In this way, by allowing only specific data to be used after restarting in the same manner as at the time of the previous startup, it is possible to avoid management problems associated with continuing the operating environment.

  Further, when the terminal is powered off, all data stored in the third storage unit (main memory) is erased. As a result, data not intended by the administrator from the security point of view can be erased and invalidated at the time of restart. In addition, changes to the data in the internal disk of the second storage unit are prohibited. As a result, it is possible to prevent falsified data or virus-infected data from being stored in the thin client device 10. Thereby, in this embodiment, it is possible to achieve both user convenience and data protection in the user terminal.

[Initialize changed data]
It should be noted that by performing a predetermined initialization operation at “C. OS termination” in FIG. 13, the user change data restored in the third storage unit 39 is erased, and the OS is set to the initial state. be able to. As the initialization operation, for example, function keys may be set so that the OS can be initialized by ending the OS while pressing a specific key. In this case, when a specific key is pressed and the OS performs the termination process, the monitoring agent does not acquire the information of the third storage unit (main memory), and the initial value of the third storage unit is kept as it is. To do. As a result, only the contents of the internal disk become valid, and the OS returns to the initial state.

  At the next “D. OS startup”, the data stored in the built-in disk is read by the OS, and all the changed data up to the previous time is cleared.

[Deploy changed data to other terminals]
As an effect other than the above-described effects of the backup control method according to the present embodiment, the change data is developed in another terminal device and can be used in another terminal device. For example, the domain name and user name can be determined when the terminal device logs in. Therefore, when the domain name and the user name used last time are logged in by another thin client terminal apparatus B, the environment used by the previous thin client terminal apparatus A can be used by another thin client terminal apparatus B. it can. Thereby, if the domain name and the user name are the same at the time of login, the same environment can be used even if the thin client terminal device is different.

  The thin client terminal device and the data backup control method have been described above by way of the embodiments. However, the present invention is not limited to the above embodiments, and various modifications and improvements can be made within the scope of the present invention.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
A first storage unit that stores information indicating at least one of a specific operation and a specific application;
In response to a write instruction to the nonvolatile second storage unit in which writing is prohibited, the write instruction is based on whether the write instruction is a specific operation indicated by the information or execution of a specific application. A determination unit that determines whether or not to transmit the data according to the server device;
A thin client terminal device.
(Appendix 2)
A terminal-side transmitter that transmits data related to the write instruction to the server device;
A terminal-side receiving unit that receives data related to the write instruction from the server device;
Have
When the determination unit determines to transmit the data related to the write instruction to the server device, the terminal-side transmission unit transmits all the data related to the write instruction or the difference data from the data related to the previous write instruction And
The terminal-side receiving unit receives the combined data of all the data related to the write instruction and the difference data, or receives all the data and the difference data stored by the server device separately. To
The thin client terminal device according to attachment 1.
(Appendix 3)
A volatile third storage unit that stores the received composite data or the received all data and difference data after the OS of the thin client terminal device is terminated;
A control unit configured to set an operating environment of the thin client terminal device based on data stored in the second storage unit and the third storage unit when the OS of the thin client terminal device is restarted;
The thin client terminal device according to appendix 1 or 2, comprising:
(Appendix 4)
Storing information indicating a specific operation and / or a specific application;
Data related to the write instruction based on whether the write instruction is a specific operation indicated by the information or execution of a specific application with respect to the write instruction to the second storage unit where writing is prohibited To determine whether to transmit to the server device,
A data backup control program that causes a computer to execute processing.
(Appendix 5)
Sending data related to the write instruction to the server device;
Receiving data related to the write instruction from the server device;
Have
When it is determined that the data related to the write instruction is transmitted to the server device, all the data related to the write instruction or difference data from the data related to the previous write instruction is transmitted,
Receive all data and difference data related to the write instruction in a batch, or receive all data and difference data stored by the server device separately,
The data backup control program according to appendix 4, which causes a computer to execute processing.
(Appendix 6)
After the OS of the thin client terminal device ends, the received composite data, or the received all data and difference data are stored in a volatile third storage unit,
When the OS of the thin client terminal device is restarted, an operating environment of the thin client terminal device is set based on data stored in the second storage unit and the third storage unit.
Appendix 4 is the data backup control program according to 5, which causes the computer to execute processing.

  10: Thin client terminal device, 11: CPU, 13: Input device, 14: Display device, 15: Volatile main memory, 16: Storage, 20: Storage server device, 21: CPU, 23: Main storage device, 24 : Auxiliary storage device, 31: terminal side control unit, 32: program execution unit, 33: first storage unit, 34: determination unit, 35: terminal side transmission unit, 36: terminal side reception unit, 37: input unit, 38: Second storage unit, 39: Third storage unit, 41: Server side control unit, 42: Server side reception unit, 43: Server side transmission unit, 44: Data storage unit

Claims (4)

A first storage unit that stores information indicating at least one of a specific operation and a specific application;
In response to a write instruction to the nonvolatile second storage unit in which writing is prohibited, the write instruction is based on whether the write instruction is a specific operation indicated by the information or execution of a specific application. A determination unit that determines whether or not to transmit the data according to the server device;
A thin client terminal device. A terminal-side transmitter that transmits data related to the write instruction to the server device;
A terminal-side receiving unit that receives data related to the write instruction from the server device;
Further comprising
When the determination unit determines to transmit the data related to the write instruction to the server device, the terminal-side transmission unit transmits all the data related to the write instruction or the difference data from the data related to the previous write instruction And
The terminal-side receiving unit receives the combined data of all the data related to the write instruction and the difference data, or receives all the data and the difference data stored by the server device separately. The thin client terminal device according to claim 1. A volatile third storage unit that stores the received composite data or the received all data and difference data after the OS of the thin client terminal device is terminated;
A control unit that sets data stored in the second storage unit and the third storage unit when the OS is restarted;
The thin client terminal device according to claim 1, further comprising: Storing information indicating a specific operation and / or a specific application;
Data related to the write instruction based on whether the write instruction is a specific operation indicated by the information or execution of a specific application with respect to the write instruction to the second storage unit where writing is prohibited To determine whether to transmit to the server device,
A data backup control program that causes a computer to execute processing.

Images