JP2011034520A - Emergency web server switching system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system in which an emergency server carries out response to the access for the system, when access to a Web server is concentrated by any cause. <P>SOLUTION: The system includes a system management server 1 and an emergency server 2 which works under it. The system management server 1 can communicate with a DNS server 3 and a Web server 4 in which a registered user opens a Web site through the Internet N. The system management server 1 includes a storage means for storing various kinds of option data for simplifying setting by the registered user and information necessary for server switching/restoration; a means for forming a user setting screen through which the user can perform emergency setting; a means for registering the setting content by the user in the storage means; a means for receiving a server switching/restoration request from the user; a means for requesting change of DNS setting for server change in emergency; and a means for transmitting data including an emergency display page to the emergency server 2. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

The present invention relates to a system in which an emergency server acts as a proxy for access when response performance for Web access is degraded for some reason.

With the spread of the Internet, the importance and dependence of Web sites as advertising means, sales means, and business contact means are increasing. For this reason, companies of a wide variety of industries have opened Web sites regardless of the size. However, while it is convenient, it is also true that there is a possibility that a company that sells a product with a habit or a website or blog such as a talented person who utters a problem may become temporarily incapacitated for the time being. is there. In the case of rushing access, for example, in online shopping, there are problems in online inquiries from customers, as well as daily operations such as sending and receiving e-mails and basic operations themselves as well as advertising.
For this reason, a number of patent applications have been filed for technologies that deal with concentration of access to a specific server. For example, “Network Security System” described in Patent Document 1 and “DoS Attack or DDoS Attack” described in Patent Document 2 are dealt with. One example is “method, network device, and analysis device”.

JP 2005-328373 A JP 2006-164038 A

For large corporations and public institutions with ample funds and technical capabilities, it is possible to clear such problems by installing multiple servers and developing a system that filters access requests. is there. However, it is difficult to expect such a measure from a company without individuals or professional staff. However, if you do not deal with it at all, you will miss business opportunities and damage customer trust. Moreover, since individuals and small businesses often use a Web server as a mail server or use the same line even if the server is different, there is a possibility that even an email transmission / reception may be disturbed.
None of the existing patent applications, including Patent Documents 1 and 2, attempted to solve such problems with individuals and small businesses in mind.

  In view of such a problem, the present invention started from assuming an individual or a small-sized company that has established a Web site as a user. In other words, even if a small-scale company or individual that has established a Web site suffers damage such as so-called “flame”, it is necessary to provide a mechanism that can minimize damage by a simple method at a low cost. Objective.

In order to achieve the above object, an invention according to claim 1 is an emergency Web server switching system including a system management server and an emergency server,
The system management server is capable of communicating via the Internet with a DNS server, a user-side Web server and a user terminal by a website opening user,
The system management server includes option data storage means, server change information storage means,
User setting screen creation means, user setting item registration means, user trigger reception means, DNS setting means, emergency server management means, and emergency server access load monitoring means .
The option data storage means stores various option data for allowing the user to easily set screen design templates to be displayed by the user in an emergency, conditions for automatic switching / restoration of servers, and the like.
The server change information storage means stores information necessary for server switching / restoration for each user. The information includes the domain name and IP address of the user's original Web server, information for specifying the template of the emergency display screen data (example: template number), server switching / restoration trigger type (instructed by the user) Or whether the system performs it automatically).
The user setting screen creation means creates a user setting screen so that the user can make emergency settings using the data extracted from the option data storage means. In order to reduce the burden on the user, this screen is designed so that the user's judgment can be minimized and the screen can be set by a simple operation mainly using a mouse click.
The user setting item registration means registers the contents set by the user on the user setting screen in the server change information storage means.
The user trigger receiving means receives a server switching request and a server restoration request from the user.
The DNS setting means requests the DNS server to change the DNS setting for switching to the emergency server or restoring to the original Web server.
The emergency server management means transmits data including emergency display page data necessary for server switching to the emergency server.
The emergency server access load monitoring means monitors the access load of the emergency server and visualizes the monitoring result in response to the user's request. As a result, the user operating the Web site can use the system of the present invention. By registering and setting information required in an emergency in advance, access to the emergency server can be redirected in a short time when there is a flood of access to your Web server. Therefore, other processes performed by the Web server such as mail transmission / reception and other processes using the same line can be continued as usual. Since the user of this system is not required to have any specialized knowledge for server switching, there is no difficulty in introducing the system of the present invention.
Needless to say, settings by the user and requests to the system management server are made via the user terminal.

In order to achieve the above object, the invention according to claim 2 is the invention according to claim 1, wherein the system management server monitors the access load of the web server on the user side, and the access load. And an emergency server change determination means for determining automatic server switching or server automatic restoration according to a predetermined determination condition.
The means for monitoring the access load of the user-side Web server is not particularly limited, but one of the methods is that the system management server periodically accesses the Web server and totals and analyzes the response time as in the following embodiment. It is.
As described above, since abnormal situations such as access concentration are automatically determined on the system side and server switching is automatically performed, the burden on the user is greatly reduced.

In order to achieve the above object, the invention according to claim 3 is the invention according to claim 1 or 2, wherein information from the user received by the user trigger receiving means of the system management server is registered in advance. It is transmitted from a mobile phone.
Thereby, even if the user cannot operate the system via a communication line that is loaded in an emergency such as concentration of access, the user can operate using the mobile phone.

To achieve the above object, according to a fourth aspect of the present invention, in the invention according to any one of the first to third aspects, the option data storage means includes an emergency display page data template to be displayed in an emergency. Are stored in an arbitrary number, and the user creates emergency display page data by selecting one of the templates via the user setting screen and making necessary inputs.
This saves the user from having to think about the screen design in preparation for emergencies that rarely occur.

In order to achieve the above object, the invention according to claim 5 is the invention according to any one of claims 1 to 4, wherein the option data storage means is automatically switched or automatically restored by the emergency server change determination means. An arbitrary number of determination conditions are stored, and the user can select one of the determination conditions via the user setting screen.
As a result, as long as the user selects one of the judgment conditions prepared on the system side, the system side will automatically make an emergency judgment and response. do not need. In addition, since switching can be performed with a minimum amount of knowledge, a responsible person unfamiliar with the computer can switch.

  Even if access to the Web server is concentrated, it is possible to suppress the influence on other operations such as mail transmission / reception. It is desirable to make necessary settings for the system in advance in case of an emergency, but it can be easily set without specialized knowledge. Although the risk such as “flame” may increase in the future, it is unlikely to decrease, so the present invention provides a system that is extremely useful for individuals and small businesses that establish websites. .

It is a system configuration figure of a 1st embodiment of the present invention. It is a functional block diagram of the system management server of the 1st Embodiment of this invention. It is a figure which shows the example of the domain name and IP address of the server of the 1st Embodiment of this invention. It is a figure which illustrates the system management screen of the 1st Embodiment of this invention. It is a figure which illustrates the setting screen for users of a 1st embodiment of the present invention. It is a figure which illustrates the template selection screen of the page for emergency display of the 1st Embodiment of this invention. It is a figure which illustrates the template selection screen of the page for emergency display of the 1st Embodiment of this invention. It is a figure which illustrates the user setting item of the 1st Embodiment of this invention. It is a figure which illustrates the server change instruction | indication screen by the registered user of the 1st Embodiment of this invention. It is a figure which illustrates the page for emergency display of the 1st Embodiment of this invention. It is a functional block diagram of the system management server of the 2nd Embodiment of this invention. It is a figure which illustrates the screen which selects the conditions for the server automatic change of the 2nd Embodiment of this invention. It is a figure which illustrates the user setting item of the 2nd Embodiment of this invention. It is a processing flow figure of the system management server of the 2nd Embodiment of this invention. It is a functional block diagram of the system management server of the 3rd Embodiment of this invention. It is an example of the HTML file redirected to the server for emergency of the 3rd Embodiment of this invention.

<< First Embodiment >>
In the first embodiment, as shown in FIG. 1, a system management server 1, an emergency server 2, a DNS server 3, a user-side Web server 4, a user terminal 5, and a general user (hereinafter, “client”) terminal 6, each connected to the Internet N.
The system management server 1 and the emergency server 2 are separately connected to each other via a communication line N2.

The user-side Web server 4 is a server in which a user registered in the system of the present embodiment (hereinafter referred to as “registered user”) opens a Web site. Although only one user-side Web server 4 is shown in FIG. 1, anyone can register with this system as long as they agree to the contract, so the number of user-side Web servers 4 is not limited.
The user terminal 5 is an operation means by a registered user, and includes a user PC (5a) and a mobile phone 5b for user operation. When the user-side Web server 4 is also used as the user PC (5a), or when the user-side Web server 4 and the user PC (5a) are using the same line, the user PC (5a) starts when the access is concentrated. Since this system cannot be operated in an emergency, the user-operated mobile phone 5b is used for an emergency operation.
In the following description, some operation by the “registered user” is performed via the user terminal 5.

The DNS server 3 is a server having zone information for storing associations between domain names and IP addresses, and having a function of extracting an IP address from a domain name or extracting a domain name from an IP address. It is assumed that the system management server 1 can request the DNS server 3 to change the DNS setting.

The system management server 1 has a function of operating and managing the system of the present embodiment, and includes a storage unit 7, a processing unit 8, and a communication interface unit 9, as shown in FIG.

The storage unit 7 includes option data storage means 10 and server change information storage means 11.
The processing unit 8 includes a user setting screen creation means 12, a user setting item registration means 13, a user trigger reception means 14, a DNS setting means 15, an emergency server management means 16, and an emergency server access load monitoring means 17. Including.
However, the classification of each means is merely for convenience of explanation.
Each means is implemented by hardware and software according to its function. In the case of software, the CPU executes a program stored in a storage means such as a ROM or a hard disk. Since these are well-known matters, description thereof will be omitted.
The communication interface unit 9 communicates with other information processing apparatuses via a communication network.
Although not shown in FIG. 2, the system management server 1 stores work intermediate data, parameters, screen data (see FIG. 4, FIG. 5, etc.) that serve as an interface with the registered user, etc. A storage means is provided. In addition, input / output means such as a keyboard and a display and drivers are also provided.

The option data storage means 10 displays an emergency display page template (see FIGS. 6 and 7), and a selection of judgment conditions (see FIG. 12) when the Web server is automatically switched or restored. Remember. Since these optional data are prepared in the system, the registered user can easily set for server switching / restoration even without expert knowledge.
The server change information storage unit 11 stores information necessary for changing (switching or restoring) a server in an emergency for each registered user. For example, the domain name, IP address and website URL of the user-side web server 4, emergency display page, and conditions such as whether the user instructs switching or restoration or whether to automate (see FIG. 8) are stored. .

The user setting screen creation means 12 creates a user setting screen (see FIGS. 6 and 12, etc.) that allows the registered user to make emergency settings using the data extracted from the option data storage means 10.
The user setting item registration unit 13 generates information necessary for emergency server switching based on information input by the registered user via the user setting screen and stores the information in the server change information storage unit 11.
The user trigger receiving unit 14 receives a server switching request and a server restoration request from a registered user.
The DNS setting unit 15 requests the DNS server 3 to change the DNS setting based on the data extracted from the server change information storage unit 11.
The emergency server management means 16 transmits necessary data including emergency display page data to the emergency server 2.
The emergency server access load monitoring means 17 monitors the access load of the emergency server 2. At the same time, screen data that visualizes the monitoring result according to the request of the registered user is also created.

The emergency server 2 is a server that accepts access from the client terminal 6 in place of the original user-side Web server 4 in an emergency, and is managed by the system management server 1. When the system management server 1 performs server switching processing, it accepts access from the client terminal 6 instead of the original user-side Web server 4. The emergency server 2 includes a file upload function, storage means for storing the correspondence between the URL of the registered user's Web site and the file name of the emergency page, and the like.

Subsequently, the operation of the present embodiment will be described.
An example of the domain name and IP address of each server used in the following description is as shown in FIG.

In order to receive the server switching service by the system of this embodiment, user registration is required in advance. At this time, in addition to the personal information such as the user name and address, the URL and IP address of the user-side Web server 4 being used are also registered. Furthermore, if it is expected that the user-operated mobile phone 5b will be used for emergency operations, a password and model-specific information may be registered. This is because a server switching request or the like is assumed as an emergency operation, but to prevent such an important operation from being performed by an unauthorized person.

