Patent application number | Description | Published |
20120017111 | KERNEL SWAPPING SYSTEMS AND METHODS FOR RECOVERING A NETWORK DEVICE - In certain embodiments, a method is disclosed for recovering a failed client device in a network. The method includes booting a failed one of a plurality of client devices in the network with a generic image having a generic kernel usable with each of the plurality of client devices. The method further includes downloading, using said generic kernel, from at least one backup server an abbreviated kernel uniquely associated with the failed client device, the abbreviated kernel comprising substantially less data than an original kernel of the failed client device immediately prior to failure of the failed client device, the abbreviated kernel comprising a boot kernel image and at least one device driver. The method includes swapping the abbreviated kernel with the generic kernel; restoring, using said abbreviated kernel, remaining backup data from the at least one backup server to the failed client device; and rebooting the failed client device. | 01-19-2012 |
20120254119 | RESTORING COMPUTING ENVIRONMENTS, SUCH AS AUTORECOVERY OF FILE SYSTEMS AT CERTAIN POINTS IN TIME - A method and system for restoring a computing environment from a secondary data store, and facilitating such restoration, is described. In some examples, the system copies the configuration parameters of a computing environment, such as a file system, as well as the data within the file system, and transfers the copies to secondary storage for later restoration. For example, the system may generate an xml file of the configuration parameters of the computing environment when a backup operation of the computing environment is performed, and store the xml file along with copies of the data from the computing environment in secondary storage. | 10-04-2012 |
20130262390 | MIGRATION OF EXISTING COMPUTING SYSTEMS TO CLOUD COMPUTING SITES OR VIRTUAL MACHINES - Software, firmware, and systems are described herein that migrate functionality of a source physical computing device to a destination virtual machine. A non-production copy of data associated with a source physical computing device is created. A configuration of the source physical computing device is determined. A configuration for a destination virtual machine is determined based at least in part on the configuration of the source physical computing device. The destination virtual machine is provided access to data and metadata associated with the source physical computing device using the non-production copy of data associated with the source physical computing device. | 10-03-2013 |
20130262638 | MIGRATION OF AN EXISTING COMPUTING SYSTEM TO NEW HARDWARE - Software, firmware, and systems are described herein that migrate functionality of a source physical computing device to a destination physical computing device. A non-production copy of data associated with a source physical computing device is created. A configuration of the source physical computing device is determined. A configuration for a destination physical computing device is determined based at least in part on the configuration of the source physical computing device. The destination physical computing device is provided access to data and metadata associated with the source physical computing device using the non-production copy of data associated with the source physical computing device. | 10-03-2013 |
20130282662 | INTEGRATED SNAPSHOT INTERFACE FOR A DATA STORAGE SYSTEM - A data storage system includes a generic snapshot interface, allowing for integration with a wide variety of snapshot-capable storage devices. The generic interface can be a programming interface (e.g., an application programming interface [API]). Using the snapshot interface, storage device vendors can integrate their particular snapshot technology with the data storage system. For instance, the data storage system can access a shared library of functions (e.g., a dynamically linked library [DLL]) provided by the vendor (or another by appropriate entity) and that complies with the specifications of the common programming interface. And by invoking the appropriate functions in the library, the data storage system implements the snapshot operation on the storage device. | 10-24-2013 |
20140046900 | GENERIC FILE LEVEL RESTORE FROM A BLOCK-LEVEL SECONDARY COPY - Systems and methods are provided which perform a file level restore by utilizing existing operating system components (e.g., file system drivers) that are natively installed on the target computing device. These components can be used to mount and/or interpret a secondary copy of the file system. For instance, the system can instantiate an interface object (e.g., a device node such as a pseudo device, device file or special file) on the target client which includes file system metadata corresponding to the backed up version of the file system. The interface provides a mechanism for the operating system to mount the secondary copy and perform file level access on the secondary copy, e.g., to restore one or more selected files. | 02-13-2014 |
20140201151 | SYSTEMS AND METHODS TO SELECT FILES FOR RESTORATION FROM BLOCK-LEVEL BACKUP FOR VIRTUAL MACHINES - A data storage system receives a user instruction through a user interface to restore a specific virtual machine file from a block-level backup. The system accesses a file index which is created during the block-level backup by accessing the file allocation table of the underlying host system and associating the blocks with the file location information of the virtual machine files stored in the file allocation table. The system further creates a file level table based at least in part on the virtual machine file information stored in the file index, displays a listing of the virtual machine files from the file level table, and receives a user selected virtual machine file to restore. | 07-17-2014 |
20140201152 | SYSTEMS AND METHODS TO PROCESS BLOCK-LEVEL BACKUP FOR SELECTIVE FILE RESTORATION FOR VIRTUAL MACHINES - A data storage system protects virtual machines using block-level backup operations and restores the data at a file level. The system accesses the virtual machine file information from the file allocation table of the host system underlying the virtualization layer. A file index associates this virtual machine file information with the related protected blocks in a secondary storage device during the block-level backup. Using the file index, the system can identify the specific blocks in the secondary storage device associated with a selected restore file. As a result, file level granularity for restore operations is possible for virtual machine data protected by block-level backup operations without restoring more than the selected file blocks from the block-level backup data. | 07-17-2014 |
20140201162 | SYSTEMS AND METHODS TO RESTORE SELECTED FILES FROM BLOCK-LEVEL BACKUP FOR VIRTUAL MACHINES - A data storage system restores selected virtual machine files from a block-level backup without restoring blocks associated with files other than the selected virtual machine file. The system identifies the one or more blocks associated with a selected file from a file index that is created during the block-level backup of the virtual machine by accessing the file allocation tables of the underlying host system and associating the locations of the blocks with the file information from the file allocation table for the virtual files of the virtual machine. The system further restores the identified blocks without restoring blocks associated with files other than the selected file and/or file version, recreates the selected file from the restored blocks, and presents the restored file to the user. | 07-17-2014 |
20140201737 | SEAMLESS VIRTUAL MACHINE RECALL IN A DATA STORAGE SYSTEM - The data storage system according to certain aspects can manage the archiving of virtual machines to (and restoring of virtual machines from) secondary storage. The system may archive virtual machines (VMs) that are determined to have a low level of utilization. The system may create a virtual machine placeholder for an archived VM, which may be a “light” or minimal version of the VM that acts like the actual VM. By using a VM placeholder, a VM may appear to be active and selectable by the user. When the user selects the VM, the VM placeholder can interact with the user in similar manner as the VM. Accessing the VM placeholder may trigger restore of the archived VM from secondary storage. The restore of the archived VM may be “seamless” to the user since the VM remains available while it is being restored. | 07-17-2014 |