Abstract: A method of managing backup data. The method includes accessing, via a backup manager, index data of an initial snapshot and accessing, via the backup manager, index data of a subsequent snapshot. The method further includes determining, via the backup manager, whether the index data of the subsequent snapshot is different from the index data of the initial snapshot. Responsive to a determination that the index data of the subsequent snapshot is different from the index data of the initial snapshot, creating an updated index data and creating an updated snapshot with the updated index data.

Abstract: Methods, devices and systems to make compressed backup copies of in-use compressed database indices are described. In general, an “oldest” time at which index pages in working memory had been updated is identified. Compressed index pages may be directly copied without the need to bring them into working memory or uncompressing them. The identified “oldest” time is then associated with the compressed backup copy. In some embodiments, an entire compressed backup copy may be associated with a single point in time (e.g., the identified “oldest” time). In other embodiments, a compressed backup copy may be associated with multiple points in time (e.g., one time for each portion of the compressed index that is being backed-up). Compressed indices copied in accordance with the invention may be used during restore operations to reconstruct database indices using the identified “oldest” time and database log files.

Abstract: A system reserves and manages a hidden service partition through components of the hardware platform of a computing device. The hidden partition is not accessible by way of a host operating system on the computing device. A hardware platform controller provisions a portion of nonvolatile storage through configuration settings of the hardware platform controller. When the host system requests settings related to storage in the system, the request is routed through the interfaces of the hardware platform, and the hardware platform controller reports in accordance with the configuration settings, hiding the service partition. The hidden partition is dynamically modifiable through secure remote access to the hardware platform controller, not through the host system such as operating system or BIOS.

Abstract: Methods, apparatus, and products for backing up an image in a computing system that includes computer memory, including: receiving, by a backup image manager, an image for one or more computing devices within the computing system; identifying, by the backup image manager, available protected computer memory within the computing system, wherein the available protected computer memory within the computing system is restricted from alteration by a user of the computing system; slicing, by the backup image manager, the image into a plurality of image slices; and storing, by the backup image manger, one or more of the image slices in the available protected computer memory.

Abstract: An archival storage cluster of symmetric nodes includes a metadata management system that organizes metadata objects. Each metadata object may have a unique name, and metadata objects are organized into regions. A region is selected by hashing one or more object attributes and extracting a given number of bits of the resulting hash value. The number of bits may be controlled by a configuration parameter. Each region is stored redundantly. A region comprises a set of region copies. In particular, there is one authoritative copy of the region, and zero or more backup copies. The number of backup copies may be controlled by a configuration parameter. Region copies are distributed across the nodes of the cluster to balance the number of authoritative region copies per node, and the number of total region copies per node. Backup region copies are maintained synchronized to their associated authoritative region copy.

Abstract: Embodiments of the invention determine if a user preference or other piece of data is being synchronized too frequently. If the user preference is being synchronized too frequently, synchronization of the user preference is throttled to prevent it from synchronizing for some number of synchronization cycles. If the user preference rarely changes, the user preference is rewarded by throttling it less often.

Abstract: Systems and methods for replicating data from a production server to a backup server include identifying one or more data blocks of a file that were modified after a first time instant and before a second time instant. The file may be associated with a protected directory of the production server. An representative data block (e.g., including a hash value) for at least one of the identified data blocks may be computed using a cryptography algorithm, e.g., MD5 or SHA-1. The computed cryptographic data block representing the identified data block may then be sent for replication to the backup server. An operation performed between the first time instant and the second time instant on one or more files of the protected directory may be recorded, and sent to the backup server.

Abstract: A single system merges primary data storage, data protection, and intelligence. Intelligence is provided through in-line data analytics, and data intelligence and analytics are gathered on protected data and prior analytics, and stored in discovery points, all without impacting performance of primary storage. As data is written it is automatically mirrored for data protection as part of a High Availability (HA) process. Real-time analysis is done in-line with the HA processing, enabling a variety of data analytics. Data content can mined from within files or blocks. The gathered intelligence is used to tag objects with extended metadata, enabling both valuable search options and rapid restore options. Data recovery begins with metadata restoration, followed by near-instantaneous access to “hot” regions of data being restored, allowing site operation to continue or resume while a restore is ongoing.

Abstract: In one aspect, a method includes generating a write signature command. The write signature command is configured to write a signature to an offset in a storage array without data and to enable the storage array to write the data with the same signature to a volume if the data is available at the storage array.

Abstract: Described are embodiments of an invention for prioritizing data items for backup in a computing environment. The computing environment includes a plurality of clients coupled through a network to a backup system for backing up items stored locally on the client. Each client includes a continuous data protection (CDP) module that prioritizes the order of files transmitted to the backup system for storage on one or more storage devices based on policy. The CDP module builds an initial backup list and a CDP backup list. The initial backup list includes any item that meets the criteria of the initial backup profile. The CDP backup list includes items that have been modified since the initial backup process began. The data that is the most critical to a user is often the most recently modified data. Thus, the CDP module preferentially performs a backup of items on the CDP backup list.

Abstract: Methods and systems for allowing the backing-up of electronic data, its accessibility in times of need, and the ability to restore this data without denying user access to it while the restoration occurs. Also, the data may continue to be backed-up while it is being restored. One method allows for the removal of duplicated data from within the on or off-site copy and subsequent incremental on or off-site-site copies of the data. In this way, the amount of bandwidth and storage required may be reduced. For example, if there are two sets of files required to run two applications and some or all of these files are identical then only one copy need be made and sent and stored. This also applies where the on-site appliance is connected to more than one client server, such that data which is common to the client servers may only be copied once.

Abstract: A disclosed method includes distinguishing static and dynamic persistent data, copying the static persistent data at the source data store to the destination data store on a basis of frequencies of updates, copying the dynamic persistent data to the destination data store, updating a bitmap data structure during the copying of the dynamic persistent data to indicate which blocks of the dynamic persistent data have been modified during the copying step, identifying the blocks that have been modified during the copying step using the bitmap data structure, and iteratively copying the identified blocks to the destination data store. The method may further include determining when the number of the identified blocks is below a predetermined threshold and suspending the virtual machine prior to the next copying step.

Abstract: A data portion is evicted from a buffer, where the evicted data portion is modified from a corresponding data portion in a persistent storage. Write elision is applied to suppress writing the evicted data portion to the persistent storage. Subsequent to applying the write elision and in response to reading a version of the data portion, a redo of a modification of the read data portion is applied.

Abstract: A backup image generator can create a primary image and periodic delta images of all or part of a primary server. The images can be sent to a network attached storage device and a remote storage server. In the event of a failure of the primary server, the failure can be diagnosed to develop a recovery strategy. Based on the diagnosis, at least one delta image may be applied to a copy of the primary image to generate an updated primary image at either the network attached storage or the remote storage server. The updated primary image may be converted to a virtual server in a physical to virtual conversion at either the network attached storage device or remote storage server and users may be redirected to the virtual server. The updated primary image may also be restored to the primary server in a virtual to physical conversion. As a result, the primary data storage may be timely backed-up, recovered and restored with the possibility of providing server and business continuity in the event of a failure.

Abstract: Local seeding of a restore storage for restoring a backup from a remote deduplication vault storage. In one example embodiment, a method of local seeding of a restore storage for restoring a backup from a remote deduplication vault storage includes determining which blocks included in a backup of a source storage at a point in time, which is stored in the remote vault storage, are available in a local seeded storage containing common blocks, reading the locally available blocks from the local seeded storage, reading the non-locally available blocks from the remote vault storage, and storing the read blocks in the restore storage in the same position as stored in the source storage at the point in time. The remote vault storage is remote from the restore storage and the local seeded storage is local to the restore storage.

Abstract: Methods, apparatus and computer program products implement embodiments of the present invention that include defining, in a storage system including receiving, by a storage system, a storage request, and identifying, based on the storage request, one or more storage management units. For each of the storage management units, a master partition table having multiple master entries and one or more backup partition tables is identified, each of the backup partition tables having backup entries in a one-to-one-correspondence with the master entries. The storage request is performed, and upon the storage request being performed, any changes to essential metadata in the one or more master partition tables are identified, and the identified changes are stored to the essential metadata in the one or more backup partition tables.

Abstract: Techniques to perform an incremental backup of a large-scale distributed database, such as a massively parallel processing (MPP) database, are disclosed. In various embodiments, a set of table partitions each of which satisfies one or more criteria to be included in a current incremental backup is determined at backup time, at least in part by comparing a current table partition meta-information with corresponding meta-information from a prior backup. The table partitions in the set are included in the incremental backup, while other table partitions not in the set are not backed up. In some embodiments, certain tables are designated to be of a type such that existing records are not modified. Tables are partitioned in a manner that isolates changes, e.g., added rows, in a relative few table partitions, leaving others unchanged and therefore able to be omitted from subsequent incremental backups.

Abstract: Various systems and methods for using multiple clients for data backup are described. For example, one method involves accessing a namespace, where the namespace indicates locations of files. At least a portion of the namespace is divided into sets, where the sets correspond to a subset of the files. The files of the subset are accessed by plurality of nodes, and the accessing is based on the sets. Each of the nodes accesses the files of the subset. The nodes are used to store, at data storage, the files of the subset.

Abstract: 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.

Abstract: A single system merges primary data storage, data protection, and intelligence. Intelligence is provided through in-line data analytics, and data intelligence and analytics are gathered on protected data and prior analytics, and stored in discovery points, all without impacting performance of primary storage. As data is written it is automatically mirrored for data protection as part of a High Availability (HA) process. Real-time analysis is done in-line with the HA processing, enabling a variety of data analytics. Data content can mined from within files or blocks. The gathered intelligence is used to tag objects with extended metadata, enabling both valuable search options and rapid restore options. Data recovery begins with metadata restoration, followed by near-instantaneous access to “hot” regions of data being restored, allowing site operation to continue or resume while a restore is ongoing.

Abstract: Renamed directory handling for incremental file migration is described. A directory is stored in a storage device. An inode number associated with the directory in a directory table is identified. A determination is made whether the inode number equals an inode number associated with another directory in the directory table. At least one of a file and a subdirectory associated with the directory in the file system is stored into the directory in the storage device if the inode number equals the inode number associated with another directory in the directory table.

Abstract: A method of and system for enhanced storage allows more data to be backed up than would otherwise be possible. Instead of storing uncompressed base images and incremental images, differentials of non-current base images are compressed and stored. Furthermore, incremental images that are older than the current base image are removed. By only saving differential base images that are compressed, aside from the newest base image, and deleting older incremental images, a significant amount of space is saved. A removable drive is used as temporary storage in the process of generating a compressed differential base for previous base images. Additionally, a process ensures that previous base images are differentials of the most recent base image and not each other.

Abstract: An optimized backup image of a virtual machine is generated. The virtual machine is associated with a virtual disk. The virtual disk includes one or more virtual volumes. Generating the optimized backup image includes excluding one or more invalid sectors of the virtual disk from the optimized backup image.

Abstract: Change tracking between snapshots of a source storage. In one example embodiment, a method includes various steps. For example, the method includes, at time t(1), starting tracking, in a change log, locations in a source storage of all blocks that are changed after time t(1). The method also includes, between time t(1) and time t(3), changing a block in the source storage. The method further includes, at time t(3), creating a first snapshot of the source storage. The method also includes, after time t(3), creating a first image backup using the first snapshot. The method further includes, at time t(8), creating a second snapshot of the source storage. The method also includes, at time t(11), creating an incremental image backup that includes all blocks in the second snapshot that are tracked as having been changed in the change log after time t(1).

Abstract: A record of changes to virtual machine data of a virtual machine and a record of changes to snapshots of the virtual machine that have been received since the virtual machine was last backed up are maintained. In response to it being time to perform an incremental backup of the virtual machine, a portion of the virtual machine data is backed up based on the record of changes to the virtual machine data, and a portion of the snapshots is backed up based on the record of changes to the snapshots. In response to it being time to migrate the virtual machine to a second host device, the virtual machine data, the record of changes to the virtual machine data, the record of changes to the snapshots, and one or more of the snapshots are migrated to the second host device.

Abstract: Change tracking for multiphase deduplication. In one example embodiment, a method of tracking changes to a source storage of a source system for multiphase deduplication includes a change tracking phase that includes performing various steps for only allocated blocks in the source storage that are changed between a prior point in time and a subsequent point in time. These steps include temporarily storing a copy of the changed block in a volatile memory of the source system prior to writing the changed block to the source storage, performing a hash function only once on the copy of the changed block, while the copy is temporarily stored in a volatile memory of the source system, to calculate a hash value, writing the changed block to the source storage, and tracking, in a change log, a location in the source storage of the changed block and the corresponding hash value.

Abstract: Local seeding of a restore storage for restoring a backup from a remote deduplication vault storage. In one example embodiment, a method of local seeding of a restore storage for restoring a backup from a remote deduplication vault storage includes determining which blocks included in a backup of a source storage at a point in time, which is stored in the remote vault storage, are available in a local seeded storage containing common blocks, reading the locally available blocks from the local seeded storage, reading the non-locally available blocks from the remote vault storage, and storing the read blocks in the restore storage in the same position as stored in the source storage at the point in time. The remote vault storage is remote from the restore storage and the local seeded storage is local to the restore storage.

Abstract: Multiphase deduplication. In one example embodiment, a method of multiphase deduplication includes an analysis phase and a backup phase. The analysis phase includes analyzing each allocated block stored in a source storage at a point in time to determine if the block is duplicated in a vault storage. The backup phase is performed after completion of the analysis phase and includes storing, in the vault storage, each unique nonduplicate block from the source storage.

Abstract: A system, method, and medium for performing incremental backups of a data set within a deduplication storage system. An incremental backup of a data set is initiated, and the changed data items of the data set are deduplicated. An extents catalog is created to fully describe the data set. References associated with the unchanged data items of the data set are retrieved from the extents catalog and then sent to a deduplication engine. The deduplication engine uses the references to retrieve fingerprints associated with the unchanged data items from a previous reference map. Then, the deduplication engine creates a new reference map for the incremental backup and stores the newly generated and retrieved fingerprints in the new reference map.

Abstract: Architecture that eliminates the need for on-disk full backups of data retaining only changes that have occurred, in a separate table. Thus, the architecture provides for incremental recovery of incremental changes in a relational database (e.g., SQL). The architecture provides improved recovery time and recovery point objectives. By using the incremental capture of changed data (e.g., in an XML format), the capability is provided to capture schema changes, query the incremental change data and efficiently restore user data to an earlier point-in-time state. Changes (e.g., insert, update and delete operations) are tracked (e.g., continuously) by a set of triggers and the incrementally captured changed rows are inserted in a data capture table (a differential change “delta” table) in a human-readable format (e.g., XML). Rollback is also provided.

Abstract: A method for providing data protection in object-based storage environments may include: 1) taking a first snapshot, at a first time, of a set of partitions that store data of a file system on a set of object storage devices; 2) using the first snapshot to sync the data of the file system with a data protection node; 3) taking a second snapshot, at a second time, of the set of partitions; 4) using information from the set of object storage devices to identify at least one object that changed between the first and second times; 5) using object identification information to deduce file identification information that identifies a file that comprises the changed object; and 6) sending the changed object and the file identification information to the data protection node. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Techniques for data backup management are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for data backup management comprising identifying a base image for a plurality of data backup endpoints, creating, using at least one computer processor, a backup of the base image, storing the backup of the base image as a common backup for the plurality of data backup endpoints, and tracking changes to the base image at one or more of the plurality of data backup endpoints.

Abstract: A system and method include creating a full backup copy of selected data from a storage device. A series of incremental backups are created over time following the creation of the full backup copy. The oldest incremental backup is merged into the full backup at a desired time.

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: Method and apparatus for file sharing between continuous and scheduled backups is described. One example relates to backing up source data stored by a computer system. A first portion of the source data is backed up at points in time in response to a backup schedule to produce a plurality of partial backups. A second portion of the source data is backed up continuously in response to changes of the second portion to maintain a replica of the second portion. The replica of the second portion is linked to the plurality of partial backups to produce a respective plurality of full backups of the source data.

Abstract: Pruning previously-allocated free blocks from a synthetic backup. In one example embodiment, a method of pruning previously-allocated free blocks from a synthetic backup includes identifying multiple sequential backups to be included in a synthetic backup, accessing a copy of a file system block allocation map (FSBAM) of the most recent of the multiple sequential backups that was stored with the most recent backup, identifying a set of blocks that includes the most recent block for each unique block position contained within the multiple sequential backups, pruning the set of blocks to exclude all blocks that are identified as being free in the FSBAM, storing the pruned set of blocks in the synthetic backup, and storing a copy of the FSBAM with the synthetic backup.

Abstract: Systems and methods are provided for performing backup operations while a user is using a device. In one implementation, a method is provided. A backup operation of data including a plurality of related items is initiated. Modifications to one or more items of the plurality of related items are monitored for during the backup operation. The backup operation is completed. If a modification occurred to one or more items, a second backup operation is performed for the modified items.

Abstract: The disclosed techniques that can use deduplication information on a source computer platform to improve the process of performing data backups or restoration from/to the computer platform. In one example aspect, a data backup operation can re-use some of the work already done by a source computer's deduplication system. For example, a storage operation could read a deduplication database on the source computer platform to determine the duplicativeness of a given data chunk being transferred to a backup storage system, without having to perform computations such as data chunk hashing and comparison with previously generated hashes. The technique may additionally or alternatively reuse hashes generated by the source computer during deduplication of the data file on the source computer's file system during deduplication at the external backup storage system.

Abstract: Methods and systems for saving draft electronic communications, such as web e-mails, are described herein. One such described method comprises automatically saving a draft web-email in the e-mail web page. A second such described method comprises saving a draft web e-mail in a cookie residing on the client machine. A third such described method comprises automatically saving a draft web e-mail at the host that provides the Web e-mail service. A fourth such described method comprises interacting with a central installed client component to save a draft web e-mail one the user's machine at the client side.

Abstract: Systems and methods are disclosed for backing up a client data set on a computer by identifying changed files; generating a first sub-file signature for one or more segments of a changed file; subsequently generating a second sub-file signature for each file segment to detect insertions, removals, and rearrangements of data in the file; transmitting one more changed segment(s) in the file; and writing a manifest file reflecting the new target state.

Abstract: Time required for a file server to determine files to be migrated from a first storage region to a second storage region is reduced. A file service system coupled to the storage system for providing a first storage region and a second storage region stores identifiers of files that have been accessed by a client, in accessed file identifier information and determines the files to be migrated from the first storage region to the second storage region based on metadata of the files stored in the first storage region and the accessed file identifier information.

Abstract: Pruning previously-allocated free blocks from a synthetic backup. In one example embodiment, a method of pruning previously-allocated free blocks from a synthetic backup includes identifying multiple sequential backups to be included in a synthetic backup, accessing a copy of a file system block allocation map (FSBAM) of the most recent of the multiple sequential backups that was stored with the most recent backup, identifying a set of blocks that includes the most recent block for each unique block position contained within the multiple sequential backups, pruning the set of blocks to exclude all blocks that are identified as being free in the FSBAM, storing the pruned set of blocks in the synthetic backup, and storing a copy of the FSBAM with the synthetic backup.

Abstract: Various method, system, and computer program product embodiments for performing a backup of a source storage volume to a target storage volume are provided. In one exemplary embodiment, a flashcopy of the source storage volume to the target storage volume is initiated. The content of the source storage volume is stored on the target storage volume in a space efficient manner. The space requirement of the stored content on the target storage volume is monitored. The flashcopy is terminated when the space requirement reaches a predetermined level. The stored content on the target storage volume is copied to a backup storage medium. A new flashcopy of the source storage volume is initiated.

Abstract: Techniques are described for managing data storage and retrieval, such as by generating a hash value for a beginning and/or ending portion of a new data group to be stored, attempting to match each generated hash value to a plurality of hash values associated with other existing data groups that are already stored, and comparing the new data group and an identified existing data group to determine any identical extended initial or final portion of the two data groups. The new data group may then be stored as the portion unique to the new data group, along with a reference to the existing identical extended portion of the existing data group. The new stored data group may be later retrieved using the unique portion of the data group, along with the existing extended portions corresponding to other stored data groups for any stored references.

Abstract: There are provided a waveform observing apparatus and the system thereof in which, when a removable storage medium is inserted into the waveform observing apparatus to capture a copy of measured data, a difference copy is made while including the latest measured data collected by the waveform observing apparatus at the time, sixteenth and seventeenth measured data temporarily stored in a buffer memory are filed and stored in the state of being housed in a fourth measured data file, into a body memory. Copies of a third measured data file including part of the difference copy and a new fourth measured data file are written into the USB memory. When the USB memory is inserted into a personal computer, a hard disk of the personal computer comes into a state where its third measured data file is overwritten and stored and the fourth measured data file is newly stored.

Abstract: A method, article of manufacture, and apparatus for protecting data. In some embodiments, this includes tracking changed blocks in a virtual machine, determining a MFT range of the virtual machine, identifying a common region between the changed blocks and MFT range, parsing the common region to determine a list of changed files, and storing the list of changed files in a file index.

Abstract: Methods and apparatuses for performing secure incremental backup and restore operations are disclosed.

Abstract: Various systems and methods can select an incremental modification detection technique to apply to a data object during generation of an incremental backup. For example, a method can involve accessing information indicating an access characteristic of a data object and then selecting an incremental modification detection technique (from a set of more than one different incremental modification detection techniques), in response to the information. The incremental modification detection technique is selected to be applied to the data object when generating an incremental backup. The set of incremental modification detection techniques can include change tracking and content differencing techniques.

Abstract: The present invention relates to a method, system, and computer program product for data backup, the method comprising: performing first chunking on current data by using the same chunking method as that used by original backup data to obtain a current chunk; calculating hash value of the current chunk; and acquiring, from a hash value table of the original backup data, an identifier of a matched chunk whose hash value is the same as the calculated hash value of the current chunk, and incrementing number of continuous matched chunks by one. Since the pertinence between original backup data and current data is maximally utilized, performance of de-duplication method can be efficiently improved.

Abstract: Systems, methods, and media for synthesizing a view of a file system are provided herein. Methods may include receiving a request to obtain a view of at least a portion of a file system backup for a device, responsive to the request, mounting one or more backup files for the device on a backup node, generating a view of the at least a portion of a file system created from the one or more mounted backup files, the view being accessible via the intermediary node that is communicatively coupled with the backup node.