CN108234212A - Mixed cloud disaster recovery method, server and storage medium - Google Patents

Mixed cloud disaster recovery method, server and storage medium Download PDF

Info

Publication number
CN108234212A
CN108234212A CN201711498524.8A CN201711498524A CN108234212A CN 108234212 A CN108234212 A CN 108234212A CN 201711498524 A CN201711498524 A CN 201711498524A CN 108234212 A CN108234212 A CN 108234212A
Authority
CN
China
Prior art keywords
data center
cloud
target data
publicly
operational visit
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.)
Pending
Application number
CN201711498524.8A
Other languages
Chinese (zh)
Inventor
赖秋林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sangfor Technologies Co Ltd
Original Assignee
Sangfor Network Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Sangfor Network Technology Shenzhen Co Ltd filed Critical Sangfor Network Technology Shenzhen Co Ltd
Priority to CN201711498524.8A priority Critical patent/CN108234212A/en
Publication of CN108234212A publication Critical patent/CN108234212A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention discloses a kind of mixed cloud disaster recovery methods,Server and storage medium,The present invention is by server when detecting that local data center processing business access request breaks down,Obtain the fault type of the failure,One data center is chosen as target data center from publicly-owned cloud data center and the local data center according to the fault type,Operational Visit request is sent to the target data center,So that the target data center handles Operational Visit request,Corresponding data center is selected to carry out business processing by the type of failure,Distribution according to need and the elasticity of publicly-owned cloud data center can be utilized,Idle does not need to occupy mass data resource,Reduce the probability of secondary system disaster,Reduce the risk of system data communication,Improve Information Security,Reduce the input of resource,It is quicker to cope with failure,Processing mode is simpler convenient.

Description

