CN103064767B - Method and device for driver backup and restoration - Google Patents

Abstract

The invention discloses a method and a device for backup and recovery of a drive, wherein the method for backup of the drive comprises the following steps: acquiring information of a driver in an operating system; according to the information of each drive program, taking the drive program which does not belong to the system and the corresponding equipment is not a central processing unit, an optical drive and virtual equipment as a candidate backup drive program; and judging whether the equipment information file corresponding to each candidate backup driving program exists, and if so, backing up the corresponding equipment information file and the driving program file. The invention reduces the storage space occupied by driving the backup data, and can install the required driver according to the backed-up driver when operating the system again, thereby avoiding the trouble of identifying the models of different devices and searching the driver when reinstalling the operating system, having shorter time and improving the efficiency of installing the driver.

Description

Method and device for driver backup and recovery

technical field

The invention relates to the technical field of computers, in particular to a method and device for driving backup and restoration.

Background technique

A driver is a type of interface program used by the operating system to control the normal operation of hardware devices. The operating system sends instructions to the driver, and the driver drives the hardware to work, and can also adjust the performance of the hardware. For example, after the operating system is installed, the display color of the screen cannot display true color. This is because only the most basic driver program that comes with the graphics card is used, resulting in the performance of the graphics card not being able to perform normally. In order to make the performance of the graphics card play normally, it is necessary to install a driver specially developed by the graphics card manufacturer for the graphics card.

The installation of drivers is also the most troublesome problem when users debug and maintain computers. For example, after reinstalling the system, drivers for graphics cards, sound cards, network cards, video heads, printers, etc. need to be installed. During the driver installation process, It is very cumbersome and inefficient to identify the models of different devices and find the corresponding drivers.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a method and device for driver backup and recovery that overcome the above problems or at least partially solve the above problems.

According to one aspect of the present invention, a method for driver backup is provided, including: obtaining information about drivers in the operating system; The drivers of processor, optical drive and virtual device are used as candidate backup drivers; it is judged whether the device information files corresponding to each candidate backup driver exist, and if they exist, the corresponding device information files and driver files are backed up.

Wherein the information of the driver includes the file name of the device information file, device category, hardware ID, description information and manufacturer information; the information according to each driver will not belong to the system's own and corresponding Devices that are not central processing units, optical drives, or virtual device drivers as candidate backup drivers include: judging whether it belongs to the driver program that comes with the system according to the file name of the device information file corresponding to each driver; For the driver program that comes with the system, judge whether the corresponding device is a central processing unit or an optical drive according to its corresponding device type; for drivers that do not belong to the system and the corresponding device is not a central The device type, hardware ID, description information and manufacturer information to determine whether the corresponding device is a virtual device; the driver that does not belong to the system and the corresponding device is not a central processing unit, optical drive or virtual device is used as a candidate backup driver program.

The driver file is obtained by opening the device information file, obtaining the name of the corresponding driver file, and searching under the system disk directory according to the name of the driver file.

Optionally, if there are at least two device information files corresponding to the candidate backup driver with the same file name, only the device information file and the driver file corresponding to one of the candidate backup drivers are backed up.

Optionally, the backup step includes: according to a preset backup path, storing the device information file and the driver program file to a local disk or server other than the system disk pointed to by the preset backup path.

Optionally, the above method further includes: determining the hardware device in the operating system that needs to restore the driver; according to the hardware device that needs to restore the driver, obtain the corresponding device information file and the driver file from the backup data; Device information files and driver files are loaded into the operating system.

Optionally, the determining the hardware device that needs to restore the driver in the operating system includes: detecting whether there is an unknown device in the operating system, and if it exists, determining the unknown device as a hardware device that needs to restore the driver; or, obtaining A list of hardware devices in the operating system, receiving a user's selection input of one or more hardware devices in the list, and determining the one or more hardware devices as hardware devices that need to restore drivers.

According to another aspect of the present invention, there is also provided a device for driver backup, including: an acquirer configured to acquire driver information in an operating system; a filter configured to A driver that does not belong to the system itself and whose corresponding device is not a central processing unit, an optical drive, or a virtual device is used as a candidate backup driver; the backup device is configured to determine the device information file corresponding to each candidate backup driver Whether it exists, if it exists, back up the corresponding device information file and driver program file.

Wherein the information of the driver includes the file name of the device information file, device category, hardware ID, description information and manufacturer information; the filter includes: a first judging module configured to correspond to each driver according to The file name of the device information file judges whether it belongs to the driver program that comes with the system; the second judging module is configured to judge whether the corresponding device is a central processing device according to the corresponding device type for the driver program that does not belong to the system device or optical drive; the third judging module is configured to judge according to the corresponding device category, hardware ID, description information and manufacturer information for drivers that do not belong to the system and whose corresponding devices are not central processing units and optical drives Whether the corresponding device is a virtual device; the determination module is configured to use a driver that does not belong to the system itself, and the corresponding device is not a central processing unit, an optical drive, or a virtual device as a candidate backup driver.

The driver file is obtained by opening the device information file, obtaining the name of the corresponding driver file, and searching under the system disk directory according to the name of the driver file.

Optionally, if there are at least two device information files corresponding to the candidate backup driver with the same file name, only the device information file and the driver file corresponding to one of the candidate backup drivers are backed up.

Optionally, the backup device is specifically configured to store the device information file and the driver program file to a local disk or server other than the system disk pointed to by the preset backup path according to a preset backup path.

Optionally, the above device further includes: a driver restoration determiner, configured to determine the hardware device whose driver program needs to be restored in the operating system; a driver backup acquirer, configured to restore the driver program to the hardware device according to the need, from the backup Obtain corresponding device information files and driver program files from the data; the driver loader is configured to load the device information files and driver program files into the operating system.

Optionally, the drive recovery determiner includes: a first drive recovery determination module configured to detect whether there is an unknown device in the operating system, and if so, determine the unknown device as a hardware device that needs to restore the driver; And/or, the second drive recovery determination module is configured to obtain a list of hardware devices in the operating system, receive user selection input for one or more hardware devices in the list, and set the one or more hardware devices to Identify hardware devices that require driver recovery.

According to another aspect of the present invention, there is also provided a method for driver recovery, including: determining the hardware device in the operating system that needs to restore the driver program; according to the hardware device that needs to restore the driver program, obtain the corresponding The device information file and the driver program file, wherein the backup data is the backup data of the driver program in the operating system; the device information file and the driver program file are loaded into the operating system.

Optionally, the determining the hardware device that needs to restore the driver in the operating system includes: detecting whether there is an unknown device in the operating system, and if it exists, determining the unknown device as a hardware device that needs to restore the driver; or, obtaining A list of hardware devices in the operating system, receiving a user's selection input of one or more hardware devices in the list, and determining the one or more hardware devices as hardware devices that need to restore drivers.

According to still another aspect of the present invention, there is also provided a device for driver restoration, including: a driver restoration determiner configured to determine a hardware device in an operating system that needs to restore a driver; a driver backup acquirer configured to Describe the hardware device that needs to restore the driver program, and obtain the corresponding device information file and driver program file from the backup data, wherein the backup data is the backup data of the driver program in the operating system; the driver loader is configured to convert the device Information files and driver files are loaded into the operating system.

Optionally, the drive recovery determiner includes: a first drive recovery determination module configured to detect whether there is an unknown device in the operating system, and if so, determine the unknown device as a hardware device that needs to restore the driver; Alternatively, the second drive recovery determination module is configured to obtain a list of hardware devices in the operating system, receive user selection input on one or more hardware devices in the list, and determine the one or more hardware devices as Hardware devices that require driver recovery.

The technical scheme of the present invention can automatically back up the driver programs in the operating system that are not included in the system and whose corresponding devices are not central processing units, CD-ROM drives and virtual devices. On the one hand, it avoids searching for drivers when reinstalling the operating system On the other hand, because only the drivers that must be backed up are backed up, the storage space taken by the backup data is reduced. When reinstalling the operating system, the corresponding driver can be loaded into the operating system according to the backed-up driver data, and it is no longer necessary to identify the models of different devices, and it is not necessary to search for the driver disc. The operation is simple and the time required is relatively short. Short, improve the efficiency of driver installation.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same components. In the attached picture:

Fig. 1 is the method flowchart of the drive backup of an embodiment of the present invention;

Fig. 2 shows a schematic diagram of a drive backup device according to an embodiment of the present invention;

FIG. 3 shows a flowchart of a method for driving recovery according to an embodiment of the present invention;

Fig. 4 shows a schematic diagram of a drive recovery device according to an embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Fig. 1 is the method flowchart of the drive backup of an embodiment of the present invention; As shown in the figure, the method for drive backup comprises:

Step S110: Obtain information about the driver in the operating system.

The operating system here can be a desktop operating system, such as MacOSX, Debian, Ubuntu, LinuxMint, SuseLinux, Fedora and other Unix and Unix-like operating systems, as well as Windows operating systems such as Windows2000, WindowsXP, WindowsVista, Windows7, Windows8; it can also be a server operation System, such as SUNSolaris, IBM-AIX, HP-UX, FreeBSD and other Unix series operating systems, RedHatLinux, CentOS, Debian, Ubuntu and other Linux series operating systems, and WindowsServer2003, WindowsServer2008, WindowsServer2008R2 and other Windows series operating systems; it can also be embedded Operating systems, such as embedded Linux, WindowsCE and other embedded operating systems, as well as Android, iOS, Symbian, WindowsPhone and BlackBerryOS and other operating systems widely used in smart phones and tablet computers. The embodiment of the present invention is described only by taking the Windows operating system as an example, and other operating systems may be executed with reference to the Windows operating system.

Obtaining the information of the driver in the operating system can be achieved by calling the system API (Application Programming Interface, application programming interface) function used to enumerate the device driver. driver, and get the detailed information of each driver, which can include hardware ID, device category, description information, manufacturer information, INF (DeviceINFormationFile, device information file) file name, etc., among which the most important for driver backup The information is the INF file name. The device category is the category to which the hardware device belongs. The general information of the hardware device in the system device manager contains the device category item. The corresponding content of the device category item, such as processor, graphics card, etc., is the device of the hardware device. Category; manufacturer information is the producer information of the hardware device. The general information of the hardware device in the system device manager contains a manufacturer item, and the content corresponding to the manufacturer item is the manufacturer information of the hardware device; hardware ID Refers to the serial number of the hardware device. The hardware ID item is included in the detailed information of the hardware device in the device manager of the system, and the hardware ID of the hardware device can be found under the hardware ID item; the description information refers to the device's status in the system. Name, which is the name of the device as it appears in Device Manager. INF is a file format launched by Microsoft for hardware device manufacturers to release their drivers. The INF file contains hardware device information or scripts to control hardware operations. In the INF file, it is specified how to install the hardware driver into the system, where the source file is, which folder it is installed in, how to add its own related information in the registry, and so on.

Step S120: according to the information of each driver, take the driver that does not belong to the system and whose corresponding device is not a central processing unit, an optical drive, or a virtual device as a candidate backup driver.

Since many drivers in the operating system are self-contained, they already exist when the operating system is installed, and there is no need to back them up. Even if the drivers are lost, they can be restored through system repair. In addition, there are drivers such as virtual CD-ROM software and virtual machine software that may install some virtual devices, and these drivers are built-in by the virtual CD-ROM software and virtual machine software, and do not need to be backed up. If these drivers that do not need to be backed up are backed up, it is meaningless and a waste of storage space.

When implementing this step specifically, to judge whether a driver program belongs to the driver program that comes with the system, it can generally be judged according to the INF file name corresponding to each driver program, for example, the INF file name that generally does not belong to the driver program that comes with the system Start with OEM, therefore, you can judge whether the driver is included with the system by first judging whether the INF file name of the driver starts with OEM. If the INF file name of the driver starts with OEM, you can determine whether the driver The program is not native to the system. However, some drivers that are not included in the system do not need to be backed up. For example, some CPUs (Central Processing Unit, central processing unit) sometimes need to install a third-party driver. The INF file name of the third-party driver also starts with OEM. However, this driver is generally provided by the motherboard's BIOS (BasicInputOutputSystem, basic input and output system), and does not need to be backed up. Since the device type corresponding to the CPU driver is processor (processor), you can set the device type to processor Filter out the driver program to exclude this type of driver program from the backup; on the other hand, since the driver program of the CD-ROM drive is generally built-in by the system, no backup is required, and whether the INF file name starts with OEM is excluded from the backup, but the driver of the virtual CD-ROM is not included in the system, and since the driver of the virtual CD-ROM is included in the virtual CD-ROM software, it does not need to be backed up. Filtering out further excludes the driver of the virtual CD-ROM from the list of backup; in addition, the driver of the virtual device is also included in the virtual device software, and does not need to be backed up, and because the driver of the virtual device can pass its corresponding device category, hardware ID, description information, and manufacturer information to determine whether the corresponding device is a virtual device. The device category, hardware ID, description information, and manufacturer information are associated with each other. When making a specific decision, one or more of the obtained driver's corresponding device category, hardware ID, description information, and manufacturer information can be used. To determine, for example, some manufacturers, such as Vmware, only manufacture virtual devices. If the manufacturer information of the driver obtained through the system API function is Vmware, it can be directly determined that the device corresponding to the driver is a virtual device. In this way, the driver of the virtual device can also be further excluded from the backup.

In addition, some devices in the operating system, such as switchable dual graphics cards or multi-function card readers, are enumerated as multiple devices through the system API function used to enumerate device drivers, but these multiple devices are passed through a Installed by the installer, the corresponding INF file is the same, that is, there are at least two device information files corresponding to the driver with the same file name. In this case, only the device information file and driver file corresponding to one of the drivers Make a backup to avoid backing up multiple copies of the same driver data, further reducing the storage space occupied by the backup data.

Step S130: Determine whether the device information file corresponding to each candidate backup driver exists, and if so, back up the corresponding device information file and driver file.

When implementing this step, you can search whether there is a file with the same file name in the operating system disk directory according to the file name of the device information file corresponding to each candidate backup driver. For the Windows system, in the windows\INF directory If a file with the same file name is found, it means that the device information file corresponding to the candidate backup driver exists.

When backing up candidate backup drivers with device information files, the corresponding driver data (device information files and driver files) can be stored in a local location other than the system disk pointed to by the preset backup path according to the preset backup path disk or server. For example, when storing the driver data to a local disk other than the system disk, assuming that the C disk is the system disk, then you can preset the backup path as: D:\Drivers, and store the driver data of the corresponding driver to this preset Under the backup path, the D disk here can be a fixed disk, or a U disk (USB flash disk, USB flashdisk) for mobile storage, etc. If you choose the local disk to store the driver data, then you cannot choose to format the entire disk when reinstalling the system, otherwise the backup driver data will be lost. For this reason, the drive data can also be stored on the server, so that the choice of full disk formatting can not be limited by the backup path. In addition, corresponding driver data can also be stored in sub-directories. For example, separate backup storage directories can be established for motherboards, graphics cards, sound cards, printers and other devices, so as to find the driver data of each device.

The above-described embodiment judges the information of the acquired driver, excludes the driver that comes with the system and the installed software from the list of backups, and only does not belong to the system, and the corresponding equipment is not a central processing unit or a CD-ROM. The drivers that come with installed software such as virtual devices and virtual devices are used as candidate backup drivers, and then the candidate backup drivers that exist in the device information files are backed up. In this way, since only the drivers that must be backed up are backed up, the backup data is reduced. The storage space occupied, and when reinstalling the operating system, the required driver can be installed according to the backed up driver, avoiding the trouble of identifying different device models and finding the driver when reinstalling the operating system, and the time required Shorter, which improves the efficiency of driver installation.

Compatible with the foregoing method embodiment of drive backup in the present invention, Fig. 2 shows a schematic diagram of a device for drive backup in an embodiment of the present invention, as shown in the figure, the device for drive backup includes:

The acquirer 210 is configured to acquire the information of the driver in the operating system;

The filter 220 is configured to use, according to the information of each driver, a driver that does not belong to the system and whose corresponding device is not a central processing unit, an optical drive, or a virtual device as a candidate backup driver;

The backup device 230 is configured to determine whether a device information file corresponding to each candidate backup driver exists, and if so, back up the corresponding device information file and driver file.

Optionally, the information of the driver includes the file name, device category, hardware ID, description information and manufacturer information of the device information file; the filter includes: a first judging module configured to According to the file name of the device information file corresponding to the driver program, it is judged whether it belongs to the driver program that comes with the system; the second judging module is configured to judge the corresponding device according to the corresponding device type for the driver program that does not belong to the system. Whether it is a central processing unit and an optical drive; the third judging module is configured to, according to its corresponding device category, hardware ID, description information and The manufacturer information determines whether the corresponding device is a virtual device; the determination module is configured to use a driver that does not belong to the system itself, and the corresponding device is not a central processing unit, an optical drive, or a virtual device as a candidate backup driver.

Optionally, the driver file is obtained by opening the device information file, obtaining the name of the corresponding driver file, and searching under the system disk directory according to the name of the driver file.

Optionally, if there are at least two device information files corresponding to the candidate backup driver with the same file name, only the device information file and the driver file corresponding to one of the candidate backup drivers are backed up.

Optionally, the backup device is specifically configured to store the device information file and driver program file to a local disk or server other than the system disk according to a preset backup path.

Optionally, the above-mentioned device for driver backup further includes: a driver recovery determiner configured to determine the hardware device that needs to restore the driver program; Obtain corresponding device information files and driver program files from the data; the driver loader is configured to load the device information files and driver program files into the operating system.

Optionally, the drive recovery determiner includes: a first drive recovery determination module configured to detect whether there is an unknown device in the operating system, and if so, determine the unknown device as a hardware device that needs to restore the driver; And/or, the second drive recovery determination module is configured to obtain a list of hardware devices in the operating system, receive user selection input on one or more hardware devices in the list, and use one of the received user selection inputs One or more hardware devices were identified as hardware devices that require driver recovery.

After the driver program in the operating system is backed up, the driver program can be quickly loaded into the operating system according to the backed up driver data when the operating system is reinstalled.

FIG. 3 shows a flowchart of a method for driving recovery according to an embodiment of the present invention; as shown in the figure, the method for driving recovery includes:

Step S310: Determine the hardware device in the operating system that needs to restore the driver.

When implementing this step, there can be multiple ways to automatically determine the hardware device that needs to restore the driver in the operating system. For example, it can detect whether there is an unknown device in the operating system, and if it exists, then determine the unknown device as requiring recovery. Drivers for hardware devices. For another example, a list of hardware devices in the operating system may also be obtained, wherein the hardware devices in the list may be hardware devices corresponding to the drivers backed up in the aforementioned embodiment of the driver backup method, and a user request for one of the list in the list may be received. or multiple hardware devices, and then determine the received one or more hardware devices selected by the user as the hardware devices that need to restore the driver.

Step S320: Obtain the corresponding device information file and driver program file from the backup data according to the hardware device whose driver program needs to be restored, wherein the backup data is the backup data of the driver program in the operating system.

After step S310 determines the hardware device that needs to restore the driver, it can automatically follow the storage path of the backup data (local disk or server except the system disk) according to the hardware device, such as the name or ID of the hardware device, from the hardware device. Search the backup data under the storage path to obtain the corresponding device information file and driver program file, wherein the backup data here may be the drive data stored in the above-mentioned embodiment of the drive backup method. In addition, when the backup data is stored in sub-directories of motherboards, graphics cards, sound cards, printers and other devices, the corresponding device information files and driver files can also be automatically found from the storage path according to the name of the hardware device that needs to restore the driver. Step S330: Load the device information file and driver program file into the operating system.

Since the device information file specifies how to install the hardware driver into the operating system, where the source file is, which folder it is installed in, how to add its own information in the registry, etc., according to the instructions in the device information file, The driver file can be automatically loaded into the target folder.

Wherein, when receiving the user's selection input on one or more hardware devices in the list, and then determining the one or more hardware devices received by the user's selection input as the hardware device that needs to restore the driver, if described from the user side, Taking the WindowsXP system as an example, the user can restore the driver of the selected hardware device through the following steps:

1. Open the device manager of the operating system, the user can see the list of hardware devices in the operating system;

2. Select the hardware device that needs to restore the driver from the list, click the right mouse button (you can also set it to click the left mouse button), and select "Update Driver" in the menu;

3. In the pop-up dialog box, select "Install from the computer's device driver list or a specified location";

4. In the next dialog box, click the "Have Disk" button;

5. Click the "Browse" button in the pop-up file selection dialog box;

6. In the directory selection dialog box, select the directory where the backup driver is located;

7. Click the "Next" button to proceed with the installation, during which there may be several confirmation dialog boxes that need to be confirmed by the user.

For other operating systems or operating systems of other versions of Windows, the operation steps for restoring the driver of the selected hardware device may be slightly different, and will not be repeated here.

The above-mentioned embodiment can automatically determine or accept the hardware device in the operating system specified by the user that needs to restore the driver, and then quickly find the corresponding device information file and driver file, and automatically install them into the operating system. The operation is simple and the required The time is short, which improves the efficiency of restoring the driver, and avoids the trouble of identifying the models of each hardware device and searching for the corresponding driver CD when restoring the driver.

Compatible with the aforementioned embodiment of the drive recovery method of the present invention, FIG. 4 shows a schematic diagram of a drive recovery device according to an embodiment of the present invention. As shown in the figure, the recovery device includes:

The driver restoration determiner 410 is configured to determine the hardware device in the operating system that needs to restore the driver;

The driver backup obtainer 420 is configured to restore the hardware device of the driver according to the needs, and obtain the corresponding device information file and driver file from the backup data, wherein the backup data is the backup data of the driver in the operating system;

The driver loader 430 is configured to load the device information file and the driver program file into the operating system.

Optionally, the drive recovery determiner includes: a first drive recovery determination module configured to detect whether there is an unknown device in the operating system, and if so, determine the unknown device as a hardware device that needs to restore the driver; Alternatively, the second drive recovery determination module is configured to obtain a list of hardware devices in the operating system, receive user selection input on one or more hardware devices in the list, and use one or more of the received user selection input A hardware device is identified as a hardware device that needs to restore the driver.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings), as well as any method or method so disclosed, may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in the device according to the embodiments of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (14)

1. A method of driving a backup, comprising:

acquiring information of a driver in an operating system;

according to the information of each driver, taking the driver which does not belong to the system and the corresponding equipment is not a central processing unit, an optical drive and virtual equipment as a candidate backup driver, and the method comprises the following steps: judging whether the corresponding equipment is a central processing unit or an optical drive according to the equipment type corresponding to each drive program; judging whether the corresponding equipment is virtual equipment or not according to the equipment type, the hardware ID, the description information or the manufacturer information corresponding to each driver;

and judging whether the equipment information file corresponding to each candidate backup driving program exists, and if so, backing up the corresponding equipment information file and the driving program file.

2. The method of claim 1, wherein the driver's information includes a file name of a device information file, a device class, a hardware ID, description information, and manufacturer information;

the step of taking the driver which does not belong to the system and the corresponding device is not a central processing unit, an optical drive or a virtual device as a candidate backup driver according to the information of each driver comprises:

judging whether the device information files belong to the drivers of the system according to the file names of the device information files corresponding to the drivers;

judging whether the corresponding equipment is a central processing unit or an optical drive according to the corresponding equipment type of the drive program which does not belong to the system;

judging whether the corresponding equipment is virtual equipment or not according to the corresponding equipment type, hardware ID, description information and manufacturer information of the equipment, wherein the equipment does not belong to a system self-contained device and is not a drive program of a central processing unit and an optical drive;

and taking the driver which does not belong to the system self-bring and corresponds to the device and is not the central processor, the optical drive and the virtual device as a candidate backup driver.

3. The method according to claim 1, wherein the driver file is obtained by opening the device information file, obtaining a name of the corresponding driver file, and searching in a system disk directory according to the name of the driver file.

4. The method as claimed in claim 1, if there are at least two backup drivers with the same file name of their corresponding device information files, backing up only the device information file and the driver file corresponding to one of the candidate backup drivers.

5. The method of claim 1, the step of backing up comprising:

and storing the equipment information file and the driver program file to a local disk or a server which is pointed by the preset backup path and is except for the system disk according to the preset backup path.

6. The method of claim 1, further comprising:

determining hardware equipment needing to recover a driver in an operating system;

according to the hardware equipment needing to recover the driver, acquiring a corresponding equipment information file and a corresponding driver file from backup data;

and loading the equipment information file and the driver program file into an operating system.

7. The method of claim 6, the determining a hardware device in the operating system that requires a recovery driver comprising:

detecting whether unknown equipment exists in an operating system, and if so, determining the unknown equipment as hardware equipment needing to recover a driver;

or,

the method comprises the steps of obtaining a list of hardware devices in an operating system, receiving selection input of one or more hardware devices in the list from a user, and determining the one or more hardware devices as the hardware devices needing driver restoration.

8. An apparatus to drive a backup, comprising:

an acquirer configured to acquire information of a driver in an operating system;

the filter is configured to take the drivers which do not belong to the system and correspond to the devices which are not the central processor, the optical drive and the virtual device as candidate backup drivers according to the information of each driver, and comprises the following steps: judging whether the corresponding equipment is a central processing unit or an optical drive according to the equipment type corresponding to each drive program; judging whether the corresponding equipment is virtual equipment or not according to the equipment type, the hardware ID, the description information or the manufacturer information corresponding to each driver;

and the backup device is configured to judge whether the equipment information file corresponding to each candidate backup driving program exists or not, and if so, backup the corresponding equipment information file and the driving program file.

9. The apparatus of claim 8, wherein the information of the driver includes a file name of a device information file, a device class, a hardware ID, description information, and manufacturer information;

the screen includes:

the first judging module is configured to judge whether the device information files belong to the drivers of the system according to the file names of the device information files corresponding to the drivers;

the second judgment module is configured to judge whether the corresponding equipment is a central processing unit or an optical drive according to the corresponding equipment type of the drive program which does not belong to the system;

the third judging module is configured to judge whether the corresponding equipment is virtual equipment or not according to the corresponding equipment type, the hardware ID, the description information and the manufacturer information of the equipment, wherein the equipment does not belong to the system and the corresponding equipment is not a driving program of a central processing unit and an optical drive;

and the determining module is configured to take the drivers which do not belong to the system and correspond to the devices which are not the central processor, the optical drive and the virtual device as candidate backup drivers.

10. The apparatus according to claim 8, wherein the driver file is obtained by opening the device information file, obtaining a name of the corresponding driver file, and searching in a system disk directory according to the name of the driver file.

11. The apparatus of claim 8, wherein if at least two of the candidate backup drivers have the same device information file, only one of the candidate backup drivers is backed up with the device information file and the driver file.

12. The apparatus of claim 8, wherein the backup appliance is configured to store the device information file and the driver file to a local disk or a server other than a system disk pointed by a preset backup path according to the preset backup path.

13. The apparatus of claim 8, further comprising:

a driver recovery determiner configured to determine a hardware device in the operating system that requires recovery of the driver;

the drive backup acquirer is configured to acquire a corresponding device information file and a corresponding driver file from backup data according to the hardware device needing to recover the driver;

a driver loader configured to load the device information file and the driver file into an operating system.

14. The apparatus of claim 13, the drive recovery determiner comprising:

the first drive recovery determining module is configured to detect whether unknown equipment exists in an operating system, and if so, determine the unknown equipment as hardware equipment needing to recover a drive program;

and/or the presence of a gas in the gas,

the second driver recovery determining module is configured to acquire a list of hardware devices in an operating system, receive a selection input of a user on one or more hardware devices in the list, and determine the one or more hardware devices as the hardware devices needing to recover the driver.