A method for automatically installing and uninstalling a specified driver on a disaster recovery machine

Abstract

The present invention discloses a method for automatically installing and uninstalling a specified driver on a disaster recovery machine, formulating a WinPE tool; optimizing the disaster recovery process; creating a disaster recovery machine through a virtualization platform interface; organizing backup data into the form of a disk and adding it to the disaster recovery machine; adding an optical drive to the disaster recovery machine; adding a customized winpe system in the optical drive; modifying the boot from the optical drive, and turning on the power of the disaster recovery machine; after entering winpe, the program in winpe automatically performs compatibility processing; looping querying the power state of the disaster recovery machine; if it is in the power-on state, looping querying until the winpe in the previous step is automatically shut down after processing; if it is in the shutdown state, removing the optical drive, modifying it to boot the system from the disk; turning on the disaster recovery machine and entering the system. The present invention enters the system through winpe for the first time, and needs to load very few drivers, enters the system faster, and does not load the relevant programs and drivers of the original system.

Description

Technical Field

[0001] The present invention relates to the technical field of disaster recovery, in particular to a method for automatically installing and uninstalling a designated driver on a disaster recovery machine. Background Art

[0002] The existing disaster recovery technology backs up the Windows system of the source machine, and then uses the backup data to pull it up on the disaster recovery machine of the virtualization platform. The problem that needs to be solved is that the disk driver cannot be recognized after the cross-platform, resulting in the inability to boot into the system. For example, the virtio-related drivers need to be installed when the backup data of the physical machine is pulled up on the disaster recovery machine on the KVM virtualization platform. Without the relevant drivers, the disaster recovery machine may not be able to recognize the disk and cannot boot into the system.

[0003] There are generally three options:

[0004] Solution 1: Pre-install the drivers required for cross-platform on the original production machine. For example, if the source machine is a physical machine with Windows system installed and KVM as the virtualization platform, migrate the source machine system to the KVM disaster recovery machine. In order to enter the system normally and ensure performance, it is necessary to install KVM-related drivers (disk driver, network card driver, memory driver, etc.) on the source machine. In this way, the backup data will contain related drivers after the backup, and the KVM disaster recovery machine can enter the system normally.

[0005] Solution 2: Set the disk controller type of the disaster recovery machine to IDE mode. Usually, you can enter the system in this mode. After entering the system, manually install the relevant drivers to provide hardware adaptation performance.

[0006] Solution 3: Set the disk controller type of the disaster recovery machine to ide mode, add the driver package set to the CD-ROM drive of the disaster recovery machine, and automatically install the driver from the CD-ROM drive after entering the system. After the installation is complete, it will automatically restart and change the disk controller type to other modes, such as setting the KVM disaster recovery machine to virtio mode.

[0007] The above three solutions all have disadvantages:

[0008] Solution 1: You need to install the relevant drivers on the source machine in advance, and then back up. Installing the driver may pose a serious threat to the source machine system. For example, the installation of the driver conflicts with the original machine, causing the system to freeze, affecting the business system on the source machine; even after restarting the machine, you cannot enter the system. The present invention does not need to install the driver on the source machine in advance. Through the customized WinPE tool, when the disaster recovery machine is started, the required driver is first injected from the WinPE system to the disaster recovery machine system disk.

[0009] Solution 2: A lot of manual operations are required, and the operator is required to be familiar with which drivers to install. The operator's professionalism is highly required. The disaster recovery process of the present invention is automatically completed by the program from the normal entry into the system, without a lot of manual intervention.

[0010] Disadvantages of Solution 3: Compared with Solution 2, it is optimized, but it does not take into account the drivers and programs contained in the source machine, which conflict with the virtualization platform itself. Therefore, the system cannot be entered in IDE mode, let alone reinstalling related drivers after entering the system. It has great limitations and poor adaptability. Summary of the invention

[0011] In order to solve the above problems, the present invention provides a method for automatically installing and uninstalling a specified driver on a disaster recovery machine with high processing efficiency and good compatibility.

[0012] In order to achieve the above object, the present invention is implemented by the following technical solutions:

[0013] The present invention is a method for automatically installing and uninstalling a specified driver on a disaster recovery machine, comprising the following steps:

[0014] Step 1, develop WinPE tools;

[0015] Step 2: Optimize the disaster recovery process;

[0016] Step 2.1: Create a disaster recovery machine through the virtualization platform interface;

[0017] Step 2.2: Organize the backup data into disks and add them to the disaster recovery machine.

[0018] Step 2.3, add a CD-ROM drive to the disaster recovery machine;

[0019] Step 2.4, add the customized winpe system to the CD-ROM drive;

[0020] Step 2.5: Change the boot mode to CD-ROM and power on the disaster recovery machine.

[0021] Step 2.6, after entering winpe, the program in winpe will automatically perform compatibility processing, and the system will shut down after the processing is completed;

[0022] Step 2.7, loop query the power status of the disaster recovery machine; if it is in the power-on state, loop query until it automatically shuts down after winpe processing in step 2.6 is completed; if it is in the power-off state, remove the optical drive and change it to boot the system from the disk;

[0023] Step 2.8: Start the disaster recovery machine and enter the system.

[0024] A further improvement of the present invention is that the WinPE customization steps are as follows:

[0025] Step 1.1: Package the relevant virtualization drivers required by the disaster recovery machine into WinPE;

[0026] Step 1.2, write the compatibility processing program DRTool;

[0027] Step 1.3, write a startup script to call DRTool.

[0028] A further improvement of the present invention is that the specific operation of step 2.6 is:

[0029] Step 2.61, after entering WinPE, the system automatically calls DRTool;

[0030] Step 2.62: DRTool uninstalls the related drivers in the system disk of the disaster recovery machine through the dism program that comes with the system, deletes the related driver files in the system disk of the disaster recovery machine, loads the system disk registry of the disaster recovery machine, and deletes and cleans up the registry information associated with the deleted drivers.

[0031] Step 2.63: DRTool uses the dism program to install the virtualization-related drivers packaged in WinPE to the system disk of the disaster recovery machine, then loads the system disk registry of the disaster recovery machine and adds the relevant registry of the installed driver.

[0032] Step 2.64, DRTool searches and cleans up the specified programs and files in the system disk of the disaster recovery machine;

[0033] Step 2.65: DRTool executes the script pre-installed in the system disk of the disaster recovery machine to perform further deep cleaning;

[0034] Step 2.66, after the processing is completed, the machine will shut down automatically.

[0035] A further improvement of the present invention is that the relevant drivers in step 2.62 include a storage controller driver and a network card driver.

[0036] The beneficial effect of the present invention is that the WinPE disaster recovery customization tool in the present invention can be customized and developed according to the compatibility scenario and scope, and is flexible and changeable.

[0037] The present invention enters the system through winpe for the first time, needs to load few drivers, is relatively fast to start the system, and does not load the related programs and drivers of the original system. At the same time, the present invention automatically performs compatibility processing after entering the winpe system, deletes the related conflicting programs and drivers, and then installs the related available drivers. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is the work flow chart of the present invention. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] The present invention is a method for automatically installing and uninstalling a specified driver on a disaster recovery machine, optimizing the process in the existing disaster recovery technology, and providing a customized winpe tool. The winpe customized content includes installing and uninstalling a specified driver, querying and deleting a specified program and a registry. The method is specifically as follows:

[0041] Step 1, develop WinPE tools;

[0042] WinPE customization content is:

[0043] Step 1.1: Package the relevant virtualization drivers required by the disaster recovery machine into WinPE;

[0044] Step 1.2, write the compatibility processing program DRTool, which is responsible for installing and uninstalling drivers, deleting specified programs and registry information, and executing the preset scripts on the system disk of the disaster recovery machine. This method can make up for the adaptability of WinPE. Customized WinPE may not take into account the deletion of some programs in special environments. A script file can be preset on the source machine before backing up, and the script can be executed in WinPE during disaster recovery. There is no need to create a new WinPE for adaptation;

[0045] Step 1.3, write a startup script to call DRTool.

[0046] The WinPE tool of the present invention can be customized and developed according to compatibility scenarios and scopes, and is flexible and changeable.

[0047] Step 2: Optimize the disaster recovery process;

[0048] Step 2.1: Create a disaster recovery machine through the virtualization platform interface;

[0049] Step 2.2: Organize the backup data into disks and add them to the disaster recovery machine.

[0050] Step 2.3, add a CD-ROM drive to the disaster recovery machine;

[0051] Step 2.4, add the customized winpe system to the CD-ROM drive;

[0052] Step 2.5: Change the boot mode to CD-ROM and power on the disaster recovery machine.

[0053] Step 2.6, after entering winpe, the program in winpe will automatically perform compatibility processing, and the system will shut down after the processing is completed;

[0054] WinPE workflow is:

[0055] (1) After entering WinPE, the system automatically calls DRTool;

[0056] (2) DRTool uninstalls the relevant drivers in the system disk of the disaster recovery machine through the dism program that comes with the system, deletes the relevant driver files in the system disk of the disaster recovery machine, loads the system disk registry of the disaster recovery machine, and deletes and cleans up the registry information associated with the deleted drivers;

[0057] (3) DRTool uses the dism program to install WinPE built-in packaged virtualization-related drivers, such as storage controller drivers and network card drivers, to the system disk of the disaster recovery machine. It then loads the system disk registry of the disaster recovery machine and adds the relevant registry of the installed drivers.

[0058] (4) DRTool searches for and cleans up the specified programs and files in the system disk of the disaster recovery machine;

[0059] (5) DRTool executes the script pre-installed in the system disk of the disaster recovery machine. The script is an automatically defined behavior and can be placed before the backup. It will be saved during the backup for further deep cleaning.

[0060] (6) After the processing is completed, the machine will automatically shut down;

[0061] Step 2.7, loop query the power status of the disaster recovery machine; if it is in the power-on state, loop query until it automatically shuts down after winpe processing in step 2.6 is completed; if it is in the power-off state, remove the optical drive and change it to boot the system from the disk;

[0062] Step 2.8: Start the disaster recovery machine and enter the system.

[0063] The method of the present invention does not require the installation of the required drivers on the production machine in advance, and does not pose a threat to the production machine system. The customized tool can automatically complete the driver uninstallation and installation of the original system environment when entering the winpe system for the first time, and does not require manual installation and uninstallation. The first startup of the disaster recovery machine is to enter the winpe system, so there is no conflict between the original system program and the virtualization platform. After entering the winpe system tool, the specified conflicting programs, services, registry and other conflicting contents can be automatically deleted.

[0064] In addition, the customized winpe in the present invention can be replaced with an independent existing windows environment, which deploys relevant driver package files and compatibility processing programs as an environment for preprocessing compatibility issues. The backup data of the original system is first mounted on the windows system in the form of a disk for preprocessing, deleting programs and drivers, installing specified drivers, etc. After the processing is completed, it is mounted on the disaster recovery machine and started directly. However, this solution requires the deployment of a preprocessing environment in advance.

[0065] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for automatically installing and uninstalling a specified driver on a disaster recovery machine, characterized in that: The following steps are involved: Step 1, develop WinPE tools; Step 2: Optimize the disaster recovery process; Step 2.1: Create a disaster recovery machine through the virtualization platform interface; Step 2.2: Organize the backup data into disks and add them to the disaster recovery machine. Step 2.3, add a CD-ROM drive to the disaster recovery machine; Step 2.4, add the customized WinPE system to the CD-ROM drive; Step 2.5: Change the boot mode to CD-ROM and power on the disaster recovery machine. Step 2.6, after entering WinPE, the program in WinPE will automatically perform compatibility processing, and the system will shut down after the processing is completed; Step 2.7, loop query the power status of the disaster recovery machine; if it is in the power-on state, loop query until the WinPE process in step 2.6 is completed and the machine automatically shuts down; if it is in the power-off state, remove the optical drive and change it to boot the system from the disk; Step 2.8, start the disaster recovery machine and enter the system; The specific operations of step 2.6 are as follows: Step 2.61, after entering WinPE, the system automatically calls DRTool; Step 2.62: DRTool uninstalls the related drivers in the system disk of the disaster recovery machine through the dism program that comes with the system, deletes the related driver files in the system disk of the disaster recovery machine, loads the system disk registry of the disaster recovery machine, and deletes and cleans up the registry information associated with the deleted drivers. Step 2.63: DRTool uses the dism program to install the virtualization-related drivers packaged in WinPE to the system disk of the disaster recovery machine, then loads the system disk registry of the disaster recovery machine and adds the relevant registry of the installed driver. Step 2.64, DRTool searches and cleans up the specified programs and files in the system disk of the disaster recovery machine; Step 2.65: DRTool executes the script pre-installed in the system disk of the disaster recovery machine to perform further deep cleaning; Step 2.66, after the processing is completed, the machine will shut down automatically.

2. According to claim 1, a method for automatically installing and uninstalling a specified driver on a disaster recovery machine is characterized in that: The steps for WinPE customization are as follows: Step 1.1: Package the relevant virtualization drivers required by the disaster recovery machine into WinPE; Step 1.2, write the compatibility processing program DRTool; Step 1.3, write a startup script to call DRTool.

Images