In addition to the above user personal information, the registered user also sets necessary information in the system so that the server can be changed quickly in an emergency.
In order for a registered user to be able to make settings easily on a GUI (Graphical User Interface) basis, the user setting screen creation means 12 of the system management server 1 generates a user setting screen and transmits it to the registered user side. A registered user can perform necessary settings only by performing a selection operation using radio buttons and check boxes, or a minimum key input operation. The information processing apparatus used by the registered user for setting may be the user-side Web server 4 or the user PC (5a) or the mobile phone 5b.
When the registered user first accesses this system, a main menu screen P1 as illustrated in FIG. 4 is transmitted. When the “user setting” menu item is selected, a transition is made to a user setting screen P2 as illustrated in FIG.

When the button “Generate general-purpose display screen” is clicked on the screen P2, a transition is made to a template selection screen P3 as illustrated in FIG. In FIG. 6, two types of general-purpose display screen templates are displayed. If the registered user inputs any number and clicks the “Confirm” button, the template number is stored in the server change information storage unit 11. Is memorized. If the “return” button is clicked, a transition is made to the setting screen P2 of FIG. Here, if a registered user name or the like is appropriately inserted somewhere in the text of the selected template, display screen data when an emergency server switch is performed is created. The registered user name or the like may be inserted on the system management server 1 side when the server is switched.

When a specific product display screen is to be created, when the button “Generate specific product display screen” is clicked on the screen P2, a transition is made to a template selection screen P4 as illustrated in FIG. In FIG. 7, two types of templates for the specific product display screen are displayed. If the registered user inputs any number and clicks the “Confirm” button, the template is stored in the server change information storage unit 11. The number is stored. If the “return” button is clicked, a transition is made to the setting screen P2 of FIG. Here, if a product name, a registered user name, and the like are appropriately inserted into the selected template, display screen data when emergency server switching is performed is created (see FIG. 10).

The general-purpose display screen can be displayed universally whatever the cause of the difficulty in accessing the user-side Web server 4 from the client terminal 6 (whether access has been flooded or a failure has occurred in the communication line, etc.) It is a screen. Therefore, it has already been completed at the time of setting.
On the other hand, the display screen for specific products is a screen that shows which products related to access are concentrated when access to pages related to specific products is inundated. A template is selected at the time of setting, and when a server switch is actually required, a specific product name is entered in the product name column, which is finally completed.

Server switching and restoration can be performed either by an instruction from a registered user or by determination by the system. Hereinafter, the former is called “manual” and the latter is called “automatic”. That is, since there are manual and automatic triggers for changing the server, the registered user selects one in advance.
In the first embodiment, switching and restoration are performed manually.
The user setting item registration unit 13 registers the contents of the above user settings in the server change information storage unit 11. As a result, the setting data stored in the server change information storage unit 11 is as shown in FIG.
In this way, if preparation is made before an emergency occurs, it is possible to cope smoothly even in an emergency. Moreover, even if the original page data is not created for rare emergency situations, the template can be selected, so that the burden on the registered user can be greatly reduced.

Incidentally, access from the client terminal 6 normally proceeds in the following procedure.
In the example of FIG. 3, the URL of the site managed by the user-side Web server 4 is http: // www. AAA. jp /, the IP address is 1.2.3.4. The client terminal 6 is http: // www. AAA. When accessing jp /, the client terminal 6 sends the domain name AAA. Queries the IP address corresponding to jp. Since the DNS server 3 returns the IP address = 1.2.3.4, the client terminal 6 accesses the user-side Web server 4 with the IP address.

However, when access to the user-side Web server 4 is concentrated, responses to requests from the client terminal 6 are significantly slowed down or timed out. In this case, other business operations being processed by the user-side Web server 4 and other business operations using the same line are also hindered. When the registered user recognizes such an inconvenient situation, the system management server 1 is accessed and the menu item “switch / restore instruction” on the main menu screen P1 is selected. Since the screen changes to the screen P5 illustrated in FIG. 9, “switch” is selected. When “switch” is selected, either a general-purpose display screen or a specific product display screen is selected. If the display screen for specific product is selected, a specific product name is input. FIG. 10 is an emergency display page generated by the system management server 1 when the product name “Matcha flavored Castella” is input on the screen P5. The file name for storing this page data is pageA. It is set as html.

When the operation by the registered user is accepted by the user trigger receiving unit 14, the emergency server management unit 16 transmits the emergency display page data of FIG. 10 to the emergency server 2. At the same time, the URL (http: //www.AAA.jp/) corresponding to the file name (pageA.html) is also transmitted. On the emergency server 2 side, this correspondence is stored, and if the character string of the access request from the client terminal 6 starts with “http: //www.AAA.jp/”, the corresponding file pageA. html is transmitted to the client terminal 6.

The DNS setting means 15 sends the domain name AAA. A request is made to change the IP address corresponding to jp from the current “1.2.3.4” to “111.3.4” which is the IP address of the emergency server 2. Thereby, the zone information of the DNS server 3 becomes the zone information (after setting change) in FIG.
Thus, the server switching process by the system management server 1 is completed.

Access from the client terminal 6 after server switching is handled as follows.
The client terminal 6 is http: // www. AAA. When accessing jp /, the client terminal 6 sends the domain name AAA. Queries the IP address corresponding to jp. Since the DNS server 3 returns IP address = 111.2.3.4, the client terminal 6 accesses the emergency server 2. The emergency server 2 starts with the file pageA. Since the request character string starts with the character string “http: //www.AAA.jp/”. html is transmitted to the client terminal 6.
It is considered that access concentrates on the emergency server 2. Therefore, in order to speed up the response, the file pageA. It is desirable to expand html on the memory of the emergency server 2.
Thus, since the access from the client terminal 6 is performed with respect to the emergency server 2, the original user-side Web server 4 can process other tasks without delay. In many cases, the Web server is used as a mail server. In this case, if the IP address of the mail server is not changed, the user-side Web server 4 may be used as it is as usual. it can.

The operation when the concentration of access has calmed down and the registered user determines to restore the server will be described.
Here, since the access load state of the emergency server 2 can be monitored through the system management server 1, the registered user can determine that the concentration of access has calmed down. Note that the system management server 1 creates screen data in which the access load is graphed in response to a request from the user terminal 5 and transmits the screen data to the user terminal 5, but details thereof are omitted.
The registered user accesses the system, selects the menu item “server switching / restoration” on the screen P1, and transitions to the screen P5 illustrated in FIG. When the user trigger receiving unit 14 receives that “Restore” has been selected, the system management server 1 performs the following processing.
First, the DNS setting means 15 sends a domain name AAA. A setting change is requested so that the IP address corresponding to jp is returned to 1.2.3.4. Thereby, the access request from the client terminal 6 goes to the original user-side Web server 4.
At the same time, the emergency server management means 16 sends the file pageA. Delete html.

<< Second Embodiment >>
This embodiment is different from the first embodiment in which the system management server automatically determines and performs server switching and server restoration, and performs switching and restoration according to an instruction from a registered user.
Hereinafter, the difference will be mainly described. In the figure, the same reference numerals as in the first embodiment are used if the functions are the same.
A functional block diagram of the system management server 21 of this embodiment is shown in FIG. Web server access load monitoring means 18 and emergency server change determination means 19 are added to the system management server 1 of FIG.
The Web server access load monitoring means 18 monitors the access load of the user-side Web server 4, and the emergency server change determination means 19 performs automatic server switching or automatic restoration according to the determination conditions set by the user based on the access load. Judge whether necessary or not.

When the registered user first accesses the system and selects the menu item “user setting” on the screen P1 as illustrated in FIG. 4, the registered user transitions to the user setting screen P2 as illustrated in FIG. In this screen P2, when “automatic” is selected for server switching, the screen changes to a condition setting screen P6 as illustrated in FIG. Since the conditions for automatic switching read from the option data storage means 10 are listed on this screen P6, the registered user selects any one. If a “recommended” condition is provided as shown in FIG. 12, it is convenient for the user.
The restoration condition is also selected by the registered user in the same manner.
As a result of the above selection, information as shown in FIG. 13 is stored in the server change information storage unit 11. The server change information storage unit 11 also stores a switching flag. It is assumed that ON is set during switching to the emergency server 2 and OFF is set otherwise.

The processing of the system management server 21 will be described with reference to the flowchart of FIG.
Here, description will be made assuming that there is only one registered user.
If the switching flag is OFF (OFF in step S1), the Web server access load monitoring means 18 monitors the access load by a predetermined method (step S2). When the emergency server change determination means 19 determines that the monitoring result matches the automatic switching condition (yes in step S3), server switching processing is performed (step S4). This server switching process includes a process for transmitting emergency display page data to the emergency server 2, a DNS setting change request to the DNS server 3, and setting a switch flag to ON. If necessary, notify the registered user that server automatic switching has been performed. On the other hand, if it is determined that the switching condition is not met (no in step S3), the Web server access load monitoring means 18 continues monitoring (step S2).

When the switching flag is ON (ON in step S1), the emergency server access load monitoring means 17 monitors the access load of the emergency server 2 (step S5). When the emergency server change determination means 19 determines that the monitoring result matches the automatic restoration condition (yes in step S6), server restoration processing is performed (step S7). This server restoration process includes a DNS setting change request to the DNS server 3 and a process such as setting the switch flag to OFF.
If necessary, notify the registered user that the server has been automatically restored. When the automatic restoration process is completed, the process returns to step S1.
On the other hand, if the automatic restoration condition is not met (no in step S6), the emergency server access load monitoring means 17 continues to monitor the access load (step S5).
In FIG. 14, it has been described that there is one registered user. However, when there are a plurality of registered users, the processes from step S1 to step S7 are repeated for the number of registered users.

In the second embodiment, since switching and restoration are automatically performed, even if there is no specialized staff on the registered user side, it is possible to cope with the minimum necessary, and normal operations can be performed even if access is concentrated. Yes.

<< Third Embodiment >>
This embodiment differs from the first embodiment in that a redirect by a registered user is used together with a DNS setting change.
Hereinafter, the difference will be mainly described. In the figure, the same reference numerals as in the first embodiment are used if the functions are the same.
A functional block diagram of the system management server 31 of this embodiment is shown in FIG. Redirect notification receiving means 20 is added to the system management server 1 of FIG.
This redirect notification receiving means 20 receives a redirect setting notification or a redirect release notification from the registered user to the emergency server 2.

The registered user sends a server switching request to the system management server 31 and changes the HTML file describing screen data normally accessed from the client terminal 6 to an HTML file composed of a code that redirects the server 2 for emergency. To do. An example of such an HTML file is shown in FIG. 16, and the portion enclosed by a broken-line rectangle in the figure is http: // www. AAA. jp / from http: // www. XXX. This is a code that describes redirection to jp / AAA /. Here, XXX. Since jp is the domain name of the emergency server 2, access to the user-side Web server 4 is redirected to the emergency server 2. The registered user transmits a notification that the redirect has been made to the emergency server 2 to the system side, and the notification is received by the redirect notification receiving means 20.

On the other hand, when receiving a switching request from a registered user, the system management server 31 transmits an emergency display page to the emergency server 2 and changes the DNS setting, as in the first embodiment. The URL of this registered user's emergency display page in the emergency server 2 is http: // www. XXX. jp / AAA / pageA. It is assumed that it is html. The emergency server management means 16 sends a redirect URL (http://www.AAA.jp/) and a redirect destination URL (http://www.XXX.jp/AAA/) to the emergency server 2. Memorize the correspondence.

The client terminal 6 passes through the DNS server 3 on which the change of the DNS setting has been reflected to http: // www. AAA. When accessing jp /, a page browsing request is transmitted to the emergency server 2. The emergency server 2 is http: // www. AAA. For access to jp /, please visit http: // www. XXX. jp / AAA / is regarded as the same access and pageA. html is transmitted to the client terminal 6.

Changes in the DNS settings are not reflected immediately, and it takes some time until the DNS servers in various places are thoroughly implemented. During that time, the original user-side Web server 4 is accessed as usual. In this case, since the access request is directed to the emergency server 2 by using the redirect together, the load on the user-side Web server 4 is reduced, and adverse effects on other tasks such as mail transmission / reception can be reduced.

When a registered user transmits a server restoration request to the system management server 31, the registered user also deletes the redirect description part of the HTML file in the user-side Web server 4. Thereby, when the user-side Web server 4 returns to normal, it is no longer redirected to the emergency server 2.

《Other forms》
In the first embodiment, the trigger is manual, and in the second embodiment, the trigger is automatic. However, switching may be performed manually and restoration may be performed automatically, or switching may be performed automatically and restoration may be performed manually. Absent.
Various screen designs and transitions between screens that serve as an interface between the system management server and the registered user of the above embodiment are merely examples.
Moreover, the conditions for automatic switching / restoration are merely examples. Further, although the access load is monitored by the system management server, a dedicated device for monitoring may be provided.
Furthermore, in order to re-specify the template of the emergency display page, the registered user may instruct the server switching a plurality of times. However, if the switch to the emergency server has already been performed, the DNS setting is not changed.
In short, for the present invention, when the access to the user-side Web server 4 is concentrated, the emergency server 2 registered in advance is made to handle the access in order to prevent other business operations from being affected. In addition, it is important that this can be realized without giving a special burden to the user.

The present invention can demonstrate its true value when a small company or an individual who has opened his own website but has no specialized staff becomes a registered user. Since there is rarely a flood of access to a specific Web site, it is registered in the system in the sense of a kind of insurance so that the server switching service can be enjoyed whenever necessary. Since the emergency server is shared in this system, the larger the number of registrants, the lower the system registration fee per registrant. If there is no situation in which a proxy server is used, the registration fee is a kind of abandonment, but it can be divided into insurance. If a proxy server is used, the subsequent registration fee may be increased. Since a situation such as so-called “flame” can be dealt with inexpensively and easily, an individual or a company that wants to open a Web site can open the Web site with confidence by using the system of the present invention.
When a user shares a rental server operated by a small business with other users, there is a possibility that the service may be stopped or the contract may be canceled if a user concentrates on the website There is. Even in such a utilization method, the present invention can perform an effective countermeasure.

1, 21, 31 System management server 2 Emergency server 3 DNS server 4 User-side Web server 5 (5a, 5b) User terminal 6 Client terminal 10 Option data storage means 11 Server change information storage means 12 User setting screen creation Means 13 User setting item registration means 14 User trigger reception means 15 DNS setting means 16 Emergency server management means 17 Emergency server access load monitoring means 18 Web server access load monitoring means 19 Emergency server change determination means 20 Redirect notification reception Mean N Internet

Claims (5)

An emergency web server switching system including a system management server and an emergency server,
The system management server is capable of communicating via the Internet with a DNS server, a user-side Web server and a user terminal by a website opening user,
The system management server
Option data storage means for storing various option data for simplifying the setting by the user;
Server change information storage means for storing information necessary for server switching / restoration including the domain name and IP address of the user-side Web server;
User setting screen creation means for creating a user setting screen that allows the user to make emergency settings using the data extracted from the option data storage means;
User setting item registration means for registering the setting content by the user in the server change information storage means;
User trigger receiving means for receiving a server switching request and a server restoration request from a user;
DNS setting means for requesting the DNS server to change settings based on data obtained by referring to the server change information storage means;
The emergency server management means for transmitting data including emergency display page data to be used when switching to the emergency server and the access load of the emergency server are monitored, and the monitoring result is obtained in response to a user request. Emergency server access load monitoring means to be visualized,
An emergency Web server switching system comprising: The system management server
Web server access load monitoring means for monitoring the access load of the user-side Web server;
The emergency web server switching system according to claim 1, further comprising emergency server change determination means for determining automatic server switching or automatic server restoration according to a predetermined determination condition based on the access load. . 3. The emergency Web server switching system according to claim 1, wherein information from the user received by the user trigger receiving means is transmitted from a mobile phone registered in advance. The optional data storage means stores an arbitrary number of emergency display page data templates to be displayed in an emergency,
The user creates emergency display page data by selecting any template through the user setting screen created by the user setting screen creating means and making necessary input. The emergency Web server switching system according to any one of Items 1 to 3. The option data storage means stores an arbitrary number of determination conditions for automatic switching or automatic restoration by the emergency server change determination means,
The emergency Web server switching system according to any one of claims 1 to 4, wherein the user can select any determination condition via the user setting screen created by the user setting screen creating means. .

Images