Symantec Corporation

Powerquest Corporation

Veritas Technologies LLC

Val Arbon

Donald Kleinschnitz

Roland Whatcott

Derrick S Shadel

Daniel Hardman

Andy Vincent Lawrence

Jonathan Ludwig

Roy M Jenevein

Paul E Madden

Heidi S Kramer

Jared R Gaunt

A data backup manager links data backup robustness to an external state. The data backup manager monitors the external state. Responsive to the external state, the data backup manager adjusts parameters controlling data backup, such as backup frequency, backup content, and backup retention time. The data backup manager can increase these parameters responsive to an increase in an external distress state level, and decrease them in response to a decrease in the external distress state level.

Linking dynamic computer data protection to an external state

The present invention provides tools and techniques for facilitating () management of storage (), software (), and other resources of a computer () at a distinct management computer () using a disassociated ample image () of the managed computer's storage. Ample images may be searched () to identify () infected files or illegal files, to extract () disk usage information, or for other reasons. Ample images may be modified () and then deployed () back to the original imaged computer and/or to other computers outside the management node. Modifications may change () application software, change () hardware drivers to match hardware changes on the target computer(s), manipulate () partitions, and/or perform other steps to optimize storage, software, or other resources.

Using disassociated images for computer and storage resource management

Methods are provided for retargeting captured images to new hardware. An image taken from a computer having hardware drivers and other system information in one hardware configuration can be modified to adapt it for use on a computer having different hardware requiring different drivers, even when the second hardware configuration was not known at the time of imaging. Systems and configured storage media for retargeting captured images to new hardware are also provided.

Retargeting a captured image to new hardware while in a pre-boot environment

Restoring access to running states of multiple primary computing systems onto a single computing system. The captured running states each include, or are altered to include, at least one device driver that is configured to interface with a common virtualization component that runs on the single computing system. The common virtualization component is configured to at least indirectly interface with hardware on the single computing system. The hardware potentially operates using a different interface than the device driver is configured to interface with. The system identifies a boot order for each of the primary computing systems, and then starts the running states for each of the primary computing systems in the appropriate boot order in a manner that takes advantage of the virtual environment exposed by the single computing system.

Recovery and operation of captured running states from multiple computing systems on a single computing system

Tools and techniques are provided for using a snapshot, not a full volume copy, to preserve deleted items when creating an image file with other items from a computer storage volume. One method classifies items as desired or not, enables snapshotting, then deletes undesired items, then creates a blockwise volume image in which the deleted items are not imaged, and finally disables snapshotting. Systems and configured storage media for imaging selected files and folders are also provided.

Selective file and folder snapshot image creation

An initial setup method () stores recovery tools () and a further setup script () on a computer () which has an operating system () that need not have any recovery capabilities. At the user site, a further setup method () reserves () a container space () in the file system space (), creates () an image () of the main partition (), and stores () the image in the container. If the partition is corrupted later, the computer can still be booted using virtual boot tools (), the image can be retrieved () from the container even though the partition around it was lost, and the image can then be deployed onto disk () 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.

Computer imaging recovery without a working partition or a secondary medium

The invention provides tools and techniques for running pre-boot code on a computer from a file stored in a file system on the computer. The pre-boot code may include an operating system which is not otherwise installed on the system. For instance, the pre-boot code may be used to boot a DOS operating system on a computer which lacks a DOS hard disk partition. The pre-boot code may contain code to perform operations that are difficult to perform after the operating system is booted, such as code for monitoring the boot process to help debug it. The pre-boot code is obtained from the file without using booted file system code, and is then executed. The code may be obtained by redirecting floppy drive I/O to read the pre-boot code from a copy in memory, or to read it as needed from one or more files on the hard disk.

Booting an operating system or running other pre-boot code from a file stored under a different operating system

The invention provides systems and methods for storing and recovering images in a computer partition, and more particularly to tools and techniques for placing and extracting images to and from the same partition that is imaged. Both a factory image and a user-updateable image may be stored on the same partition. Copies of a portion of the partition data and/or the system data for the imaged partition can be stored at a specified location within the imaged partition, in a separate partition, or on a removable recovery medium, thereby allowing images to be recovered after disruption of the imaged partition's system data. The image may be stored contiguously or non-contiguously. The image may also be stored as a system file or as an image container which comprises one or more than one image file. To speed restoration time and to assist recovery, the image may be stored at or near the end of the partition. Familiar or novel image formats may be used. By storing one or more partition images in the imaged partition, the invention eliminates consumer confusion between bootable partition size and disk size, without sacrificing the advantages provided by imaging.

Growing community of inventors

Orem, UT, United States of America

Val Arbon