Management device, management method, and management program

Abstract

In a production environment (E1), an autonomous management system (MS) detects a change in a parameter file (PF). In response to detecting a change in the parameter file (PF), the autonomous management system (MS) updates a parameter file (f1) included in a DB container (Cr1) according to the change, and writes content of the change to a parameter table (T1) provided in a database (DB1) included in the DB container (Cr1). In a disaster response environment (E2), an autonomous management system (MS') detects a change in a parameter table (T1') in a database (DB1') included in a DB container (Cr1'). In response to detecting a change in the parameter table (T1'), the autonomous management system (MS') updates a parameter file (PF') according to the change.

Description

Technical Field

[0001] The present invention relates to a management device, a management method, and a management program.

Background Art

[0002] Conventionally, it is important to take disaster countermeasures (disaster prevention) for business systems in preparation for unexpected situations such as natural disasters and human disasters. For example, in a system that requires high availability, a disaster prevention environment is operated separately from the production environment by the hot standby method, and when a disaster occurs, a switch is made from the production environment to the disaster prevention environment. In addition, in order to reduce the cost of system operation management, containerized databases have come to be used.

[0003] As prior art, there is one in which the main database system determines from a query request from a client application that the workload from the query can be shifted to the sub-database system, and instructs the client application to instruct the sub-database system to execute the query. In addition, a token and a unique sequence number are assigned in response to each write operation at the main office, the token and the updated data are transmitted to the remote office, and there is a technique for determining a gap during the sequence to confirm the missing updated data by using the sequence number to determine the order.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] <* However, with conventional technologies, it is difficult to properly manage parameter information related to container management, including databases, which is referenced by a management unit (e.g., an autonomous management system) that manages containers deployed in various environments such as production environments and disaster recovery environments.

[0006] In one aspect, the present invention aims to appropriately manage parameter information related to the management of a container that includes a database. [Means for solving the problem]

[0007] In one embodiment, a management device is provided having a control unit that performs the following processing: In the first environment, among the redundant first and second environments, detects changes in management parameter information related to the management of a first container, including a database, which is referenced by a management unit that manages containers deployed in the first environment; updates control parameter information related to the control of the first container, which is included in and referenced by the first container, in accordance with the change, and writes the content of the change to change history information provided in the database; In the second environment, detects changes in change history information in a database included in a second container, which is deployed in the second environment and synchronized with the first container by a data synchronization function; and updates management parameter information related to the management of the second container, which is referenced by a management unit that manages containers deployed in the second environment, in accordance with the change. [Effects of the Invention]

[0008] According to one aspect of the present invention, it has the effect of enabling appropriate management of parameter information related to the management of a container including a database. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is an explanatory diagram showing one embodiment of the control method according to the embodiment. [Figure 2] Figure 2 is an explanatory diagram showing an example of the system configuration of the information processing system 200. [Figure 3] Figure 3 is a block diagram showing an example of the hardware configuration of the information processing device 201, etc. [Figure 4] Figure 4 is a block diagram showing an example of the functional configuration of the information processing device 201 in the production environment E1. [Figure 5] Figure 5 is a block diagram showing an example of the functional configuration of the information processing device 202 for the disaster response environment E2. [Figure 6] Figure 6 is an explanatory diagram showing an example of the operation of the information processing system 200. [Figure 7] Figure 7 is an explanatory diagram illustrating an example of transaction processing associated with changes to the parameter file PF. [Figure 8] Figure 8 is a sequence diagram showing an example of operation in the production environment E1. [Figure 9] Figure 9 is a sequence diagram showing an example of operation in disaster response environment E2. [Figure 10] Figure 10 is an explanatory diagram showing an example of the contents of the parameter table T1. [Figure 11] Figure 11 is an explanatory diagram showing an example of updating the parameter table T1. [Figure 12] Figure 12 is a flowchart showing an example of the DB container deployment procedure for the information processing device 201 in the production environment E1. [Figure 13] Figure 13 is a flowchart showing an example of the management process procedure for the information processing device 201 in the production environment E1. [Figure 14] Figure 14 is a flowchart showing an example of the management processing procedure for the information processing device 202 of the disaster response environment E2. [Figure 15] Figure 15 is a flowchart showing an example of the promotion process procedure for the information processing device 202 of the disaster response environment E2. [Figure 16] Figure 16 is an explanatory diagram showing examples of container deployment in various environments. [Figure 17] Figure 17 is an explanatory diagram showing a specific example of a parameter file PF.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of a management device, a management method, and a management program according to the present invention will be described in detail with reference to the drawings.

[0011] (Embodiment) FIG. 1 is an explanatory diagram showing an example of a management method according to an embodiment. In FIG. 1, a management device 101 is a computer that manages containers. A container is equivalent to an isolated user space created by partitioning the kernel of an OS (Operating System) internally and operates as one of the processes of the OS.

[0012] For example, a container is a package that combines an application, middleware, libraries, etc. Each container is controlled, for example, based on a parameter file. Since general application containers operate independently, even if a container goes down during the execution of a process, the same process can be executed according to the parameter file.

[0013] On the other hand, there are cases where not only applications but also databases (DBs: Databases) are containerized. A DB container (database container) has data, unlike an application container, and thus is required to be continuously operated. For this reason, controls such as synchronizing data among multiple DB containers, such as deploying the database in a redundant configuration, are performed.

[0014] Conventionally, in order to reduce the costs associated with the operation and management of containers, there are container orchestration tools for automatically performing management such as container deployment and scaling. As a container orchestration tool, for example, there is Kubernetes (k8s). Kubernetes is a registered trademark.

[0015] Furthermore, when building business systems in a Kubernetes environment, there is a technology (autonomous management system) that creates, modifies, and deletes parameter files for each container based on a parameter file that centrally manages the settings of the business system. The parameter file contains, for example, container configuration information and database settings (e.g., authentication information such as passwords). In addition, the autonomous management system may autonomously determine the optimal parameters according to the operational status of the business system and reflect them in the container.

[0016] Therefore, it is important to implement disaster recovery measures for business systems in order to ensure business continuity even in the event of unforeseen circumstances such as natural or man-made disasters. For example, one approach is to use a hot standby method to operate a disaster recovery environment separately from the production environment, and then switch from the production environment to the disaster recovery environment in the event of a disaster, thereby ensuring business continuity.

[0017] On the other hand, in business systems that utilize containers including databases, it is necessary to have the same parameter files and data in both the production and disaster recovery environments in order to perform operations equivalent to those in the production environment during a disaster. For example, the database itself is synchronized using methods such as streaming replication.

[0018] Streaming replication is a technology for synchronizing data in real time. With streaming replication, not only the database data itself, but also the parameter information reflected in the database, is synchronized. For example, by transferring database update information from the production environment to the disaster recovery environment in real time, it becomes possible to maintain the same state for the databases in both the production and disaster recovery environments.

[0019] Furthermore, in business systems within a Kubernetes environment, autonomous management systems manage containers based on parameter files. Therefore, it is conceivable to create a backup of the parameter files referenced by the autonomous management system in the production environment and restore it to the disaster recovery environment, thereby maintaining the same parameter files in the disaster recovery environment as in the production environment.

[0020] Existing technologies for maintaining the same parameter files in the disaster recovery environment as in the production environment include, for example, backup and restore tools that periodically back up and restore the entire Kubernetes environment. There are also centralized management tools that manage parameter files centrally and apply them to both the production and disaster recovery environments.

[0021] However, conventional technologies have difficulty properly managing parameter files related to the management of database containers (DB containers) that are referenced by autonomous management systems. For example, depending on the timing of backups, there may be discrepancies between the parameter files used by the autonomous management system in the disaster recovery environment and the parameter information reflected within the DB container.

[0022] DB container parameter information is synchronized in real time from the production environment to the disaster recovery environment via streaming replication. However, with existing backup and restore tools, the parameter files used by the autonomous management system are backed up at a time specified by the user and restored to the disaster recovery environment.

[0023] Therefore, if the production environment fails before the parameter files used by the autonomous management system in the production environment are backed up, discrepancies in parameter information may occur in the disaster recovery environment. For example, in the disaster recovery environment, while the parameter information within the DB container is updated via streaming replication, the parameter files used by the autonomous management system may not be updated, leading to discrepancies.

[0024] In this case, even if the environment is switched from the production environment to the disaster recovery environment in the event of a disaster, the autonomous management system will not be able to manage the containers. For example, if the database password is not transmitted to the autonomous management system's parameter file, the autonomous management system will not be able to connect to the database after the switch from the production environment to the disaster recovery environment, and will not be able to manage the database.

[0025] To prevent such discrepancies with existing technologies, it is necessary to create backups immediately as soon as parameter information is changed in the production environment. However, changes to parameter information in the production environment are not only made manually by system administrators, but can also be made autonomously by autonomous management systems.

[0026] Therefore, system administrators must monitor parameter information changes made by the autonomous management system, as well as manually change parameter information, and manually create backups. However, since changes made by the autonomous management system are made irregularly depending on the operational status of the business system, it is difficult to determine the timing for performing backups.

[0027] Thus, manually creating backups by system administrators and others complicates operational management and carries the risk of human error, such as incorrect command input. Furthermore, existing centralized management tools are not designed to pull parameter information that changes autonomously in the production environment and push it to the disaster recovery environment (there are constraints on the direction of information).

[0028] Therefore, this embodiment describes a management method for appropriately managing parameter information related to the management of a container including a database (DB container). Here, an example of processing by the management device 101 is described. The management device 101 is deployed in the redundant first environment 110 and the second environment 120, respectively. The first environment 110 is, for example, the production environment. The second environment 120 is the disaster recovery environment.

[0029] Here, the control device 101 located in the first environment 110 will be referred to as "first control device 101-1," and the control device 101 located in the second environment 120 will be referred to as "second control device 101-2."

[0030] Under the first environment 110, the first management device 101-1 detects changes in management parameter information 112 referenced by the management unit 111. The management unit 111 manages the containers deployed in the first environment 110. The management unit 111 corresponds to, for example, an autonomous management system. The management parameter information 112 is information relating to the management of the first container 113. The first container 113 is a container (DB container) containing a database 114, deployed in the first environment 110.

[0031] The management parameter information 112 includes, for example, the configuration information of the first container 113 and the values ​​of parameters set in the database 114 contained in the first container 113. The configuration information of the first container 113 includes, for example, the CPU (Central Processing Unit) and memory specifications of the first container 113.

[0032] The parameters set in database 114 are, for example, the password for connecting to database 114. The management parameter information 112 may be changed manually, for example, by a system administrator, or by the management unit 111 according to the operational status of the business system.

[0033] When the first management device 101-1 detects a change in the management parameter information 112, it updates the control parameter information 115 contained in the first container 113 according to the change and writes the details of the change to the change history information 116 provided in the database 114.

[0034] The control parameter information 115 is information relating to the control of the first container 113, which is referenced by the first container 113. The control parameter information 115 includes, for example, the configuration information of the first container 113 and the values ​​of parameters set in the database 114 contained in the first container 113.

[0035] The first container 113 is controlled based on control parameter information 115. In the first environment 110, if there is a discrepancy in the information related to the first container 113 between the management parameter information 112 referenced by the management unit 111 and the control parameter information 115 within the first container 113, the management unit 111 will not be able to properly operate and manage the first container 113.

[0036] Therefore, when the management parameter information 112 is changed, the first management device 101-1 updates the control parameter information 115 in the first container 113 in accordance with the change. Furthermore, the first management device 101-1 writes the details of the change to the management parameter information 112 to the change history information 116 in the database 114.

[0037] In the second environment 120, the second management device 101-2 detects changes in the change history information 126 within the database 124 contained in the second container 123. Here, the second container 123 is a container (DB container) deployed in the second environment 120 and synchronized with the first container 113 by a data synchronization function.

[0038] One example of a data synchronization function is streaming replication. With streaming replication, data is synchronized in real time between the first container 113 in the first environment 110 (the source) and the second container 123 in the second environment 120 (the destination).

[0039] This updates the control parameter information 125 and change history information 126 within the second container 123. The control parameter information 125 is information relating to the control of the second container 123, referenced by the second container 123, and corresponds to the control parameter information 115 of the first container 113. The change history information 126 corresponds to the change history information 116 of the first container 113.

[0040] The second management device 101-2, upon detecting a change in the change history information 126, updates the management parameter information 122 referenced by the management unit 121 accordingly. The management unit 121 manages the containers deployed in the second environment 120. The management unit 121 corresponds to, for example, an autonomous management system. The management parameter information 122 is information relating to the management of the second container 123 and corresponds to the management parameter information 112 of the first environment 110.

[0041] In this way, the second management device 101-2 can utilize a data synchronization function (for example, streaming replication) to detect changes in parameter information (management parameter information 112, control parameter information 115) in the first environment 110 from the change history information 126, and update the management parameter information 122 in the second environment 120.

[0042] Based on these considerations, the management device 101 (first management device 101-1, second management device 101-2) can appropriately manage parameter information related to the management of DB containers (first container 113, second container 123). For example, the management device 101 can prevent discrepancies between the control parameter information 125 in the second container 123 and the management parameter information 122 referenced by the management unit 121 in the second environment 120.

[0043] As a result, when the configuration of the first environment 110 (e.g., the production environment) is changed, the management device 101 does not require system administrators or others to manually change the configuration of the second environment 120 (e.g., the disaster recovery environment), thereby reducing operational management costs and human errors (operational mistakes).

[0044] Furthermore, the management device 101 can properly manage the operation of the database 124 in the second container 123 when switching from the first environment 110 to the second environment 120 in the event of a disaster. For example, the management device 101 can avoid situations where the management unit 121 is unable to connect to the database 124 and therefore unable to perform operation management, which can occur if authentication information such as passwords is not transmitted to the management unit 121.

[0045] (Example of system configuration for information processing system 200) Next, we will describe an example of the system configuration of the information processing system 200, including the management device 101 shown in Figure 1. Here, we will explain using the case where the management device 101 shown in Figure 1 is applied to the information processing devices 201 and 202 within the information processing system 200 as an example.

[0046] Figure 2 is an explanatory diagram showing an example of the system configuration of the information processing system 200. In Figure 2, the information processing system 200 includes an information processing device 201, an information processing device 202, and an administrator terminal 203. In the information processing system 200, the information processing device 201, the information processing device 202, and the administrator terminal 203 are connected via a wired or wireless network 210. The network 210 is, for example, the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

[0047] Here, the information processing device 201 is the computer of the production environment E1. The production environment E1 is the environment in which the system actually used by the user runs. The system is, for example, a business system. The first management device 101-1 shown in Figure 1 corresponds to, for example, the information processing device 201. Also, the first environment 110 shown in Figure 1 corresponds to, for example, the production environment E1.

[0048] The information processing device 201 can run one or more containers Cr. A container Cr can be, for example, a DB container or an application container. A DB container is a container that includes a database. An application container is a container that does not include a database.

[0049] Furthermore, the information processing device 201 is capable of running the autonomous management system MS. The autonomous management system MS is software that manages container Cr deployed in the production environment E1. The information processing device 201 can be implemented, for example, by one or more servers.

[0050] The information processing device 202 is the computer for the disaster response environment E2. The production environment E1 and the disaster response environment E2 are redundant for disaster countermeasures. The disaster response environment E2 is a standby system synchronized with the production environment E1 (operational system). The disaster response environment E2 is operational so that it can be switched over from the production environment E1 immediately in the event of a disaster. The second management device 101-2 shown in Figure 1 corresponds to, for example, the information processing device 202. Also, the second environment 120 shown in Figure 1 corresponds to, for example, the disaster response environment E2.

[0051] The information processing device 202 can run one or more containers Cr'. Container Cr' corresponds to container Cr in the production environment E1. Furthermore, the information processing device 202 can run the autonomous management system MS'. The autonomous management system MS' is software that manages containers Cr' deployed in the disaster response environment E2. The information processing device 202 can be implemented, for example, by one or more servers.

[0052] The administrator terminal 203 is a computer used by the system administrator of the information processing system 200. The administrator terminal 203 may be, for example, a PC (Personal Computer) or a tablet PC.

[0053] (Example hardware configuration of information processing device 201, etc.) Next, we will describe an example of the hardware configuration of information processing devices 201 and 202. Here, information processing devices 201 and 202 will be referred to as "information processing devices 201, etc."

[0054] Figure 3 is a block diagram showing an example of the hardware configuration of an information processing device 201, etc. In Figure 3, the information processing device 201, etc. includes a CPU 301, memory 302, disk drive 303, disk 304, communication interface 305, portable recording medium interface 306, and portable recording medium 307. Each component is connected by a bus 300.

[0055] Here, the CPU 301 controls the entire information processing device 201 and other components. The CPU 301 may have multiple cores. The memory 302 includes, for example, ROM (Read Only Memory), RAM (Random Access Memory), and flash ROM. Specifically, for example, flash ROM stores the OS program, ROM stores the application program, and RAM is used as the work area for the CPU 301. Programs stored in memory 302 are loaded into the CPU 301, causing the CPU 301 to execute the coded processes.

[0056] The disk drive 303 controls the reading and writing of data to the disk 304 according to the control of the CPU 301. The disk 304 stores the data written under the control of the disk drive 303. The disk 304 is, for example, a magnetic disk, an optical disk, etc.

[0057] The communication interface 305 is connected to the network 210 via a communication line, and then connected to an external computer via the network 210. The communication interface 305 manages the interface between the network 210 and the inside of the device, and controls the input and output of data from the external computer. The communication interface 305 is, for example, a modem or a LAN adapter.

[0058] The portable recording medium interface 306 controls the reading and writing of data to the portable recording medium 307 according to the control of the CPU 301. The portable recording medium 307 stores the data written under the control of the portable recording medium interface 306. The portable recording medium 307 is, for example, a CD (Compact Disc)-ROM, a DVD (Digital Versatile Disk), or a USB (Universal Serial Bus) memory.

[0059] Furthermore, the information processing device 201, etc., may have, in addition to the components described above, an input device, a display, etc. Also, the information processing device 201, etc., does not have to have, for example, the portable recording medium I / F 306 and the portable recording medium 307 among the components described above. The administrator terminal 203 shown in Figure 2 can also be realized with a hardware configuration similar to that of the information processing device 201, etc. However, the administrator terminal 203 may have, in addition to the components described above, an input device, a display, etc.

[0060] (Example of the functional configuration of the information processing device 201) Next, we will describe an example of the functional configuration of the information processing device 201 in the production environment E1.

[0061] Figure 4 is a block diagram showing an example of the functional configuration of the information processing device 201 in the production environment E1. In Figure 4, the information processing device 201 includes a creation unit 401, a first detection unit 402, and a first update unit 403. The creation unit 401 to the first update unit 403 function as a control unit 400, and specifically, this function is realized, for example, by having the CPU 301 execute a program stored in a storage device such as the memory 302, disk 304, or portable recording medium 307 of the information processing device 201 shown in Figure 3, or by using a communication I / F 305. The processing results of each functional unit are stored in a storage device such as the memory 302 or disk 304. More specifically, for example, each functional unit may be realized by the autonomous management system MS shown in Figure 2.

[0062] In the following explanation, any DB container within container Cr in the production environment E1 may be referred to as "DB container Cr#". The database contained within DB container Cr# may be referred to as "database DB#". Furthermore, the DB container within container Cr' in the disaster recovery environment E2 that corresponds to DB container Cr# in the production environment E1 may be referred to as "DB container Cr#'".

[0063] The DB container Cr# in the production environment E1 is synchronized with the DB container Cr#' in the disaster recovery environment E2 via a data synchronization function. However, DB container Cr# acts as the source and destination for synchronization. The data synchronization function is, for example, streaming replication.

[0064] Streaming replication allows, for example, to maintain the same database state in DB container Cr# and DB container Cr#' by transferring update information from DB container Cr# to DB container Cr#' in real time. For example, update information from DB container Cr# is stored as a WAL (Write-Ahead Log, transaction log). Streaming replication transfers this WAL to DB container Cr#' in real time, and then applies the WAL in DB container Cr#'.

[0065] When the creation unit 401 deploys the DB container Cr# to the production environment E1, it creates a parameter table T# within the database DB# contained in the DB container Cr#. The parameter table T# stores the changes to the parameter information related to the management of the container Cr deployed to the production environment E1. The change history information 116 shown in Figure 1 corresponds to, for example, the parameter table T#.

[0066] Parameter information includes, for example, configuration information for the DB container Cr# and parameter values ​​set for the database DB# contained within the DB container Cr#. Configuration information for the DB container Cr# represents, for example, the CPU and memory specifications of the DB container Cr#. Parameters set for the database DB# include, for example, the password and specifications of the database DB#. Parameter information initially registered in the parameter table T# is specified, for example, by the system administrator.

[0067] For example, consider the case where DB container Cr1, as shown in Figure 6 below, is deployed to the production environment E1. In this case, the creation unit 401 creates parameter table T1 within the database DB1 contained in DB container Cr1. To explain in more detail, for example, the creation unit 401 creates parameter table T1 using a CREATE TABLE statement like the following.

[0068] CREATE TABLE statement=create table update_parameter (param_name text, param_value_text, create_at timestamp, param_value_updated_text, , update_at timestamp);

[0069] The contents of parameter table T1 will be described later using Figure 10. Note that "param_name text" corresponds to the "parameter name" shown in Figure 10 below. "param_value_text" corresponds to the "value" shown in Figure 10. "create_at timestamp" corresponds to the "timestamp" shown in Figure 10. "param_value_updated_text" corresponds to the "updated value" shown in Figure 10. "update_at timestamp" corresponds to the "update timestamp" shown in Figure 10.

[0070] The first detection unit 402 detects changes in the parameter file PF, which is referenced by the autonomous management system MS. Here, the autonomous management system MS is a management unit that manages the container Cr deployed in the production environment E1 (see Figure 2). The parameter file PF contains parameter information (management parameter information) related to the management of the container Cr deployed in the production environment E1.

[0071] For example, the parameter file PF contains parameter information related to the management of the DB container Cr# deployed in the production environment E1. The parameter file PF also contains parameter information related to the management of application containers deployed in the production environment E1. The parameter file PF can be modified by a system administrator, for example, using the administrator terminal 203 shown in Figure 2. Furthermore, the parameter file PF may be autonomously modified by the autonomous management system MS, for example, depending on the operational status of business systems running in the production environment E1.

[0072] Specifically, for example, the first detection unit 402 periodically checks the contents of the parameter file PF at regular intervals. The regular interval can be set arbitrarily, for example, to a few seconds. The first detection unit 402 then compares the most recent stored contents of the parameter file PF with the previous stored contents.

[0073] Here, if there is a difference between the latest stored content and the previous stored content, the first detection unit 402 detects a change in the parameter file PF. On the other hand, if there is no difference between the latest stored content and the previous stored content, the first detection unit 402 does not detect a change in the parameter file PF.

[0074] Furthermore, the first detection unit 402 may detect changes to the parameter file PF by detecting modification processing performed on the parameter file PF by a system administrator using the administrator terminal 203. Alternatively, the first detection unit 402 may detect changes to the parameter file PF by detecting autonomous modification processing performed on the parameter file PF by the autonomous management system MS.

[0075] The first update unit 403, upon detecting a change in the parameter file PF, updates the parameter file f# contained in the DB container Cr# according to the change and writes the details of the change to the parameter table T# provided in the database DB#. Here, the parameter file f# is information (control parameter information) related to the control of the DB container Cr#, which is referenced by the DB container Cr#.

[0076] The parameter file f# contains, for example, configuration information for the DB container Cr# and parameter values ​​set for the database DB# contained within the DB container Cr#. The DB container Cr# is controlled based on the parameter file f#. More specifically, for example, the first update unit 403 writes to the parameter table T# using an INSERT statement like the following.

[0077] INSERT statement = INSERT into update_parameter(update value, update timestamp) VALUES (updated value, updated time);

[0078] An example of updating parameter table T1 will be described later using Figure 11.

[0079] Furthermore, when the first update unit 403 writes the contents of the detected changes to the parameter file PF to the parameter table T#, it may choose not to write the contents of the changes to the parameter file f# if it fails to update the parameter file f# in accordance with the changes.

[0080] Specifically, for example, the first update unit 403 retrieves the changed parameter information from the parameter file PF when it detects a change in the parameter file PF. Then, the first update unit 403 performs the process of updating the parameter file f# in the DB container Cr# and the process of writing to the parameter table T# in the database DB#, all within a single transaction, using the changed parameter information.

[0081] As a result, if updating parameter file f# fails, the changes from parameter file PF will not be written to parameter table T#. Similarly, if writing the changes from parameter file PF to parameter table T# fails, parameter file f# will not be updated.

[0082] Furthermore, the first update unit 403 may, upon detecting a change in the parameter file PF, update the parameter files contained in other containers among the containers Cr deployed in the production environment E1 that are different from the DB container Cr#, in accordance with the change. These other containers may be, for example, application containers that do not contain a database.

[0083] Parameter files contained within other containers are referenced by those other containers and contain information related to the control of those other containers (control parameter information). As a result, the first update unit 403 reflects the changes made to the parameter file PF in the parameter files of other containers (for example, application containers).

[0084] In disaster recovery environment E2, when a change in the parameter table T#' within the database DB#' contained in DB container Cr#', which is synchronized with DB container Cr# by the data synchronization function, the parameter file PF' referenced by the autonomous management system MS' is updated accordingly.

[0085] (Example of the functional configuration of the information processing device 202) Next, we will describe an example of the functional configuration of the information processing device 202 for the disaster response environment E2.

[0086] Figure 5 is a block diagram showing an example of the functional configuration of the information processing device 202 for disaster response environment E2. In Figure 5, the information processing device 202 includes a second detection unit 501 and a second update unit 502. The second detection unit 501 to the second update unit 502 function as a control unit 500, and specifically, this function is realized, for example, by having the CPU 301 execute a program stored in a storage device such as the memory 302, disk 304, or portable recording medium 307 of the information processing device 202 shown in Figure 3, or by using a communication I / F 305. The processing results of each functional unit are stored in a storage device such as the memory 302 or disk 304. More specifically, for example, each functional unit may be realized by the autonomous management system MS' shown in Figure 2.

[0087] The second detection unit 501 detects changes to the parameter table T#' within the database DB#' contained in the DB container Cr#'. The DB container Cr#' is deployed in the disaster recovery environment E2 and synchronized with the DB container Cr# in the production environment E1 via a data synchronization function (e.g., streaming replication).

[0088] The parameter table T#' is synchronized with the parameter table T# in the database DB contained in the DB container Cr# of the production environment E1 via a data synchronization function (e.g., streaming replication). The change history information 126 shown in Figure 1 corresponds to, for example, the parameter table T#'.

[0089] Specifically, for example, the second detection unit 501 periodically checks the contents of the parameter table T#' at regular intervals. The regular interval can be set arbitrarily, for example, to a few seconds. The second detection unit 501 then compares the most recent stored contents of the parameter table T#' with the previous stored contents.

[0090] Here, if there is a difference between the latest stored content and the previous stored content, the second detection unit 501 detects a change in the parameter table T#'. On the other hand, if there is no difference between the latest stored content and the previous stored content, the second detection unit 501 does not detect a change in the parameter table T#'.

[0091] The second update unit 502, upon detecting a change in the parameter table T#', updates the parameter file PF', which is referenced by the autonomous management system MS', accordingly. Here, the autonomous management system MS' is the management unit that manages the container Cr' deployed in the disaster response environment E2 (see Figure 2).

[0092] The parameter file PF' contains parameter information (management parameter information) related to the management of container Cr' deployed in disaster recovery environment E2. For example, parameter file PF' includes parameter information related to the management of DB container Cr#' deployed in disaster recovery environment E2. It also includes parameter information related to the management of application containers deployed in disaster recovery environment E2.

[0093] Specifically, for example, the second update unit 502 detects a change in the parameter table T#' and retrieves the changed parameter information from the parameter table T#'. Then, the second update unit 502 updates the parameter file PF' using the retrieved changed parameter information.

[0094] In this case, the second update unit 502 may, for example, recursively update the parameter file PF' using the values ​​of both the old and new parameters until it succeeds, in order to ensure that the changes in the parameter table T#' are reflected in the parameter file PF'.

[0095] Here, the parameter file f#' within DB container Cr#' is synchronized with the parameter file f# within DB container Cr# in production environment E1 by a data synchronization function (e.g., streaming replication). However, there is a non-zero possibility that, due to some malfunction, the parameter file f#' may not be synchronized with the parameter file f#.

[0096] Therefore, if the second update unit 502 successfully updates the parameter file PF', it may update the parameter file f#' in the DB container Cr#' in accordance with the detected changes in the parameter table T#'. This ensures that the second update unit 502 does not cause any discrepancies between the parameter file PF' referenced by the autonomous management system MS' and the parameter file f#' in the DB container Cr#'.

[0097] Furthermore, if the second update unit 502 successfully updates the parameter file PF', it may update the parameter files contained in other containers among the containers Cr' deployed in the disaster recovery environment E2 that are different from the DB container Cr#', in accordance with the detected changes in the parameter table T#'. In this way, the second update unit 502 reflects the updated contents of the parameter file PF' in the parameter files of other containers (for example, application containers).

[0098] Furthermore, considering the possibility that parameter file f#' may not be synchronized with parameter file f# due to some malfunction, the second update unit 502 may determine whether the same changes as those in parameter table T#' have been reflected in parameter file f#' before updating parameter file PF'.

[0099] The statement that the changes are the same as those in parameter table T#' means that the same changes have been made to the same aspects as those in parameter table T#'. Here, if the changes are reflected in parameter file f#', the second update unit 502 may update parameter file PF'. On the other hand, if the changes are not reflected in parameter file f#', the second update unit 502 may choose not to update parameter file PF'.

[0100] In the production environment E1, when a change in the parameter file PF referenced by the autonomous management system MS is detected, the parameter file f# contained in the DB container Cr# is updated accordingly, and the details of the change are written to the parameter table T# in the database DB#.

[0101] Furthermore, the information processing device 201 may have the functional units (second detection unit 501, second update unit 502) of the information processing device 202 shown in Figure 5. When the information processing device 201 is deployed in the disaster response environment E2, it performs processing using the functional units (second detection unit 501, second update unit 502). Also, the information processing device 202 may have the functional units (creation unit 401 to first update unit 403) of the information processing device 201 shown in Figure 4. When the information processing device 202 is deployed in the production environment E1, it performs processing using the functional units (creation unit 401 to first update unit 403).

[0102] (Example of operation of information processing system 200) Next, we will describe an example of the operation of the information processing system 200. Here, we assume that the DB container Cr1 in the production environment E1 and the DB container Cr1' in the disaster recovery environment E2 are synchronized by streaming replication (data synchronization function). Furthermore, we will explain using an example where each functional unit of the information processing device 201 located in the production environment E1 is implemented by the "autonomous management system MS", and each functional unit of the information processing device 202 located in the disaster recovery environment E2 is implemented by the "autonomous management system MS'".

[0103] Figure 6 is an explanatory diagram showing an example of the operation of the information processing system 200. In Figure 6, the production environment E1 and the disaster recovery environment E2 within the information processing system 200 are shown. Assume that the parameter file PF has been modified in the production environment E1 by the system administrator 600 or the autonomous management system MS.

[0104] In this case, the autonomous management system MS detects the change in the parameter file PF. Upon detecting the change in the parameter file PF, the autonomous management system MS updates the parameter file f1 contained in the DB container Cr1 according to the change and writes the details of the change to the parameter table T1 located in the database DB1.

[0105] For example, suppose the setting value of the parameter "param1" for the database DB1 itself is changed from "aaa" to "bbb" in the parameter file PF. In this case, the autonomous management system MS changes the value of "param1" in the parameter file f1 contained in DB container Cr1 from "aaa" to "bbb".

[0106] Furthermore, the autonomous management system MS writes to the parameter table T1 in the database DB1 that the value of "param1" has changed from "aaa" to "bbb". In this case, the autonomous management system MS performs the update process of the parameter file f1 and the write process to the parameter table T1 within a single transaction, for example, as shown in Figure 7.

[0107] Figure 7 is an explanatory diagram illustrating an example of transaction processing associated with changes to the parameter file PF. In Figure 7, when the autonomous management system MS detects a change in the parameter file PF, it performs two processes within a single transaction: an update process to add the corresponding changes to the parameter file f1, and a write process to write the contents of those changes to the parameter table T1.

[0108] In this case, if the autonomous management system MS is unable to write the changes to parameter table T1, it will not modify parameter file f1. Furthermore, if the autonomous management system MS is unable to modify parameter file f1, it will not write the changes to parameter table T1.

[0109] This allows the autonomous management system MS to prevent discrepancies in changes between parameter file f1 and parameter table T1.

[0110] Returning to the explanation of Figure 6, when parameter file PF is changed, the parameter file f1 is updated and written to parameter table T1. Streaming replication then propagates the information from the production environment E1 to the disaster recovery environment E2, synchronizing the DB container Cr1 in the production environment E1 with the DB container Cr1' in the disaster recovery environment E2.

[0111] As a result, in disaster response environment E2, the autonomous management system MS' detects changes to the parameter table T1' within the database DB1' contained in the DB container Cr1'. Upon detecting the changes to the parameter table T1', the autonomous management system MS' updates the parameter file PF' accordingly.

[0112] For example, the autonomous management system MS' retrieves the changed parameter information from the parameter table T1'. Here, parameter information indicating that the value of "param1" has changed from "aaa" to "bbb" is retrieved from the parameter table T1'. Then, the autonomous management system MS' changes the value of "param1" in the parameter file PF' from "aaa" to "bbb".

[0113] Furthermore, the autonomous management system MS' may update the value of "param1" in the parameter file f1' of DB container Cr1' to "bbb". However, if streaming replication is successfully performed between DB container Cr1 in the production environment E1 and DB container Cr1' in the disaster recovery environment E2, the value of "param1" in the parameter file f1' will already be changed to "bbb".

[0114] This allows the autonomous management system MS' to eliminate discrepancies between its own parameter file PF' and the parameter file f1' in the DB container Cr1', enabling it to reflect changes to parameter file PF in the production environment E1 to parameter file PF' in the disaster recovery environment E2.

[0115] Here, using the sequence diagrams in Figures 8 and 9, we will explain examples of operation in each environment (production environment E1, disaster recovery environment E2). Here, we will explain using the example of when the system administrator 600 modifies the parameter file PF referenced by the autonomous management system MS.

[0116] Figure 8 is a sequence diagram showing an example of operation in the production environment E1. In the sequence diagram of Figure 8, first, the system administrator 600 modifies the parameter file PF using the administrator terminal 203 (see Figure 2) (step S801).

[0117] The autonomous management system MS detects a change in the parameter file PF (step S802). At this time, the autonomous management system MS obtains the changed parameter information from the parameter file PF. Then, using the changed parameter information, the autonomous management system MS updates the parameter file f1 of the DB container Cr1 and writes the changes to the parameter table T1 of the DB container Cr1 (step S803).

[0118] After this, the data synchronization function (streaming replication) propagates information from the production environment E1 to the disaster recovery environment E2, and the DB container Cr1 in the production environment E1 and the DB container Cr1' in the disaster recovery environment E2 are synchronized.

[0119] Figure 9 is a sequence diagram showing an example of operation in disaster response environment E2. In the sequence diagram of Figure 9, the autonomous management system MS' detects a change in the parameter table T1' of the DB container Cr1' (step S901). At this time, the autonomous management system MS' obtains the changed parameter information from the parameter table T1'.

[0120] Then, the autonomous management system MS' updates the parameter file PF' using the changed parameter information (step S902). If the autonomous management system MS' successfully updates the parameter file PF', it also updates the parameter file f1' of the DB container Cr1' using the changed parameter information (step S903).

[0121] This allows system administrator 600 to automatically configure production environment E1 and disaster recovery environment E2 to the same configuration simply by changing the parameter file PF used by the autonomous management system MS in production environment E1. Therefore, system administrator 600 does not need to manually change the configuration in disaster recovery environment E2 when changing the configuration of production environment E1, thereby reducing operational management costs and human error (operational mistakes).

[0122] (Contents of parameter table T#) Next, we will explain the contents of parameter table T# using Figure 10. Here, we will use parameter table T1, which is located in database DB1 contained in DB container Cr1 shown in Figure 6, as an example.

[0123] Figure 10 is an explanatory diagram showing an example of the contents stored in parameter table T1. In Figure 10, parameter table T1 has fields for parameter name, value, timestamp, update value, and update timestamp, and by setting information in each field, change history information (for example, change history information 1000-1 to 1000-5) is stored as records.

[0124] Here, the parameter name is the name of the parameter related to the management of container Cr deployed in the production environment E1. The parameter includes, for example, configuration information for DB container Cr1 (DB container memory, DB container CPU, etc.) and parameters set for database DB1 contained within DB container Cr1 (DB password, DB memory, etc.). The value is the value of the parameter.

[0125] The timestamp indicates the date and time when the parameter was initially registered in parameter table T1. For example, parameter table T1 is created when DB container Cr1 is deployed to the production environment E1. In this case, the timestamp will be the date and time when DB container Cr1 was deployed.

[0126] However, if a new parameter is added after the deployment of DB container Cr1, the timestamp of that parameter may be, for example, the date and time the parameter was added. The updated value is the value of the updated parameter. The update timestamp indicates the date and time the parameter value was updated.

[0127] Furthermore, parameter table T1 is replicated using the data synchronization function (streaming replication) and stored in database DB1' of DB container Cr1' deployed in disaster recovery environment E2. As a result, the parameter names become the names of the parameters related to the management of container Cr' deployed in disaster recovery environment E2.

[0128] Next, we will explain an example of updating the parameter table T1 using Figure 11.

[0129] Figure 11 is an explanatory diagram showing an example of updating parameter table T1. In Figure 11, change history information 1000-2 and 1000-4 in parameter table T1 have been updated (bolded portion in Figure 11).

[0130] In change history information 1000-2, the parameter name "DB container memory" has been updated with the updated value "400MB" and the update timestamp "2023-06-10 00:00:00.000000". This entry indicates that the value of the parameter name "DB container memory" was changed to the updated value "400MB" on the update timestamp "2023-06-10 00:00:00.000000".

[0131] In change history information 1000-4, the parameter name "DB memory" has been updated with the updated value "200MB" and the update timestamp "2023-06-10 00:00:00.000000". This entry indicates that the value of the parameter name "DB memory" was changed to the updated value "200MB" on the update timestamp "2023-06-10 00:00:00.000000".

[0132] Furthermore, writes to parameter table T1 are propagated to parameter table T1' in the DB container Cr1' of disaster recovery environment E2 via data synchronization (streaming replication). As a result, changes to parameter table T1' are detected by the autonomous management system MS' of disaster recovery environment E2.

[0133] (Various processing procedures of the information processing device 201 in the production environment E1) Next, we will describe the various processing procedures of the information processing device 201 in the production environment E1. The various processes of the information processing device 201 are executed, for example, by the autonomous management system MS of the production environment E1.

[0134] First, using Figure 12, we will explain the DB container deployment process for the information processing device 201 in the production environment E1.

[0135] Figure 12 is a flowchart showing an example of the DB container deployment procedure for the information processing device 201 in the production environment E1. In the flowchart of Figure 12, first, the information processing device 201 deploys the DB container Cr# to the production environment E1 based on the parameter file PF (step S1201).

[0136] The parameter file PF is created, for example, by the system administrator and entered into the information processing device 201 (initial setup).

[0137] Then, the information processing device 201 refers to the parameter file PF and creates a parameter table T# in the database DB# contained in the DB container Cr# deployed in the production environment E1 (step S1202), thereby ending the series of processes according to this flowchart.

[0138] This allows the information processing device 201 to create a parameter table T# in the database DB# of the DB container Cr# when deploying the DB container Cr# to the production environment E1, in order to write the changes made to the parameter file PF.

[0139] Next, using Figure 13, we will explain the management procedure for the information processing device 201 in the production environment E1.

[0140] Figure 13 is a flowchart showing an example of the management processing procedure for the information processing device 201 in the production environment E1. In the flowchart of Figure 13, first, the information processing device 201 determines whether or not it has detected a change in the parameter file PF used by the autonomous management system MS (step S1301).

[0141] Here, the information processing device 201 waits to detect a change in the parameter file PF (step S1301: No). If the information processing device 201 detects a change in the parameter file PF (step S1301: Yes), it retrieves the changed parameter information from the parameter file PF (step S1302).

[0142] Next, the information processing device 201 updates the parameter file f# in the DB container Cr# using the changed parameter information (step S1303). Then, the information processing device 201 determines whether or not the update of the parameter file f# in the DB container Cr# was successful (step S1304).

[0143] If the update of parameter file f# fails (step S1304: No), the information processing device 201 terminates the series of processes according to this flowchart. On the other hand, if the update of parameter file f# is successful (step S1304: Yes), the information processing device 201 uses the changed parameter information to write the changes to parameter file PF to parameter table T# in database DB# (step S1305), and then terminates the series of processes according to this flowchart.

[0144] As a result, the information processing device 201 can update the parameter file f# and write to the parameter table T# in response to changes in the parameter file PF. Consequently, data synchronization between the DB container Cr1 in the production environment E1 and the DB container Cr1' in the disaster recovery environment E2 propagates changes to the parameter file PF in the production environment E1 to the parameter file f#' and parameter table T1' in the DB container Cr1' in the disaster recovery environment E2.

[0145] Furthermore, the information processing device 201 can prevent discrepancies in changes between parameter file f1# and parameter table T# by writing to parameter table T# only when it has successfully updated parameter file f# in DB container Cr#.

[0146] Furthermore, if updating the parameter file f# fails in step S1304, the information processing device 201 may perform error processing. In error processing, for example, an error notification is sent to the administrator terminal 203 indicating that the parameter file f# in the DB container Cr# could not be updated in response to the change in the parameter file PF. As a result, the system administrator can take some action to resolve the discrepancy between the parameter file PF in the production environment E1 and the parameter file f# in the DB container Cr#. Also, if writing to the parameter table T# fails in step S1305, the information processing device 201 may perform error processing.

[0147] (Various processing procedures for the information processing device 202 of the disaster response environment E2) Next, the various processing procedures of the information processing device 202 of the disaster response environment E2 will be described. The various processing operations of the information processing device 202 are performed, for example, by the autonomous management system MS' of the disaster response environment E2.

[0148] First, using Figure 14, we will explain the management processing procedure of the information processing device 202 for the disaster response environment E2.

[0149] Figure 14 is a flowchart showing an example of the management processing procedure for the information processing device 202 in the disaster response environment E2. In the flowchart of Figure 14, first, the information processing device 202 determines whether or not it has detected a change in the parameter table T#' in the database DB#' contained in the DB container Cr#' (step S1401).

[0150] Here, the information processing device 202 waits to detect a change in the parameter table T#' (step S1401: No). If the information processing device 202 detects a change in the parameter table T#' (step S1401: Yes), it retrieves the changed parameter information from the parameter table T#' (step S1402).

[0151] Next, the information processing device 202 refers to the changed parameter information and determines whether the same changes as those in the parameter table T#' have been reflected in the parameter file f#' within the DB container Cr#' (step S1403). If the changes have been reflected in the parameter file f#' (step S1403: Yes), the information processing device 202 updates the parameter file PF' used by the autonomous management system MS' using the changed parameter information (step S1404).

[0152] The information processing device 202 then determines whether the update of the parameter file PF' was successful (step S1405). If the update of the parameter file PF' was successful (step S1405: Yes), the information processing device 202 updates the parameter files in other containers of the disaster response environment E2 using the changed parameter information (step S1406), and then terminates the series of processes according to this flowchart.

[0153] Furthermore, if the changes are not reflected in the parameter file f#' in step S1403 (step S1403: No), the information processing device 202 performs error processing (step S1407) and terminates the series of processes according to this flowchart. In this error processing, for example, an error notification is sent to the administrator terminal 203 indicating that the changes have not been reflected in the parameter file f#' in the DB container Cr#'.

[0154] Furthermore, if the update of the parameter file PF' fails in step S1405 (step S1405: No), the information processing device 202 performs error processing (step S1407) and terminates the series of processes according to this flowchart. In this error processing, for example, an error notification is sent to the administrator terminal 203 indicating that the changes to the parameter file PF' used by the autonomous management system MS' have not been reflected.

[0155] The information processing device 202 may omit the processing in step S1403. In this case, the information processing device 202 may update the parameter files contained in each container Cr' (including DB container Cr#') of the disaster recovery environment E2 using the changed parameter information in step S1406.

[0156] This allows the information processing device 202 to eliminate discrepancies between the parameter file PF' used by the autonomous management system MS' and the parameter file f#' in the DB container Cr#', enabling changes to the parameter file PF in the production environment E1 to be reflected in the parameter file PF' in the disaster recovery environment E2.

[0157] Using Figure 15, the procedure for promoting the information processing device 202 of the disaster response environment E2 will be explained.

[0158] Figure 15 is a flowchart showing an example of the promotion process procedure for the information processing device 202 of the disaster response environment E2. In the flowchart of Figure 15, the information processing device 202 determines whether or not it has received a promotion request for the disaster response environment E2 (step S1501). A promotion request for the disaster response environment E2 is made, for example, by a system administrator executing a command requesting promotion on the administrator terminal 203.

[0159] Here, the information processing device 202 waits to receive a request to promote disaster recovery environment E2 (step S1501: No). If the information processing device 202 receives a request to promote disaster recovery environment E2 (step S1501: Yes), it initiates the promotion process for the DB container Cr#' (step S1502).

[0160] Then, the information processing device 202 synchronizes the unsynchronized parameter information in the parameter table T#' with the parameter files in each container Cr' (step S1503), and completes the series of processes according to this flowchart.

[0161] This allows the information processing device 202 to switch the DB container Cr' from the backup system to the production system in response to promotion requests from system administrators and others. Furthermore, by synchronizing unsynchronized parameter information, the information processing device 202 can eliminate discrepancies between the parameter file PF' and the parameter files within each container Cr', even if, for example, a management process like the one shown in Figure 14 fails to complete properly due to some malfunction caused by a disaster.

[0162] (Examples) Next, we will describe an example of the information processing system 200. First, we will describe an example of container deployment in each environment (production environment E1, disaster recovery environment E2).

[0163] Figure 16 is an explanatory diagram showing examples of container deployment in each environment. In Figure 16, the production environment E1 has DB container Cr1, application container Cr2, and application container Cr3 deployed. DB container Cr1 contains database DB1 and parameter file f1. Database DB1 has a parameter table T1. DB container Cr1 is controlled based on parameter file f1.

[0164] Application container Cr2 contains parameter file f2. Application container Cr2 is controlled based on parameter file f2. Application container Cr3 contains parameter file f3. Application container Cr3 is controlled based on parameter file f3.

[0165] Furthermore, the production environment E1 is equipped with an autonomous management system MS. The autonomous management system MS manages the DB container Cr1, application container Cr2, and application container Cr3 by referring to the parameter file PF.

[0166] Disaster recovery environment E2 is deployed with DB container Cr1', application container Cr2', and application container Cr3'. DB container Cr1' corresponds to DB container Cr1 in production environment E1. Application container Cr2' corresponds to application container Cr2 in production environment E1. Application container Cr3' corresponds to application container Cr3 in production environment E1.

