US20050125460A1 - [method for resotoring backup data] - Google Patents

[method for resotoring backup data] Download PDF

Info

Publication number
US20050125460A1
US20050125460A1 US10/707,708 US70770804A US2005125460A1 US 20050125460 A1 US20050125460 A1 US 20050125460A1 US 70770804 A US70770804 A US 70770804A US 2005125460 A1 US2005125460 A1 US 2005125460A1
Authority
US
United States
Prior art keywords
data
backup data
restoring
backup
application
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.)
Abandoned
Application number
US10/707,708
Inventor
Lindeng Yu
Zhong-Yang Wang
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.)
Wistron Corp
Original Assignee
Wistron Corp
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 Wistron Corp filed Critical Wistron Corp
Assigned to WISTRON CORPORATION reassignment WISTRON CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WANG, ZHONG-YANG, YU, LINDENG
Publication of US20050125460A1 publication Critical patent/US20050125460A1/en
Priority to US11/755,750 priority Critical patent/US7707190B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1464Management of the backup or restore process for networked environments

Definitions

  • the present invention relates to a method for restoring backup data, and more particularly, to a method for restoring backup data in a mobile device (e.g. PDA).
  • a mobile device e.g. PDA
  • the mobile device such as the Personal Digital Assistant (PDA) and the mobile phone are the electronic apparatus that are made in consider of easy carry.
  • PDA Personal Digital Assistant
  • the data recorded in the electronic apparatus is critical to the users, if the data recorded in the electronic apparatus is damaged due to any accident, it will be a great loss and will bring a significant inconvenience to the users. Therefore, frequently backing up data becomes a routine job for the users using the electronic apparatus.
  • the PDA is gradually accepted by the users.
  • the user can build up customer information, send/receive e-mail, manage calendar, roughly edit/read document, and perform like operation with the help of a Personal Information Manager (PIM).
  • PIM Personal Information Manager
  • the PDA also provides a function similar to the Personal Computer (PC) for allowing user to install various application programs.
  • the PDA can further provide multimedia functions, such as playing MP3 and movies by installing the relevant application programs. Therefore, the important PIM data and the application data generated by various application programs (e.g. Word document files and MP3 music files) are recorded in the PDA.
  • a backup program is commonly installed in the PDA for users to backup the important data.
  • the backup data mentioned above is commonly saved outside the PDA, for example, it is saved in a PC which is connected to the PDA via a link.
  • FIG. 1A is a schematic block diagram illustrating the backing up data between different PDAs.
  • FIG. 1B is a schematic block diagram illustrating a PDA 2 of FIG. 1A after the data had been restored to it using a conventional technique.
  • the data in the PDA 110 is to be backed up and the backup data file 130 is to be obtained, the data of the PDA 110 is restored into the PDA 120 by using the backup data file 130 .
  • the system file/device driver 112 is commonly embedded in a read only memory (ROM) inside the PDA 110 , thus it is not possible to rewrite it, and it will not disappear due to the PDA hardware reset. Therefore, its backup is not required.
  • ROM read only memory
  • the PDA 110 copies its registry 111 , the PIM data 114 , the user-installed application program DLL 113 , and various application programs and its application data 115 into the backup data file 130 .
  • the data in the backup data file 130 is restored, such that the registry 121 a , the PIM data 124 a , the application program DLL 123 a , and various application programs and its application data 125 a are replaced with the registry 121 b , the PIM data 124 b , the application program DLL 123 b , and various application programs and its application data 125 b.
  • the system setup and hardware device drivers among different PDAs are not all the same. Therefore, if the data is just roughly restored (replaced) by using the above method, the system may be crashed due to the difference among the PDA hardware, the system file/device driver, the registry, the application program as well as the difference existed in various application programs.
  • the method detects a correlation between the system to which the data is restored and the system where the data is backed up from previously, then it is determined which backup data can be restored, so as to avoid the system crash problem due to the inconsistency between the restore data and system.
  • the mobile device can execute a self-restore program included in the backup data file and perform the data restore operation without having to install additional restore program.
  • the present invention provides a method for restoring backup data in an electronic system.
  • the method comprises providing a backup data file, and the backup data file includes at least one record of application data.
  • an application program corresponding to the application data is searched within a registry of the electronic system. If it is found, the application data is restored; otherwise, the application data is not restored.
  • the backup data file further comprises a Personal Information Manager (PIM) data
  • the method for restoring backup data further comprises a step of reading and restoring the PIM data to the electronic system.
  • PIM Personal Information Manager
  • the backup data file further comprises an original model data
  • the method for restoring backup data further comprises reading the model data of the electronic system; and comparing the model data with the original model data, if they are matched, all backup data in the backup data file are restored.
  • the present invention further provides a method for restoring backup data in a mobile device.
  • the method comprises providing a backup data file, and the backup data file comprises a self-restore program. Then, the self-restore program is executed in the mobile device to restore data.
  • step of executing the self-restore program and performing the data restore further comprises determining whether the backup data file contains the backup data or not, if it dose not, the execution of the self-restore program is terminated.
  • the backup data file further comprises a PIM data
  • the step of executing the self-restore program and performing the data restore further comprises a step of reading and restoring the PIM data to the mobile device.
  • the backup data file further comprises at least one record of application data.
  • the step of executing the self-restore program and performing the data restore further comprises searching an application program corresponding to the application data within a registry of the mobile device. If it is found, the application data is restored; otherwise, the application data is not restored.
  • the present invention since which backup data can be restored is determined by detecting the target system to which the data is restored before restoring the backup data, the present invention can prohibit the restoring (overwriting) data which is inconsistent with the target system to the target system, and further prevents the system crash problem from happening.
  • the present invention further provides a self-restored backup data file which can restore the backup data without having to install the restore program.
  • FIG. 1A is a schematic block diagram illustrating the backing up data between different PDAS.
  • FIG. 1B is a schematic block diagram illustrating a PDA 2 of FIG. 1A after the data had been restored to it using a conventional technique.
  • FIG. 2 is a flow chart illustrating a method for restoring backup data according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram illustrating an internal data of a PDA 2 in FIG. 1A after the data had been restored to it according to an embodiment of the present invention.
  • FIG. 4 is a flow chart illustrating another method for restoring backup data according to an embodiment of the present invention.
  • FIG. 5 is a structure diagram of a backup data file according to an embodiment of the present invention.
  • the PDA is exemplified for describing the present invention hereinafter.
  • the data/programs saved in the PDA are roughly classified into following categories: the system file/device driver, the registry, the user-installed application program and its related dynamic-link library (DLL), the application data generated by the application program, and the PIM data.
  • the system file/device driver is commonly embedded in a read only memory (ROM) inside the PDA, thus it is not possible to rewrite it, and it will not disappear due to the PDA hardware reset.
  • the registry is a configuration data file of the entire system, and the registry is not suitable for other PDA, thus the registry cannot be just roughly restored/replaced.
  • the application program and its related DLL may be relevant to the system, in order to avoid the system crash; it cannot be just roughly restored/replaced. These files may be restored through the re-installation. Since the application data and the PIM data are the user's specific personal data, and the lose will not be recovered once it is lost/damaged, these are the data most concerned by the user. Therefore, it is required to irregularly backup the application data and the PIM data, such that the recovering of the important data at any time is possible.
  • FIG. 2 is a flow chart illustrating a method for restoring backup data according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram illustrating an internal data of a PDA 2 in FIG. 1A after the data had been restored to it according to an embodiment of the present invention.
  • a backup data file is provided (step S 201 ).
  • the backup data file may be generated by backing up the internal data/file of the same PDA previously, or may be generated by backing up the internal data/file of another PDA.
  • the data of the PDA 120 before the data is restored to it comprises a registry 121 a , a DLL 123 a , a PIM data 124 a , and a plurality of application data 125 a (wherein these application data corresponds to the application program B, C, and D, respectively).
  • step S 202 and S 203 the PDA model data stored in the backup data file 130 is compared with the model of the PDA that performs the restore. If they are matched, the inconsistent problem of the backup data and the system does not exist, and the step S 208 is performed, in which step all backup data in the backup data file 130 are restored to the PDA that performs the restore (for example, a conventional restore method is used in this part of the work).
  • the backup data stored in the backup data file 130 is different from the model of the PDA that performs the restore, in order to avoid the system crash, the backup data cannot be easily restored.
  • the PIM data is restored first (step S 204 ).
  • the backup data of the PDA 110 is restored to another PDA (a PDA 320 ) according to an embodiment of the present invention.
  • the PIM data 324 is replaced with the PIM data of the PDA 110 . Since the model of the PDA 110 is different from the model of the PDA 320 , the registry 321 and the DLL 323 cannot be replaced.
  • the step S 205 is then performed, in which step the application program corresponding to the application data 115 stored in the backup data file 130 is searched within a registry 321 of the PDA 320 . If the application program corresponding to the application data stored in the backup data file 130 is founded in the PDA 320 , the step S 206 is performed to recover the corresponding application data. Otherwise, the application data is not restored (step S 207 ). In the present embodiment, the application program B, C, and D had been installed in the PDA 320 , thus the data corresponding to the application program B, C in the application data 115 stored in the backup data file 130 is restored. It is emphasized that in the present embodiment, the application data corresponding to the application program B, C in the PDA 110 is restored.
  • the original application data in the PDA 320 e.g. the application data 325 a and the application data 325 b shown in the diagram
  • the application data 325 c which is an original application data in the PDA 320 is also reserved in the present embodiment.
  • FIG. 4 is a flow chart illustrating another method for restoring backup data according to an embodiment of the present invention.
  • a backup data file is provided (step S 401 ). Similar to the backup data file 130 in the previous embodiment, the backup data file, for example, comprises a registry, a DLL, a PIM data, and a plurality of application data. Comparing with the backup data file in the previous embodiment, the backup data file in the present embodiment further comprises a self-restore program.
  • the backup data file of the self-restore program is such as a file complying with a Portable Executable (PE) format, and the detail information of the PE file format please referring to the related documents from Microsoft.
  • FIG. 5 is a structure diagram of a backup data file according to an embodiment of the present invention.
  • the backup data file 500 comprises a self-restore program 501 , a backup data file head 502 , a backup document data 503 , a backup document information 504 , a backup database data 505 , a backup database information 506 , a backup registry data 507 , and a backup registry information 508 .
  • the self-restore program 501 in the backup data file is executed (step S 402 ).
  • the backup data file head 502 records how many records of data and the length of each record of the data in the backup data file 500 .
  • step S 403 it is determined whether the backup data is existed in the backup data file 500 by checking the file head 502 . If it is determined that there is no backup data in the backup data file 500 , in step S 404 , the data backup and restore process is terminated. Otherwise, the step S 405 is performed. Since the process of steps S 405 ⁇ S 411 are the same as in the previous embodiment, its detail description is omitted here.
  • the method provided by the present invention can dynamically query the file types supported by the object system (e.g. PDA), recover the supported relevant file and data as well as all PIM data. Therefore, the present invention can avoid the system crash due to the system hardware difference, and successfully restore the important user data back to the system.
  • the object system e.g. PDA
  • the backup data file dose not support the self-restore function, it is required to use a restore program to restore its data.
  • the software of the mobile device is generally installed via a PC, thus once in the case that the mobile device cannot find a PC to install its software and the data has to be immediately restored, the advantages of the present invention is more obvious.
  • the backup data file can be self-restored, it is no need to install the restore program, it makes the data restore more convenient.

Abstract

A method for restoring backup data in an electronic system is provided. The method provides a backup data file, and the backup data file includes at least one record of application data. Then, an application program corresponding to the application data is searched within a registry of the electronic system. If it is found, the application data is restored; otherwise, the application data is not restored. The present invention further provides a method for restoring backup data in a mobile system. The method provides a backup data file, and the backup data file includes a self-restore program. Then, the self-restore program is performed in the mobile device to restore data. Therefore, the present invention can restore data to the mobile device without having to install additional restore program.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application claims the priority benefit of Taiwan application serial no. 92134148, filed Dec. 4, 2003.
  • BACKGROUND OF INVENTION
  • 1. Field of the Invention
  • The present invention relates to a method for restoring backup data, and more particularly, to a method for restoring backup data in a mobile device (e.g. PDA).
  • 2. Description of the Related Art
  • Various electronic apparatus are commonly used in modern life to process our daily activities, such as communication, calendar management, and document preparation. Accompanying with the technology progress, various electronic apparatus are made thinner and smaller for easy carry. The mobile device, such as the Personal Digital Assistant (PDA) and the mobile phone are the electronic apparatus that are made in consider of easy carry. Usually, the data recorded in the electronic apparatus is critical to the users, if the data recorded in the electronic apparatus is damaged due to any accident, it will be a great loss and will bring a significant inconvenience to the users. Therefore, frequently backing up data becomes a routine job for the users using the electronic apparatus.
  • For example, since the characteristic of smaller size and versatile functions, the PDA is gradually accepted by the users. In the PDA, the user can build up customer information, send/receive e-mail, manage calendar, roughly edit/read document, and perform like operation with the help of a Personal Information Manager (PIM). The PDA also provides a function similar to the Personal Computer (PC) for allowing user to install various application programs. The PDA can further provide multimedia functions, such as playing MP3 and movies by installing the relevant application programs. Therefore, the important PIM data and the application data generated by various application programs (e.g. Word document files and MP3 music files) are recorded in the PDA. In order to prevent the data from carelessly damaging, a backup program is commonly installed in the PDA for users to backup the important data. The backup data mentioned above is commonly saved outside the PDA, for example, it is saved in a PC which is connected to the PDA via a link.
  • Analyzing the data/program saved in the PDA, it is found that they can be roughly classified into following categories: the system file/device driver, the registry, the user-installed application program and its related dynamic-link library (DLL), the application data generated by the application program, and the PIM data. The user can restore the backup data to the original PDA at any time with the help of non-regularly backing up the internal data of the PDA. However, it is common that we have to load the backup data of the original PDA into another PDA and restore it therein, for example, in the case of replacing the PDA with a new one. FIG. 1A is a schematic block diagram illustrating the backing up data between different PDAs. FIG. 1B is a schematic block diagram illustrating a PDA 2 of FIG. 1A after the data had been restored to it using a conventional technique. Referring to both FIG. 1A and FIG. 1B, it is assumed that the data in the PDA 110 is to be backed up and the backup data file 130 is to be obtained, the data of the PDA 110 is restored into the PDA 120 by using the backup data file 130. Wherein, the system file/device driver 112 is commonly embedded in a read only memory (ROM) inside the PDA 110, thus it is not possible to rewrite it, and it will not disappear due to the PDA hardware reset. Therefore, its backup is not required.
  • When performing the backup operation, the PDA 110 copies its registry 111, the PIM data 114, the user-installed application program DLL 113, and various application programs and its application data 115 into the backup data file 130. After the backup data file 130 is loaded into the PDA 120, the data in the backup data file 130 is restored, such that the registry 121 a, the PIM data 124 a, the application program DLL 123 a, and various application programs and its application data 125 a are replaced with the registry 121 b, the PIM data 124 b, the application program DLL 123 b, and various application programs and its application data 125 b.
  • The system setup and hardware device drivers among different PDAs are not all the same. Therefore, if the data is just roughly restored (replaced) by using the above method, the system may be crashed due to the difference among the PDA hardware, the system file/device driver, the registry, the application program as well as the difference existed in various application programs.
  • Further, even the system crash problem mentioned above does not exist, for example, in the case of restoring the backup data to the same PDA, in the conventional art, in order to restore the data, it is required to install a backup/restore program which is used in generating the backup data file (it is because all programs are disappeared after the hardware is reset). Therefore, it is very inconvenient to the user.
  • SUMMARY OF INVENTION
  • In the light of the above problems, it is an object of the present invention to provide a method for restoring backup data. The method detects a correlation between the system to which the data is restored and the system where the data is backed up from previously, then it is determined which backup data can be restored, so as to avoid the system crash problem due to the inconsistency between the restore data and system.
  • It is another object of the present invention to provide a method for restoring backup data. With such method, the mobile device can execute a self-restore program included in the backup data file and perform the data restore operation without having to install additional restore program.
  • The present invention provides a method for restoring backup data in an electronic system. The method comprises providing a backup data file, and the backup data file includes at least one record of application data. Then, an application program corresponding to the application data is searched within a registry of the electronic system. If it is found, the application data is restored; otherwise, the application data is not restored.
  • According to a method for restoring backup data described in an embodiment of the present invention, the backup data file further comprises a Personal Information Manager (PIM) data, and the method for restoring backup data further comprises a step of reading and restoring the PIM data to the electronic system.
  • According to a method for restoring backup data described in an embodiment of the present invention, the backup data file further comprises an original model data, and the method for restoring backup data further comprises reading the model data of the electronic system; and comparing the model data with the original model data, if they are matched, all backup data in the backup data file are restored.
  • The present invention further provides a method for restoring backup data in a mobile device. The method comprises providing a backup data file, and the backup data file comprises a self-restore program. Then, the self-restore program is executed in the mobile device to restore data.
  • According to a method for restoring backup data described in an embodiment of the present invention, wherein the step of executing the self-restore program and performing the data restore further comprises determining whether the backup data file contains the backup data or not, if it dose not, the execution of the self-restore program is terminated.
  • According to a method for restoring backup data described in an embodiment of the present invention, the backup data file further comprises a PIM data, and the step of executing the self-restore program and performing the data restore further comprises a step of reading and restoring the PIM data to the mobile device.
  • According to a method for restoring backup data described in an embodiment of the present invention, the backup data file further comprises at least one record of application data. In addition, the step of executing the self-restore program and performing the data restore further comprises searching an application program corresponding to the application data within a registry of the mobile device. If it is found, the application data is restored; otherwise, the application data is not restored.
  • With the present invention, since which backup data can be restored is determined by detecting the target system to which the data is restored before restoring the backup data, the present invention can prohibit the restoring (overwriting) data which is inconsistent with the target system to the target system, and further prevents the system crash problem from happening. In addition, the present invention further provides a self-restored backup data file which can restore the backup data without having to install the restore program.
  • BRIEF DESCRIPTION OF DRAWINGS
  • The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention, and together with the description, serve to explain the principles of the invention.
  • FIG. 1A is a schematic block diagram illustrating the backing up data between different PDAS.
  • FIG. 1B is a schematic block diagram illustrating a PDA 2 of FIG. 1A after the data had been restored to it using a conventional technique.
  • FIG. 2 is a flow chart illustrating a method for restoring backup data according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram illustrating an internal data of a PDA 2 in FIG. 1A after the data had been restored to it according to an embodiment of the present invention.
  • FIG. 4 is a flow chart illustrating another method for restoring backup data according to an embodiment of the present invention.
  • FIG. 5 is a structure diagram of a backup data file according to an embodiment of the present invention.
  • DETAILED DESCRIPTION
  • Since the system setup and hardware device drivers among different electronic systems are not all the same. Therefore, if the data is just roughly restored by using the above method, the system may be crashed due to the existing difference. The PDA is exemplified for describing the present invention hereinafter. However, the present invention is not necessarily limited by it. The data/programs saved in the PDA are roughly classified into following categories: the system file/device driver, the registry, the user-installed application program and its related dynamic-link library (DLL), the application data generated by the application program, and the PIM data. Wherein, the system file/device driver is commonly embedded in a read only memory (ROM) inside the PDA, thus it is not possible to rewrite it, and it will not disappear due to the PDA hardware reset. Therefore, its backup is not required. The registry is a configuration data file of the entire system, and the registry is not suitable for other PDA, thus the registry cannot be just roughly restored/replaced. The application program and its related DLL may be relevant to the system, in order to avoid the system crash; it cannot be just roughly restored/replaced. These files may be restored through the re-installation. Since the application data and the PIM data are the user's specific personal data, and the lose will not be recovered once it is lost/damaged, these are the data most concerned by the user. Therefore, it is required to irregularly backup the application data and the PIM data, such that the recovering of the important data at any time is possible.
  • FIG. 2 is a flow chart illustrating a method for restoring backup data according to an embodiment of the present invention. FIG. 3 is a schematic diagram illustrating an internal data of a PDA 2 in FIG. 1A after the data had been restored to it according to an embodiment of the present invention. Referring to FIG. 1A, FIG. 2, and FIG. 3, at first, a backup data file is provided (step S201). The backup data file may be generated by backing up the internal data/file of the same PDA previously, or may be generated by backing up the internal data/file of another PDA. For example, the PDA 110 in FIG. 1A backs up its internal data, which comprises a registry 111, a DLL 113, a PIM data 114, and a plurality of application data 115 (wherein these application data corresponds to the application program A, B, and C, respectively), and generates a backup data file 130. Meanwhile, the data of the PDA 120 before the data is restored to it comprises a registry 121 a, a DLL 123 a, a PIM data 124 a, and a plurality of application data 125 a (wherein these application data corresponds to the application program B, C, and D, respectively).
  • In step S202 and S203, the PDA model data stored in the backup data file 130 is compared with the model of the PDA that performs the restore. If they are matched, the inconsistent problem of the backup data and the system does not exist, and the step S208 is performed, in which step all backup data in the backup data file 130 are restored to the PDA that performs the restore (for example, a conventional restore method is used in this part of the work).
  • If the PDA model data stored in the backup data file 130 is different from the model of the PDA that performs the restore, in order to avoid the system crash, the backup data cannot be easily restored. In such case, the PIM data is restored first (step S204). As shown in FIG. 3, the backup data of the PDA 110 is restored to another PDA (a PDA 320) according to an embodiment of the present invention. Meanwhile, the PIM data 324 is replaced with the PIM data of the PDA 110. Since the model of the PDA 110 is different from the model of the PDA 320, the registry 321 and the DLL 323 cannot be replaced.
  • The step S205 is then performed, in which step the application program corresponding to the application data 115 stored in the backup data file 130 is searched within a registry 321 of the PDA 320. If the application program corresponding to the application data stored in the backup data file 130 is founded in the PDA 320, the step S206 is performed to recover the corresponding application data. Otherwise, the application data is not restored (step S207). In the present embodiment, the application program B, C, and D had been installed in the PDA 320, thus the data corresponding to the application program B, C in the application data 115 stored in the backup data file 130 is restored. It is emphasized that in the present embodiment, the application data corresponding to the application program B, C in the PDA 110 is restored. However, the original application data in the PDA 320 (e.g. the application data 325 a and the application data 325 b shown in the diagram) is not overwritten. In addition, the application data 325 c, which is an original application data in the PDA 320 is also reserved in the present embodiment.
  • In accordance with an aspect of the present invention, another embodiment is exemplified hereinafter. FIG. 4 is a flow chart illustrating another method for restoring backup data according to an embodiment of the present invention. Referring to FIG. 4, at first, a backup data file is provided (step S401). Similar to the backup data file 130 in the previous embodiment, the backup data file, for example, comprises a registry, a DLL, a PIM data, and a plurality of application data. Comparing with the backup data file in the previous embodiment, the backup data file in the present embodiment further comprises a self-restore program. The backup data file of the self-restore program is such as a file complying with a Portable Executable (PE) format, and the detail information of the PE file format please referring to the related documents from Microsoft. FIG. 5 is a structure diagram of a backup data file according to an embodiment of the present invention. Referring to FIG. 5, the backup data file 500 comprises a self-restore program 501, a backup data file head 502, a backup document data 503, a backup document information 504, a backup database data 505, a backup database information 506, a backup registry data 507, and a backup registry information 508.
  • When it is required to restore the backup data, the self-restore program 501 in the backup data file is executed (step S402). The backup data file head 502 records how many records of data and the length of each record of the data in the backup data file 500. Thus, in step S403, it is determined whether the backup data is existed in the backup data file 500 by checking the file head 502. If it is determined that there is no backup data in the backup data file 500, in step S404, the data backup and restore process is terminated. Otherwise, the step S405 is performed. Since the process of steps S405˜S411 are the same as in the previous embodiment, its detail description is omitted here.
  • In is known from the above embodiments that the method provided by the present invention can dynamically query the file types supported by the object system (e.g. PDA), recover the supported relevant file and data as well as all PIM data. Therefore, the present invention can avoid the system crash due to the system hardware difference, and successfully restore the important user data back to the system.
  • In addition, if the backup data file dose not support the self-restore function, it is required to use a restore program to restore its data. In considering the physical user environment, since the software of the mobile device is generally installed via a PC, thus once in the case that the mobile device cannot find a PC to install its software and the data has to be immediately restored, the advantages of the present invention is more obvious. Moreover, since the backup data file can be self-restored, it is no need to install the restore program, it makes the data restore more convenient.
  • Although the invention has been described with reference to a particular embodiment thereof, it will be apparent to one of the ordinary skill in the art that modifications to the described embodiment may be made without departing from the spirit of the invention. Accordingly, the scope of the invention will be defined by the attached claims not by the above detailed description.

Claims (15)

1. A method suitable for an electronic system for restoring a backup data, comprising:
providing a backup data file comprising at least an application data; and
searching an application program corresponding to the application data within a registry of the electronic system,
if it is found that there is an application program corresponding to the application data, the application data is restored;
if it is found that there is no application program corresponding to the application data, the application data is not restored.
2. The method for restoring the backup data of claim 1, wherein the backup data file further comprises a Personal Information Manager (PIM) data, and the method for restoring the backup data further comprises:
reading and restoring the Personal Information Manager (PIM) data to the electronic system.
3. The method for restoring the backup data of claim 2, wherein the backup data file further comprises an original model data, and the method for restoring the backup data further comprises:
reading an current model data of the electronic system; and
comparing the current model data with the original model data, and if they are matched, all backup data in the backup data file are restored.
4. The method for restoring the backup data of claim 1, wherein the electronic system is a mobile device.
5. The method for restoring the backup data of claim 4, wherein the mobile device is a Personal Digital Assistant (PDA).
6. The method for restoring the backup data of claim 5, wherein the PDA is a Pocket PC.
7. The method for restoring the backup data of claim 4, wherein the mobile device is a Smart Phone.
8. A method used in a mobile device for restoring a backup data, comprising:
providing a backup data file comprising a self-restore program; and
executing the self-restore program and performing the data restore in the mobile device.
9. The method for restoring the backup data of claim 8, wherein the step of executing the self-restore program and performing the data restore comprises:
determining whether the backup data is existed in the backup data file, and if there is no backup data, the executing of the self-restore program is terminated.
10. The method for restoring the backup data of claim 9, wherein the backup data file further comprises an original model data, and the step of executing the self-restore program and performing the data restore further comprises:
reading an current model data of the mobile device; and
comparing the current model data with the original model data, and if they are matched, all backup data in the backup data file are restored.
11. The method for restoring the backup data of claim 10, wherein the backup data file further comprises a Personal Information Manager (PIM) data, and the step of executing the self-restore program and performing the data restore further comprises:
reading and restoring the Personal Information Manager (PIM) data to the mobile device.
12. The method for restoring the backup data of claim 11, wherein the backup data file at least comprises an application data, and the step of executing the self-restore program and performing the data restore further comprises:
searching an application program corresponding to the application data within a registry of the mobile device, if it is found that there is an application program corresponding to the application data, the application data is restored; and
if it is found that there is no application program corresponding to the application data, the application data is not restored.
13. The method for restoring the backup data of claim 8, wherein the mobile device is a Personal Digital Assistant (PDA).
14. The method for restoring the backup data of claim 13, wherein the PDA is a Pocket PC.
15. The method for restoring the backup data of claim 8, wherein the mobile device is a Smart Phone.
US10/707,708 2003-12-04 2004-01-06 [method for resotoring backup data] Abandoned US20050125460A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/755,750 US7707190B2 (en) 2003-12-04 2007-05-31 Method for restoring backup data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
TW92134148 2003-12-04
TW092134148A TWI248579B (en) 2003-12-04 2003-12-04 Method and system for restoring backup data

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/755,750 Division US7707190B2 (en) 2003-12-04 2007-05-31 Method for restoring backup data

Publications (1)

Publication Number Publication Date
US20050125460A1 true US20050125460A1 (en) 2005-06-09

Family

ID=34632301

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/707,708 Abandoned US20050125460A1 (en) 2003-12-04 2004-01-06 [method for resotoring backup data]
US11/755,750 Active 2024-12-15 US7707190B2 (en) 2003-12-04 2007-05-31 Method for restoring backup data

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11/755,750 Active 2024-12-15 US7707190B2 (en) 2003-12-04 2007-05-31 Method for restoring backup data

Country Status (2)

Country Link
US (2) US20050125460A1 (en)
TW (1) TWI248579B (en)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050208967A1 (en) * 2004-03-02 2005-09-22 Spartak Buniatyan Portable universal data storage device
US20070105538A1 (en) * 2005-11-04 2007-05-10 Research In Motion Limited System and method for provisioning a third party mobile device emulator
US20070220498A1 (en) * 2006-03-15 2007-09-20 Madsen Jens O Method, mobile terminal and computer program product for interworking via a card application toolkit
US7478117B1 (en) 2004-12-10 2009-01-13 Symantec Operating Corporation Restoring system state from volume shadow copy service by mounting disks
US7489782B1 (en) * 2004-02-27 2009-02-10 Symantec Operating Corporation Registry restore to original hardware
US7496783B1 (en) 2006-02-09 2009-02-24 Symantec Operating Corporation Merging cluster nodes during a restore
US7769990B1 (en) 2007-03-23 2010-08-03 Symantec Corporation Using a monitoring process to update system configuration settings during restore operations
US7886185B1 (en) 2007-03-23 2011-02-08 Symantec Corporation Creation of a device database and synthesis of device driver information during dissimilar system restore
US7941814B1 (en) 2004-02-26 2011-05-10 Symantec Operating Corporation Device driver processing for automated system restores
US8132186B1 (en) 2007-03-23 2012-03-06 Symantec Corporation Automatic detection of hardware and device drivers during restore operations
US20130283389A1 (en) * 2005-03-09 2013-10-24 Vudu, Inc. Method And System For Distributing Restricted Media To Consumers
EP2613260A3 (en) * 2012-01-09 2014-12-03 LG Electronics, Inc. Mobile terminal and controlling method thereof
US9122711B1 (en) 2012-05-24 2015-09-01 Symantec Corporation Simplified system backup protection and recovery
CN112506714A (en) * 2021-01-12 2021-03-16 博智安全科技股份有限公司 Hot backup method for Windows system and corresponding hot recovery method
US11223537B1 (en) 2016-08-17 2022-01-11 Veritas Technologies Llc Executing custom scripts from the host during disaster recovery

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100606069B1 (en) * 2004-10-25 2006-07-28 삼성전자주식회사 Method for managing database in complex phone for gam/gprs and the complex phone
US20070096685A1 (en) * 2005-10-28 2007-05-03 Q - Dog Ab, Apparatus for charging handheld units
TWI310157B (en) 2006-02-23 2009-05-21 Asustek Comp Inc Method for changing booting source of a computer system and related backuping/restoring method thereof
US20080115071A1 (en) * 2006-10-19 2008-05-15 Fair Thomas T System And Methods For Zero-Configuration Data Backup
US8504526B2 (en) * 2010-06-04 2013-08-06 Commvault Systems, Inc. Failover systems and methods for performing backup operations
US11449394B2 (en) 2010-06-04 2022-09-20 Commvault Systems, Inc. Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources
CN102591727B (en) 2012-01-04 2014-09-17 华为终端有限公司 Method for processing application data and computing node
US9811427B2 (en) 2014-04-02 2017-11-07 Commvault Systems, Inc. Information management by a media agent in the absence of communications with a storage manager
US10747630B2 (en) 2016-09-30 2020-08-18 Commvault Systems, Inc. Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, including operations by a master monitor node
US11200124B2 (en) 2018-12-06 2021-12-14 Commvault Systems, Inc. Assigning backup resources based on failover of partnered data storage servers in a data storage management system
US11099956B1 (en) 2020-03-26 2021-08-24 Commvault Systems, Inc. Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations
US11645175B2 (en) 2021-02-12 2023-05-09 Commvault Systems, Inc. Automatic failover of a storage manager

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6295541B1 (en) * 1997-12-16 2001-09-25 Starfish Software, Inc. System and methods for synchronizing two or more datasets
US6611850B1 (en) * 1997-08-26 2003-08-26 Reliatech Ltd. Method and control apparatus for file backup and restoration
US6651077B1 (en) * 2000-09-27 2003-11-18 Microsoft Corporation Backup and restoration of data in an electronic database
US20030220894A1 (en) * 2002-05-23 2003-11-27 Russon Virgil Kay System and method for preserving metadata in an electronic image file
US20040107199A1 (en) * 2002-08-22 2004-06-03 Mdt Inc. Computer application backup method and system
US20040193953A1 (en) * 2003-02-21 2004-09-30 Sun Microsystems, Inc. Method, system, and program for maintaining application program configuration settings
US6912630B1 (en) * 2001-03-30 2005-06-28 Emc Corporation Method and apparatus for computing file storage elements for backup and restore
US6950836B2 (en) * 2002-03-14 2005-09-27 International Business Machines Corporation Method, system, and program for a transparent file restore
US20060020828A1 (en) * 2003-05-29 2006-01-26 Fujitsu Limited Data restoring method, information processing apparatus, and computer-readable recording medium recording data restoring program
US7024581B1 (en) * 2002-10-09 2006-04-04 Xpoint Technologies, Inc. Data processing recovery system and method spanning multiple operating system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8117162B2 (en) * 2007-03-21 2012-02-14 International Business Machines Corporation Determining which user files to backup in a backup system

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6611850B1 (en) * 1997-08-26 2003-08-26 Reliatech Ltd. Method and control apparatus for file backup and restoration
US6295541B1 (en) * 1997-12-16 2001-09-25 Starfish Software, Inc. System and methods for synchronizing two or more datasets
US6651077B1 (en) * 2000-09-27 2003-11-18 Microsoft Corporation Backup and restoration of data in an electronic database
US6912630B1 (en) * 2001-03-30 2005-06-28 Emc Corporation Method and apparatus for computing file storage elements for backup and restore
US6950836B2 (en) * 2002-03-14 2005-09-27 International Business Machines Corporation Method, system, and program for a transparent file restore
US20030220894A1 (en) * 2002-05-23 2003-11-27 Russon Virgil Kay System and method for preserving metadata in an electronic image file
US20040107199A1 (en) * 2002-08-22 2004-06-03 Mdt Inc. Computer application backup method and system
US7024581B1 (en) * 2002-10-09 2006-04-04 Xpoint Technologies, Inc. Data processing recovery system and method spanning multiple operating system
US20040193953A1 (en) * 2003-02-21 2004-09-30 Sun Microsystems, Inc. Method, system, and program for maintaining application program configuration settings
US20060020828A1 (en) * 2003-05-29 2006-01-26 Fujitsu Limited Data restoring method, information processing apparatus, and computer-readable recording medium recording data restoring program

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7941814B1 (en) 2004-02-26 2011-05-10 Symantec Operating Corporation Device driver processing for automated system restores
US7489782B1 (en) * 2004-02-27 2009-02-10 Symantec Operating Corporation Registry restore to original hardware
US20050208967A1 (en) * 2004-03-02 2005-09-22 Spartak Buniatyan Portable universal data storage device
US7349719B2 (en) * 2004-03-02 2008-03-25 Spartak Buniatyan Portable universal data storage device
US7478117B1 (en) 2004-12-10 2009-01-13 Symantec Operating Corporation Restoring system state from volume shadow copy service by mounting disks
US20130283389A1 (en) * 2005-03-09 2013-10-24 Vudu, Inc. Method And System For Distributing Restricted Media To Consumers
US9674190B2 (en) * 2005-03-09 2017-06-06 Vudu, Inc. Method and system for distributing restricted media to consumers
US20080288237A1 (en) * 2005-11-04 2008-11-20 Research In Motion Limited System and method for provisioning a third party mobile device emulator
US7613453B2 (en) * 2005-11-04 2009-11-03 Research In Motion Limited System and method for provisioning a third party mobile device emulator
US20070105538A1 (en) * 2005-11-04 2007-05-10 Research In Motion Limited System and method for provisioning a third party mobile device emulator
US8126446B2 (en) 2005-11-04 2012-02-28 Research In Motion Limited System and method for provisioning a third party mobile device emulator
US8688098B2 (en) 2005-11-04 2014-04-01 Blackberry Limited System and method for provisioning a third party mobile device emulator
US7496783B1 (en) 2006-02-09 2009-02-24 Symantec Operating Corporation Merging cluster nodes during a restore
US20070220498A1 (en) * 2006-03-15 2007-09-20 Madsen Jens O Method, mobile terminal and computer program product for interworking via a card application toolkit
WO2007105051A2 (en) * 2006-03-15 2007-09-20 Nokia Corporation Method, mobile terminal and computer program product for interworking via a card application toolkit
WO2007105051A3 (en) * 2006-03-15 2007-11-15 Nokia Corp Method, mobile terminal and computer program product for interworking via a card application toolkit
US7886185B1 (en) 2007-03-23 2011-02-08 Symantec Corporation Creation of a device database and synthesis of device driver information during dissimilar system restore
US8132186B1 (en) 2007-03-23 2012-03-06 Symantec Corporation Automatic detection of hardware and device drivers during restore operations
US7769990B1 (en) 2007-03-23 2010-08-03 Symantec Corporation Using a monitoring process to update system configuration settings during restore operations
EP2613260A3 (en) * 2012-01-09 2014-12-03 LG Electronics, Inc. Mobile terminal and controlling method thereof
US9037906B2 (en) 2012-01-09 2015-05-19 Lg Electronics Inc. Mobile terminal and controlling method thereof
US9122711B1 (en) 2012-05-24 2015-09-01 Symantec Corporation Simplified system backup protection and recovery
US11223537B1 (en) 2016-08-17 2022-01-11 Veritas Technologies Llc Executing custom scripts from the host during disaster recovery
CN112506714A (en) * 2021-01-12 2021-03-16 博智安全科技股份有限公司 Hot backup method for Windows system and corresponding hot recovery method

Also Published As

Publication number Publication date
TW200519729A (en) 2005-06-16
US20070226278A1 (en) 2007-09-27
US7707190B2 (en) 2010-04-27
TWI248579B (en) 2006-02-01

Similar Documents

Publication Publication Date Title
US7707190B2 (en) Method for restoring backup data
EP2065806B1 (en) System and method for using a file system to automatically backup a file as a generational file
US20040193953A1 (en) Method, system, and program for maintaining application program configuration settings
EP1213937B1 (en) Method for backup and restore for JAVA applications of a portable cellular phone.
US8468136B2 (en) Efficient data backup
JP4901095B2 (en) Fail-safe way to apply custom software image updates to non-volatile storage
US6223345B1 (en) System and method for building client and server application packages
US7831821B2 (en) System backup and recovery solution based on BIOS
US20040172578A1 (en) Method and system of operating system recovery
US5960460A (en) Non-intrusive replication of hard disk
US20070250673A1 (en) Computer backup system
US6714951B2 (en) Continuous journaling of objects within a hierarchical directory tree
US20050289382A1 (en) System and method for recovering a device state
GB2434667A (en) Maintaining System Management BIOS in a computer system
US20050165871A1 (en) Method and apparatus for recycling application processes
CN101196839A (en) Data renovation and synchronization process of double-flash read-only memory
US6823348B2 (en) File manager for storing several versions of a file
US20030037279A1 (en) HDD data backup and recovery method
US20110125963A1 (en) Electronic device with data backup/restore capability
EP3343395B1 (en) Data storage method and apparatus for mobile terminal
US20090089301A1 (en) Method and System for Efficiently Managing Content on an Information Handling Device
JP6999044B2 (en) LAN booting environment infrastructure A device for file security and centralization, a computer-readable recording medium on which a method for this and a program for performing this method are recorded.
US20080282240A1 (en) Backup method for portable terminal apparatus
CN111563006B (en) Data processing method, intelligent terminal and storage medium
CN115729750A (en) Method capable of integrating third-party software into recovery environment

Legal Events

Date Code Title Description
AS Assignment

Owner name: WISTRON CORPORATION, TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YU, LINDENG;WANG, ZHONG-YANG;REEL/FRAME:014233/0188

Effective date: 20031210

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION