Restoration of an image backup using information on other information handling systems

Information

  • Patent Grant
  • 8707087
  • Patent Number
    8,707,087
  • Date Filed
    Tuesday, May 18, 2010
    14 years ago
  • Date Issued
    Tuesday, April 22, 2014
    10 years ago
Abstract
A backup and restoration process which first attempts to recover information blocks from locally connected information handling systems executing a backup/restore service before looking to the slower access cloud store to recover data blocks.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates to information handling systems and more particularly to restoration of an image backup using information from other information handling systems.


2. Description of the Related Art


As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.


It is known to provide information handling system environments with cloud storage. Cloud storage refers to a dataspace, often stored within server farms based in remote locations which may be accessed via the Internet, that functions as storage (e.g., for backing up) information from information handling systems. This dataspace is often leased by an organization to provide for information backup off site in case of disaster (fire, theft, etc). Access speed may be limited due to the average bandwidth of the Internet connection. Techniques have been developed, such as allowing bytes to relatively slowly be transferred (i.e., to drizzle) to the dataspace, to address the bandwidth issues.


These backups are increasingly likely to include images of the client information handling systems, which can be used to restore an information handling system to a fully bootable and functional state quickly. Backup images of a system can comprise the operating system, device drivers, installed applications, user preferences, user data, etc. Backing up the entire information handling system is desirable to facilitate a full restoration of a ‘crashed’ information handling system. An entire backup is also desirable so that a user can have peace of mind that everything on the information handling system is backed up. Thus, when and if the reinstallation of the backed up information is desired, the user does not have to rebuild the operating system, drivers, applications and data. The user may revert the information handling system back to a point in time when it was working The price of online storage is quickly decreasing to make the required storage affordable.


Restoring a complete information handling system image from an Internet based backup can be a very long process. Once the information handling system boots to a CD or other media, the information handling system can begin the process of pulling down bits from the dataspace. This process can potentially take many days on an average server message block (SMB) type connection. Failure of the link during the retrieval process often aborts the restore operation.


SUMMARY OF THE INVENTION

In accordance with the present invention, a restoration process is set forth which first attempts to recover information blocks from locally connected information handling system executing a backup/restore service before looking to the slower access cloud store to recover information blocks.


More specifically, in one embodiment, the invention relates to a method for allowing restoration of information to an information handling system using information from other information handling systems. The method includes storing information from all information handling systems on a network to an off site datastore; creating a common database, the common database cataloging information stored to the off site datastore; storing the common database of the cataloged information to the off site datastore; creating individual respective catalogs of information stored to the off site datastore for respective information handling systems on the network; storing in a database identities of all information handling systems in the network; determining whether a restoration is desirable; and, when a restoration is desirable, booting an information handling system to be restored to restoration media; obtaining, via the information handling system to be restored, access to the database describing identities of information handling systems in the network; recovering information for restoration from other functioning information handling system on the network as possible; determining whether there is any additional information to be restored that is not available from the functioning information handling systems; and, if there is any additional information to be restored, then obtaining the additional information from the off site datastore.


In another embodiment, the invention relates to a method for performing a backup operation, the backup operation enabling restoration of information to an information handling system using information from other information handling systems comprising: storing information from all information handling systems on a network to an off site datastore; creating a common database, the common database cataloging information stored to the off site datastore; storing the common database of the cataloged information to the off site datastore; creating individual respective catalogs of information stored to the off site datastore for respective information handling systems on the network; and, storing in a database identities of all information handling systems in the network.


In another embodiment, the invention relates to a method for performing a restoration of information to an information handling system using information from other information handling systems on a network comprising: booting an information handling system to be restored to restoration media; obtaining, via the information handling system to be restored, access to a database describing identities of information handling systems in the network; recovering information for restoration from other functioning information handling system on the network as possible; determining whether there is any additional information to be restored that is not available from the functioning information handling systems; and, if there is any additional information to be restored, then obtaining the additional information from an off site datastore.





BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.



FIG. 1 shows a system block diagram of an information handling system.



FIG. 2 shows a block diagram of an information handling system environment having a system for allowing restoration of an image backup using information from other information handling systems.



FIG. 3 shows a flow chart of the operation of a system for allowing restoration of an image backup using information from other information handling systems.



FIG. 4 shows a flow chart of the operation of a system for performing a restoration of an image backup using information from other information handling systems.





DETAILED DESCRIPTION

Referring briefly to FIG. 1, a system block diagram of an information handling system 100 is shown. The information handling system 100 includes a processor 102, input/output (I/O) devices 104, such as a display, a keyboard, a mouse, and associated controllers (each of which may be coupled remotely to the information handling system 100), a memory 106 including volatile memory such as random access memory (RAM) and non-volatile memory such as a hard disk and drive, and other storage devices 108, such as an optical disk and drive and other memory devices, and various other subsystems 110, all interconnected via one or more buses 112.


The information handling system 100 further includes a restoration system 130 stored on the memory 106 and having instructions which are executable by the processor 102. The restoration system 130 performs a restoration process which first attempts to recover information blocks from locally connected storage machines executing a backup/restore service before looking to any slower access cloud store to recover the information blocks.


For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.


Referring to FIG. 2, a block diagram of an information handling system environment having a system for allowing restoration of an image backup using information from other information handling systems is shown. More specifically, the information handling system environment includes a client information handling system 210 to be restored as well as additional networked information handling systems 212 which are still functioning properly. The environment 200 further includes an offsite datastore 220 (e.g., a cloud backup) which stores individual respective catalogs 221 of information for respective information handling system.


In a typical office or home network, vast amounts of information in a server message block (SMB) environment is common to many (or all) information handling systems in the environment. The operating system, drivers, productivity applications (such as the Office application suite available from Microsoft, Inc.) and other applications are normally present on several machines which are still operating on the network of the environment. If those information handling systems have already been cataloged during backup (e.g., via a block level hashing process (common to a de-duplication process)) and that backup database contains information of all the information handling systems that are backed up while maintaining the relationship of each information block to the machine from which it was copied along with the unique identifier for the contents of that information block (a desirable feature for de-duplication) then the restore process does not have to retrieve information from the cloud if that same information could be retrieved from the local network from a still operating information handling system. Thus, the environment allows for peer to peer awareness of information which is available on all of the information handling systems on the network. In certain embodiments, this peer to peer awareness is performed by allowing access to respective catalogs of individual information handling systems by other information handling systems on the network.


Referring to FIG. 3, a flow chart of the operation of a system 300 for performing an image backup is shown. More specifically, during the backup process all information handling systems are backed up to the off site datastore (e.g., to the cloud) at step 310. This off site backup is necessary in case of a local disaster where all local copies are destroyed or somehow damaged. Next, at step 320, a backup client on each information handling system updates or creates a database in the cloud with an identifier of the local information handling system from which the information originated, a unique hash created identifier that describes the unique content, the physical location of the information on the information handling machine and the actual information (file or block). Next, at step 330, a local copy of the updates specific to the local information handling system may also be kept local to the information handling system for rapid retrieval. This local copy does not contain another copy of the actual information since that information resides on the information handling system already in its usable form.


Referring to FIG. 4, a flow chart of the operation of a system 400 for performing a restoration of an image backup using information from other information handling systems is shown. More specifically, should a restoration become desirable (e.g., due to a system crash or a virus infestation), as determined by step 440, the information handling system to be recovered is booted to restoration media (CD, USB, etc) and connected to the local and wide area networks at step 445. Next, at step 450, the information handling system obtains access to the cloud database describing the disk cluster hashes required to restore itself. Other information handling systems on the local network may also have their own databases created during the backup process for enhanced rapid access. Next, at step 460, the information handling system requests the specific content disk blocks by their unique describing hash identifier pointer from other functioning information handling systems indicated to contain that block of information. The recovering information handling system recovers those blocks as required to rebuild its memory to the same state it was during the last backup process. Next at step 465 the blocks are verified during the recover process to continue to provide a valid has code in case the hash codes was altered since the database was created. Next, at step 470, the restoration process determines whether any additional information has not been recovered from the local information handling systems. If there is any additional information , then the restoration process obtains this additional information from the off site datastore at step 480.


By this method, cloud restoration without a local network attached storage (NAS) or appliance could be accomplished very rapidly in a business or home environment. Only information handling system specific information need be recovered at the slower internet access rate. The present invention provides an advantage of enabling offsite protection along with rapid restoration of all information (in almost all cases not involving site disaster). The rapid restoration is accessible via a trivial user interface.


The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.


Also for example, the above-discussed embodiments include software modules that perform certain tasks. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage medium such as a disk drive. Storage devices used for storing software modules in accordance with an embodiment of the invention may be magnetic floppy disks, hard disks, or optical discs such as CD-ROMs or CD-Rs, for example. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention may also include a semiconductor-based memory, which may be permanently, removably, or remotely coupled to a microprocessor/memory system. Thus, the modules may be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein. Additionally, those skilled in the art will recognize that the separation of functionality into modules is for illustrative purposes. Alternative embodiments may merge the functionality of multiple modules into a single module or may impose an alternate decomposition of functionality of modules. For example, a software module for calling sub-modules may be decomposed so that each sub-module performs its function and passes control directly to another sub-module.


Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.

Claims
  • 1. A method for allowing restoration of information to an information handling system using information from other information handling systems comprising: storing information from all information handling systems on a network to an off site datastore;creating a common database, the common database cataloging information stored to the off site datastore;storing the common database of the cataloged information to the off site datastore;creating individual respective catalogs of information stored to the off site datastore for respective information handling systems on the network;allowing access to respective catalogs of individual information handling systems by other information handling systems on the network so as to allow peer to peer awareness of information which is available on all of the information handling systems on the network;storing in a database identities of all information handling systems in the network;determining whether a restoration is desirable; and, when a restoration is desirable,booting an information handling system to be restored to restoration media;obtaining, via the information handling system to be restored, access to the database describing identities of information handling systems in the network;recovering information for restoration from other functioning information handling system on the network as possible;determining whether there is any additional information to be restored that is not available from the functioning information handling systems; and,if there is any additional information to be restored, then obtaining the additional information from the off site datastore.
  • 2. The method of claim 1 wherein: the restoration uses a server application where the server application enables local storage of the information and the common database.
  • 3. The method of claim 1 wherein: the storing information from all information handling systems on a network to an off site datastore performs an equivalency operation of information to be stored to the off site datastore and stores single copies of equivalent information to the off site datatore.
  • 4. The method of claim 3 wherein: the equivalency operation identifies cluster hashes of information blocks to be stored to the off site datastore.
  • 5. The method of claim 1 wherein: the restoration media comprises at least one of a compact disk (CD), a digital video disk (DVD) and a universal serial bus (USB) memory device.
  • 6. The method of claim 1 wherein: other information handling systems on the network also comprise respective caches of their respective databases for enhanced rapid access.
  • 7. The method of claim 1 wherein: the recovering information for restoration from other functioning information handling systems on the network performs a cluster operation to determine whether the functioning information handling system have a byte for byte equivalent of the information to be restored.
  • 8. The method of claim 1 wherein: the recovering information for restoration from other functioning information handling systems on the network performs a cluster operation to determine whether the functioning information handling system have a byte for byte equivalent of the information to be restored.
  • 9. A method for performing a backup operation, the backup operation enabling restoration of information to an information handling system using information from other information handling systems comprising: storing information from all information handling systems on a network to an off site datastore;creating a common database, the common database cataloging information stored to the off site datastore;storing the common database of the cataloged information to the off site datastore;creating individual respective catalogs of information stored to the off site datastore for respective information handling systems on the network;storing in a database identities of all information handling systems in the network; and,allowing access to respective catalogs of individual information handling systems by other information handling systems on the network so as to allow peer to peer awareness of information which is available on all of the information handling systems on the network.
  • 10. The method of claim 9 wherein: the backup operation uses a server application where the server application enables local storage of the information and the common database.
  • 11. The method of claim 9 wherein: the storing information from all information handling systems on a network to an off site datastore performs an equivalency operation of information to be stored to the off site datastore and stores single copies of equivalent information to the off site datatore.
  • 12. The method of claim 11 wherein: the equivalency operation identifies cluster hashes of information blocks to be stored to the off site datastore.
  • 13. A method for performing a restoration of information to an information handling system using information from other information handling systems on a network comprising: booting an information handling system to be restored to restoration media;obtaining, via the information handling system to be restored, access to a database describing identities of information handling systems in the network;recovering information for restoration from other functioning information handling system on the network as possible;allowing access to respective catalogs of individual information handling systems by other information handling systems on the network so as to allow peer to peer awareness of information which is available on all of the information handling systems on the network;determining whether there is any additional information to be restored that is not available from the functioning information handling systems; and,if there is any additional information to be restored, then obtaining the additional information from an off site datastore, the off site datastore storing individual respective catalogs on information for respective information handling systems on the network.
  • 14. The method of claim 13 wherein: the restoration media comprises at least one of a compact disk (CD), a digital video disk (DVD) and a universal serial bus (USB) memory device.
  • 15. The method of claim 13 wherein: other information handling systems on the network also comprise respective caches of respective databases for enhanced rapid access.
US Referenced Citations (112)
Number Name Date Kind
5490216 Richardson, III Feb 1996 A
5659614 Bailey, III Aug 1997 A
5715314 Payne et al. Feb 1998 A
5864664 Capps, Jr. et al. Jan 1999 A
5948078 Joffe Sep 1999 A
6032859 Muehlberger et al. Mar 2000 A
6170059 Pruett et al. Jan 2001 B1
6209089 Selitrennikoff et al. Mar 2001 B1
6292941 Jollands Sep 2001 B1
6301612 Selitrennikoff et al. Oct 2001 B1
6314418 Namba Nov 2001 B1
6321262 Springer Nov 2001 B1
6324525 Kramer et al. Nov 2001 B1
6389403 Dorak, Jr. May 2002 B1
6425126 Branson et al. Jul 2002 B1
6502205 Yanai et al. Dec 2002 B1
6647532 Boede et al. Nov 2003 B1
6865655 Andersen Mar 2005 B1
6931558 Jeffe et al. Aug 2005 B1
7047411 DeMello et al. May 2006 B1
7120593 Fry et al. Oct 2006 B1
7330997 Odom Feb 2008 B1
7352999 Miettinen Apr 2008 B2
7412534 Tsang et al. Aug 2008 B2
7417546 Llorca et al. Aug 2008 B2
7428413 Fink Sep 2008 B2
7483860 Cronce et al. Jan 2009 B2
7496739 Raghavan et al. Feb 2009 B1
7503072 Hughes et al. Mar 2009 B2
7506382 Padole et al. Mar 2009 B2
7516104 Scardino Apr 2009 B1
7523072 Stefik et al. Apr 2009 B2
7526451 Park et al. Apr 2009 B2
7555447 Chinnappan et al. Jun 2009 B2
7565325 Lenard et al. Jul 2009 B2
7593898 Tsuei et al. Sep 2009 B1
7783737 Fujino et al. Aug 2010 B2
7971199 Chen Jun 2011 B1
8219769 Wilk Jul 2012 B1
8219850 Wang et al. Jul 2012 B1
8341455 Maki et al. Dec 2012 B2
8452731 Preslan et al. May 2013 B2
8533156 Ryder Sep 2013 B2
20020046232 Adams et al. Apr 2002 A1
20020059270 Schlabach et al. May 2002 A1
20020076204 Nakano et al. Jun 2002 A1
20020077986 Kobata et al. Jun 2002 A1
20020088855 Hodes Jul 2002 A1
20030028439 Cox Feb 2003 A1
20030028451 Ananian Feb 2003 A1
20030033205 Nowers et al. Feb 2003 A1
20030060157 Henrick Mar 2003 A1
20030088571 Ekkel May 2003 A1
20030110126 Dunkeld et al. Jun 2003 A1
20030120928 Cato et al. Jun 2003 A1
20030149750 Franzenburg Aug 2003 A1
20040003039 Humphrey et al. Jan 2004 A1
20040022227 Lynch et al. Feb 2004 A1
20040059938 Hughes et al. Mar 2004 A1
20040093273 Laurent et al. May 2004 A1
20040128551 Walker et al. Jul 2004 A1
20040143746 Ligeti et al. Jul 2004 A1
20050027657 Leontiev et al. Feb 2005 A1
20050060388 Tatsumi et al. Mar 2005 A1
20050229047 Hanes et al. Oct 2005 A1
20050262573 Bo et al. Nov 2005 A1
20050268115 Barde et al. Dec 2005 A1
20060062426 Levy et al. Mar 2006 A1
20060161635 Lamkin et al. Jul 2006 A1
20060229904 Hunter et al. Oct 2006 A1
20060276174 Katz et al. Dec 2006 A1
20070124349 Taylor May 2007 A1
20070130233 Christensen Jun 2007 A1
20070157196 Goicea et al. Jul 2007 A1
20070174621 Ducharme Jul 2007 A1
20070233580 Pike et al. Oct 2007 A1
20070255758 Zheng et al. Nov 2007 A1
20070294566 Solyanik Dec 2007 A1
20080172583 Mahajan et al. Jul 2008 A1
20080177807 Dile et al. Jul 2008 A1
20080195871 Peinado et al. Aug 2008 A1
20080208933 Lyon Aug 2008 A1
20080215633 Dunkeld et al. Sep 2008 A1
20090083843 Wilkinson et al. Mar 2009 A1
20090089340 Ohr et al. Apr 2009 A1
20090125393 Hwang et al. May 2009 A1
20090164470 Savage et al. Jun 2009 A1
20090187491 Bull et al. Jul 2009 A1
20090193102 Trujillo Jul 2009 A1
20090228368 Brown Sep 2009 A1
20090228488 Brand et al. Sep 2009 A1
20090234892 Anglin et al. Sep 2009 A1
20090248883 Suryanarayana et al. Oct 2009 A1
20090265545 Satoh et al. Oct 2009 A1
20100106687 Marcy et al. Apr 2010 A1
20100106691 Preslan et al. Apr 2010 A1
20100122030 Peters et al. May 2010 A1
20100174918 Hoffman et al. Jul 2010 A1
20100235921 Foster Sep 2010 A1
20100257142 Murphy et al. Oct 2010 A1
20100257185 Dvir et al. Oct 2010 A1
20100257346 Sosnosky et al. Oct 2010 A1
20100257403 Virk et al. Oct 2010 A1
20100306227 Fleming et al. Dec 2010 A1
20100306267 Zamkoff et al. Dec 2010 A1
20100325735 Etchegoyen Dec 2010 A1
20110016466 Liu et al. Jan 2011 A1
20110022812 van Der Linden et al. Jan 2011 A1
20110072291 Murase Mar 2011 A1
20110099200 Blount et al. Apr 2011 A1
20110173405 Grabarnik et al. Jul 2011 A1
20110184998 Palahnuk et al. Jul 2011 A1
Non-Patent Literature Citations (12)
Entry
Backup P2P Secured peer to peer backup, http://www.ohloh.net/p/p2pbackupsmile, printed Jun. 18, 2010.
Landers et al., PeerStore: Better Performance by Relaxing in Peer-to-Peer Backup, Fakultät Für Informatik , Technische Universitat München, 2004 http://www.computer.org/portal/web/csdl/doi/10.1109/PTP.2004.1334933.
Peer-to-Peer Viral Backup: Cucku 2.0 Definitely Scores Points for Imagination, http://www.fileslinger.com/2009/05/peer-to-peer-viral-backup-cucku-20-definitely-scores-points-forimagination, printed Jun. 18, 2010.
T. Bonkenburg et al, LifeBoat—An Autonomic Backup and Restore Solution, http://www.usenix.org/event/lisa04/tech/full—papers/bonkenburg/bonkenburg.pdf, 2004 LISA XVIII—Nov. 14-19, 2004—Atlanta, GA.
M. Vrable, Cumulus: Filesystem Backup to the Cloud, http://cseweb.ucsd.edu/˜voelker/pubs/cumulus-fast09.pdf, Feb. 26, 2009.
L. Mearian, Start-up unveils hybrid cloud/on-site backup service, http://www.itworld.com/storage/64972/start-unveils-hybrid-cloudon-site-backup-service, Mar. 24, 2009.
Storage-Switzerland.com, Hybrid Cloud Backup for the SMB, http://www.storage-switzerland.com/Articles/Entries/2009/4/24—Hybrid—Cloud—Backup—for—the—SMB.html, Apr. 24, 2009.
M. Staimer, Asigra, Why Cloud Backup/Recovery (Private, Public, or Hybrid) WILL be Your Data Protection, http://www.docstoc.com/docs/16851799/Why-Cloud-Backup-Recovery-(Private-Public-or-Hybrid)-WILL-be, printed Jun. 18, 2010.
LAPLINK, Laplink Offers Licensing for Windows XP to Windows 7 Upgrade Solution, Oct. 28, 2009.
PROQUEST, Sprint and MercuryMD Team up to Offer Healthcare Providers One-Stop Shopping Opportunity for Mobility Solutions, PR Newswire, New York, Apr. 27, 2004.
Michigan Retailers Association, Member Services, Electronic Gift Card Processing FAQ, http://www.retailers.com/memberservices/giftcardsfaq.html, printed Apr. 19, 2010.
CISCO License Manager 2.2, http://www.cisco.com/en/US/products/ps7138/index.html, printed Jun. 15, 2010.
Related Publications (1)
Number Date Country
20110289350 A1 Nov 2011 US