[0167] Furthermore, the autonomous management system MS' is deployed in disaster response environment E2. The autonomous management system MS' manages the DB container Cr1', application container Cr2', and application container Cr3' by referring to the parameter file PF'.

[0168] Here, we will explain a specific example of a parameter file PF using Figure 17.

[0169] Figure 17 is an explanatory diagram illustrating a specific example of a parameter file PF. In Figure 17, the parameter file PF contains information related to the management of DB container Cr1, application container Cr2, and application container Cr3, which is referenced by the autonomous management system MS.

[0170] The parameter file (PF) contains configuration information for the DB container and the parameter settings for the database itself contained within the DB container (e.g., parameter information 1701). The parameter file (PF) also contains configuration information for the application container (e.g., parameter information 1702).

[0171] When building the production environment E1, the autonomous management system MS deploys each container Cr (DB container Cr1, application container Cr2, application container Cr3) based on the parameter file PF, for example. The parameter files (parameter files f1~f3) contained in each container Cr are created based on the parameter file PF.

[0172] For example, parameter file f1 contains the same parameter values ​​as parameter information 1701. Also, parameter files f2 and f3 contain the same parameter values ​​as parameter information 1702. However, parameter file f1 may also contain the same parameter values ​​as parameter information 1702. Also, parameter files f2 and f3 may contain the same parameter values ​​as parameter information 1701.

[0173] The parameter file 'PF' in disaster recovery environment E2 corresponds to the parameter file PF in production environment E1.

[0174] In constructing the disaster response environment E2, the autonomous management system MS' deploys each container Cr' (DB container Cr1', application container Cr2', application container Cr3') based on, for example, the parameter file PF'. The parameter files contained in each container Cr' (parameter files f1', f2', f3') are created based on the parameter file PF'.

[0175] Furthermore, the DB container Cr1 in the production environment E1 and the DB container Cr1' in the disaster recovery environment E2 are synchronized in real time via streaming replication.

[0176] Now, let's assume that in the production environment E1, the parameter file PF used by the autonomous management system MS is modified by the administrator terminal 203 (system administrator).

[0177] In this case, the autonomous management system MS detects the change in the parameter file PF and retrieves the changed parameter information from the parameter file PF. Then, using the changed parameter information, the autonomous management system MS updates the parameter files (parameter files f1~f3) of each container Cr (DB container Cr1, application container Cr2, application container Cr3) and writes the changes to the parameter table T1 of DB container Cr1.

[0178] This allows the autonomous management system MS to eliminate discrepancies between the parameter file PF used by the autonomous management system MS in the production environment E1 and the parameter files within each container Cr.

[0179] When the parameter file f1 of DB container Cr1 is updated and the changes are written to the parameter table T1 of DB container Cr1, streaming replication synchronizes the parameter table T1' of DB container Cr1' in disaster recovery environment E2 with parameter table T1.

[0180] The autonomous management system MS' periodically checks the parameter table T1' in the DB container Cr1' and detects any changes to parameter table T1'. The autonomous management system MS' retrieves the changed parameter information from the parameter file PF'. Then, the autonomous management system MS' updates the parameter file PF' using the changed parameter information.

[0181] If the autonomous management system MS' successfully updates the parameter file PF', it updates the parameter files (parameter files f1'~f3') contained in each container Cr' (DB container Cr1', application container Cr2', application container Cr3') using the changed parameter information.

[0182] This allows the information processing device 202 to reflect changes to the parameter file PF in the production environment E1 in the parameter file PF' in the disaster response environment E2, and to eliminate discrepancies between the parameter file PF' of the autonomous management system MS' and the parameter files within each container Cr'.

[0183] As described above, the information processing device 201 according to this embodiment can detect changes in the parameter file PF referenced by the autonomous management system MS in the production environment E1. The autonomous management system MS is a management unit that manages the container Cr deployed in the production environment E1. The parameter file PF is information related to the management of the DB container Cr# (management parameter information), and includes, for example, the configuration information of the DB container Cr# and the parameter values ​​set in the database DB# contained in the DB container Cr#. The information processing device 201 can then detect changes in the parameter file PF and update the parameter file f# contained in the DB container Cr# accordingly, and write the contents of the changes to the parameter table T# provided in the database DB#.

[0184] As a result, when the parameter file PF in the production environment E1 is changed, the information processing device 201 can update the parameter file f# in the DB container Cr# in accordance with the change and write the changes to the parameter table T#. Therefore, even if the parameter file PF is changed, the information processing device 201 can eliminate the discrepancy between the parameter file PF and the parameter file f# in the DB container Cr#. In addition, the information processing device 201 can propagate the changes to the parameter file PF to the disaster recovery environment E2 by utilizing data synchronization between the production environment E1 and the disaster recovery environment E2.

[0185] Furthermore, according to the information processing device 202, changes to the parameter table T#' within the database DB#' contained in the DB container Cr#' can be detected in the disaster recovery environment E2. The DB container Cr#' is a container deployed in the disaster recovery environment E2 and synchronized with the DB container Cr# in the production environment E1 by a data synchronization function. The data synchronization function is, for example, streaming replication. According to the information processing device 202, upon detecting a change in the parameter table T#', the parameter file PF' referenced by the autonomous management system MS' can be updated according to the change. The autonomous management system MS' is a management unit that manages the container Cr' deployed in the disaster recovery environment E2.

[0186] This allows the information processing device 202 to eliminate discrepancies between the parameter file PF' used by the autonomous management system MS' and the parameter file f#' in the DB container Cr#', enabling changes to the parameter file PF in the production environment E1 to be reflected in the parameter file PF' in the disaster recovery environment E2.

[0187] Furthermore, according to the information processing device 201, when writing the contents of the detected changes in the parameter file PF to the parameter table T# in the production environment E1, if the update of the parameter file f# corresponding to the changes fails, the contents of the changes can be prevented from being written to the parameter table T#.

[0188] This ensures that the information processing device 201 can reliably prevent discrepancies between the parameter file PF referenced by the autonomous management system MS and the parameter file f# of the DB container Cr#.

[0189] Furthermore, according to the information processing device 202, if the parameter file PF' is successfully updated in the disaster recovery environment E2, the parameter file f#' in the DB container Cr#' can be updated in accordance with the detected changes in the parameter table T#'.

[0190] This ensures that the information processing device 202 can reliably prevent discrepancies between the parameter file PF' referenced by the autonomous management system MS' and the parameter file f#' in the DB container Cr#'.

[0191] Furthermore, according to the information processing device 201, in response to detecting a change in the parameter file PF in the production environment E1, it can update the parameter files contained in other containers among the containers Cr deployed in the production environment E1 that are different from the DB container Cr#. These other containers are, for example, application containers that do not contain a database.

[0192] This allows the information processing device 201 to reflect changes made to the parameter file PF in the parameter files of other containers in the production environment E1.

[0193] Furthermore, according to the information processing device 202, if the parameter file PF' is successfully updated in the disaster response environment E2, the parameter files contained in other containers among the containers Cr' deployed in the disaster response environment E2 that are different from the DB container Cr#' can be updated in accordance with the detected changes in the parameter table T#'.

[0194] This allows the information processing device 202 to reflect the updates to the parameter file PF' in the parameter files of other containers in the disaster response environment E2.

