CN112436953B - Page data backup and disaster recovery page display method and device - Google Patents
Page data backup and disaster recovery page display method and device Download PDFInfo
- Publication number
- CN112436953B CN112436953B CN202010819506.0A CN202010819506A CN112436953B CN 112436953 B CN112436953 B CN 112436953B CN 202010819506 A CN202010819506 A CN 202010819506A CN 112436953 B CN112436953 B CN 112436953B
- Authority
- CN
- China
- Prior art keywords
- disaster recovery
- page
- data
- interface
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 506
- 238000000034 method Methods 0.000 title claims abstract description 65
- 230000003068 static effect Effects 0.000 claims description 54
- 238000009877 rendering Methods 0.000 claims description 40
- 238000004590 computer program Methods 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 9
- 230000008859 change Effects 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a page data backup method and device, and belongs to the technical field of Internet. The method comprises the following steps: acquiring a disaster recovery interface list at fixed time, and requesting disaster recovery data corresponding to at least one interface from a data server through the at least one interface contained in the disaster recovery interface list; and uploading the disaster recovery data to a cloud storage server. The application can realize high availability of the front-end page.
Description
Technical Field
The application relates to the field of Internet, in particular to a page data backup and disaster recovery page display method and device.
Background
In the prior art, in order to enable the front end (client) to still be normally used when the front end server or the machine room is unexpected, the front end server is usually deployed in a disaster tolerant manner, that is, the rear end server is deployed at different places, one of the servers at the places is used as a main server, and one or more of the servers at the places is used as a disaster tolerant server, so that when the front end fails to access the main server, the front end is automatically switched to access the disaster tolerant server to provide services for the front end through the disaster tolerant server.
However, in some cases, both the host server and the disaster recovery server may fail, at which point the front end will not be able to present the page information.
Disclosure of Invention
In view of this, a method and apparatus for backing up page data and displaying disaster recovery pages, a computer device and a computer readable storage medium are provided to solve the problem that the front end cannot display page information when both the main server and the disaster recovery server fail.
The application provides a page data backup method, which comprises the following steps:
acquiring a disaster recovery interface list at fixed time, and requesting disaster recovery data corresponding to at least one interface from a data server through the at least one interface contained in the disaster recovery interface list;
and uploading the disaster recovery data to a cloud storage server.
Optionally, the page data backup further includes:
acquiring a preset data interface at fixed time, and requesting corresponding interface data from the data server through the data interface;
generating static disaster recovery page data according to the interface data;
and uploading the disaster recovery page data to the cloud storage server.
Optionally, the page data backup further includes:
And configuring interfaces contained in the disaster recovery interface list.
The application provides a disaster recovery page display method, which is applied to a client and comprises the following steps:
when the client side request interface fails, an H5 disaster recovery page is started;
the disaster recovery interface is called through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server;
performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page
Optionally, the obtaining disaster recovery data stored in the cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page includes:
requesting a disaster recovery interface switch configuration file from a preset server through the H5 disaster recovery page;
determining whether the disaster recovery switch is in an on state according to the requested switch configuration file;
and if the disaster recovery switch is in an on state, calling a disaster recovery interface through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server.
Optionally, the disaster recovery page display method further includes:
if the disaster recovery switch is in a closed state, acquiring static disaster recovery page data from the cloud storage server;
and performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
Optionally, the disaster recovery page display method further includes:
when the page rendering fails according to the H5 disaster recovery page and the disaster recovery data, acquiring static disaster recovery page data from the cloud storage server;
and performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
The application also provides a page data backup device, which comprises:
the system comprises an acquisition module, a data server and a disaster recovery module, wherein the acquisition module is used for acquiring a disaster recovery interface list at fixed time and requesting disaster recovery data corresponding to at least one interface from the data server through the at least one interface contained in the disaster recovery interface list;
and the uploading module is used for uploading the disaster recovery data to a cloud storage server.
The application also provides a disaster recovery page display device, which is applied to the client and comprises:
the starting module is used for starting the H5 disaster recovery page when the client side request interface fails;
the acquisition module is used for acquiring disaster recovery data stored in the cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page;
and the rendering module is used for performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
The application also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when executing the computer program.
The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the above method.
The application also provides a page data display system, which comprises a page data backup device and a disaster recovery page display device, wherein:
the page data backup device comprises: the system comprises an acquisition module, a data server and a disaster recovery module, wherein the acquisition module is used for acquiring a disaster recovery interface list at fixed time and requesting disaster recovery data corresponding to at least one interface from the data server through the at least one interface contained in the disaster recovery interface list; the uploading module is used for uploading the disaster recovery data to a cloud storage server;
the disaster recovery page display device includes: the starting module is used for starting the H5 disaster recovery page when the client side requests the interface to fail; the acquisition module is used for acquiring disaster recovery data stored in the cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page; and the rendering module is used for performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
The beneficial effects of the technical scheme are that:
according to the embodiment of the application, the disaster recovery interface list is obtained at fixed time, and disaster recovery data corresponding to at least one interface is requested from a data server through the at least one interface contained in the disaster recovery interface list; and uploading the disaster recovery data to a cloud storage server. In this embodiment, by backing up disaster recovery data corresponding to the disaster recovery interface in advance, when the back-end main server and the disaster recovery server are available, the front-end page can still be displayed through the backup disaster recovery data, so as to achieve high availability of the front-end page.
Drawings
FIG. 1 is a block diagram of one embodiment of a system block diagram of a method for backing up page data according to the present application;
FIG. 2 is a flow chart of one embodiment of a method for backing up page data according to the present application;
FIG. 3 is a flowchart illustrating another embodiment of a page data backup method according to the present application;
FIG. 4 is a timing diagram of an automatic backup of page data according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating an embodiment of a disaster recovery page display method according to the present application;
FIG. 6 is a flowchart of another embodiment of a disaster recovery page displaying method according to the present application;
FIG. 7 is a flowchart illustrating another embodiment of a disaster recovery page displaying method according to the present application;
FIG. 8 is a flowchart illustrating another embodiment of a disaster recovery page displaying method according to the present application;
FIG. 9 is a block diagram illustrating an embodiment of a page data backup apparatus according to the present application;
FIG. 10 is a block diagram illustrating an embodiment of a disaster recovery page display device according to the present application;
fig. 11 is a schematic hardware structure diagram of a computer device for executing a page data backup method or a disaster recovery page display method according to an embodiment of the present application.
Detailed Description
Advantages of the application are further illustrated in the following description, taken in conjunction with the accompanying drawings and detailed description.
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
In the description of the present application, it should be understood that the numerical references before the steps do not identify the order in which the steps are performed, but are merely used to facilitate description of the present application and to distinguish between each step, and thus should not be construed as limiting the present application.
Fig. 1 schematically illustrates an application environment of a page data backup method according to an embodiment of the present application. In an exemplary embodiment, the system of the application environment may include a user terminal 10, a main server 20, a disaster recovery server 30, and a cloud storage server 40. The user terminal 10 has a corresponding application client or web client, and the user terminal 10 forms a wireless or wired connection with the main server 20, the disaster recovery server 30 and the cloud storage server 40. The user terminal 10 may be a PC, a mobile phone, an iPAD, a tablet computer, a notebook computer, a personal digital assistant, etc. The main server 20, disaster recovery server 30, and cloud storage server 40 may be rack-mounted servers, blade servers, tower servers, or rack-mounted servers (including independent servers or a server cluster composed of multiple servers), and the like.
It should be noted that, in normal circumstances, the main server 20 provides a page service for the client installed on the user terminal 10; when the main server 20 fails, the disaster recovery server 30 provides a page service for clients installed on the user terminal 10; when both the main server 20 and the disaster recovery server 30 fail, a page service is provided by the cloud storage server 40 for clients installed on the user terminal 10.
Referring to fig. 2, a flowchart of a page data backup method according to an embodiment of the present application is shown, and it will be understood that the flowchart in the embodiment of the present application is not used to limit the order of executing steps. As can be seen from the figure, the page data backup method provided in this embodiment includes:
step S20, a disaster recovery interface list is obtained at fixed time, and disaster recovery data corresponding to at least one interface is requested from a data server through the at least one interface contained in the disaster recovery interface list.
Specifically, in the prior art, when the front end displays the page, the front end needs to acquire the page data from the data server through a plurality of different interfaces, and then render the page data after acquiring the page data, so that the page display is realized. The page data acquired by different interfaces are different, and the front end can only display the complete front end page after acquiring the corresponding page data by all the interfaces. The interface is a data interface for performing data interaction between the front end and the data server, and is also called as an API interface. The front end may be an application client or a web client. The data server is a server for providing the front end with page data required by the presentation page, and the data server can be a primary source station content server, a standby source station content server or a prepositive CDN (Content Delivery Network ) node server.
In this embodiment, the disaster recovery interface list includes at least one interface, where the interface included in the disaster recovery interface list is a core interface of the plurality of different interfaces in the front-end obtaining the page data from the back-end data server. The core interface is a relatively important interface among the different interfaces, namely an interface for acquiring relatively important page data.
For example, when the front end takes the game center as an example, the game center displays the front end page, and because the front end page of the popular game generally includes a popular game list, a game home page, game details, game attack and the like, the game center needs to acquire popular game list data from the data server through a popular game list interface in order to display the complete front end page, and needs to acquire game home page data from the data server through a popular game home page interface. The game detail data needs to be acquired from the data server through the game detail interface, and the game attack data needs to be acquired through the game attack interface. In this embodiment, the hot game list interface, the game home page interface, the game detail interface, and the game attack interface may be used as the interfaces in the disaster recovery interface list, and of course, the hot game list interface and the game home page interface may be used only as the interfaces in the disaster recovery interface list, which is not limited in this embodiment. When the game center obtains the page data from the database through the disaster tolerant interface, the game center can display different page data at An Zhuoduan and at the IOS end through the same interface because the game quantity in the An Zhuoduan end and the IOS end are different, so that when the page data is obtained through the interface, the page data of both ends (An Zhuoduan end and IOS end) are requested to be sent down, and the follow-up normal page display on both ends is ensured. It will be appreciated that when page data is requested through the same interface on both sides, a parameter sdk _type representing the type of system, such as parameter sdk _type, will be taken: 1 represents android, sdk _type:2 represents IOS, different page data is obtained from both ends according to sdk _type parameter.
Further, in the present embodiment, when the data server feeds back the popular game list data through the popular game list data, the data server may provide 2 configuration manners to determine the popular game list data to be fed back: 1) And adding games into the background hot game list of the management platform manually by a user, wherein the games are divided into an android hot game list and an IOS hot game list, and game data contained in the hot game list is the hot game list data. 2) The background program can automatically check all games, judge whether the games are popular games according to the downloading amount, the grading, the clicking number and other dimensions of the games and a certain weight and algorithm, and finally add the games into corresponding popular game list data according to the on-shelf and off-shelf states of the IOS terminal and the An Zhuoduan.
It should be noted that the front end may be other types of clients, such as a news information client, a video client, etc.
In this embodiment, since the interface data stored in the data server may change with time, and the interfaces included in the disaster recovery interface list may also change, in this embodiment, the disaster recovery interface list needs to be acquired at regular time by a timing task, and then the interfaces in the disaster recovery interface list are sequentially traversed to acquire each interface, and after traversing to one interface, page data corresponding to the interface may be requested from the data server through the interface. All page data obtained through all interface requests in the disaster recovery interface list are the disaster recovery data, and the disaster recovery data are page data to be backed up.
In an embodiment, in order to facilitate management of the interfaces included in the disaster recovery interface list, the disaster recovery interface list may be defined in a unified external file, and when the interfaces included in the disaster recovery interface list need to be modified, the modification may be directly implemented by updating the external file, where the external file is a file that is stored locally and may be configured.
In an exemplary embodiment, the page data backup further includes:
and configuring interfaces contained in the disaster recovery interface list.
Specifically, in order to facilitate the configuration of the interfaces included in the disaster recovery interface list by the user, a disaster recovery interface configuration page may be provided, when the user needs to configure the interfaces included in the disaster recovery interface list, the user may add, delete or modify the interfaces included in the disaster recovery interface list through the configuration page, after the user completes the configuration operation of the interfaces, a configuration instruction may be generated, and then the configuration of the interfaces included in the disaster recovery interface list may be completed according to the configuration instruction.
In this embodiment, by configuring the interfaces included in the disaster recovery interface list, page data to be backed up can be flexibly selected.
And step S20, uploading the disaster recovery data to a cloud storage server.
Specifically, after disaster recovery data is obtained, the disaster recovery data can be uploaded to a cloud storage server, so that backup of disaster recovery page data is realized.
It should be noted that, since the disaster recovery data is requested from the data server each time the disaster recovery interface list is obtained, the disaster recovery data finally stored in the cloud storage database in this embodiment is the latest data, that is, when the disaster recovery data is uploaded to the cloud storage server each time, the latest uploaded disaster recovery data is replaced with the disaster recovery data uploaded before.
According to the embodiment of the invention, the disaster recovery interface list is obtained at fixed time, and disaster recovery data corresponding to at least one interface is requested from a data server through the at least one interface contained in the disaster recovery interface list; and uploading the disaster recovery data to a cloud storage server. In this embodiment, by backing up disaster recovery data corresponding to the disaster recovery interface in advance, when the back-end main server and the disaster recovery server are available, the front-end page can still be displayed through the backup disaster recovery data, so as to achieve high availability of the front-end page.
In an exemplary embodiment, referring to fig. 3, to further ensure high availability of the front-end presentation page, the page data backup method further includes:
step S30, a preset data interface is acquired at fixed time, and corresponding interface data is requested from the data server through the data interface.
Specifically, the preset data interface is an interface corresponding to the pre-set spam page data to be backed up, for example, in a game center, in order to ensure that hot game list data can be displayed in any situation, the interface corresponding to the hot game list data can be used as the preset data interface.
In addition, since the interface data requested through the preset data interface may change with time, in order to make the acquired interface data the latest data, the data interface needs to be acquired at regular time by means of a timing task.
After the data interface is obtained, data interaction can be performed between the data interface and the data server, so that interface data corresponding to the data interface is requested from the data server, for example, the data interface is a game hot list data interface, and hot game list data can be requested from the data server through the game hot list data interface.
And S31, generating static disaster recovery page data according to the interface data.
Specifically, after the interface data is obtained, static disaster recovery page data can be generated according to the data. In an embodiment, when generating the static disaster recovery page data, a template of the static disaster recovery page may be obtained first, and then the obtained interface data is written into a corresponding position of the template of the static disaster recovery page, thereby completing the generation of the static disaster recovery page data. The static disaster recovery page data is page data required by the front end for displaying the static disaster recovery page. The static disaster recovery page refers to a webpage in which the codes of the webpage are all in the page, and programs such as asp, php, jsp, net and the like do not need to be executed to generate client-side webpage codes.
It can be understood that, since the interface data in the generated disaster recovery page data is obtained from the data server through the data interface obtained at regular time, and static disaster recovery page data is generated according to the interface data every time the interface data is obtained, the disaster recovery page data finally stored in the cloud storage server is the latest disaster recovery page data, that is, the disaster recovery page data uploaded before is replaced by the disaster recovery page data every time the disaster recovery page data is uploaded to the cloud storage server.
And step S32, uploading the disaster recovery page data to the cloud storage server.
Specifically, after the disaster recovery page data is generated, the disaster recovery page data can be uploaded to the cloud storage server, so that the static disaster recovery page data can be backed up, and the static disaster recovery page data can be used as a final spam page.
According to the embodiment, the disaster recovery page data are generated and uploaded to the cloud storage server, so that the high availability of the front-end display page can be further improved.
In order to facilitate understanding of the present application, the present application will be described in detail with reference to fig. 4 and with the application of the present application to a game center.
The background of the game center starts a timing task to request the hot game list data to the data server through the hot game list interface (a data interface for acquiring the hot game list), and the data server returns the hot game list data to the background of the game center after receiving the request. And after the background of the game center acquires the hot game list data, uploading the hot game list data to the cloud storage server.
In addition, the background of the game center starts a timing task to periodically pass through the disaster recovery interface list, and after the disaster recovery interface list is obtained, the plurality of interfaces contained in the disaster recovery interface list are traversed in sequence, after the interfaces are traversed, interface data corresponding to the interfaces are requested to the data server through the traversed interfaces, and after the data server receives the request, the corresponding interface data are returned to the background of the game center. After the background of the game center acquires the interface data, the interface data is uploaded to the cloud storage server.
Referring to fig. 5, a flow chart of a disaster recovery page displaying method according to an embodiment of the present application is shown, and the method is applied to a client. As can be seen from the figure, the disaster recovery page displaying method provided in the embodiment includes:
and step S40, when the client side request interface fails, an H5 disaster recovery page is started.
Specifically, when the client side displays the page data, the client side needs to acquire the page data in an interface request mode, and when the client side fails in the interface request, the client side indicates that the client side does not successfully acquire the page data, and at the moment, the client side starts an H5 disaster recovery page.
Wherein, H5 is the abbreviation of HTML 5. HTML5 is the latest revision of HTML, a hypertext markup language. H5 has two main characteristics, firstly, the performance of the Web page is enhanced, and secondly, the functions of Web applications such as a local database and the like are added. The H5 disaster recovery page is a disaster recovery page manufactured by utilizing html 5.
It should be noted that, the H5 disaster recovery page is a backup page, which is not a page displayed when the client request interface is normal.
In this embodiment, when the interface requested by the client includes two lines, the H5 disaster recovery page is started only when the client fails to request both the interfaces of the main line and the standby line; when the interface requested by the client only comprises a main line, the H5 disaster recovery page is started when the client fails to request the line.
And S41, calling a disaster recovery interface through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server.
Specifically, disaster recovery data required by the client for displaying the disaster recovery press surface is prestored in the cloud storage server, so that when the client fails to request an interface, the disaster recovery interface can be called by the H5 disaster recovery page to acquire the disaster recovery data. The disaster recovery interface is an interface in the disaster recovery interface list of the above embodiment, and the disaster recovery data is the same as the disaster recovery data in the above embodiment, which is not described in detail in this embodiment.
In an exemplary embodiment, referring to fig. 6, the obtaining, by the H5 disaster recovery page, disaster recovery data stored in the cloud storage server by calling a disaster recovery interface includes:
step S50, requesting a disaster recovery interface switch configuration file from a preset server through the H5 disaster recovery page;
Specifically, the preset server is a device for managing a device running the disaster recovery page display method, and the disaster recovery mode of the client can be set through the server. In this embodiment, in order to cope with different situations, a plurality of disaster recovery modes may be configured for the client, for example, in an embodiment, the following two disaster recovery modes may be configured: 1) And opening a list disaster recovery page. 2) And opening a disaster recovery interface. The interface switch configuration file contains the configuration conditions of the two disaster recovery modes. When the disaster recovery mode is to start the disaster recovery interface, namely, a disaster recovery switch of the disaster recovery mode is configured to be in an on state, and when the client side requests the interface to fail, the disaster recovery mode is entered; when the disaster recovery mode is to open the list disaster recovery page, namely, when a list disaster recovery page switch for configuring the disaster recovery mode is in an open state, the disaster recovery mode is entered when the client requests an interface to fail.
Step S51, determining whether a disaster recovery switch is in an on state according to the requested switch configuration file;
and step S52, if the disaster recovery switch is in an on state, the disaster recovery interface is called through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server.
Specifically, the switch configuration file includes on-state information of the disaster recovery switch, and whether the disaster recovery switch is in an on-state or an off-state can be determined according to the on-state information, for example, if the on-state information is "1", the on-state information indicates that the disaster recovery switch is in an on-state, and if the on-state information is "0", the on-state information indicates that the disaster recovery switch is in an off-state. When the disaster recovery switch is in an on state, the H5 disaster recovery page calls a disaster recovery interface to acquire disaster recovery data stored in the cloud storage server.
According to the embodiment, the disaster recovery mode is determined by requesting the disaster recovery interface switch configuration file, so that the disaster recovery page displayed by the client is more flexible.
And step S42, performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
Specifically, because the acquired disaster recovery data includes data corresponding to a module displaying most normal pages, page rendering is performed through the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page, which is a most page module including pages normally displayed by a client.
According to the embodiment, when the client request interface fails, the H5 disaster recovery page is started to display the client page, so that the high availability of the front-end page is realized.
Further, in an exemplary embodiment, referring to fig. 7, the disaster recovery page display method further includes:
step S60, if the disaster recovery switch is in a closed state, acquiring static disaster recovery page data from the cloud storage server;
step S61, performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
Specifically, the cloud storage server also stores disaster recovery page data corresponding to the static disaster recovery page for the final spam, and when the disaster recovery switch is determined to be in the off state, the client starts the page disaster recovery mode, namely, acquires the disaster recovery page data from the cloud storage server, and then performs page rendering on the disaster recovery page data to obtain the static disaster recovery page for the final spam.
According to the embodiment, when the disaster recovery switch is in the off state, the static disaster recovery page is displayed, so that the high availability of the front-end display page is improved.
Further, in an exemplary embodiment, referring to fig. 8, the disaster recovery page display method further includes:
step S70, when page rendering fails according to the H5 disaster recovery page and the disaster recovery data, static disaster recovery page data are acquired from the cloud storage server;
And step S71, performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
Specifically, in order to avoid the defect that the client cannot display the front-end page when the client fails to perform page rendering according to the H5 disaster recovery page and the disaster recovery data, in this embodiment, when the rendering failure is detected, static disaster recovery page data is obtained from the cloud storage server, and then page rendering is performed on the disaster recovery page data to obtain a static disaster recovery page, so that high availability of the front-end display page is further realized.
Referring to FIG. 9, a block diagram of a page data backup apparatus 800 according to an embodiment of the present application is shown.
In this embodiment, the page data backup apparatus 800 includes a series of computer program instructions stored in a memory, which when executed by a processor, can implement the page data backup function of the embodiments of the present application. In some embodiments, the page data backup apparatus 800 may be divided into one or more modules based on the particular operations implemented by portions of the computer program instructions. For example, in fig. 9, the page data backup apparatus 800 may be divided into an acquisition module 801 and an upload module 802. Wherein:
An obtaining module 801, configured to obtain a disaster recovery interface list at regular time, and request, from a data server, disaster recovery data corresponding to at least one interface through at least one interface included in the disaster recovery interface list.
Specifically, in the prior art, when the front end displays the page, the front end needs to acquire the page data from the data server through a plurality of different interfaces, and then render the page data after acquiring the page data, so that the page display is realized. The page data acquired by different interfaces are different, and the front end can only display the complete front end page after acquiring the corresponding page data by all the interfaces. The interface is a data interface for performing data interaction between the front end and the data server, and is also called as an API interface. The front end may be an application client or a web client. The data server is a server for providing the front end with page data required by the presentation page, and the data server can be a primary source station content server, a standby source station content server or a prepositive CDN (Content Delivery Network ) node server.
In this embodiment, the disaster recovery interface list includes at least one interface, where the interface included in the disaster recovery interface list is a core interface of the plurality of different interfaces in the front-end obtaining the page data from the back-end data server. The core interface is a relatively important interface among the different interfaces, namely an interface for acquiring relatively important page data.
For example, when the front end takes the game center as an example, the game center displays the front end page, and because the front end page of the popular game generally includes a popular game list, a game home page, game details, game attack and the like, the game center needs to acquire popular game list data from the data server through a popular game list interface in order to display the complete front end page, and needs to acquire game home page data from the data server through a popular game home page interface. The game detail data needs to be acquired from the data server through the game detail interface, and the game attack data needs to be acquired through the game attack interface. In this embodiment, the hot game list interface, the game home page interface, the game detail interface, and the game attack interface may be used as the interfaces in the disaster recovery interface list, and of course, the hot game list interface and the game home page interface may be used only as the interfaces in the disaster recovery interface list, which is not limited in this embodiment. When the game center obtains the page data from the database through the disaster tolerant interface, the game center can display different page data at An Zhuoduan and at the IOS end through the same interface because the game quantity in the An Zhuoduan end and the IOS end are different, so that when the page data is obtained through the interface, the page data of both ends (An Zhuoduan end and IOS end) are requested to be sent down, and the follow-up normal page display on both ends is ensured. It will be appreciated that when page data is requested through the same interface on both sides, a parameter sdk _type representing the type of system, such as parameter sdk _type, will be taken: 1 represents android, sdk _type:2 represents IOS, different page data is obtained from both ends according to sdk _type parameter.
Further, in the present embodiment, when the data server feeds back the popular game list data through the popular game list data, the data server may provide 2 configuration manners to determine the popular game list data to be fed back: 1) And adding games into the background hot game list of the management platform manually by a user, wherein the games are divided into an android hot game list and an IOS hot game list, and game data contained in the hot game list is the hot game list data. 2) The background program can automatically check all games, judge whether the games are popular games according to the downloading amount, the grading, the clicking number and other dimensions of the games and a certain weight and algorithm, and finally add the games into corresponding popular game list data according to the on-shelf and off-shelf states of the IOS terminal and the An Zhuoduan.
It should be noted that the front end may be other types of clients, such as a news information client, a video client, etc.
In this embodiment, since the interface data stored in the data server may change with time, and the interfaces included in the disaster recovery interface list may also change, in this embodiment, the disaster recovery interface list needs to be acquired at regular time by a timing task, and then the interfaces in the disaster recovery interface list are sequentially traversed to acquire each interface, and after traversing to one interface, page data corresponding to the interface may be requested from the data server through the interface. All page data obtained through all interface requests in the disaster recovery interface list are the disaster recovery data, and the disaster recovery data are page data to be backed up.
In an embodiment, in order to facilitate management of the interfaces included in the disaster recovery interface list, the disaster recovery interface list may be defined in a unified external file, and when the interfaces included in the disaster recovery interface list need to be modified, the modification may be directly implemented by updating the external file, where the external file is a file that is stored locally and may be configured.
In an exemplary embodiment, to facilitate the setting of the mask parameter information, the page data backup apparatus 800 further includes: and (5) configuring a module.
The configuration module is configured to configure the interfaces included in the disaster recovery interface list.
Specifically, in order to facilitate the configuration of the interfaces included in the disaster recovery interface list by the user, a disaster recovery interface configuration page may be provided, when the user needs to configure the interfaces included in the disaster recovery interface list, the user may add, delete or modify the interfaces included in the disaster recovery interface list through the configuration page, after the user completes the configuration operation of the interfaces, a configuration instruction may be generated, and then the configuration of the interfaces included in the disaster recovery interface list may be completed according to the configuration instruction.
In this embodiment, by configuring the interfaces included in the disaster recovery interface list, page data to be backed up can be flexibly selected.
And an uploading module 802, configured to upload the disaster recovery data to a cloud storage server.
Specifically, after disaster recovery data is obtained, the disaster recovery data can be uploaded to a cloud storage server, so that backup of disaster recovery page data is realized.
It should be noted that, since the disaster recovery data is requested from the data server each time the disaster recovery interface list is obtained, the disaster recovery data finally stored in the cloud storage database in this embodiment is the latest data, that is, when the disaster recovery data is uploaded to the cloud storage server each time, the latest uploaded disaster recovery data is replaced with the disaster recovery data uploaded before.
According to the embodiment of the invention, the disaster recovery interface list is obtained at fixed time, and disaster recovery data corresponding to at least one interface is requested from a data server through the at least one interface contained in the disaster recovery interface list; and uploading the disaster recovery data to a cloud storage server. In this embodiment, by backing up disaster recovery data corresponding to the disaster recovery interface in advance, when the back-end main server and the disaster recovery server are available, the front-end page can still be displayed through the backup disaster recovery data, so as to achieve high availability of the front-end page.
In an exemplary embodiment, to further ensure high availability of the front-end presentation page, the page data backup apparatus 800 further includes: a request module and a generation module.
The request module is used for acquiring a preset data interface at fixed time and requesting corresponding interface data from the data server through the data interface.
Specifically, the preset data interface is an interface corresponding to the pre-set spam page data to be backed up, for example, in a game center, in order to ensure that hot game list data can be displayed in any situation, the interface corresponding to the hot game list data can be used as the preset data interface.
In addition, since the interface data requested through the preset data interface may change with time, in order to make the acquired interface data the latest data, the data interface needs to be acquired at regular time by means of a timing task.
After the data interface is obtained, data interaction can be performed between the data interface and the data server, so that interface data corresponding to the data interface is requested from the data server, for example, the data interface is a game hot list data interface, and hot game list data can be requested from the data server through the game hot list data interface.
And the generating module is used for generating static disaster recovery page data according to the interface data.
Specifically, after the interface data is obtained, static disaster recovery page data can be generated according to the data. In an embodiment, when generating the static disaster recovery page data, a template of the static disaster recovery page may be obtained first, and then the obtained interface data is written into a corresponding position of the template of the static disaster recovery page, thereby completing the generation of the static disaster recovery page data. The static disaster recovery page data is page data required by the front end for displaying the static disaster recovery page. The static disaster recovery page refers to a webpage in which the codes of the webpage are all in the page, and programs such as asp, php, jsp, net and the like do not need to be executed to generate client-side webpage codes.
It can be understood that, since the interface data in the generated disaster recovery page data is obtained from the data server through the data interface obtained at regular time, and static disaster recovery page data is generated according to the interface data every time the interface data is obtained, the disaster recovery page data finally stored in the cloud storage server is the latest disaster recovery page data, that is, the disaster recovery page data uploaded before is replaced by the disaster recovery page data every time the disaster recovery page data is uploaded to the cloud storage server.
The uploading module 802 is further configured to upload the disaster recovery page data to the cloud storage server.
Specifically, after the disaster recovery page data is generated, the disaster recovery page data can be uploaded to the cloud storage server, so that the static disaster recovery page data can be backed up, and the static disaster recovery page data can be used as a final spam page.
According to the embodiment, the disaster recovery page data are generated and uploaded to the cloud storage server, so that the high availability of the front-end display page can be further improved.
Referring to fig. 10, a block diagram of a disaster recovery page display device 900 according to an embodiment of the application is shown.
In this embodiment, the disaster recovery page display device 900 includes a series of computer program instructions stored in a memory, and when the computer program instructions are executed by a processor, the disaster recovery page data display function of each embodiment of the present application can be implemented. In some embodiments, disaster recovery page display device 900 can be divided into one or more modules based on the particular operations implemented by portions of the computer program instructions. For example, in fig. 10, the disaster recovery page display device 900 may be divided into an enabling module 901, an obtaining module 902, and a rendering module 903. Wherein:
And an enabling module 901, configured to enable an H5 disaster recovery page when the client fails to request an interface.
Specifically, when the client side displays the page data, the client side needs to acquire the page data in an interface request mode, and when the client side fails in the interface request, the client side indicates that the client side does not successfully acquire the page data, and at the moment, the client side starts an H5 disaster recovery page.
Wherein, H5 is the abbreviation of HTML 5. HTML5 is the latest revision of HTML, a hypertext markup language. H5 has two main characteristics, firstly, the performance of the Web page is enhanced, and secondly, the functions of Web applications such as a local database and the like are added. The H5 disaster recovery page is a disaster recovery page manufactured by utilizing html 5.
It should be noted that, the H5 disaster recovery page is a backup page, which is not a page displayed when the client request interface is normal.
In this embodiment, when the interface requested by the client includes two lines, the H5 disaster recovery page is started only when the client fails to request both the interfaces of the main line and the standby line; when the interface requested by the client only comprises a main line, the H5 disaster recovery page is started when the client fails to request the line.
And the obtaining module 902 is configured to obtain disaster recovery data stored in the cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page.
Specifically, disaster recovery data required by the client for displaying the disaster recovery press surface is prestored in the cloud storage server, so that when the client fails to request an interface, the disaster recovery interface can be called by the H5 disaster recovery page to acquire the disaster recovery data. The disaster recovery interface is an interface in the disaster recovery interface list of the above embodiment, and the disaster recovery data is the same as the disaster recovery data in the above embodiment, which is not described in detail in this embodiment.
In an exemplary embodiment, the obtaining module 902 is further configured to request, from a preset server, a disaster recovery interface switch configuration file through the H5 disaster recovery page;
specifically, the preset server is a device for managing a device running the disaster recovery page display method, and the disaster recovery mode of the client can be set through the server. In this embodiment, in order to cope with different situations, a plurality of disaster recovery modes may be configured for the client, for example, in an embodiment, the following two disaster recovery modes may be configured: 1) And opening a list disaster recovery page. 2) And opening a disaster recovery interface. The interface switch configuration file contains the configuration conditions of the two disaster recovery modes. When the disaster recovery mode is to start the disaster recovery interface, namely, a disaster recovery switch of the disaster recovery mode is configured to be in an on state, and when the client side requests the interface to fail, the disaster recovery mode is entered; when the disaster recovery mode is to open the list disaster recovery page, namely, when a list disaster recovery page switch for configuring the disaster recovery mode is in an open state, the disaster recovery mode is entered when the client requests an interface to fail.
The obtaining module 902 is further configured to determine whether the disaster recovery switch is in an on state according to the requested switch configuration file; and if the disaster recovery switch is in an on state, calling a disaster recovery interface through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server.
Specifically, the switch configuration file includes on-state information of the disaster recovery switch, and whether the disaster recovery switch is in an on-state or an off-state can be determined according to the on-state information, for example, if the on-state information is "1", the on-state information indicates that the disaster recovery switch is in an on-state, and if the on-state information is "0", the on-state information indicates that the disaster recovery switch is in an off-state. When the disaster recovery switch is in an on state, the H5 disaster recovery page calls a disaster recovery interface to acquire disaster recovery data stored in the cloud storage server.
According to the embodiment, the disaster recovery mode is determined by requesting the disaster recovery interface switch configuration file, so that the disaster recovery page displayed by the client is more flexible.
The rendering module 903 is configured to perform page rendering according to the H5 disaster recovery page and the disaster recovery data, to obtain a target disaster recovery page.
Specifically, because the acquired disaster recovery data includes data corresponding to a module displaying most normal pages, page rendering is performed through the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page, which is a most page module including pages normally displayed by a client.
According to the embodiment, when the client request interface fails, the H5 disaster recovery page is started to display the client page, so that the high availability of the front-end page is realized.
Further, in an exemplary embodiment, the obtaining module 902 is further configured to obtain static disaster recovery page data from the cloud storage server if the disaster recovery switch is in an off state.
The rendering module 903 is further configured to perform page rendering on the disaster recovery page data to obtain a static disaster recovery page.
Specifically, the cloud storage server also stores disaster recovery page data corresponding to the static disaster recovery page for the final spam, and when the disaster recovery switch is determined to be in the off state, the client starts the page disaster recovery mode, namely, acquires the disaster recovery page data from the cloud storage server, and then performs page rendering on the disaster recovery page data to obtain the static disaster recovery page for the final spam.
According to the embodiment, when the disaster recovery switch is in the off state, the static disaster recovery page is displayed, so that the high availability of the front-end display page is improved.
Further, in an exemplary embodiment, the obtaining module 902 is further configured to obtain static disaster recovery page data from the cloud storage server when page rendering fails according to the H5 disaster recovery page and the disaster recovery data.
The rendering module 903 is further configured to perform page rendering on the disaster recovery page data to obtain a static disaster recovery page.
Specifically, in order to avoid the defect that the client cannot display the front-end page when the client fails to perform page rendering according to the H5 disaster recovery page and the disaster recovery data, in this embodiment, when the rendering failure is detected, static disaster recovery page data is obtained from the cloud storage server, and then page rendering is performed on the disaster recovery page data to obtain a static disaster recovery page, so that high availability of the front-end display page is further realized.
Fig. 11 schematically illustrates a hardware architecture diagram of a computer device 10 adapted to implement a page data backup method or implement a disaster tolerant page display method according to an embodiment of the present application. In the present embodiment, the computer device 10 is a device capable of automatically performing numerical calculation and/or information processing in accordance with instructions set or stored in advance. For example, the server may be a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a rack server (including a stand-alone server or a server cluster formed by a plurality of servers), etc. As shown in fig. 11, the computer device 10 includes at least, but is not limited to: the memory 11, the processor 12, and the network interface 13 may be communicatively linked to each other via a system bus. Wherein:
The memory 11 includes at least one type of computer-readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 may be an internal storage module of the computer device 10, such as a hard disk or memory of the computer device 10. In other embodiments, the memory 11 may also be an external storage device of the computer device 10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the computer device 10. Of course, the memory 11 may also include both internal memory modules of the computer device 10 and external memory devices. In this embodiment, the memory 11 is generally used to store an operating system installed in the computer device 10 and various application software, such as program codes of a page data backup method or a disaster recovery page display method. Further, the memory 11 may be used to temporarily store various types of data that have been output or are to be output.
The processor 12 may be a central processing unit (Central Processing Unit, simply CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 12 is generally used to control the overall operation of the computer device 10, such as performing control and processing related to data interaction or communication with the computer device 10, and the like. In this embodiment, the processor 12 is configured to execute program codes or process data stored in the memory 11.
The network interface 13 may comprise a wireless network interface or a wired network interface, the network interface 13 typically being used to establish a communication link between the computer device 10 and other computer devices. For example, the network interface 13 is used to connect the computer device 10 to an external terminal through a network, establish a data transmission channel and a communication link between the computer device 10 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a global system for mobile communications (Global System of Mobile communication, abbreviated as GSM), wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, etc.
It should be noted that FIG. 11 only shows a computer device having components 11-13, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead.
In this embodiment, the page data backup method or the disaster recovery page display method stored in the memory 11 may also be divided into one or more program modules and executed by one or more processors (the processor 12 in this embodiment) to complete the present application.
The embodiment of the application provides a page data display system, which comprises a page data backup device and a disaster recovery page display device, wherein:
the page data backup device comprises: the system comprises an acquisition module, a data server and a disaster recovery module, wherein the acquisition module is used for acquiring a disaster recovery interface list at fixed time and requesting disaster recovery data corresponding to at least one interface from the data server through the at least one interface contained in the disaster recovery interface list; the uploading module is used for uploading the disaster recovery data to a cloud storage server;
the disaster recovery page display device includes: the starting module is used for starting the H5 disaster recovery page when the client side requests the interface to fail; the acquisition module is used for acquiring disaster recovery data stored in the cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page; and the rendering module is used for performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
Incidentally, the page data backup device and the disaster recovery page display device in the present application are described in detail in the above embodiments, and are not described in detail in this embodiment.
The embodiment of the application provides a nonvolatile computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the steps of the page data backup method or the disaster recovery page display method in the embodiment when being executed by a processor.
In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the computer readable storage medium may be an internal storage unit of a computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may also be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), etc. that are provided on the computer device. Of course, the computer-readable storage medium may also include both internal storage units of a computer device and external storage devices. In this embodiment, the computer readable storage medium is generally used to store an operating system and various application software installed on a computer device, for example, program codes of a page data backup method or a disaster recovery page display method in the embodiment. Furthermore, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are to be output.
The apparatus embodiments described above are merely illustrative, wherein elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over at least two network elements. Some or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment of the application. Those of ordinary skill in the art will understand and implement the present application without undue burden.
From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus a general purpose hardware platform, or may be implemented by hardware. Those skilled in the art will appreciate that all or part of the processes implementing the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and where the program may include processes implementing the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-only memory (ROM), a random access memory (RandomAccessMemory, RAM), or the like.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.
Claims (12)
1. A method for backing up page data, comprising:
the method comprises the steps of regularly acquiring a disaster recovery interface list, and requesting disaster recovery data corresponding to at least one interface from a data server through at least one interface contained in the disaster recovery interface list, wherein the at least one interface contained in the disaster recovery interface list is a core interface in a plurality of different interfaces in page data obtained from a back-end data server by a front end, and the disaster recovery data is the page data to be backed up;
and uploading the disaster recovery data to a cloud storage server.
2. The page data backup method of claim 1, wherein the page data backup further comprises:
Acquiring a preset data interface at fixed time, and requesting corresponding interface data from the data server through the data interface;
generating static disaster recovery page data according to the interface data;
and uploading the disaster recovery page data to the cloud storage server.
3. The page data backup method of claim 1, wherein the page data backup further comprises:
and configuring interfaces contained in the disaster recovery interface list.
4. The disaster recovery page display method is applied to a client and is characterized by comprising the following steps:
when the client side requests that an interface fails, an H5 disaster recovery page is started, wherein the H5 disaster recovery page is a backup page;
acquiring disaster recovery data stored in a cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page, wherein the cloud storage server is pre-stored with disaster recovery data required by a client for displaying the disaster recovery page, and the disaster recovery data is uploaded through the page data backup method according to any one of claims 1-3;
and performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
5. The method for displaying a disaster recovery page according to claim 4, wherein the obtaining disaster recovery data stored in a cloud storage server by calling a disaster recovery interface through the H5 disaster recovery page comprises:
Requesting a disaster recovery interface switch configuration file from a preset server through the H5 disaster recovery page;
determining whether the disaster recovery switch is in an on state according to the requested switch configuration file;
and if the disaster recovery switch is in an on state, calling a disaster recovery interface through the H5 disaster recovery page to acquire disaster recovery data stored in the cloud storage server.
6. The disaster recovery page display method of claim 5, wherein the disaster recovery page display method further comprises:
if the disaster recovery switch is in a closed state, acquiring static disaster recovery page data from the cloud storage server;
and performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
7. The disaster recovery page display method of claim 4 or 5, wherein the disaster recovery page display method further comprises:
when the page rendering fails according to the H5 disaster recovery page and the disaster recovery data, acquiring static disaster recovery page data from the cloud storage server;
and performing page rendering on the disaster recovery page data to obtain a static disaster recovery page.
8. A page data backup apparatus, comprising:
the system comprises an acquisition module, a data server and a storage module, wherein the acquisition module is used for acquiring a disaster recovery interface list at fixed time and requesting disaster recovery data corresponding to at least one interface from the data server through the at least one interface contained in the disaster recovery interface list, the at least one interface contained in the disaster recovery interface list is a core interface in a plurality of different interfaces in page data from a back-end data server, and the disaster recovery data is the page data to be backed up;
And the uploading module is used for uploading the disaster recovery data to a cloud storage server.
9. The disaster recovery page display device is applied to a client and is characterized by comprising the following components:
the starting module is used for starting an H5 disaster recovery page when the client side request interface fails, wherein the H5 disaster recovery page is a backup page;
the acquisition module is used for acquiring disaster recovery data stored in the cloud storage server through the H5 disaster recovery page calling disaster recovery interface, wherein the cloud storage server is pre-stored with disaster recovery data required by a client for displaying the disaster recovery page, and the disaster recovery data is uploaded through the page data backup method according to any one of claims 1-3;
and the rendering module is used for performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the page data backup method of any one of claims 1 to 3 or the steps of the disaster recovery page display method of any one of claims 4 to 7 when the computer program is executed.
11. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the steps of the page data backup method of any one of claims 1 to 3, or the steps of the disaster recovery page display method of any one of claims 4 to 7.
12. A page data display system comprises a page data backup device and a disaster recovery page display device, wherein:
the page data backup device comprises: the system comprises an acquisition module, a data server and a storage module, wherein the acquisition module is used for acquiring a disaster recovery interface list at fixed time and requesting disaster recovery data corresponding to at least one interface from the data server through the at least one interface contained in the disaster recovery interface list, the at least one interface contained in the disaster recovery interface list is a core interface in a plurality of different interfaces in page data from a back-end data server, and the disaster recovery data is the page data to be backed up; the uploading module is used for uploading the disaster recovery data to a cloud storage server;
the disaster recovery page display device includes: the starting module is used for starting an H5 disaster recovery page when the client side requests the interface to fail, wherein the H5 disaster recovery page is a backup page; the acquisition module is used for acquiring disaster recovery data stored in the cloud storage server through the H5 disaster recovery page calling disaster recovery interface, wherein the cloud storage server is pre-stored with disaster recovery data required by a client for displaying the disaster recovery page, and the disaster recovery data is uploaded through the page data backup method according to any one of claims 1-3; and the rendering module is used for performing page rendering according to the H5 disaster recovery page and the disaster recovery data to obtain a target disaster recovery page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010819506.0A CN112436953B (en) | 2020-08-14 | 2020-08-14 | Page data backup and disaster recovery page display method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010819506.0A CN112436953B (en) | 2020-08-14 | 2020-08-14 | Page data backup and disaster recovery page display method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112436953A CN112436953A (en) | 2021-03-02 |
| CN112436953B true CN112436953B (en) | 2023-11-24 |
Family
ID=74689897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010819506.0A Active CN112436953B (en) | 2020-08-14 | 2020-08-14 | Page data backup and disaster recovery page display method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112436953B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760260A (en) * | 2016-02-19 | 2016-07-13 | 浙江大华系统工程有限公司 | Backup system and backup method |
| CN106156359A (en) * | 2016-07-28 | 2016-11-23 | 四川新环佳科技发展有限公司 | A kind of data synchronization updating method under cloud computing platform |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090024626A1 (en) * | 2005-03-16 | 2009-01-22 | Matsushita Electric Industrial Co., Ltd. | Information processing terminal, content providing system, content providing method, and content providing program |
| CN202197301U (en) * | 2011-03-22 | 2012-04-18 | 辽宁国兴科技有限公司 | Different place on-line data disaster recovery system |
| CN104657420B (en) * | 2015-01-09 | 2019-06-04 | 北京京东尚科信息技术有限公司 | Page display method and system |
| CN106156231A (en) * | 2015-04-24 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of website disaster recovery method, Apparatus and system |
| CN108156013B (en) * | 2016-12-02 | 2021-08-10 | 阿里巴巴集团控股有限公司 | Page service disaster tolerance method and device and electronic equipment |
| US10839041B2 (en) * | 2017-01-25 | 2020-11-17 | Walmart Apollo, Llc | Systems, method, and non-transitory computer-readable storage media for a partial-render operation generating code for displaying a webpage |
| CN107766509B (en) * | 2017-10-23 | 2021-02-26 | 北京京东尚科信息技术有限公司 | Method and device for static backup of webpage |
| CN111240892B (en) * | 2019-12-02 | 2023-09-29 | 泰康保险集团股份有限公司 | Data backup method and device |
-
2020
- 2020-08-14 CN CN202010819506.0A patent/CN112436953B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760260A (en) * | 2016-02-19 | 2016-07-13 | 浙江大华系统工程有限公司 | Backup system and backup method |
| CN106156359A (en) * | 2016-07-28 | 2016-11-23 | 四川新环佳科技发展有限公司 | A kind of data synchronization updating method under cloud computing platform |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112436953A (en) | 2021-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR20180100171A (en) | Interface data display method and apparatus | |
| CN104965717A (en) | Method and apparatus for loading page | |
| CN112367345B (en) | Data processing method, server device and computer readable storage medium | |
| CN108510287B (en) | Client return visit judgment method, electronic device and computer readable storage medium | |
| CN111416836B (en) | Nginx-based server maintenance method and device, computer equipment and storage medium | |
| CN113411404A (en) | File downloading method, device, server and storage medium | |
| CN108280174A (en) | Front end file construction method and server, page access method and terminal | |
| CN110889143A (en) | File verification method and device | |
| CN106649581B (en) | Webpage repairing method and client | |
| CN112422604B (en) | File uploading method, device and system and computer equipment | |
| CN113495783A (en) | Service data processing method and device | |
| CN112672187B (en) | Page generation method and device, computer equipment and readable storage medium | |
| CN113365149A (en) | Live broadcast picture playing method and device of live broadcast room | |
| CN112436953B (en) | Page data backup and disaster recovery page display method and device | |
| CN111142885A (en) | eSIM device management method, device, equipment and storage medium | |
| CN106897456B (en) | Activity information publishing method, activity information driving method, related equipment and system | |
| CN107908634B (en) | Cache control method of browser and mobile terminal | |
| CN115623236A (en) | Gift special-effect resource playing method and device | |
| CN112688980B (en) | Resource distribution method and device, and computer equipment | |
| CN114553859A (en) | BMC configuration management method and device, electronic equipment and storage medium | |
| CN114063958A (en) | Page split-screen display method and device | |
| CN113360806A (en) | Live broadcast page display method and device | |
| CN103309941A (en) | Application update method, device and system | |
| CN104346101A (en) | Dynamic storage space allocation system and method | |
| CN107135430A (en) | A kind of processing system updated for interface typesetting |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |