IP Library Granted Patent US 7,216,251
Granted Patent B2
US 7,216,251 · App. 10/449,728 · Granted May 8, 2007

Computer imaging recovery without a working partition or a secondary medium

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,216,251
App. No.
10/449,728
Granted
May 8, 2007
Kind
B2
Abstract

An initial setup method ( 100 ) stores recovery tools ( 400 ) and a further setup script ( 402 ) on a computer ( 1000 ) which has an operating system ( 302 ) that need not have any recovery capabilities. At the user site, a further setup method ( 700, 800 ) reserves ( 706 ) a container space ( 500 ) in the file system space ( 304 ), creates ( 716 ) an image ( 1008 ) of the main partition ( 300 ), and stores ( 720 ) the image in the container. If the partition is corrupted later, the computer can still be booted using virtual boot tools ( 602 ), the image can be retrieved ( 914 ) from the container even though the partition around it was lost, and the image can then be deployed onto disk ( 200 ) over the corrupted partition, thereby restoring a working partition to the computer. This can be done without secondary media such as a recovery CD or floppy, and without a network connection.

Claims (38)

1. An initial setup method for a purpose such as facilitating recovery from corruption or other loss of data stored on a computer disk attached to a computer, the method comprising:

storing on the disk recovery tools which comprise virtual booting code and imaging code, the virtual booting code being capable of booting the computer attached to the disk without requiring any changes to BIOS or disk firmware from an image that was stored on the disk even if the disk has no working, hidden or other partitions at the time the virtual booting code runs, and the imaging code being capable of creating an image of a main working partition on the disk without using a second partition of any kind, storing that image in a container in the main working partition on the disk, and deploying that image back over the main partition's location onto the disk outside the container; and

storing on the disk a further setup script which when executed will cause the computer to perform steps that comprise: selecting and reserving space from anywhere on the disk in the main working partition for the container; recording on the disk a physical address for identifying the location of the container space;

creating the image of the main working partition excluding the container space; and storing the image in the container.

2. The method of claim 1 , further comprising and followed by the step of creating a master image from the computer, the master image containing the recovery tools and the further setup script.

3. A computer system comprising a processor, RAM operably connected to the processor for executing code and a disk accessible to the processor, wherein the disk is configured by tools and a further setup script; a main partition of the disk is non-working and there are no hidden or other partitions on the disk; the tools comprise virtual booting code and imaging code; the virtual booting code is capable of booting the computer without requiring any changes to BIOS or disk firmware from an image stored anywhere on the disk even though the disk has no working main partition; the imaging code is capable of reading an image of a working partition from a container on the disk, and deploying that image onto the disk; and the further setup script when executed will cause the computer to perform steps that comprise creating the image from data in the partition outside the container, and storing the image in the container.

4. The computer system of claim 3 , wherein the image of the working partition comprises a Microsoft Windows-brand operating system.

5. The computer system of claim 3 , wherein the image of the working partition comprises a Linux-brand operating system.

6. A further setup method for a purpose such as facilitating recovery from corruption or other loss of data stored on a computer disk, the method for use on a computer that has an attached disk which is configured by at least an operating system installed in a partition, the method comprising:

reserving space for a container anywhere on the disk;

recording on the disk a physical address for identifying the location of the container space without making any changes to BIOS or disk firmware;

on the computer, creating an image of the partition excluding the container space, without using a network connection;

storing the image in the container; and

storing disk recovery tools in the container if they are not part of the image.

7. The method of claim 6 , wherein the reserving step reserves the container space in a file system in the partition which will have its image created.

8. The method of claim 6 , wherein the reserving step reserves the container space outside the partition which will have its image created.

9. The method of claim 6 , wherein the step of creating an image of the partition uses at least the recorded physical address to identify the container space and exclude it from the image.

10. The method of claim 6 , further comprising the step of installing virtual boot code on the disk.

11. The method of claim 6 , further comprising the step of creating a rescue floppy.

12. A computer system comprising a processor, RAM operably connected to the processor for executing code, and a disk accessible to the processor, wherein the disk is configured by: a container holding a recovery image in a space selected and reserved from anywhere on the disk; at least one sector list data structure that identifies a physical address location of that container; and code residing and running on the computer which will allow a user to deploy the recovery image without requiring any changes to BIOS or disk firmware onto the disk outside the container when no working, hidden or other partition is present on the disk.

13. The computer system of claim 12 , wherein the disk is configured by code which will allow a user to deploy the recovery image as stated and to do so without making use of any secondary storage medium such as a floppy disk or a CD.

14. A computer system comprising a processor, RAM operably connected to the processor for executing code, and a disk accessible to the processor, wherein the disk is configured by: a container holding a recovery image in a space selected and reserved from anywhere on the disk; at least one sector list data structure that identifies a physical address location of that container; and code residing and running on the computer system which will allow a user to deploy the recovery image without requiring any changes to BIOS or disk firmware onto the disk outside the container without using any of the following: a second partition of any kind on the computer a secondary medium attached to the computer, or a network connection of the computer.

15. A computer-readable storage medium configured with code to perform an imaging setup method which comprises the steps of:

reserving space for a container from anywhere on a computer disk;

recording on the disk a physical address for identifying the location of the container space without making any changes to BIOS or disk firmware;

creating on the computer an image of a partition of the disk, the image excluding the container space;

storing the image in the container in the imaged partition; and

storing code on the disk which will allow a user to deploy the image onto the disk even if no working, hidden or other partition is present on the disk, wherein this storing step may be partly or fully accomplished by the image storing step when the image includes code for deploying the image.

16. The configured medium of claim 15 , wherein the method comprises locking the container to prevent access to the container when the image storing step is not in progress.

17. The configured medium of claim 15 , wherein the image creating step uses at least one physical address of the container space to create a used sector map that excludes the container space from the collection of sectors to be imaged.

18. The configured medium of claim 15 , wherein the step of creating an image creates a supplemental image.

19. The configured medium of claim 15 , wherein the step of creating an image creates a replacement image.

20. A method for deploying an image onto a computer hard disk, which may be performed for a purpose such as recovery from the corruption or other loss of data, the method comprising the steps of:

running virtual boot code, from the hard disk, which is capable of booting the computer without making any changes to BIOS or disk firmware when the hard disk has no working, hidden or other partitions;

locating on the hard disk within a corrupted partition a container which holds an image of a hard disk partition;

deploying the located image onto the hard disk outside the container, thereby configuring the hard disk with a working partition which replaces the corrupted partition.

21. The method of claim 20 , wherein the method is performed without the computer reading from any network connection, and without the computer reading from any removable storage medium.

22. The method of claim 20 , further comprising the step of selecting from more than one image which is stored on the hard disk, and the deploying step deploys the selected image onto the hard disk.

Assignments (14)
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC (F/K/A VERITAS US IP HOLDINGS LLC)
Reel/Frame 069712/0090 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS US IP HOLDINGS, LLC
Reel/Frame 054535/0814 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
MERGER AND CHANGE OF NAME Recorded Apr 18, 2016
From: VERITAS US IP HOLDINGS LLC; VERITAS TECHNOLOGIES LLC
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 038455/0752 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037891/0001 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 037891/0726 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2016
From: SYMANTEC CORPORATION
To: VERITAS US IP HOLDINGS LLC
Reel/Frame 037697/0412 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 1, 2012
From: POWERQUEST CORPORATION
To: SYMANTEC CORPORATION
Reel/Frame 027792/0495 →
MERGER Recorded Nov 1, 2011
From: POWERQUEST CORPORATION
To: SYMANTEC CORPORATION
Reel/Frame 027159/0001 →