[0195] Based on these considerations, the information processing devices 201 and 202 can appropriately manage parameter information (parameter file PF, parameter file f#, parameter file PF', parameter file f#') related to the management of containers (DB container Cr#, Cr#') containing databases (database DB#, DB#') in the redundant production environment E1 and the disaster recovery environment E2.

[0196] Furthermore, according to information processing devices 201 and 202, when the configuration of the production environment E1 is changed, the system administrator does not need to manually change the configuration of the disaster recovery environment E2, thereby reducing operational management costs and human errors (operational mistakes). For example, by utilizing the streaming replication function that enables real-time synchronization, the system administrator can complete the setup simply by deploying the DB container, without having to deploy separate modules dedicated to parameter synchronization.

[0197] Furthermore, by utilizing the streaming replication function, when parameter information in the production environment E1 is changed, the changed parameter information is automatically transmitted to the disaster recovery environment E2. Therefore, even if the production environment E1 goes down, the operational environment can be reproduced based on the parameter information contained in the disaster recovery environment E2.

[0198] Furthermore, according to information processing devices 201 and 202, when switching from the production environment E1 to the disaster recovery environment E2 in the event of a disaster, it is possible to avoid situations where the autonomous management system MS' cannot connect to the database DB#' within the DB container Cr#' and therefore cannot perform operational management, due to the transmission of authentication information such as the password for the database DB#.

[0199] In the explanation above, we assumed that a system (e.g., a business system) would be implemented using a container (container Cr, Cr') containing applications and databases, but this is not the only way. For example, the system could also be implemented using a virtual machine containing applications and databases.

[0200] The management method described in this embodiment can be implemented by executing a pre-prepared program on a computer such as a personal computer or workstation. This management program is recorded on a computer-readable recording medium such as a hard disk, flexible disk, CD-ROM, DVD, or USB memory, and is executed when read from the recording medium by the computer. Furthermore, this management program may be distributed via a network such as the Internet.

[0201] Furthermore, the information processing devices 201 and 202 described in this embodiment can also be implemented using application-specific ICs such as standard cells and structured ASICs (Application Specific Integrated Circuits), or PLDs (Programmable Logic Devices) such as FPGAs.

[0202] With regard to the embodiments described above, the following additional information is disclosed.

[0203] (Note 1) Of the redundant first environment and second environment, In the first environment, changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, are detected. Upon detecting the aforementioned change, the control parameter information relating to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. In the second environment, changes to the change history information in the database contained in the second container, which is deployed in the second environment and synchronized with the first container by the data synchronization function, are detected. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management device characterized by having a control unit that performs processing.

[0204] (Note 2) The control unit is, The management device according to Appendix 1, characterized in that, in the first environment described above, when writing the content of the detected change to the change history information, if the update of the control parameter information corresponding to the change fails, the content of the change is not written to the change history information.

[0205] (Note 3) The control unit is, The management device according to Appendix 1, characterized in that, if the management parameter information for managing the second container is successfully updated in the second environment, it updates the control parameter information for controlling the second container, which is included in and referenced by the second container, in accordance with the detected change in the change history information.

[0206] (Note 4) The control unit is, In the first environment, upon detecting a change in the management parameter information, the control parameter information relating to the control of the other container, which is contained in and referenced by the other container among the containers deployed in the first environment that are different from the first container, is updated in accordance with the change. In the second environment, if the management parameter information is successfully updated, the control parameter information relating to the control of the other container, which is contained in and referenced by the other container among the containers deployed in the second environment that is different from the second container, is updated in accordance with the detected change in the change history information. The control device described in Appendix 3, characterized by the features described herein.

[0207] (Note 5) The management device according to Note 1, characterized in that the management parameter information relating to the management of the first container includes the configuration information of the first container and the parameter values ​​set in the database included in the first container.

[0208] (Note 6) The management device according to Note 1, characterized in that the data synchronization function is streaming replication.

[0209] (Note 7) The first environment mentioned above is the production environment, The second environment mentioned above is a disaster response environment. The control device described in Appendix 1, characterized by the features described herein.

[0210] (Note 8) Of the redundant first environment and second environment, Under the aforementioned first environment, The system detects changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment. Upon detecting the aforementioned change, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the details of the change are written to the change history information provided in the database. The computer performs the process, In the second environment, when a change in change history information in a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function is detected, the management parameter information related to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the change. A management method characterized by the following features.

[0211] (Note 9) Of the redundant first environment and second environment, In the first environment, when a change in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, is detected, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. Under the second environment described above, The system detects changes in change history information within a database contained in a second container that is deployed in the second environment and synchronized with the first container by a data synchronization function. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management method characterized by having a computer perform the processing.

[0212] (Note 10) Of the redundant first environment and second environment, Under the aforementioned first environment, The system detects changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment. Upon detecting the aforementioned change, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the details of the change are written to the change history information provided in the database. Let the computer perform the process, In the second environment, when a change in change history information in a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function is detected, the management parameter information related to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the change. A management program characterized by the following features.

[0213] (Note 11) Of the redundant first environment and second environment, In the first environment, when a change in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, is detected, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. Under the second environment described above, The system detects changes in change history information within a database contained in a second container that is deployed in the second environment and synchronized with the first container by a data synchronization function. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management program characterized by having a computer perform the processing. [Explanation of symbols]

[0214] 101 Management device 101-1 First control device 101-2 Second control device 110 The first environment 111,121 Management Department 112,122 Management parameter information 113 Container No. 1 114,124 Databases 115,125 Control parameter information 116,126 Change history information 120 Second Environment 123 Second container 200 Information Processing Systems 201,202 Information Processing Equipment 203 Administrator Terminal 210 Network 300 bus 301 CPU 302 memory 303 Disk Drive 304 disks 305 Communication I / F 306 Portable recording medium interface 307 Portable recording media 400,500 Control Unit 401 Creation Department 402 First detection unit 403 First Update Section 501 Second detection unit 502 Second Renewal Section 600 System Administrators 1701,1702 Parameter Information

Claims

1. Of the redundant first and second environments, In the first environment, changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, are detected. Upon detecting the aforementioned change, the control parameter information relating to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. In the second environment, changes to the change history information in the database contained in the second container, which is deployed in the second environment and synchronized with the first container by the data synchronization function, are detected. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management device characterized by having a control unit that performs processing.

2. The control unit, The management device according to claim 1, characterized in that, in the first environment, when writing the detected change to the change history information, if updating the control parameter information corresponding to the change fails, the change is not written to the change history information.

3. The control unit, The management device according to claim 1, characterized in that, if the management parameter information for managing the second container is successfully updated in the second environment, the control parameter information for controlling the second container, which is included in and referenced by the second container, is updated in accordance with the detected change in the change history information.

4. The control unit, In the first environment, upon detecting a change in the management parameter information, the control parameter information relating to the control of the other container, which is contained in and referenced by the other container among the containers deployed in the first environment that are different from the first container, is updated in accordance with the change. In the second environment, if the management parameter information is successfully updated, the control parameter information relating to the control of the other container, which is contained in and referenced by the other container among the containers deployed in the second environment that is different from the second container, is updated in accordance with the detected change in the change history information. The control device according to feature 3.

5. Of the redundant first and second environments, Under the first environment described above, The system detects changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the container deployed in the first environment. Upon detecting the aforementioned change, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the details of the change are written to the change history information provided in the database. The computer performs the process, In the second environment, when a change in change history information in a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function is detected, the management parameter information related to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the change. A management method characterized by the following features.

6. Of the redundant first and second environments, In the first environment, when a change in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, is detected, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. Under the second environment described above, The system detects changes in change history information within a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management method characterized by having a computer perform the processing.

7. Of the redundant first and second environments, Under the first environment described above, The system detects changes in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the container deployed in the first environment. Upon detecting the aforementioned change, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the details of the change are written to the change history information provided in the database. Let the computer perform the process, In the second environment, when a change in change history information in a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function is detected, the management parameter information related to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the change. A management program characterized by the following features.

8. Of the redundant first and second environments, In the first environment, when a change in management parameter information related to the management of the first container, including a database, which is referenced by the management unit that manages the containers deployed in the first environment, is detected, the control parameter information related to the control of the first container, which is included in and referenced by the first container, is updated in accordance with the change, and the content of the change is written to the change history information provided in the database. Under the second environment described above, The system detects changes in change history information within a database contained in a second container deployed in the second environment and synchronized with the first container by a data synchronization function. Upon detecting the aforementioned change, the management parameter information relating to the management of the second container, which is referenced by the management unit that manages the container deployed in the second environment, is updated in accordance with the aforementioned change. A management program characterized by having a computer perform the processing.