Mixed cloud disaster recovery method, server and storage medium
Technical field
The present invention relates to a kind of data disaster tolerance field more particularly to mixed cloud disaster recovery method, server and storage mediums.
Background technology
With the development of information technology, the value of data is continuously increased.Therefore, Data Disaster-Tolerance Technology, which receives, widely grinds Study carefully and pay close attention to.People would generally reach data reliability requirement in different geographical location Backup Data copies.It is but traditional Data store arranging method resource expenditure it is huge.And inexpensive, the on-demand purchase of cloud computing and dynamic make it gradually be known as The standby optimal selection built of calamity.Current cloud disaster tolerance mode mainly in a manner of hot standby based on, first build beyond the clouds and local number According to the consistent application system in center, data are then synchronized to by disaster tolerance system by high in the clouds, can be led to when breaking down Cross the system take over business in high in the clouds.And this hot standby mode for realizing cloud disaster tolerance, has the following disadvantages:Calamity cannot be met for 3- (i.e. business data needs 3 parts of data and deposits in 2 kinds of different media 2-1 rules, and a copy of it has 1 number in production environment According to being stored in strange land environment), data only have 2 parts;There is no the most effective distribution according to need using public cloud and elasticity, need to account for beyond the clouds With with the consistent amount of cloud host of private data center service;Due to carry out hot standby duplication, both sides need to keep network communication, Therefore the network in high in the clouds cannot be consistent with original production, not so can there are network address collisions;The system on both sides is all straight Lead in succession, therefore can also bring some safety problems;Either local fault or overall failure can only all do whole switchings, Increase the possibility of the secondary disaster instead for large business system;Disaster tolerance construction needs often progress DR test that could ensure Really break down after can successful switch take over business, although and this hot standby mode can be drilled, need elder generation Suspend calamity for business, and dirty data is also cleared up after drilling, the O&M complexity of disaster tolerance is higher.
Invention content
It is a primary object of the present invention to a kind of mixed cloud disaster recovery method, server and storage mediums, it is intended to solve existing The hot standby O&M complexity for realizing cloud disaster tolerance is higher in technology, and can only do that all switchings cause the secondary disaster when breaking down can The problem of energy property is larger.
To achieve the above object, the present invention provides a kind of mixed cloud disaster recovery method, the mixed cloud disaster recovery method include with Lower step:
Server obtains the event of the failure when detecting that local data center processing business access request breaks down Hinder type;
One data center is chosen from publicly-owned cloud data center and the local data center according to the fault type As target data center;
Operational Visit request is sent to the target data center, so that the target data center is to the industry Business access request is handled.
Preferably, it is described that Operational Visit request is sent to the target data center, so that the target data Center handles Operational Visit request, specifically includes:
Operational Visit request is sent to the target data center, so that the target data is centrally through target Data handle Operational Visit request, and the target data is backed up for the local data center in the local number It is used to handle the data of the Operational Visit request according to center and the publicly-owned cloud data center.
Preferably, it is described that Operational Visit request is sent to the target data center, so that the target data Operational Visit request is handled centrally through target data, is specifically included:
When the local data center is in the target data center, locally take over environmental response is in the Operational Visit It asks and Operational Visit request is handled by the target data, the local take over environment is in the local The data take over environment of virtualization setting in the clear area of data center;
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to described Publicly-owned cloud data center so that the publicly-owned cloud data center by the target data to the Operational Visit request at Reason.
Preferably, it is described when the publicly-owned cloud data center is in the target data center, it please by the Operational Visit It asks and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center visits the business by the target data It asks that request is handled, specifically includes:
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to tenant Virtual private cloud, so that tenant's virtual private cloud is handled Operational Visit request by the target data, Tenant's virtual private cloud is to virtualize to set in the clear area of the corresponding publicly-owned cloud platform of the publicly-owned cloud data center That puts is exclusively used in handling the data take over environment of the target data.
Preferably, it is described when the publicly-owned cloud data center is in the target data center, it please by the Operational Visit It asks and is sent to tenant's virtual private cloud, so that tenant's virtual private cloud please to the Operational Visit by the target data It asks before being handled, the mixed cloud disaster recovery method further includes:
When the target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction;
The virtual cloud is created into instruction and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center root Parameter and default network configuration parameters are configured in the corresponding publicly-owned cloud platform of the publicly-owned cloud data center according to default cloud host Virtualization sets tenant's virtual cloud in clear area.
Preferably, it is described to choose one from publicly-owned cloud data center and the local data center according to the fault type A data center specifically includes as target data center:
When the fault type is local fault, using the local data center as the target data center;
When the fault type is global fault, using the publicly-owned cloud data center as the target data center.
Preferably, it is described when detecting that local data center handles the Operational Visit request failure, obtain institute The fault type of failure is stated, is specifically included:
When detecting that local data center handles the Operational Visit request appearance failure, the failure pair is analyzed The data answered account for the defective proportion of the total data resource of the local data center;
When the defective proportion is less than preset ratio, the fault type for judging the failure is the local fault;
When the defective proportion is greater than or equal to the preset ratio, the fault type for judging the failure is described complete Office's failure.
Preferably, it is described to choose one from publicly-owned cloud data center and the local data center according to the fault type Before a data center is as target data center, the mixed cloud disaster recovery method further includes:
The target data is sent to default disaster tolerance front end processor, so that the default disaster tolerance front end processor is to the number of targets It is compressed according to being encrypted, and passes through Virtual Private Network and the target data after ciphered compressed is transmitted in the public cloud data The heart.
In addition, to achieve the above object, the present invention also proposes a kind of mixed cloud Disaster Recovery Service, the mixed cloud disaster tolerance clothes Business device includes:Memory, processor and it is stored in the mixed cloud disaster tolerance that can be run on the memory and on the processor The step of program, the mixed cloud disaster tolerance program is arranged for carrying out mixed cloud disaster recovery method as described above.
In addition, to achieve the above object, the present invention also proposes a kind of storage medium, and mixing is stored on the storage medium Cloud disaster tolerance program realizes the step of mixed cloud disaster recovery method as described above when the mixed cloud disaster tolerance program is executed by processor Suddenly.
Mixed cloud disaster recovery method proposed by the present invention, the present invention are detecting local data center processing industry by server When access request of being engaged in breaks down, the fault type of the failure is obtained, according to the fault type from publicly-owned cloud data center With one data center of selection in the local data center as target data center, Operational Visit request is sent to The target data center so that the target data center handles Operational Visit request, passes through the class of failure Type selects corresponding data center to carry out business processing, can utilize distribution according to need and the elasticity of publicly-owned cloud data center, idle It does not need to occupy mass data resource, reduces the probability of secondary system disaster, reduce the risk of system data communication, improve Information Security reduces the input of resource, and reply failure is quicker, and processing mode is simpler convenient.
Description of the drawings
Fig. 1 is the mixed cloud Disaster Recovery Service structure diagram of hardware running environment that the embodiment of the present invention is related to;
Fig. 2 is the flow diagram of mixed cloud disaster recovery method first embodiment of the present invention;
Fig. 3 is the flow diagram of mixed cloud disaster recovery method second embodiment of the present invention;
Fig. 4 is the flow diagram of mixed cloud disaster recovery method 3rd embodiment of the present invention.
The embodiments will be further described with reference to the accompanying drawings for the realization, the function and the advantages of the object of the present invention.
Specific embodiment
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
The solution of the embodiment of the present invention is mainly:The present invention is detecting local data center processing by server When Operational Visit request is broken down, the fault type of the failure is obtained, according to the fault type from public cloud data A data center is chosen in the heart and the local data center as target data center, the Operational Visit is asked to send To the target data center, so that the target data center handles Operational Visit request, pass through failure Type selects corresponding data center to carry out business processing, can utilize distribution according to need and the elasticity of publicly-owned cloud data center, not busy When do not need to occupy mass data resource, reduce the probability of secondary system disaster, reduce the risk of system data communication, carry High Information Security, reduces the input of resource, reply failure is quicker, and processing mode is simpler convenient, solves The hot standby O&M complexity for realizing cloud disaster tolerance is higher in the prior art, and all switchings can only be done when breaking down and cause the secondary disaster Possibility it is larger the technical issues of.
With reference to Fig. 1, Fig. 1 is the mixed cloud Disaster Recovery Service structure of hardware running environment that the embodiment of the present invention is related to Schematic diagram.
As shown in Figure 1, the mixed cloud Disaster Recovery Service can include:Processor 1001, such as CPU, communication bus 1002, User's end interface 1003, network interface 1004, memory 1005.Wherein, communication bus 1002 is used to implement between these components Connection communication.User's end interface 1003 can include display screen (Display), input unit such as keyboard (Keyboard), Optional user's end interface 1003 can also include standard wireline interface and wireless interface.Network interface 1004 can optionally wrap Include standard wireline interface and wireless interface (such as WI-FI interfaces).Memory 1005 can be high-speed RAM memory or Stable memory (non-volatile memory), such as magnetic disk storage.Memory 1005 optionally can also be independent In the storage device of aforementioned processor 1001.
It will be understood by those skilled in the art that the mixed cloud Disaster Recovery Service structure shown in Fig. 1 is not formed to the prison The restriction of measurement equipment can include either combining certain components or different component cloth than illustrating more or fewer components It puts.
As shown in Figure 1, it can lead to as in a kind of memory 1005 of computer storage media including operating system, network Believe module, user terminal interface module and mixed cloud disaster tolerance program.
Mixed cloud Disaster Recovery Service of the present invention calls the mixed cloud disaster tolerance stored in memory 1005 by processor 1001 Program, and perform following operate:
Server obtains the event of the failure when detecting that local data center processing business access request breaks down Hinder type;
One data center is chosen from publicly-owned cloud data center and the local data center according to the fault type As target data center;
Operational Visit request is sent to the target data center, so that the target data center is to the industry Business access request is handled.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
Operational Visit request is sent to the target data center, so that the target data is centrally through target Data handle Operational Visit request, and the target data is backed up for the local data center in the local number It is used to handle the data of the Operational Visit request according to center and the publicly-owned cloud data center.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
When the local data center is in the target data center, locally take over environmental response is in the Operational Visit It asks and Operational Visit request is handled by the target data, the local take over environment is in the local The data take over environment of virtualization setting in the clear area of data center;
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to described Publicly-owned cloud data center so that the publicly-owned cloud data center by the target data to the Operational Visit request at Reason.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to tenant Virtual private cloud, so that tenant's virtual private cloud is handled Operational Visit request by the target data, Tenant's virtual private cloud is to virtualize to set in the clear area of the corresponding publicly-owned cloud platform of the publicly-owned cloud data center That puts is exclusively used in handling the data take over environment of the target data.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
When the target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction;
The virtual cloud is created into instruction and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center root Parameter and default network configuration parameters are configured in the corresponding publicly-owned cloud platform of the publicly-owned cloud data center according to default cloud host Virtualization sets tenant's virtual cloud in clear area.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
When the fault type is local fault, using the local data center as the target data center;
When the fault type is global fault, using the publicly-owned cloud data center as the target data center.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
When detecting that local data center handles the Operational Visit request appearance failure, the failure pair is analyzed The data answered account for the defective proportion of the total data resource of the local data center;
When the defective proportion is less than preset ratio, the fault type for judging the failure is the local fault;
When the defective proportion is greater than or equal to the preset ratio, the fault type for judging the failure is described complete Office's failure.
Further, processor 1001 can call the mixed cloud disaster tolerance program stored in memory 1005, also perform with Lower operation:
The target data is sent to default disaster tolerance front end processor, so that the default disaster tolerance front end processor is to the number of targets It is compressed according to being encrypted, and passes through Virtual Private Network and the target data after ciphered compressed is transmitted in the public cloud data The heart.
The present embodiment is detecting that local data center processing business access request goes out through the above scheme, by server During existing failure, the fault type of the failure is obtained, according to the fault type from publicly-owned cloud data center and the local number According to a data center is chosen in center as target data center, Operational Visit request is sent to the target data Center so that the target data center handles Operational Visit request, is selected corresponding by the type of failure Data center carries out business processing, can utilize distribution according to need and the elasticity of publicly-owned cloud data center, and idle does not need to occupy big Data resource is measured, the probability of secondary system disaster is reduced, reduces the risk of system data communication, improve data safety Property, reduce the input of resource, reply failure is quicker, and processing mode is simpler convenient.
Based on above-mentioned hardware configuration, mixed cloud disaster recovery method embodiment of the present invention is proposed.
With reference to Fig. 2, Fig. 2 is the flow diagram of mixed cloud disaster recovery method first embodiment of the present invention.
In the first embodiment, the mixed cloud disaster recovery method includes the following steps:
Step S10, server is when detecting that local data center processing business access request breaks down, described in acquisition The fault type of failure;
It should be noted that mixed cloud has merged public cloud, private clound and local data center, it is cloud computing in recent years Main Patterns and developing direction, enterprise can be placed on public cloud according to the requirement certain applications of business, and certain applications are placed on privately owned Then cloud data center gets through the public cloud and private clound both sides, the respective advantage of the two is made full use of to be provided for enterprise Better services support;Disaster tolerance system refers in strange land relatively far apart, establish two sets or the mostly identical internet skill of set function Art system can carry out state of health monitoring and function switch from each other, and system is because of unexpected (such as fire, earthquake) at one When being stopped, entire application system can be switched to another place so that the system function can continue to work normally.Disaster tolerance skill Art is a component part of the High availability of system, and disaster tolerance system more emphasizes shadow of the processing external environment to system It rings, particularly influence of the catastrophic event to entire Internet technology node, the other system of node level is provided and restores function.
It is understood that the server is detecting the local data center processing business access request appearance event During barrier, i.e., the source system that described local data center processing business accesses breaks down or mistake, can analyze at this time described It the fault type of failure and then is handled accordingly according to the fault type of the failure.
Step S20, one is chosen from publicly-owned cloud data center and the local data center according to the fault type Data center is as target data center;
It should be noted that the publicly-owned cloud data center is the cloud that can be used that third party provider provides to the user Data center, the publicly-owned cloud data center are capable of providing free or low-cost shared resource by Internet use Service, corresponding data center can be selected as number of targets after obtaining the fault type of the failure according to the fault type It is handled accordingly according to center and then to Operational Visit request.
Further, the step S20 specifically includes following steps:
When the fault type is local fault, using the local data center as the target data center;
When the fault type is global fault, using the publicly-owned cloud data center as the target data center.
It is understood that when the fault type is the local fault, using the local data center as institute State target data center, it is only necessary to from local recovery data, do and switch without entire business, secondary failure can be avoided Occur;When the fault type is the global fault, using the publicly-owned cloud data center as the target data center, The fault type, for distinguishing the preset type of different faults, can be local fault or global event for technical staff Barrier, naturally it is also possible to be the fault type of other sets itselfs, the present embodiment does not limit this.
Correspondingly, the step S10 specifically includes following steps:
When detecting that local data center handles the Operational Visit request appearance failure, the failure pair is analyzed The data answered account for the defective proportion of the total data resource of the local data center;
When the defective proportion is less than preset ratio, the fault type for judging the failure is the local fault;
When the defective proportion is greater than or equal to the preset ratio, the fault type for judging the failure is described complete Office's failure.
It should be noted that when detecting that local data center handles the Operational Visit request appearance failure, Analyze the defective proportion that the corresponding data of the failure account for the total data resource of the local data center, that is, the area broken down Domain accounts for the ratio of local data center;The preset ratio is pre-set defective proportion, can be technical staff according to big Measure data experiment or training obtains a more accurately ratio or technical staff is empirically determined according to regular job Fixed proportion, can also be according to the different corresponding preset flexibility and changeabilities of Operational Visit acquisition request type of service selection Ratio, naturally it is also possible to be preset ratio determining by other means, the present embodiment does not limit this.
It is understood that by the way that the defective proportion and the preset ratio are compared, institute can be effectively distinguished The failure for stating failure is to belong to smaller failure i.e. local fault, still falls within larger failure i.e. global fault, passes through differentiation The fault type of the failure can use corresponding data center to carry out the processing of Operational Visit request, save the throwing of resource Enter, reduce the waste of resource.
Step S30, Operational Visit request is sent to the target data center, so that the target data center Operational Visit request is handled.
It should be understood that Operational Visit request is sent to the target data center, so that the number of targets Operational Visit request is handled according to center, the target data center can pass through standby at the preset a certain moment Data of the part at the target data center ask the Operational Visit to carry out respective handling, can be to the Operational Visit It asks to carry out business recovery or pause preservation processing is carried out to Operational Visit request, can also be and carry out other The processing of form, the present embodiment do not limit this.
The present embodiment is detecting that local data center processing business access request goes out through the above scheme, by server During existing failure, the fault type of the failure is obtained, according to the fault type from publicly-owned cloud data center and the local number According to a data center is chosen in center as target data center, Operational Visit request is sent to the target data Center so that the target data center handles Operational Visit request, is selected corresponding by the type of failure Data center carries out business processing, can utilize distribution according to need and the elasticity of publicly-owned cloud data center, and idle does not need to occupy big Data resource is measured, the probability of secondary system disaster is reduced, reduces the risk of system data communication, improve data safety Property, reduce the input of resource, reply failure is quicker, and processing mode is simpler convenient.
Further, Fig. 3 is the flow diagram of mixed cloud disaster recovery method second embodiment of the present invention, as shown in figure 3, base Mixed cloud disaster recovery method second embodiment of the present invention is proposed in first embodiment, and in the present embodiment, the step S30 is specifically wrapped Include following steps:
Step S31, Operational Visit request is sent to the target data center, so that the target data center Operational Visit request is handled by target data, the target data is backed up for the local data center in institute It states local data center and the publicly-owned cloud data center is used to handle the data of the Operational Visit request.
It should be noted that the target data is backed up for the local data center in the local data center and institute Publicly-owned cloud data center is stated for handling the data of Operational Visit request, generally by backup tool by the target data It stores in the target data center, it, can be from the number of targets when the local data center breaks down or is wrong Data recovery and the processing of corresponding service are carried out according to center, when the target data center is the local data center, is write from memory Recognize in the local data center and be stored with the target data, when the target data center is the publicly-owned cloud data center When, generally the target data is stored in the user-specific memory block of the publicly-owned cloud data center, during idle time not The cloud host resource of the publicly-owned cloud data center is occupied, cloud host is just created only when disaster tolerance or DR test Distribution according to need disaster tolerance countermeasure, the cloud host is important component of the cloud computing in infrastructure application, positioned at cloud Industrial chain pyramid bottom is calculated, product is originated from cloud computing platform.Platform integration the Internet, applications three big key elements:Meter It calculates, store, network, user oriented provides the Internet infrastructure service of publicization.
Further, the step S31 specifically includes following steps:
When the local data center is in the target data center, locally take over environmental response is in the Operational Visit It asks and Operational Visit request is handled by the target data, the local take over environment is in the local The data take over environment of virtualization setting in the clear area of data center;
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to described Publicly-owned cloud data center so that the publicly-owned cloud data center by the target data to the Operational Visit request at Reason.
It should be noted that the local take over environment is set to be virtualized in the clear area of the local data center The data take over environment put;When the local data center is in the target data center, i.e., fault type at this time is institute Local fault is stated, the resource input of local data center can be reduced by the local take over environment, and the local connects Pipe ring border can be also used for the use of other test business before the target data is taken over, it is possible to prevente effectively from data resource Waste.
Further, the step is when the publicly-owned cloud data center is in the target data center, by the business Access request is sent to the publicly-owned cloud data center so that the publicly-owned cloud data center by the target data to described Operational Visit request is handled, and is specifically included:
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to tenant Virtual private cloud, so that tenant's virtual private cloud is handled Operational Visit request by the target data, Tenant's virtual private cloud is to virtualize to set in the clear area of the corresponding publicly-owned cloud platform of the publicly-owned cloud data center That puts is exclusively used in handling the data take over environment of the target data.
It is understood that tenant's virtual private cloud is publicly-owned cloud platform corresponding in the publicly-owned cloud data center Clear area in virtualization setting the data take over environment for being exclusively used in handling the target data;Tenant's virtual private cloud (Virtual Private Cloud, VPC) is the dynamic configuration pond of a public cloud computing resources, need using cryptographic protocol, The multi-tenant architecture of public cloud, is become single tenant architecture, reaches multiple rents in public cloud by tunnel protocol and other security procedures Security isolation between family ensures that the business of tenant's VPC network internals is independent and safe and virtually privately owned by the tenant Cloud carries out business isolation processing to the target data, and it is consistent with local can to ensure that public cloud takes over rear network topology.
It should be understood that when being the publicly-owned cloud data center at the target data center, i.e., failure classes at this time Type is the global fault, the Operational Visit can be asked in predetermined time to carry out phase by tenant's virtual private cloud It should handle, tenant's virtual cloud is located in the user-specific memory block of the publicly-owned cloud data center, does not do disaster tolerance usually and drills When white silk or disaster tolerance switch, the target data can only be present in the user-specific memory block, without being transferred to State the publicly-owned cloud platform of publicly-owned cloud data center.
In the concrete realization, tenant's virtual private cloud asks to carry out by the target data to the Operational Visit Processing can be asked to carry out business recovery processing according to the Operational Visit, can be by tenant's virtual private cloud Automation business recovery is realized in resource layout, with reference to physical to virtual (Physical to Virtual, P2V) or virtually to void Intend the conversion that (Virtual to Virtual, V2V) technology does cloud virtual, the resource layout can be according to the cloud made Host is configured and network configuration carries out creating cloud host, on-premise network and taking over tasks, after the business of having taken over, it is possible into The access switching of the entire business of row receives the Operational Visit request, and passes through the mesh according to Operational Visit request It marks data and carries out corresponding business recovery.
It is understood that P2V refers to move in the physical hard disk of operating system, application program or data form computer It moves on in a virtual environment or in disk partition, V2V refers to operating system, application program or data form computer Moved in a kind of virtualized environment in another virtual environment or in disk partition because the realization of public cloud be all with Virtualization mode exists, thus business migration to public cloud process be typically necessary carry out P2V conversion.
Correspondingly, the step visits the business when the publicly-owned cloud data center is in the target data center Ask that request is sent to tenant's virtual private cloud, so that tenant's virtual private cloud visits the business by the target data Before asking that request is handled, the mixed cloud disaster recovery method is further comprising the steps of:
When the target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction;
The virtual cloud is created into instruction and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center root Parameter and default network configuration parameters are configured in the corresponding publicly-owned cloud platform of the publicly-owned cloud data center according to default cloud host Virtualization sets tenant's virtual cloud in clear area.
It should be noted that the default cloud host configuration parameter and the default network configuration parameters are the cloud data Center creates instruction for creating the environmental parameter that tenant's virtual cloud needs according to the virtual cloud, and the default host is matched It can be that technical staff tests or train the ratio obtained according to mass data to put parameter and the default network configuration parameters Accurate parameter or technical staff is according to the empirically determined preset parameter of regular job, can also be according to difference The corresponding preset flexibility and changeability of type of service selection parameter, naturally it is also possible to be parameter determining by other means, The present embodiment does not limit this.
In the concrete realization, parameter and the default network configuration parameters being configured by the default cloud host can generate Corresponding preset arrangement rule can be realized according to the preset arrangement rule and automatically create cloud host and automatic recycling cloud master Machine, during idle time phase cloud host do not need to be created, when needing to use tenant's virtual private cloud, i.e., when described When target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction, is created and instructed according to the virtual cloud, Using the default cloud host configuration parameter and the default network configuration parameters in the free area of the publicly-owned cloud data center The cloud host is created in domain and network and take over business has been configured, virtualization sets tenant's virtual cloud;Pass through above-mentioned side Formula, which can be realized, not to be needed to create any cloud host during idle time, reduces the input of resource, and only when disaster tolerance switching or The characteristics of cloud host can be just created when needing to do DR test, public cloud distribution according to need is utilized well.
The present embodiment is sent to the target data center through the above scheme, by the way that the Operational Visit is asked, with The target data is made to be handled centrally through target data Operational Visit request, the target data is described Ground data center backup is asked in the local data center and the publicly-owned cloud data center for handling the Operational Visit Data, the target data center be the local data center when, locally take over environmental response is in the Operational Visit It asks and Operational Visit request is handled by the target data, be described publicly-owned at the target data center During cloud data center, Operational Visit request is sent to tenant's virtual private cloud, so that tenant's virtual private cloud is led to The target data is crossed to handle Operational Visit request, it is virtually private by the local take over environment and the tenant There is cloud that business can be isolated in LAN, avoid direct and publicly-owned cloud platform and interconnect the problem of safety brought is poor, And Operational Visit request is handled by target data, idle does not need to occupy mass data resource, reduces The probability of secondary system disaster reduces the risk of system data communication, improves Information Security, reduces the throwing of resource Enter, reply failure is quicker, and processing mode is simpler convenient.
Further, Fig. 4 is the flow diagram of mixed cloud disaster recovery method 3rd embodiment of the present invention, as shown in figure 4, base Mixed cloud disaster recovery method 3rd embodiment of the present invention is proposed in second embodiment, in the present embodiment, before the step S31, The mixed cloud disaster recovery method is further comprising the steps of:
Step S301, the target data is sent to default disaster tolerance front end processor, so that the default disaster tolerance front end processor pair Compression is encrypted in the target data, and passes through Virtual Private Network and the target data after ciphered compressed is transmitted to the public affairs There is cloud data center.
It should be noted that the default disaster tolerance front end processor is synchronizes the target data to the publicly-owned cloud data center One or more servers with store function, be generally deployed in the local data center and generation business together, pass through LAN or netted channel (Fibre Channel, FC) network connection, for summarizing from the data of each server sync i.e. The target data, and the target data is sent to the publicly-owned cloud data center.
It is understood that the local data center can be local virtualized server or physical server, Target data is synchronized to the disaster tolerance front end processor by the local data center by disaster tolerance client, and the disaster tolerance front end processor converges After total target data, by accelerating Virtual Private Network (Virtual Private Network, VPN) the mesh Mark data are encrypted and are transferred to after compressing the user-specific memory block of the publicly-owned cloud data center, the public cloud number According to center after the encryption of the disaster tolerance front end processor transmission and the compressed target data is received, after encryption and compression The target data be decrypted and decompress, be then saved in user-specific memory block, do not do DR test or disaster tolerance usually When switching, the target data can only be present in the user-specific memory block, without being transferred to the public cloud The publicly-owned cloud platform of data center.
If it should be understood that the fault type of the failure is the local fault, that can be by the disaster tolerance The data preserved in front end processor take in local take over environment, if the fault type of the failure is the global event During barrier, that can transfer the target data by the user-specific memory block of the publicly-owned cloud data center and pass through the rent Family virtual private cloud carries out business processing, can will be described after detecting that the local data center completes fault restoration The newly-increased data transmission generated in publicly-owned cloud data center is to the local data center;It can be fast by the disaster tolerance front end processor Quick-recovery local fault can also ensure the safety of original business, and the same of public network safe transmission can be realized with reference to Virtual Private Network When public network can also be avoided to transmit happening for unstable cause and loss of data.
In the concrete realization, the target data can be carried out at data desensitization by tenant's virtual private cloud Reason, thereby may be ensured that DR test does not influence the normal operation of other systems;It can also be by will be in the public cloud data The heart is built elsewhere to realize data disaster tolerance, such as:It can be the public cloud Constructing data center in tenant void Intend realizing in a manner of cloud host and cloud storage in private clound, but after will appear take over business, formal business and disaster tolerance industry All inside same virtual private cloud, bad isolation between business can mutually have an impact for business;It can also the public cloud Constructing data center is converted into an all-in-one machine to tenant center, then passes through application programming interface with high in the clouds The mode of (Application Programming Interface, API) docking service take-over is realized, but appears in industry Business amount is influenced when more by the Internet transmission, can not accomplish quick disaster-containing pipe, in addition if in the public cloud data The heart and generation business are put together, then when there is fire when global faults, can not be connect by the publicly-owned cloud data center The effect of disaster tolerance is not achieved in pipe business.
The present embodiment is sent to default disaster tolerance front end processor through the above scheme, by the target data, so that described default Compression is encrypted to the target data in disaster tolerance front end processor, and passes through Virtual Private Network by the target data after ciphered compressed The publicly-owned cloud data center is transmitted to, if the fault type of the failure is the local fault, that can be by described The data preserved in disaster tolerance front end processor take in local take over environment;It being capable of fast quick-recovery by the disaster tolerance front end processor Local fault can also ensure the safety of original business, can realize public network safety with reference to Virtual Private Network, can avoid public affairs Net transmits happening for unstable cause and loss of data, and idle does not need to occupy mass data resource, reduces system two The probability of secondary disaster reduces the risk of system data communication, improves Information Security, reduces the input of resource, reply Failure is quicker, and processing mode is simpler convenient.
In addition, the embodiment of the present invention also proposes a kind of storage medium, mixed cloud disaster tolerance journey is stored on the storage medium Sequence realizes following operation when the mixed cloud disaster tolerance program is executed by processor:
When detecting that local data center processing business access request breaks down, the failure classes of the failure are obtained Type;
One data center is chosen from publicly-owned cloud data center and the local data center according to the fault type As target data center;
Operational Visit request is sent to the target data center, so that the target data center is to the industry Business access request is handled.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
Operational Visit request is sent to the target data center, so that the target data is centrally through target Data handle Operational Visit request, and the target data is backed up for the local data center in the local number It is used to handle the data of the Operational Visit request according to center and the publicly-owned cloud data center.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
When the local data center is in the target data center, locally take over environmental response is in the Operational Visit It asks and Operational Visit request is handled by the target data, the local take over environment is in the local The data take over environment of virtualization setting in the clear area of data center;
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to described Publicly-owned cloud data center so that the publicly-owned cloud data center by the target data to the Operational Visit request at Reason.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to tenant Virtual private cloud, so that tenant's virtual private cloud is handled Operational Visit request by the target data, Tenant's virtual private cloud is virtualizes in the clear area of the corresponding publicly-owned cloud platform of the publicly-owned cloud data center The data take over environment for being exclusively used in handling the target data of setting.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
When the target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction;
The virtual cloud is created into instruction and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center root The corresponding publicly-owned cloud platform of parameter and default network configuration parameters in the publicly-owned cloud data center is configured according to default cloud host Clear area in virtualization tenant's virtual cloud is set.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
When the fault type is local fault, using the local data center as the target data center;
When the fault type is global fault, using the publicly-owned cloud data center as the target data center.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
When detecting that local data center handles the Operational Visit request appearance failure, the failure pair is analyzed The data answered account for the defective proportion of the total data resource of the local data center;
When the defective proportion is less than preset ratio, the fault type for judging the failure is the local fault;
When the defective proportion is greater than or equal to the preset ratio, the fault type for judging the failure is described complete Office's failure.
Further, following operation is also realized when the mixed cloud disaster tolerance program is executed by processor:
The target data is sent to default disaster tolerance front end processor, so that the default disaster tolerance front end processor is to the number of targets It is compressed according to being encrypted, and passes through Virtual Private Network and the target data after ciphered compressed is transmitted in the public cloud data The heart.
The present embodiment is detecting that local data center processing business access request goes out through the above scheme, by server During existing failure, the fault type of the failure is obtained, according to the fault type from publicly-owned cloud data center and the local number According to a data center is chosen in center as target data center, Operational Visit request is sent to the target data Center so that the target data center handles Operational Visit request, is selected corresponding by the type of failure Data center carries out business processing, can utilize distribution according to need and the elasticity of publicly-owned cloud data center, and idle does not need to occupy big Data resource is measured, the probability of secondary system disaster is reduced, reduces the risk of system data communication, improve data safety Property, reduce the input of resource, reply failure is quicker, and processing mode is simpler convenient.
It should be noted that herein, term " comprising ", "comprising" or its any other variant are intended to non-row His property includes, so that process, method, article or system including a series of elements not only include those elements, and And it further includes other elements that are not explicitly listed or further includes intrinsic for this process, method, article or system institute Element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that including this Also there are other identical elements in the process of element, method, article or system.
The embodiments of the present invention are for illustration only, do not represent the quality of embodiment.
It these are only the preferred embodiment of the present invention, be not intended to limit the scope of the invention, it is every to utilize this hair The equivalent structure or equivalent flow shift that bright specification and accompanying drawing content are made directly or indirectly is used in other relevant skills Art field, is included within the scope of the present invention.

