Abstract:
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.
Abstract:
Techniques for providing data preview before recalling large data files are disclosed. In one aspect, a data file is made accessible while being offline by converting the data file from a native format to a preview format, storing the data file in the preview format in a primary storage that is locally available and moving, after the conversion to the preview format, the data file in the native format to a secondary storage. When a viewing request is received for the data file, the data file in the preview format is displayed to fulfill the viewing request.
Abstract:
Techniques for enabling user search of content stored in a file archive include providing a search interface comprising a search rules portion and an action rules portion, receiving a file archive search criterion comprising at least one search rule, and searching the file archive using the search criterion. The techniques also include generating a set of files filtered using the search criterion and performing an action specified in the action rules portion on a file included in the set of files.
Abstract:
The data storage system according to certain aspects can implement table level database restore. Table level database restore may refer to restoring a database table and its related data without restoring the entire database. The data storage system may use table metadata index to implement table level restore. A table metadata index may be created for each table, e.g., during a backup of the database. The table metadata index for a table can include any type of information for restoring the table and its related data. Some examples of the type of information included in the table metadata index include the following: container for the table, table backup location, system data, table index, table relationships, etc. Table metadata index can make the restoring of tables fast and efficient by packaging information that can be used to restore a table and its related data in an easily accessible manner.
Abstract:
A data storage system can scan one or more information stores of primary storage and analyze the metadata of files stored in the one or more information stores of primary storage to identify multiple, possibly relevant, secondary copy operations that can be performed on the files. The storage system can also identify primary storage usage information of each file during the scan and use that information to generate reports regarding the usage of the primary storage.
Abstract:
A data storage system allows a user to search a secondary copy such as a back up, archive, or snapshot and receive an abbreviated version of the secondary copy of the file system as a result of the search. The abbreviated version of the secondary copy of the file system may include metadata such as a listing of secondary copy data that correspond with a search term or other filtering criteria provided by the user. An operating system of the user's computing device may mount the abbreviated version so that it can be displayed within a view of the file system of the computing device. Once a user selects one or more desired data objects listed in the abbreviated version, the selected actual one or more data objects are retrieved from secondary storage.
Abstract:
This application discloses a system for presenting data to a user based on requests to move data from primary storage to secondary storage. The system receives a request to move data that satisfies at least one criterion, from primary to secondary data storage. The system then identifies an initial database query from the request, and further builds a nested database query from the initial database query according to a database schema. Next, the system estimates a size of a result of executing the nested database query. Finally, the system provides for display to the user the estimated size.
Abstract:
A data storage system allows a user to search a secondary copy such as a back up, archive, or snapshot and receive an abbreviated version of the secondary copy of the file system as a result of the search. The abbreviated version of the secondary copy of the file system may include metadata such as a listing of secondary copy data that correspond with a search term or other filtering criteria provided by the user. An operating system of the user's computing device may mount the abbreviated version so that it can be displayed within a view of the file system of the computing device. Once a user selects one or more desired data objects listed in the abbreviated version, the selected actual one or more data objects are retrieved from secondary storage.
Abstract:
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.
Abstract:
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.