Claims (10)

1. a kind of mixed cloud disaster recovery method, which is characterized in that the mixed cloud disaster recovery method includes:
Server obtains the failure classes of the failure when detecting that local data center processing business access request breaks down Type;
One data center's conduct is chosen from publicly-owned cloud data center and the local data center according to the fault type Target data center;
Operational Visit request is sent to the target data center, so that the business is visited at the target data center Ask that request is handled.
2. mixed cloud disaster recovery method as described in claim 1, which is characterized in that described to be sent to Operational Visit request The target data center so that the target data center handles Operational Visit request, specifically includes:
Operational Visit request is sent to the target data center, so that the target data is centrally through target data Operational Visit request is handled, the target data is backed up for the local data center in the local data The heart and the publicly-owned cloud data center are used to handle the data of the Operational Visit request.
3. mixed cloud disaster recovery method as claimed in claim 2, which is characterized in that described to be sent to Operational Visit request The target data center, so that the target data is handled Operational Visit request centrally through target data, It specifically includes:
When the local data center is in the target data center, locally take over environmental response is asked in the Operational Visit And Operational Visit request is handled by the target data, the local take over environment is in the local data The data take over environment of virtualization setting in the clear area at center;
When the publicly-owned cloud data center is in the target data center, Operational Visit request is sent to described publicly-owned Cloud data center, so that the publicly-owned cloud data center is handled Operational Visit request by the target data.
4. mixed cloud disaster recovery method as claimed in claim 3, which is characterized in that described at the target data center is described During publicly-owned cloud data center, Operational Visit request is sent to the publicly-owned cloud data center, so that the public cloud number Operational Visit request is handled according to centrally through the target data, is specifically included:
When the publicly-owned cloud data center is in the target data center, it is virtual that Operational Visit request is sent to tenant Private clound, so that tenant's virtual private cloud is handled Operational Visit request by the target data, it is described Tenant's virtual private cloud is the virtualization setting in the clear area of the corresponding publicly-owned cloud platform of the publicly-owned cloud data center It is exclusively used in handling the data take over environment of the target data.
5. mixed cloud disaster recovery method as claimed in claim 4, which is characterized in that described at the target data center is described During publicly-owned cloud data center, Operational Visit request is sent to tenant's virtual private cloud, so that the tenant is virtually privately owned Before cloud is handled Operational Visit request by the target data, the mixed cloud disaster recovery method further includes:
When the target data center is the publicly-owned cloud data center, generation virtual cloud creates instruction;
The virtual cloud is created into instruction and is sent to the publicly-owned cloud data center, so that the publicly-owned cloud data center is according to pre- If the free time of parameter and default network configuration parameters in the corresponding publicly-owned cloud platform of the publicly-owned cloud data center is configured in cloud host Virtualization sets tenant's virtual cloud in region.
6. the mixed cloud disaster recovery method as described in any one of claim 1-5, which is characterized in that described according to the failure classes Type chooses a data center as target data center from publicly-owned cloud data center and the local data center, specific to wrap It includes:
When the fault type is local fault, using the local data center as the target data center;
When the fault type is global fault, using the publicly-owned cloud data center as the target data center.
7. mixed cloud disaster recovery method as claimed in claim 6, which is characterized in that described to detect local data center processing When the Operational Visit request is broken down, the fault type of the failure is obtained, is specifically included:
When detecting that local data center handles the Operational Visit request appearance failure, it is corresponding to analyze the failure Data account for the defective proportion of the total data resource of the local data center;
When the defective proportion is less than preset ratio, the fault type for judging the failure is the local fault;
When the defective proportion is greater than or equal to the preset ratio, the fault type for judging the failure is the global event Barrier.
8. the mixed cloud disaster recovery method as described in any one of claim 2-5, which is characterized in that described according to the failure classes Before type chooses a data center as target data center from publicly-owned cloud data center and the local data center, institute Mixed cloud disaster recovery method is stated to further include:
The target data is sent to default disaster tolerance front end processor so that the default disaster tolerance front end processor to the target data into Row ciphered compressed, and pass through Virtual Private Network and the target data after ciphered compressed is transmitted to the publicly-owned cloud data center.
9. a kind of mixed cloud Disaster Recovery Service, which is characterized in that the mixed cloud Disaster Recovery Service includes:Memory, processor And the mixed cloud disaster tolerance program that is stored on the memory and can run on the processor, the mixed cloud disaster tolerance program It is arranged for carrying out such as the step of mixed cloud disaster recovery method described in any item of the claim 1 to 8.
10. a kind of storage medium, which is characterized in that mixed cloud disaster tolerance program, the mixed cloud are stored on the storage medium It is realized when disaster tolerance program is executed by processor such as the step of mixed cloud disaster recovery method described in any item of the claim 1 to 8.
CN201711498524.8A 2017-12-29 2017-12-29 Mixed cloud disaster recovery method, server and storage medium Pending CN108234212A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711498524.8A CN108234212A (en) 2017-12-29 2017-12-29 Mixed cloud disaster recovery method, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711498524.8A CN108234212A (en) 2017-12-29 2017-12-29 Mixed cloud disaster recovery method, server and storage medium

Publications (1)

Publication Number Publication Date
CN108234212A true CN108234212A (en) 2018-06-29

Family

ID=62642445

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711498524.8A Pending CN108234212A (en) 2017-12-29 2017-12-29 Mixed cloud disaster recovery method, server and storage medium

Country Status (1)

Country Link
CN (1) CN108234212A (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109783216A (en) * 2019-01-17 2019-05-21 广东石油化工学院 Multi-workflow load-balancing method and system under a kind of mixing cloud environment
CN110012054A (en) * 2018-12-28 2019-07-12 阿里巴巴集团控股有限公司 A kind of method for processing business and system based on alliance's chain network
CN110351128A (en) * 2019-06-27 2019-10-18 北京大米科技有限公司 A kind of method for processing business, device, storage medium and server
CN111064802A (en) * 2019-12-26 2020-04-24 北京奇艺世纪科技有限公司 Network request processing method and device, electronic equipment and storage medium
CN111464332A (en) * 2020-03-06 2020-07-28 中国人民财产保险股份有限公司 Disaster recovery method, device and equipment
CN111741135A (en) * 2020-08-19 2020-10-02 广州汽车集团股份有限公司 Hybrid cloud disaster recovery system and control method thereof
CN112433891A (en) * 2020-12-02 2021-03-02 中国建设银行股份有限公司 Data processing method and device and server
CN115277727A (en) * 2022-06-30 2022-11-01 达闼机器人股份有限公司 Data disaster recovery method, system, device and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103778031A (en) * 2014-01-15 2014-05-07 华中科技大学 Distributed system multilevel fault tolerance method under cloud environment
CN106844487A (en) * 2016-12-23 2017-06-13 航天星图科技(北京)有限公司 A kind of distributed memory system replicated based on storehouse
CN107005580A (en) * 2014-11-04 2017-08-01 瑞典爱立信有限公司 Network function virtualization services are linked
CN107203440A (en) * 2017-05-27 2017-09-26 郑州云海信息技术有限公司 A kind of integration is backed up in realtime disaster tolerance system and building method
EP3240240A1 (en) * 2016-04-25 2017-11-01 Cisco Technology, Inc. Network architecture for predictive services management in cable network environments

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103778031A (en) * 2014-01-15 2014-05-07 华中科技大学 Distributed system multilevel fault tolerance method under cloud environment
CN107005580A (en) * 2014-11-04 2017-08-01 瑞典爱立信有限公司 Network function virtualization services are linked
EP3240240A1 (en) * 2016-04-25 2017-11-01 Cisco Technology, Inc. Network architecture for predictive services management in cable network environments
CN106844487A (en) * 2016-12-23 2017-06-13 航天星图科技(北京)有限公司 A kind of distributed memory system replicated based on storehouse
CN107203440A (en) * 2017-05-27 2017-09-26 郑州云海信息技术有限公司 A kind of integration is backed up in realtime disaster tolerance system and building method

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110012054A (en) * 2018-12-28 2019-07-12 阿里巴巴集团控股有限公司 A kind of method for processing business and system based on alliance's chain network
US11102284B2 (en) 2018-12-28 2021-08-24 Advanced New Technologies Co., Ltd. Service processing methods and systems based on a consortium blockchain network
CN109783216A (en) * 2019-01-17 2019-05-21 广东石油化工学院 Multi-workflow load-balancing method and system under a kind of mixing cloud environment
CN110351128A (en) * 2019-06-27 2019-10-18 北京大米科技有限公司 A kind of method for processing business, device, storage medium and server
CN111064802A (en) * 2019-12-26 2020-04-24 北京奇艺世纪科技有限公司 Network request processing method and device, electronic equipment and storage medium
CN111064802B (en) * 2019-12-26 2022-04-22 北京奇艺世纪科技有限公司 Network request processing method and device, electronic equipment and storage medium
CN111464332A (en) * 2020-03-06 2020-07-28 中国人民财产保险股份有限公司 Disaster recovery method, device and equipment
CN111741135A (en) * 2020-08-19 2020-10-02 广州汽车集团股份有限公司 Hybrid cloud disaster recovery system and control method thereof
CN111741135B (en) * 2020-08-19 2020-12-15 广州汽车集团股份有限公司 Hybrid cloud disaster recovery system and control method thereof
CN112433891A (en) * 2020-12-02 2021-03-02 中国建设银行股份有限公司 Data processing method and device and server
CN115277727A (en) * 2022-06-30 2022-11-01 达闼机器人股份有限公司 Data disaster recovery method, system, device and storage medium
CN115277727B (en) * 2022-06-30 2024-03-19 达闼机器人股份有限公司 Data disaster recovery method, system, device and storage medium

Similar Documents

Publication Publication Date Title
CN108234212A (en) Mixed cloud disaster recovery method, server and storage medium
US10997063B1 (en) System testing from production transactions
US9838294B2 (en) Network development and testing as a cloud service
CN109471710B (en) Task request processing method and device, processor, terminal and server
US11522780B1 (en) Monitoring networks by detection of noisy agents
Ahrenholz et al. CORE: A real-time network emulator
CN105022659B (en) virtual machine state control method and system
JP2019197561A (en) Rolling security platform
JP2014506045A (en) Network stimulation engine
US10263856B2 (en) Dynamic highlight
US9423956B2 (en) Emulating a stretched storage device using a shared storage device
CN103718535B (en) The alleviation of hardware fault
JP5549237B2 (en) Test environment construction program, test environment construction method, and test apparatus
CN105787364B (en) Automatic testing method, device and system for tasks
KR101680702B1 (en) System for web hosting based cloud service
US9442811B2 (en) Emulating a stretched storage device using a shared replicated storage device
US9021008B1 (en) Managing targeted scripts
AU2019213376A1 (en) Capturing and encoding of network transactions for playback in a simulation environment
CN106031128A (en) Providing mobile device management functionalities
CN107506295A (en) Method of testing, equipment and the computer-readable recording medium of virtual machine backup
KR20230086805A (en) Change Impact Simulation Analysis
CN109039959A (en) A kind of the consistency judgment method and relevant apparatus of SDN network rule
US20150256446A1 (en) Method and apparatus for relaying commands
Lieskovan et al. Building open source cyber range to teach cyber security
Berenberg et al. Deployment archetypes for cloud applications

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
TA01 Transfer of patent application right

Effective date of registration: 20200616

Address after: Nanshan District Xueyuan Road in Shenzhen city of Guangdong province 518000 No. 1001 Nanshan Chi Park building A1 layer

Applicant after: SANGFOR TECHNOLOGIES Inc.

Address before: Nanshan District Xueyuan Road in Shenzhen city of Guangdong province 518000 No. 1001 Nanshan Chi Park A1 building five floor

Applicant before: Shenxin network technology (Shenzhen) Co.,Ltd.

TA01 Transfer of patent application right
RJ01 Rejection of invention patent application after publication

Application publication date: 20180629

RJ01 Rejection of invention patent application after publication