EP2477114A2 - System und Verfahren zum Hochleistungsschutz von Unternehmensdaten - Google Patents

System und Verfahren zum Hochleistungsschutz von Unternehmensdaten Download PDF

Info

Publication number
EP2477114A2
EP2477114A2 EP12001733A EP12001733A EP2477114A2 EP 2477114 A2 EP2477114 A2 EP 2477114A2 EP 12001733 A EP12001733 A EP 12001733A EP 12001733 A EP12001733 A EP 12001733A EP 2477114 A2 EP2477114 A2 EP 2477114A2
Authority
EP
European Patent Office
Prior art keywords
backup
snapshot
application
blocks
volume
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP12001733A
Other languages
English (en)
French (fr)
Other versions
EP2477114A3 (de
EP2477114B1 (de
Inventor
Peter Chi-Hsiung Liu
Soubir Acharya
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Precisely Software Inc
Original Assignee
Syncsort Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Syncsort Inc filed Critical Syncsort Inc
Priority to EP13005349.9A priority Critical patent/EP2713271B1/de
Publication of EP2477114A2 publication Critical patent/EP2477114A2/de
Publication of EP2477114A3 publication Critical patent/EP2477114A3/de
Application granted granted Critical
Publication of EP2477114B1 publication Critical patent/EP2477114B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1456—Hardware arrangements for backup
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/16—Protection against loss of memory contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2071—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using a plurality of controllers
    • G06F11/2074—Asynchronous techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • the present invention is in the field of information technology, and more particularly relates to high performance, enterprise-level backup and disaster recovery systems.
  • An embodiment of the present invention is being made available as part of Backup Express® (BEX), a software product of Syncsort Incorporated, the assignee of the present application.
  • BEX Backup Express
  • FAR Fast Application Recovery
  • the instant availability aspect of the invention is provided by:
  • the snapshotting and instant availability features of the invention are used in connection with storage hardware components to provide an "Enterprise Image Destination" (EID) for backup images created in accordance with the present invention.
  • EID Enterprise Image Destination
  • the EID software is further distinguished in being operable with storage hardware from a wide variety of vendors, including inexpensive ATA storage hardware.
  • a "Double Protection" feature is provided whereby point-in-time images in the EID may themselves be backed up to selected media or replicated in other EIDs.
  • the invention also provides a feature, referred to as "lazy mirroring," whereby a replacement physical primary facility may be created while working with a second storage unit as the primary source file system.
  • the second storage unit in accordance with this feature could be a secondary logical volume previously brought online pursuant to the "instant availability" feature of the invention referenced above, where a replacement physical primary volume is being created at the same time; or it could be (as another example) a surviving unit of a mirrored storage system where another mirror unit is being "resilvered" or replaced at the same time.
  • Other applications of the "lazy mirroring" technique are possible as well.
  • the "lazy mirroring" in accordance with the invention is further characterized by being able to proceed without an interruption in processing.
  • the invention provides a technique based on block comparisons for greatly speeding up distributed backup operations by eliminating redundant data when multiple systems with partially common contents (e.g., operating system files and common databases) are being backed up. Where it is determined that a block to be backed up already exists in the backup set, the existing block is used in the directory or catalog of the backup, rather than storing both blocks. A similar technique is employed so as to eliminate redundant blocks in a file system.
  • partially common contents e.g., operating system files and common databases
  • APM Advanced Protection Manager
  • This feature is implemented entirely in software and once installed on a node would allow that node to function as a nearline destination for application aware Forever Image Incrementals.
  • This EID node could be configured in various ways (local disks, iSCSI storage etc.) to offer various degrees of protection and reliability. Image backups from various nodes would be consolidated, nearlined and versioned on this device. Instant Availability for file-systems and applications would be leveraged off these versioned images.
  • Fig. 1 shows a typical enterprise deployment of an embodiment of the invention, showing a secondary storage server 107 utilizing inexpensive SATA disk drives, connected in turn to further arrays of servers 103, NAS device 104, a remote secondary storage device 105 and tape storage 106.
  • This backup arrangement is used to remotely manage backup and recovery for networks comprising both small (101) and large (102) remote sites.
  • Block level backup clients are used to perform block level backup operations where indicated (111, 112, 114, 115).
  • Replication to tertiary storage 113 wherein secondary storage server 107 also serves as a tertiary storage
  • tape 116 to tape drive 106
  • the EID node would have locally attached SATA drives configured as hot-pluggable RAID5. This storage would be used as a repository for images. Versioning would be implemented via snapshots available on the system (VSS for Win2003 or LVM/EVMS for Linux). Images would be exported as read-write LUNs via bundled iSCSI target software.
  • the EID node would only have a small local drive (ideally mirrored) to hold the OS and EID software.
  • a back-end iSCSI storage array (or similar network intelligence) would be used as the actual destination for backup images.
  • a storage array would necessarily need to expose LUN creation, snapshot creation, LUN cloning, LUN masking/un-masking features to be a candidate for participation in a bundled EID solution.
  • VSS/VDS or SMI-S APIs may be used to standardize on the interface between EID software and external storage.
  • Double Protection (Refer to Double Protection document)
  • First backups to disk on EID nodes could go to tape devices on the SAN or other disk distinct from the storage where the first backups reside. This would be second or third tier storage residing on the SAN or attached to some remote appliance (possibly another EID node).
  • EID is the key enabler for an End-to-End solution for data protection based on multi-tiered storage.
  • APM client node
  • nodes would be configured with the APM client and support for multiple snapshot providers (if available).
  • the APM client would be capable of backing up BID targets to secondary storage, which can be to vendor-supplied storage hardware or generic ATA storage hardware.
  • the snapshot support could be basic (bundled EOFM) or complex - each volume may have a separate snapshot provider. (When multiple snapshot providers are present, their use must be pre-configured or indicated by the EID node) Application support when implemented is available simultaneously for both secondary and EID targets.
  • APM Server - EID node
  • This node would have the EID software installed with a storage specific plug-in depending on the back-end iSCSI storage (if any).
  • the plugin configuration would be hardwired during installation along with licensing information.
  • the basic configuration would be supported on two different set of commodity OSs - Windows 2003/NTFS and Linux 2.6 with ext3fs/xfs with LVM/EVMS.
  • the requirement essentially is 64-bit journaling file-system with sparse file support with multiple persistent snapshots. Any system meeting these criteria could be a candidate for an EID node. (Additional properties of the file-system like compression and/or encryption although not essential could be employed to provide additional features at additional complexity and/or overhead)
  • Fig. 2 schematically illustrates the creation of a point-in-time snapshot, block-level incremental backup, and point-in-time full volume image, as well as a file-level restore operation.
  • the Protocol director contacts APPH (Application Helper, which mediates application (SQL Server, Exchange, etc.)-specific interaction at the beginning and end of backup) with BACKUP_PREPARE.
  • APPH Application Helper, which mediates application (SQL Server, Exchange, etc.)-specific interaction at the beginning and end of backup) with BACKUP_PREPARE.
  • APPH contacts the Snapshot Handler, which encapsulates snapshot code and incremental block tracking interfaces, to snapshot a set of volumes and flush change journals.
  • the Snapshot Handler would do DISCOVER_LUNS as part of file system discovery.
  • iSCSI or FCP (Fibre Channel Protocol) vendors it would invoke a vendor specific method to take a snapshot of the set of volumes that reside on the same iSCSI storage entity (for example a volume containing a set of LUNs on a storage device).
  • a specialized provider would exist per storage vendor providing this functionality or VSS or SMI-S providers could be used if available from the storage vendor. Additional configuration information will be required per back-end storage node to provide this functionality, which would have to be obtained from the database. (This information may be cached or saved as part of a local configuration file.) Since most external providers would not provide change journal support both external (or VSS mediated), a bundled EOFM snapshot would need to be taken. The EOFM snapshot would solely be used for flushing the change journal and tracking changed blocks. The external snapshot would represent the real backup instance or a consistent source for remote copy. The EOFM snapshot needs to be taken first, followed by the external snapshot to produce a consistent image. A small window exists between both snapshots where blocks may change.
  • APPH would at the end of the process create a content file for the backup specification.
  • This file will be augmented with vendor specific info with possibly a logical name and a persistent snapshot id along with a local snapshot volume created by EOFM, VSS or third-party provider.
  • SVH contacts the EID software with a CREATE_RELATIONSHIP message (for the first backup) and passes the content file as the source path.
  • the EID software on the EID node then establishes connection with corresponding software ("Node software") on the source node and passes the content file path.
  • Node software software
  • the Node software on the source side then reads and passes the contents of the content file back to EID software on the EID node.
  • the EID software examines the vendor specific snapshot info and determines whether the vendor is supported and licensed. If the answer is yes the EID software tries to determine via local query snapshots existing on the shared storage device and if it determines the shared snapshot can be used as backup then the process completes.
  • the allocation bitmap is also obtained at this point.
  • the EID software stores the relationship, a combination of the source node+source drive(or unique id)+destination node+lun name in its local database.
  • the allocation bitmap is also saved indexed by snapshot id.
  • the CREATE_SNAPSHOT from SVH returns with the shared snapshot in the previous step.
  • File history is generated (optionally) on the EID node using the backup LUN.
  • the File history is to be conveyed to Backup Express Master server in some implementation specific way.
  • Checksums may be calculated for all allocated blocks on the LUN image and saved away in the EID database indexed by snapshot id. Checksums are important for three reasons:
  • the APPS volume comprises files generated on the live file-system after the snapshot is taken and as part of the POST_BACKUP event. These files do not exist in the shared snapshot. These files need to be independently backed up. Variation II 'Local Copy To Backup LUN' has to be used in this case. Although APPS appears as a virtual volume, the backup of APPS is effected by copying whole files (file by file backup) and not volume-oriented block copy.
  • the EID software determines that the shared snapshot cannot be used, it creates a backup LUN on the iSCSI storage or locally, naming it uniquely with the source node + drive id combination.
  • the hostname+portid+targetname+lunid is returned to the source EID software as part of the initial handshake.
  • the source side Node software then calls MAP_LUN (which indirectly uses iSCSI login) with the information passed from the EID node.
  • MAP_LUN exposes a device mapped to the local namespace.
  • the Node software begins to copy allocated blocks from the local snapshot of the device to the iSCSI-mapped device. During this process it passes status/checksums/progress to the EID Software via the already established channel.
  • the EID software takes a snapshot of the backup LUN or some covering entity and returns the snapshot id.
  • the EID software needs to remember the last successful block written and pass this on during the initial handshake indicating that this is part of re-starting an aborted backup.
  • File history is generated (optionally) on the EID node using the backup LUN.
  • the File history is to be conveyed to Backup Express Master server in some implementation specific way.
  • Checksums may be calculated for all allocated blocks on the LUN image and saved away in the EID database indexed by snapshot id.
  • the APPS volume comprises files generated on the live file-system after the snapshot is taken and as part of the POST_BACKUP event. These files do not exist in the backup snapshot.
  • the APPS LUN After the APPS LUN has been mapped locally, it has to be formatted as a locally recognized file system. Then APPS directories/files are copied whole (file by file) from APPH directed locations (and not from a snapshot) onto the APPS backup LUN. During incremental backups the APPS LUN has to be cleared and a new set of APPS files copied. (The older snapshots would retain the previous versions of APPS files)
  • the EID software determines that the shared snapshot cannot be used, it creates a backup LUN on the iSCSI storage or locally, naming it uniquely with the source node + drive id combination. LUN creation may fail if it is not supported on this node (really basic configuration) If this happens hostname+portid+targetname+lunid is not returned to the source Node software as part of the initial handshake and Variation III is indicated.
  • Source side Node software begins to read allocated blocks from the local snapshot of the device and send it across the network to the destination EID software.
  • the destination EID software reads from the channel and writes out a sparse file on some pre-defined volume on the destination. Either end in this process may generate checksums.
  • the EID software takes a snapshot of the volume containing the backup image file and returns the snapshot id to the DMA.
  • the EID software needs to remember the last successful block written and pass this on during the initial handshake indicating that this is part of re-starting an aborted backup.
  • File History File history is generated (optionally) on the EID node using the backup image.
  • Checksums may be calculated for all allocated/changed blocks on the backup image and saved away in the EID database indexed by snapshot id.
  • APPS directories/files are read whole (file by file) from APPH directed locations (and not from a snapshot) and copied across the network to the destination EID software where a directory structure (under a pre-determined backup directory location) is created to reflect an identical copy of the files at the source.
  • a directory structure under a pre-determined backup directory location
  • the APPS directory has to be cleared and a new set of APPS files transferred and re-created from the source. (The older snapshots would retain the previous versions of APPS files)
  • EID backups depend on snapshot creation, LUN creation, LUN cloning etc. Both the source side and the EID side of the backup process are consumers of these services.
  • an interface with an associated vendor specific provider in the form of a DLL or a shared library) needs to be implemented. The default implementation would use the bundled iSCSI provider on the EID node, but could be replaced by a vendor specific implementation if warranted.
  • the interface would provide generic LUN creation/deletion, LUN cloning, snapshot creation/deletion functionality.
  • An augmented version of the interface might add functionality for block level mirroring and other salient features (for example: a Secondary to Tertiary Replication feature), which may be taken advantage of for supporting efficient/elegant Double Protection methodology.
  • a small database on the EID node is needed to maintain configuration (like back-end iSCSI storage), licensing, snapshot ids, checksum info etc. This would be especially necessary where the EID node is back-ending some iSCSI/shared SAN storage. Backup Express infrastructure would be dealing with a unique snapshot-id, but the EID software has to translate this to an exact network entity by de-referencing the snapshot-id via the local database.
  • a simple implementation may be a set of directories named with snapshot ids containing block allocation bitmaps, incremental bitmaps, checksums, file history etc.
  • Double Protection to disk prolongs the life of a backup image on disk further by creating another backup on disk of the original/first backup. Every effort is made in this case to create subsequent backups by transferring incremental data to update tertiary backups.
  • Various scenarios are:
  • Multi-tiered storage visible to EID node is Multi-tiered storage visible to EID node
  • the tertiary disk storage is accessible from the EID node (Secondary and Tertiary storage may be part of a large multi-tiered storage deployment accessed via a uniform single vendor interface - Hitachi TagmaStore).
  • DP backup in this case would proceed via a local block-level incremental copy performed by the EID software after the appropriate tertiary location is selected and a LUN un-masked/mounted on the local EID node.
  • the EID software would trigger and image transfer/update via vendor specific API set to create a Double Protection backup.
  • the remote EID node When tertiary storage is physically separated from the EID node, the remote EID node would initiate the backup via "Network Copy" to pull data from the local EID node.
  • the applicable Backup Client transfer method When data has to be transferred between an EID node and a secondary node, the applicable Backup Client transfer method would be used, i.e. the secondary would be contacted and asked to pull data from the EID node.
  • the EID Software would recognize a DP2D backup and update the secondary image from appropriate (usually latest) snapshot using saved bitmaps.
  • the Protocol director initiates an EID backup, much like a regular EID backup except that the snapshot phase is skipped.
  • a CREATE_RELATIONSHIP is sent to the destination EID software (this could be an EID node co-located with the destination, a remote EID node, or another type of secondary).
  • the EID software detects that it is the source node for the backup, it uses appropriate mechanism to either copy the image locally (using allocated or incremental bitmaps saved with the backup) to a tertiary destination or invoke a vendor specific method to affect this transfer.
  • the EID software detects that the source is remote it initiates a regular EID backup using a previously described mechanism. The backup is saved on the destination EID node like a regular EID backup, implying that this process can be cascaded indefinitely.
  • the snapshot-id which comes back from the NOTIFY response to secondary snapshot creation, is cataloged as part of the DP backup and linked with the original first backup. (For detailed explanation see the separate discussion of Double Protection.)
  • NDMP Directory Browse function may be used by contacting the EID software. Browsing may be provided by mounting the backup LUN on the EID node and then browsing the file-system using existing 'snap dir list' mechanism or by generating 'rawtoc' from the image file when browsing is necessary. Double Protection to tape requires that file history be generated during a Double Protection operation either as part of the image or to construct a file-by-file archival format if the option to mount the LUN as a recognizable file system is not available.
  • EID node determines that LUNs cannot be exposed to the requesting node (e.g., for security reasons) or that after the initial handshake completes the requesting node cannot map the LUN.
  • a traditional restore proceeds where the EID software reads the requested files from the backup image and sends them over the network and the Node software on the restore target recreates the file locally from the received data.
  • 'rawtoc' is required, either pre-existing from a post backup process or created on the fly for restore (and then cached if desired).
  • MAP_LUNS will be called (as implemented in the Snapshot Handler) to map a set of volumes via iSCSI or FCP on the restore target from the selected snapshot.
  • the Snapshot Handler will call CREATE_LUN_FROM_LUN on the EID node to create and expose a LUN within a snapshot.
  • the APPS volume will then be similarly mapped to the local namespace either via a local iSCSI mount or a network mount. Once this step completes SSSVH will direct APPH to complete the restore. APPH will copy log files if necessary from the APPS volume to the IA volumes to recover the application or database. Note that the EID software is not contacted for IA restores at all.
  • the backup data transmitted across the network as part of a differential block level image has a disk signature attached to beginning which has the appropriate information to virtualize the backup of a volume as a whole SCSI disk with a single valid partition.
  • this read-only image is transformed into an iSCSI addressable read-write LUN by creating a sparse file backed by the image within the snapshot.
  • This LUN file is persistent and can function as primary storage aggregating changes as well as original unchanged data from the backup image.
  • the LUN can both be mounted as a stand-alone disk or part of a RAID set.
  • Volume rollback is only possible ifrestore happens to original location and all change journals since the time of backup exist. If these criteria are not made a full volume restore can be triggered (this is a de-generate case of volume rollback anyway) or the restore job fails. (Given the functionality of IA restores this may not need to be implemented at all.)
  • volume rollback is desired, in which case a VOLUME_ROLLBACK message is sent by the Protocol director to the Snapshot Handler (much like MAP_LUN). This message contains the backup jobid (which uniquely identifies the point-in-time of the backup) and the volume in question. If volume rollback is possible the Snapshot Handler locks and dismounts (applications hosted by the volume are shut down or off-lined by APPH) the volume in question and then takes a snapshot to flush the change journal. All change journals since the time of the snapshot that is being restored to, are logical-ANDed to create a bitmap file which is returned (the file name only) to the Protocol director. The Protocol director adds the bitmap file to the content file and passes this on to the EID software, which uses the bitmap file to restore only a set of blocks from the mapped LUN or across the network.
  • a VOLUME_ROLLBACK message is sent by the Protocol director to the Snapshot Handler (much like MAP_LUN). This message
  • the allocation bitmap has to be passed to the Node software on the restore target from the EID node so that only the allocated blocks are copied. If network copy is used the EID node already knows which blocks to send.
  • the volume is unlocked and re-mapped in the local namespace and applications/databases re-started and on-lined.
  • This mode of restore requires back-end storage support of single file or LUN rollback.
  • Volume locking and application shutdown happens on the restore target node mediated by the Snapshot Handler and APPH exactly like above.
  • the EID software on determining that the back-end storage supports this feature and that the snapshot and the restore target LUN are logically related calls a back-end API (part of the plug-in interface) with two arguments - the snapshot that is the being restored from and the target logical entity or LUN that back-ends the volume on the restore target node.
  • Volume rollback on the back-end storage happens asynchronously and may take a while depending on the divergence between the live file- system and the snapshot (but should be quick since only local copy is involved). Once this completes the restore ends and applications can be re-started. (An example of this scenario is a single file LUN snapshot revert on an NAS device.)
  • Full Volume Restores Only important for large full volume restores. May be implemented by a restart mechanism similar to backup but with the checkpoint tracked by restore target Node software and communicated on a re-connect. Whether restore needs to be re-started after cancel by the DMA is outside the scope of this document.
  • Error recovery should be un-necessary since the restore involves local copy. Re-startability after cancel/suspend may be desirable.
  • the Linux Node software may be driven by a modified version of jndmpc to work exactly like above, taking advantage of an iSCSI initiator if available on the custom Linux kernel. Error Recovery/Restartability would be essential in this situation.
  • a standard mechanism needs to exist for browsing snapshots for ExpressDR backups of a given node. This should be part on an interface exposed by the EID software or the Snapshotg Handler on the EID Node.
  • a snapshot directory listing may be sufficient with a pre-defined naming convention for snapshots, or a suitable interface may need to be defined for enumerating matching snapshots.
  • Nearlined data needs to be more secure than data on offline media (like tape) since data is live and accessible over the network given proper permissions or if a small set of accounts are compromised.
  • One option would be to encrypt data that resides on nearline storage (Native file-system encryption could be used if available). This would slow down Instant Availability Restores but the added security may make it worthwhile. Double Protection to disk and/or tape, especially if they are for long term archival reasons are also prime candidates for encryption.
  • a few user accounts (Backup Express admin and root or Administrator on the EID node) protecting backups of a lot of machines consolidated on a single EID node, may not be secure enough for most enterprises. Multiple admins each having responsibilities/rights over a set of backup images may be more acceptable (In this situation the super-user would not necessarily have rights over all backup images).
  • Some style of RBAC may be implemented by using existing security mechanism on Windows 2003 or Linux 2.6.
  • Double Protection to disk or tape targeted at specialized compliance appliances like secondary WORM storage or WORM tapes enable an end-to-end solution starting from backup, to near-term restore and long-term archival to meet compliance requirement
  • Self Provisioned Restore refers to administrator-less data recovery where end users typically restore files without help-desk or administrator mediation. This is possible as data is stored on the EID node preserving original file-system security. Once Instant Availability or other techniques are used to map volumes back to some well known location users can find and restore data using existing and familiar tools. (The Backup Express GUI may also be used to find and restore data without having to login as an administrator.) An intrinsic property of the EID architecture enables self-provisioned end-user restore and thus reduces TCO (Total Cost of Ownership) significantly.
  • TCO Total Cost of Ownership
  • Fig. 3 shows block-level incremental backup and file-level incremental restore operations in greater detail than Fig. 2 , in a manner that illustrates a number of the foregoing principles.
  • the example shown involves the following events and operations:
  • Double Protection protects first image backups to intelligent disk storage by backing them up to tape or disk, managing their life-cycle and providing direct restore from tape when first backups have expired or disk storage is unavailable.
  • APM TO DISK (APM2D):
  • Double Protection creates at least one (and as many as desired) virtual copy of the first backup to disk or tape.
  • the crucial point here is that subsequent backups are identical untransformed copies. Since the first backups are frozen point-in-time images, copies can be made at any time in the future and still capture the original state of the file system. Twinning is not needed anymore since as many copies of an original backup can be made as soon as or whenever policy dictates. For supported applications, application consistent snapshots are saved to tape as if the tape backup was done at the time of the original first backup.
  • the GUI would present in a Double Protection screen a list of first backup jobs, which are candidates for double protection. This would look like a traditional image/or NDMP backup screen except for the fact that the left pane would be backup jobs. (Device selection may be avoided initially by implicitly selecting default cluster and mediapool for the containing nodegroup).
  • the DP job would be saved as a NDMP job with the first backup jobname or a first backup jobid as part of the definition.
  • the schedule would be simple - just a backup schedule like APM2D, no base incremental or differentials settings.
  • DP jobs with a specific instance selected of a first backup job i.e. jobid
  • job handler When job handler receives JOB_START and determines that this is a DP job would issue a CREATE_DP_JOB to the database specifying job name or job id as argument.
  • the dB can obtain given the jobid (and by looking up the snapid) the backup document for the job. Given a job name the latest backup job id would be used to find the backup document for the job.
  • the backup document contains the entire state of the first backup needed to be able to construct an NDMP job to tape identical to the original APM2D job. A one-to-one mapping of tasks in the original would be created in the DP_JOB resulting in an equal set of source statements.
  • APM2D job with tasks C:, D:, APPS: would be translated to three tasks /vol/vol1/.snapshot/snapname/qtree1, /vol/vol1/.snapshot/snapname/qtree2, and /vol/vol1/.snapshot/snapname/APPS-qtree.
  • CREATE_DP_JOB would return a temporary job name whose definition once obtained by job handler would allow the NDMP job to proceed. Once this job creates a copy to tape it would be as if a backup to tape was run at the original time of the disk backup.
  • the first backup jobid and taskids are needed for co-relating the DP jobs tasks with respect to the first backup.
  • CREATE_DP_JOB dB could pre-catalog the DP job creating catalog entries, which would be validated if an actual TASK_CATALOG came in.
  • the CREATE_DP_JOB could also be called by SVH when a necessary condition is triggered (running out of snapshots etc.). SVH could then run this job via JOB_START etc. following a backup or even before a backup.
  • Double Protection jobs are APM backups mediated via the EID software or external NDMP data servers (including proprietary NAS backup methods).
  • the first backups could be image files or replicated directories.
  • the EID software backs these up it would recognize that DP backups are being made and back them up preserving original format if image or as logical backups if they are replicated directories.
  • External agents would back up images or replicated directories in their native format (dump or tar).
  • DP backups In the event DP backups go to tape the legacy job handler path would be used. DP backups directed towards tertiary disks (Secondary to Tertiary Replication) would be handled by SSSVH or by some external agent (may involve simple scripts followed by a cataloging utility step)
  • DP backups may transform image backups to logical backups in some portable format like tar, cpio, or pax. These backups could go to WORM tapes or WORM drive to meet compliance requirement. Data would be restorable from this archive using file history saved during first backups. Direct Access Restore (DAR) would require re-saving file history with associated fh_info thus requiring file history generation during the double protection process.
  • DAR Direct Access Restore
  • Each DP job would catalog as many tasks as the original backup in 'sscat'. New fields in sscat for original task and job ids would be added to track reference to the original job. (As part of this we could also add a snapid filed as part of sscat since this is a high level and crucial construct for first backup jobs)
  • the DP jobs would have their own equivalent disk entries in sscat with path names reflecting secondary disk locations.
  • Example sscat (partial columns): JOBID TASKID ORIGINAL JOBID* JOBNAME DISK 1000055 1 0 first backup C: 1000055 2 0 First backup D: 1000055 3 0 First backup APPS: 1000100 1 1000055 Double P /vol/vol1/qtreeC 1000100 2 1000055 Double P /vol/vol1/qtreeD 1000100 3 1000055 Double P /vol/vol1/qtreeAPPS
  • first backups and subsequent DP backups are treated as separate jobs, each would have their own retention period. As first backups expire checks would be made to ensure that DP backups exist depending on policy. A warning may be issued or a DP job may be triggered at this point if a determination is made that there are unprotected first backups.
  • the catalog entries for the first backup would be retained and not deleted to preserve file history.
  • the backup document would also be retained since this is necessary for application restore.
  • the original j ob id is always retained as part of the promoted job, since this is what needs to be reflected a part of the restore browse. If multiple DP jobs exist for a given first backup they all contain the original job id, which would point to the original ssfile.
  • This process should be relatively simple since a single pass through the catalog table would be all that is required during condensation.
  • Restore browse would return the $NDMPDATA from the original job instance for restore presentation.
  • the RJI process would also be enhanced to include file history from the original ssfile to create a proper restore specification. The process would involve producing the tape windows involved in the DP backup along with the restore path names from the original ssfile. The root directories (the only thing cataloged) in ssfile for the DP backup would be ignored.
  • DP tape backups being regular NDMP backups would show up under regular NDMP restores and can be used to restore directly to any compatible file system. In situations where the original secondary disk location is destroyed or corrupted these backups can be restored to original location to either recreate APM2D locations or to stage restores or effect virtualization. These restores can be handled by job handler as normal NDMP restores and can be part of a complete solution if no applications are involved.
  • a disaster recovery or full node backup of the secondary disk node is treated as a separate backup and may be used independently to restore the secondary in case of disaster.
  • the APM2D restore view would be unchanged, except for the fact that if DP backups exist for first backups they would not be displayed. For expired backups if DP backups exist they would show up and be presented as nearlined backups.
  • the restore browse process would need to be augmented to return NDMP backup instances as APM2D backups.
  • the restore selection would be passed on to SSSVH as today. (It is possible to create a NDMP restore job for application restore if job handler implements the restore side of APPH processing but this may be limited in terms of handling fault tolerance well.)
  • Protocol director After APPH has been contacted for application restore and the restore file list determined the Protocol director would try to cycle through available disk destinations in order to satisfy the restore selection. If this fails (first backups have expired or disk destinations are unreachable) a NDMP restore job from tape would be constructed and run via JOB_START (presumably run by job handler). Once this successfully completes APPH will again be contacted and the restore completed.
  • a primary volume may be mirrored onto a secondary volume in accordance with the following procedure:
  • the "lazy mirroring" technique may be used, for example, to restore a physical primary device after an "instantly available" virtual device has been utilized, for example, after the failure of a primary device.
  • the virtual device will be used temporarily, in that the data on it will be intact as of the point-in-time of its snapshot. However, the virtual device may be only a temporary solution, and the business will need to restore to a replacement primary device as soon as is feasible.
  • "Lazy Mirroring" provides this capability in a manner that allows processing to continue unintenupted, and allows the actual copying to proceed at its own pace while minimizing the load on other system components.
  • the "lazy mirroring” technique may also be advantageously used to "resilver” a mirror that has crashed or gone out of sync, while the primary mirror remains in production.
  • the "lazy mirror" technique may be used anywhere where it is desired to copy a volume without stopping it, and to do so without engaging in extraordinary measures to save time.
  • Such redundancy may be eliminated in a backup context by taking a digest of every block written to the backup data set, and putting the digest data in a list or database. Comparison of block digests is preferably performed on the server side.
  • a node to be backed up If a node to be backed up has a large number of blocks that have changed and need to be backed up, it sends a list of those blocks with their digests to the backup server (it may also be the case that the node has created in advance lists of block digests for some other purpose, such as determining which of its own blocks have changed, such that those digests do not have to involve a separate step to create them).
  • the server compares the block digests and requests those blocks for backup, which it has determined it does not already have (the list or database of blocks is stored in such a way as to facilitate rapid lookup using the digest as a key).
  • the complete list of blocks sent by the remote node is saved (including those sent over plus those that the server determined it already had), as part of the backup catalog.
  • the node being backed up has only a small number of changed blocks, it simply sends them in that circumstance and skips the redundancy check.
  • a similar technique is employed for eliminating redundancy in a single file system.
  • Each block to be written to the file system is digested, and compared against the digest of the blocks already stored (here again, the list or database of blocks is stored in such a way as to facilitate rapid lookup using the digest as a key). If the identical content block already exists on file system, the existing directory point is used and the duplicate block is not written. When a file are deleted, its blocks are deallocated from that file. If other files use the same block, those allocations remain in effect (a block is not "free" until no files reference it).
  • the examples illustrate the ability provided by the present invention to bring an application on-line quickly on a stand-by or original server by attaching to virtual storage created out of backup images on a filer, such as a NAS filer.
  • Consistent volume images from source nodes are nearlined with their associated application consistent state as backups, typically on NAS Filers. Users deal with application logical objects while the Backup Express agent creates hot base backups of physical objects that comprise the application. Forever Incremental Images ensure that only blocks changed since the last backup is copied to the filer without sacrificing the fact that all database backups are full. Since the application data and state is nearlined restore is affected very quickly by recovering a point in time copy of the application files, then bringing the application online and applying a small number of redo-log records. FAR recreates storage as it existed at the time of backup, establishing the physical relationships that the application logically expects and then recovering the application to a fully functional instance.
  • Application restore is broadly a two step process: data file(s) need to be restored followed by application recovery (sometimes known as roll-forward recovery).
  • the user selects an instance of backup or a PIT image (usually latest) depending on nature of disaster, type of user error or other business need.
  • the first step is accomplished by creating addressable virtual storage (LUNs) on the fly on the filer from the user selected PIT volume images. These LUNs are then made visible to the target node in question. These are then attached as local disks on the restore target via iSCSI login to the filer. This process is near instantaneous since no actual data movement is involved. Once application data files are visible in the local namespace of the target node, applications are then programmatically recovered using appropriate application specific API.
  • LUNs addressable virtual storage
  • FAR is not the end of the story. As FAR completes block change tracking may be enabled and local slice attachment may be done if needed. This enables background restore to proceed while the application is up and running. Incremental backups may be started from the point in time of restore since tracking of changed blocks is enabled. The application may eventually fail back to the original or another node with minimum downtime with all recent changes (since restore) preserved.
  • IV for APPs verifies application backups near-instantly by restoring (FAR) to an alternate verification node or the original node when possible. The application is then recovered to complete the process. This can be scheduled so that every backup is always checked for integrity and no additional fire-drills need to be performed for recreating disaster scenarios.
  • PIT Image Used Usually latest but could be images from the past if verification is batched.
  • Lightweight Verification The application (usually database) restarts/recovers correctly thus verifying correctness of backup.
  • SQL Server Mounting databases are usually a significant verification step. Further verification can be done via 'DBCC' or by running SQL queries.
  • Verification is a transient operation and an iSCSI logoff or reboot will clear the machine state.
  • IV for APPs may be configured so that the next verification run will clean up previous verification mappings. The machine state with mapped drives need not be preserved and thus no further backups are necessary of this alternate node.
  • FAR brings back the application instance on a stand-by or the original node near-instantly, minimizing down time.
  • the application state at the time of backup is restored. Changes made after the last backup is are lost unless the application logs are available (either salvaged from the original node or from some replicated location). If current application logs are available and subsequently applied the application can be rolled forward to the time of failure with no loss of data.
  • PIT Image Used Usually latest but depending on reason for disaster (for example: virus attack) an image preceding the event.
  • SQL Server Stand-by databases, replication, and/or log-shipping are expensive and administration intensive options for SQL Server availability.
  • FAR is an option that is easy to deploy with reduced administration cost combining the power of fast backups and quick availability on demand.
  • Redundant destination A high end filer (possibly at a remote site) can mirror the backup images stored on the original backup destination (for example, to tertiary storage). This configuration lends itself to restore being redirected to the high-end filer and not the original filer. Background restore to a local slice is not needed in this case as the filer storage would be high-end and permanent. Quality of restored storage:
  • the backup after restore could continue from the target machine or a NAS block-level backup maybe initiated since the storage has been effectively migrated to the NAS device.
  • the LUNs on the filer may be cloned to break their dependency from the original snapshots since permanent storage on the filer has been established with its own storage life-cycle.
  • PIT Image Used Depends on when a fine grain object was deleted or was in an uncorrupted state.
  • SQL Server Table level restore - 'bcp' or other tools may be used to restore tables from an alternate FARed instance.
  • PIT Image Used Usually staggered from the backup schedule and dictated by how many instances need to remain nearline.
  • Image backup to tape is performed of the FAR volume(s) (License needed). After successful backup iSCSI mappings are removed and the stage is set for the next cycle.
  • the LUNs will then be cloned (in the background) while the application is up and running to free them from the bondage of the snapshot containing them.
  • the snapshots can then be re-cycled to reclaim space.
  • Backup after restore (BAR) can then resume of the volumes backed by the LUN or of filer volumes or quota-trees containing the LUN.
  • Fig. 4 (A & B) illustrates an instant availability and recovery scenario that utilizes Instant Availability to virtually eliminate business interruption during the recovery process:
  • clause 2 may refer to the method of clause 1, further comprising backing up application-specific metadata.
  • clause 3 may refer to the method of clause 1, in which there is a software process for controlling backups, software for mediating application-specific interaction at the beginning and end of the backup, and snapshot handling software, further comprising the following steps: said controlling process sending a message to said mediating process to cause said snapshot handling software to snapshot the target set of volumes and flush change journals; snapshotting said target set of volumes to create a snapshot image; creating a content file for the backup specification; and sending said content file and snapshot image to a storage device under the control of said controlling process.
  • clause 4 may refer to the method of clause 1, wherein the data for said backup comprises a differential block level image and has a disk signature attached to beginning which has the appropriate information to virtualize the backup of a volume as a whole SCSI disk with a single valid partition.
  • clause 5 may refer to the method of clause 1 wherein said snapshotting step comprises talcing an internal snapshot for the purpose of flushing change journals and tracking changed blocks, followed by an external snapshot to produce a consistent snapshot image.
  • clause 6 may refer to an enterprise image destination for backup images created in accordance with the method of clause 1, wherein such images maybe consolidated, nearlined and versioned, comprising: one or more data storage units accessible by said enterprise image destination; software adapted for operating said enterprise image destination, said software comprising support for journaling FS with sparse file support for accommodating multiple persistent snapshots; interface providing support for LUN creation/deletion, LUN cloning, and snapshot creation and deletion; and a database associating snapshot IDs with block allocation bitmaps and incremental bitmaps.
  • clause 7 may refer to the enterprise image destination of clause 6 wherein one or more of said data storage units are provided by a storage device of a type selected from the group consisting of (i) shared storage, (ii) local copy to backup LUN, and (iii) network storage.
  • clause 8 may refer to the enterprise image destination of clause 6 wherein said interface is a plugin interface.
  • clause 9 may refer to the enterprise image destination of clause 6 wherein said interface further supports block-level mirroring.
  • clause 10 may refer to the method of clause 3, initiated by an enterprise image destination of clause 6 in order to create a backup image of a client node, further comprising steps effecting the following additional data flow: (1) establishing a connection with the corresponding software on the client node and passing to the client node a path to a content file; (2) with the software on the client node, reading and passing the content of the content file back to software on said enterprise image destination node.
  • clause 11 may refer to the method of clause 10 wherein one or more of said data storage units used by said enterprise image destination are provided by a storage device of a type selected from the group consisting of (i) shared storage, (ii) local copy to backup LUN, and (iii) network storage.
  • clause 12 may refer to the method of clause 10 wherein said storage unit comprises a network storage device, further comprising using software on said client node, reading allocated blocks from the local snapshot of the device to be backed up; sending said blocks across the network to the destination software on the enterprise image destination node; and using software on said enterprise destination node, reading from the channel of said network and writing the date read to a sparse file on a pre-defined volume on said network storage device.
  • said storage unit comprises a network storage device, further comprising using software on said client node, reading allocated blocks from the local snapshot of the device to be backed up; sending said blocks across the network to the destination software on the enterprise image destination node; and using software on said enterprise destination node, reading from the channel of said network and writing the date read to a sparse file on a pre-defined volume on said network storage device.
  • clause 13 may refer to a machine-readable medium containing a backup image of a primary storage unit created in accordance with clause 1.
  • clause 14 may refer to a method of creating a backup image of a machine-readable backup image as described in clause 13, comprising making a tertiary backup copy of said medium, wherein said tertiary backup copy is a full, complete and self-contained backup of the primary storage unit.
  • clause 15 may refer to a method of creating a tertiary backup image in accordance with clause 14 wherein said tertiary backup image is created on tape.
  • clause 16 may refer to a method of creating a tertiary backup image in accordance with clause 14 wherein the primary backup image is transformed to a logical backup in a portable format of the type selected from the group essentially consisting of tar, cpio, or pax.
  • clause 17 may refer to the method of clause 14 wherein said tertiary backup image is recorded on WORM tapes or a WORM drive.
  • clause 18 may refer to the method of clause 14 further comprising restoring data using the file history saved during creation of the primary backup image.
  • clause 19 may refer to a machine-readable medium containing a tertiary backup copy of a primary storage unit, created in accordance with clause 14.
  • clause 20 may refer to a method of creating or updating a tertiary backup image on a tertiary node from a primary backup image stored in a node constituting an enterprise image destination as described in clause 6, said method comprising using software on said enterprise image destination to contact said tertiary node and pass to it a message to request data from said enterprise image destination node; using software on said tertiary node to request said data; receiving said request at the enterprise image destination node and recognizing it as a request to create or update a tertiary backup image; designating the appropriate snapshot image using saved bitmaps; and sending the appropriate snapshot image to said tertiary node.
  • clause 21 may refer to a method of providing an immediately available restoration of a backup image created in accordance with clause 1, comprising creating and exposing a LUN within a snapshot to create a restore volume; and mapping the restore volume to the local namespace.
  • clause 22 may refer to a method of providing an immediately available restoration of a backup image created in accordance with clause 2, comprising creating and exposing a LUN within a snapshot to create a restore volume containing both backup data and application-specific metadata; and mapping the restore volume to the local namespace.
  • clause 23 may refer to the method of clause 22 wherein said backup image is a read-only image, further comprising transforming said image into an iSCSI addressable read-write LUN by creating a sparse file backed by said read-only backup image.
  • clause 24 may refer to a method of restoring a primary storage device capable of aggregating changes as well as retaining original unchanged data from said read-only backup image comprising mounting a LUN created in accordance with clause 22 and using said LUN as primary storage.
  • clause 25 may refer to a method of recovering an application or database comprising: performing a restore operation in accordance with clause 21; copying log files if necessary from the source volume to the restore volumes to recover said application or database.
  • Exemplary, clause 26 may refer to a method of rolling back a volume to an earlier state, comprising, addressing said volume by a unique job identifier and locking and dismounting the volume so addressed; taking a snapshot of said volume to flush the change journal; mapping said snapshot as a mountable volume; logically ANDing all change journals since the time of the desired state that is being restored to, to create a bitmap file; adding the contents of said the bitmap file to the content file associated with said snapshot; using said bitmap file to restore only a set of blocks from said mapped volume.
  • clause 27 may refer to the method of clause 23 wherein said target LUN is back-ended on a separate node, further comprising determining whether the back-end storage supports addressing in accordance with clause 26, and that the snapshot being restored from and the restore target LUN are logically related; and calling a back-end API with the identifier of the snapshot being restored and the target entity or LUN that back-ends the volume on the target node.
  • clause 28 may refer to the method of restoring a backup image created in accordance with clause 1, in operations under a virtualization server, on a virtual machine running on said server, comprising creating and exposing a LUN within a snapshot to create a restore volume; and mapping the restore volume to the local namespace of said virtual machine.
  • Exemplary, clause 29 may refer to a method for mirroring a primary volume onto a secondary volume, comprising: creating a list of blocks to be copied from the primary volume to the secondary volume; writing new blocks to both the primary and secondary volumes as they arrive; as blocks are written, removing those blocks from said list of blocks; traversing said list, and copying blocks encountered as a result of such traversal from the primary volume to the secondary volume; continuing the preceding two steps until all blocks on said list have been copied.
  • clause 30 may refer to a method for resilvering a mirror that has crashed or gone out of sync, from a primary mirror that remains in production, comprising mirroring said primary mirror to a new secondary mirror in accordance with the method of clause 29.
  • clause 31 may refer to a method of reducing redundancy in a primary data set being backed up on a changed block basis to a backup server used to back up a plurality of data sets, comprising taking a digest of each block that has changed in said primary data set; saving the digest data; comparing the block digests of said blocks to the digests of blocks previously saved by said server, and determining which blocks said server does not already have; sending to said server only those blocks that said server has determined that it does not already have, together with the associated digests; updating the collection of digests saved on said server by adding said associated digests; and constructing a catalog of said backup from the list of blocks sent to the backup server plus those blocks which said server determined that it already had.
  • Exemplary, clause 32 may refer to a method of reducing redundancy in a file system, comprising: taking a digest of each block as it is to be written to the file system; comparing the digest of said block with the digests of the blocks already stored in the file system; if the identical content block already exists on file system, using the existing directory pointer and not writing the duplicate block; when a file are deleted, deallocating the associated blocks from that file; and freeing any block when no files reference it.
  • Exemplary, clause 33 may refer to a method for rapidly restoring an application from a set of one or more backup images to a target node, comprising selecting said backup images; and creating addressable virtual storage LUNs from said images on an on-demand basis; making said LUNs visible to said target node; attaching said LUNs as local disks on the restore target via iSCSI protocols. programmatically recovering said application using appropriate application-specific APIs.
  • clause 34 may refer to the method of clause 33 for use in the case of recovery from a failure, further comprising applying application-specific log files to roll said restore operation forward to the point of failure.
  • clause 35 may refer to a method for rapidly verifying a backup of an application created in accordance with clause 1, comprising, rapidly restoring said backup in accordance with the method of clause 33 onto a machine running said application; verifying that said application restarts and recovers correctly.
  • clause 36 may refer to the method of clause 33, further comprising, using application specific techniques to verify that the application data is correct and that any logical objects of said application function properly.
  • clause 37 may refer to a method for effecting fine-grained partial restoration of a primary system, comprising: restoring said system in MI to an alternate node in accordance with the method of clause 33; using application-specific tools to extract the desired partial data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Emergency Protection Circuit Devices (AREA)
  • Retry When Errors Occur (AREA)
  • Hardware Redundancy (AREA)
  • Processing Or Creating Images (AREA)
  • Closed-Circuit Television Systems (AREA)
EP12001733.0A 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten Active EP2477114B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP13005349.9A EP2713271B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US69371505P 2005-06-24 2005-06-24
EP06785435A EP1907972B1 (de) 2005-06-24 2006-06-23 System und verfahren zum hochleistungs-unternehmens-datenschutz

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP06785435A Division EP1907972B1 (de) 2005-06-24 2006-06-23 System und verfahren zum hochleistungs-unternehmens-datenschutz
EP06785435.6 Division 2006-06-23

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP13005349.9A Division EP2713271B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten
EP13005349.9A Division-Into EP2713271B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten

Publications (3)

Publication Number Publication Date
EP2477114A2 true EP2477114A2 (de) 2012-07-18
EP2477114A3 EP2477114A3 (de) 2012-10-24
EP2477114B1 EP2477114B1 (de) 2014-01-15

Family

ID=37595877

Family Applications (4)

Application Number Title Priority Date Filing Date
EP06785435A Active EP1907972B1 (de) 2005-06-24 2006-06-23 System und verfahren zum hochleistungs-unternehmens-datenschutz
EP13005349.9A Active EP2713271B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten
EP12001733.0A Active EP2477114B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten
EP06785436A Active EP1907935B1 (de) 2005-06-24 2006-06-23 System und verfahren zum virtualisieren von backup-bildern

Family Applications Before (2)

Application Number Title Priority Date Filing Date
EP06785435A Active EP1907972B1 (de) 2005-06-24 2006-06-23 System und verfahren zum hochleistungs-unternehmens-datenschutz
EP13005349.9A Active EP2713271B1 (de) 2005-06-24 2006-06-23 System und Verfahren zum Hochleistungsschutz von Unternehmensdaten

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP06785436A Active EP1907935B1 (de) 2005-06-24 2006-06-23 System und verfahren zum virtualisieren von backup-bildern

Country Status (10)

Country Link
US (6) US8346726B2 (de)
EP (4) EP1907972B1 (de)
JP (4) JP2009506399A (de)
CN (3) CN101495970B (de)
AT (2) ATE555438T1 (de)
AU (2) AU2006262045B2 (de)
CA (3) CA2954888C (de)
DE (1) DE602006019875D1 (de)
HK (4) HK1119800A1 (de)
WO (2) WO2007002398A2 (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103176868A (zh) * 2013-04-02 2013-06-26 浪潮电子信息产业股份有限公司 一种文件状态备份方法
CN104375904A (zh) * 2014-10-30 2015-02-25 浪潮电子信息产业股份有限公司 一种基于快照差异化数据传输的容灾备份方法
WO2016064387A1 (en) * 2014-10-22 2016-04-28 Hewlett Packard Enterprise Development Lp Data restoration using block disk presentations

Families Citing this family (406)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009506399A (ja) * 2005-06-24 2009-02-12 シンクソート インコーポレイテッド バックアップイメージを仮想化するシステム及び方法
US9378099B2 (en) 2005-06-24 2016-06-28 Catalogic Software, Inc. Instant data center recovery
US7747831B2 (en) * 2006-03-20 2010-06-29 Emc Corporation High efficiency portable archive and data protection using a virtualization layer
US7831787B1 (en) 2006-03-20 2010-11-09 Emc Corporation High efficiency portable archive with virtualization
US8321377B2 (en) * 2006-04-17 2012-11-27 Microsoft Corporation Creating host-level application-consistent backups of virtual machines
US9235477B1 (en) * 2006-04-24 2016-01-12 Emc Corporation Virtualized backup solution
US9317222B1 (en) 2006-04-24 2016-04-19 Emc Corporation Centralized content addressed storage
US8065273B2 (en) * 2006-05-10 2011-11-22 Emc Corporation Automated priority restores
US9684739B1 (en) 2006-05-11 2017-06-20 EMC IP Holding Company LLC View generator for managing data storage
US8032351B2 (en) * 2006-11-30 2011-10-04 Symantec Corporation Running a virtual machine directly from a physical machine using snapshots
US9043391B2 (en) 2007-02-15 2015-05-26 Citrix Systems, Inc. Capturing and restoring session state of a machine without using memory images
US20080201455A1 (en) 2007-02-15 2008-08-21 Husain Syed M Amir Moving Execution of a Virtual Machine Across Different Virtualization Platforms
JP5246388B2 (ja) 2007-03-08 2013-07-24 日本電気株式会社 仮想装置構成システム、及びその方法
KR101506254B1 (ko) * 2007-04-02 2015-03-26 삼성전자 주식회사 무선 단말 장치 및 시스템 보호 방법
US7805631B2 (en) 2007-05-03 2010-09-28 Microsoft Corporation Bare metal recovery from backup media to virtual machine
JP2008293256A (ja) * 2007-05-24 2008-12-04 Nec Corp 冗長構成サーバシステムにおけるファイルバックアップ方法、プログラム、及び、冗長構成サーバシステム
US8166476B2 (en) * 2007-08-24 2012-04-24 Symantec Corporation On-demand access to a virtual representation of a physical computer system
US8793226B1 (en) * 2007-08-28 2014-07-29 Netapp, Inc. System and method for estimating duplicate data
US9507784B2 (en) * 2007-12-21 2016-11-29 Netapp, Inc. Selective extraction of information from a mirrored image file
US8639897B1 (en) * 2007-12-31 2014-01-28 Symantec Operating Corporation Method to restore application specific content from volume images
US20090210427A1 (en) * 2008-02-15 2009-08-20 Chris Eidler Secure Business Continuity and Disaster Recovery Platform for Multiple Protected Systems
JP5374056B2 (ja) * 2008-02-26 2013-12-25 株式会社バッファロー データ管理方法
JP4822024B2 (ja) * 2008-02-29 2011-11-24 日本電気株式会社 フォールトトレラントサーバ、フルバックアップ方法、およびフルバックアッププログラム
US8006116B1 (en) * 2008-03-31 2011-08-23 Symantec Corporation Systems and methods for storing health information with computing-system backups
US8051044B1 (en) * 2008-04-01 2011-11-01 Acronis, Inc. Method and system for continuous data protection
US8126847B1 (en) * 2008-04-30 2012-02-28 Network Appliance, Inc. Single file restore from image backup by using an independent block list for each file
US8200638B1 (en) 2008-04-30 2012-06-12 Netapp, Inc. Individual file restore from block-level incremental backups by using client-server backup protocol
US7890793B1 (en) * 2008-05-21 2011-02-15 Symantec Corporation Techniques for restoring file system resources
JP5075736B2 (ja) * 2008-05-27 2012-11-21 株式会社日立製作所 仮想サーバのシステム障害回復方法及びそのシステム
US8949187B1 (en) * 2008-05-30 2015-02-03 Symantec Corporation Systems and methods for creating and managing backups based on health information
US8862547B2 (en) * 2008-06-05 2014-10-14 Elm Technologies, Inc. Centralizing data backup records from multiple servers onto a central server
US8041678B2 (en) 2008-06-20 2011-10-18 Microsoft Corporation Integrated data availability and historical data protection
EP2291731A4 (de) * 2008-06-25 2013-01-02 Novell Inc Kopieren von arbeitslastdateien auf einen virtuellen datenträger
US8060476B1 (en) 2008-07-14 2011-11-15 Quest Software, Inc. Backup systems and methods for a virtual computing environment
US8725967B2 (en) * 2008-08-08 2014-05-13 Amazon Technologies, Inc. Providing executing programs with access to stored block data of others
US8239348B1 (en) * 2008-08-14 2012-08-07 Symantec Corporation Method and apparatus for automatically archiving data items from backup storage
US8150801B2 (en) 2008-08-20 2012-04-03 Microsoft Corporation Recovery of a computer that includes virtual disks
US8037032B2 (en) * 2008-08-25 2011-10-11 Vmware, Inc. Managing backups using virtual machines
US8615489B2 (en) * 2008-08-25 2013-12-24 Vmware, Inc. Storing block-level tracking information in the file system on the same block device
US8117410B2 (en) * 2008-08-25 2012-02-14 Vmware, Inc. Tracking block-level changes using snapshots
US8176272B2 (en) 2008-09-04 2012-05-08 International Business Machines Corporation Incremental backup using snapshot delta views
US8307177B2 (en) 2008-09-05 2012-11-06 Commvault Systems, Inc. Systems and methods for management of virtualization data
US8429649B1 (en) 2008-09-25 2013-04-23 Quest Software, Inc. Systems and methods for data management in a virtual computing environment
US8321860B2 (en) * 2008-10-27 2012-11-27 Bank Of America Corporation Local collector
US8549327B2 (en) * 2008-10-27 2013-10-01 Bank Of America Corporation Background service process for local collection of data in an electronic discovery system
US8499297B2 (en) 2008-10-28 2013-07-30 Vmware, Inc. Low overhead fault tolerance through hybrid checkpointing and replay
US8473697B1 (en) 2008-10-29 2013-06-25 Netapp, Inc. Method and system for volume based snapshot restore
EP2300921B1 (de) 2008-10-30 2011-11-30 International Business Machines Corporation Flashcopy-handling
CN101739287A (zh) * 2008-11-13 2010-06-16 国际商业机器公司 管理虚拟机的装置、系统和方法
CN101408856A (zh) * 2008-11-21 2009-04-15 清华大学 一种用于容灾备份的系统和方法
US8145607B1 (en) * 2008-12-09 2012-03-27 Acronis Inc. System and method for online backup and restore of MS exchange server
US8898108B2 (en) * 2009-01-14 2014-11-25 Vmware, Inc. System and method for scheduling data storage replication over a network
US7996708B1 (en) * 2009-03-16 2011-08-09 Symantec Corporation Techniques for file system resource restoration
JP5206864B2 (ja) * 2009-03-18 2013-06-12 富士通株式会社 更新プログラム、情報処理装置、および更新方法
JP5352299B2 (ja) * 2009-03-19 2013-11-27 株式会社日立製作所 高信頼性計算機システムおよびその構成方法
US9207984B2 (en) 2009-03-31 2015-12-08 Amazon Technologies, Inc. Monitoring and automatic scaling of data volumes
US8713060B2 (en) 2009-03-31 2014-04-29 Amazon Technologies, Inc. Control service for relational data management
US8332365B2 (en) 2009-03-31 2012-12-11 Amazon Technologies, Inc. Cloning and recovery of data volumes
US9705888B2 (en) 2009-03-31 2017-07-11 Amazon Technologies, Inc. Managing security groups for data instances
US8996468B1 (en) 2009-04-17 2015-03-31 Dell Software Inc. Block status mapping system for reducing virtual machine backup storage
US8074038B2 (en) * 2009-05-12 2011-12-06 Microsoft Corporation Converting luns into files or files into luns in real time
JP5227887B2 (ja) * 2009-05-21 2013-07-03 株式会社日立製作所 バックアップ管理方法
US9201485B2 (en) * 2009-05-29 2015-12-01 Red Hat, Inc. Power management in managed network having hardware based and virtual resources
US20100306177A1 (en) * 2009-05-29 2010-12-02 Khosravi Hormuzd M Host operating system independent storage-related remote access and operations
US8504529B1 (en) 2009-06-19 2013-08-06 Netapp, Inc. System and method for restoring data to a storage device based on a backup image
US8307175B2 (en) * 2009-06-26 2012-11-06 Intel Corporation Data recovery and overwrite independent of operating system
US8732427B2 (en) * 2009-08-03 2014-05-20 Quantum Corporation Systems and methods for collapsing a derivative version of a primary storage volume
US9778946B2 (en) 2009-08-07 2017-10-03 Dell Software Inc. Optimized copy of virtual machine storage files
US8438349B2 (en) * 2009-08-21 2013-05-07 Symantec Corporation Proxy backup of virtual disk image files on NAS devices
JP4990332B2 (ja) * 2009-08-25 2012-08-01 株式会社日立製作所 データバックアップ管理システム、計算機システム及びプログラム記録媒体
CN102012789B (zh) * 2009-09-07 2014-03-12 云端容灾有限公司 集中管理式备份容灾系统
US8386731B2 (en) * 2009-09-14 2013-02-26 Vmware, Inc. Method and system for optimizing live migration of persistent data of virtual machine using disk I/O heuristics
US8412678B2 (en) * 2009-09-16 2013-04-02 Strategic Technologies, Inc. Systems and methods for providing business continuity services
US8774142B2 (en) * 2009-09-16 2014-07-08 Samsung Electronics Co., Ltd. Flexible and integrated frame structure design for supporting multiple topologies with visible light communication
CN101661415B (zh) * 2009-09-21 2012-07-11 中兴通讯股份有限公司 一种保存快照数据的方法及存储快照系统
US8862848B2 (en) 2009-09-24 2014-10-14 International Business Machines Corporation Data storage using bitmaps
CN102511036B (zh) 2009-09-25 2015-09-30 国际商业机器公司 数据存储
US9135283B2 (en) 2009-10-07 2015-09-15 Amazon Technologies, Inc. Self-service configuration for data environment
WO2011046813A2 (en) 2009-10-12 2011-04-21 Veeam Software International Ltd. Item-level restoration and verification of image level backups
US8150808B2 (en) 2009-10-21 2012-04-03 Delphix Corp. Virtual database system
US8161077B2 (en) 2009-10-21 2012-04-17 Delphix Corp. Datacenter workflow automation scenarios using virtual databases
CN101694635B (zh) * 2009-10-22 2013-10-16 中兴通讯股份有限公司 基于虚拟磁带库备份的控制方法、系统及近线存储节点
US8074107B2 (en) 2009-10-26 2011-12-06 Amazon Technologies, Inc. Failover and recovery for replicated data instances
US8335765B2 (en) 2009-10-26 2012-12-18 Amazon Technologies, Inc. Provisioning and managing replicated data instances
US8676753B2 (en) 2009-10-26 2014-03-18 Amazon Technologies, Inc. Monitoring of replicated data instances
US8930652B2 (en) * 2009-11-11 2015-01-06 Red Hat Israel, Ltd. Method for obtaining a snapshot image of a disk shared by multiple virtual machines
US8639769B2 (en) * 2009-12-18 2014-01-28 International Business Machines Corporation Handling of data transfer in a LAN-free environment
US8204863B2 (en) 2009-12-21 2012-06-19 International Business Machines Corporation Multi-phase file system restore with selective on-demand data availability
US8341122B2 (en) 2009-12-22 2012-12-25 International Business Machines Corporation Restore of full system backup and incremental backups using multiple simultaneous device streams
US9098456B2 (en) * 2010-01-13 2015-08-04 International Business Machines Corporation System and method for reducing latency time with cloud services
US9032243B2 (en) * 2010-01-27 2015-05-12 International Business Machines Corporation Target operating system and file system agnostic bare-metal restore
US8751738B2 (en) 2010-02-08 2014-06-10 Microsoft Corporation Background migration of virtual storage
US9015129B2 (en) * 2010-02-09 2015-04-21 Veeam Software Ag Cross-platform object level restoration from image level backups
US8533411B2 (en) * 2010-03-11 2013-09-10 International Business Machines Corporation Multiple backup processes
US8346727B1 (en) * 2010-03-15 2013-01-01 Symantec Corporation Optimized image archiving
US8793447B2 (en) * 2010-03-30 2014-07-29 Netapp, Inc. Restoration of a parent LUN through modification of a read-write clone LUN as the parent LUN
US8407517B2 (en) 2010-04-08 2013-03-26 Hitachi, Ltd. Methods and apparatus for managing error codes for storage systems coupled with external storage systems
US20110252208A1 (en) * 2010-04-12 2011-10-13 Microsoft Corporation Express-full backup of a cluster shared virtual machine
US9684573B2 (en) * 2010-04-29 2017-06-20 Veritas Technologies Llc Dismounting a storage volume
US8453145B1 (en) 2010-05-06 2013-05-28 Quest Software, Inc. Systems and methods for instant provisioning of virtual machine files
US8788770B2 (en) 2010-05-25 2014-07-22 International Business Machines Corporation Multiple cascaded backup process
US11449394B2 (en) 2010-06-04 2022-09-20 Commvault Systems, Inc. Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources
US9569446B1 (en) * 2010-06-08 2017-02-14 Dell Software Inc. Cataloging system for image-based backup
US9507670B2 (en) 2010-06-14 2016-11-29 Veeam Software Ag Selective processing of file system objects for image level backups
US8560825B2 (en) * 2010-06-30 2013-10-15 International Business Machines Corporation Streaming virtual machine boot services over a network
US8548944B2 (en) 2010-07-15 2013-10-01 Delphix Corp. De-duplication based backup of file systems
US8782434B1 (en) 2010-07-15 2014-07-15 The Research Foundation For The State University Of New York System and method for validating program execution at run-time
US8566640B2 (en) * 2010-07-19 2013-10-22 Veeam Software Ag Systems, methods, and computer program products for instant recovery of image level backups
US9547562B1 (en) * 2010-08-11 2017-01-17 Dell Software Inc. Boot restore system for rapidly restoring virtual machine backups
US8438299B2 (en) 2010-08-17 2013-05-07 Computer Associates Think, Inc. Generic data collection plugin and configuration file language for SMI-S based agents
CN102375696A (zh) * 2010-08-20 2012-03-14 英业达股份有限公司 利用虚拟磁盘的数据存储系统与数据存取方法
US8898114B1 (en) 2010-08-27 2014-11-25 Dell Software Inc. Multitier deduplication systems and methods
US8694745B2 (en) * 2010-09-15 2014-04-08 Symantec Corporation Physical to virtual disks creation (P2V) method, by harvesting data from critical sectors
US8666944B2 (en) * 2010-09-29 2014-03-04 Symantec Corporation Method and system of performing a granular restore of a database from a differential backup
US8620870B2 (en) 2010-09-30 2013-12-31 Commvault Systems, Inc. Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system
US9110727B2 (en) * 2010-10-05 2015-08-18 Unisys Corporation Automatic replication of virtual machines
US8417672B2 (en) * 2010-10-11 2013-04-09 Microsoft Corporation Item level recovery
US8402004B2 (en) 2010-11-16 2013-03-19 Actifio, Inc. System and method for creating deduplicated copies of data by tracking temporal relationships among copies and by ingesting difference data
US8843489B2 (en) 2010-11-16 2014-09-23 Actifio, Inc. System and method for managing deduplicated copies of data using temporal relationships among copies
US8904126B2 (en) 2010-11-16 2014-12-02 Actifio, Inc. System and method for performing a plurality of prescribed data management functions in a manner that reduces redundant access operations to primary storage
US9858155B2 (en) 2010-11-16 2018-01-02 Actifio, Inc. System and method for managing data with service level agreements that may specify non-uniform copying of data
US8417674B2 (en) 2010-11-16 2013-04-09 Actifio, Inc. System and method for creating deduplicated copies of data by sending difference data between near-neighbor temporal states
US8818955B2 (en) * 2010-11-17 2014-08-26 International Business Machines Corporation Reducing storage costs associated with backing up a database
US8468174B1 (en) 2010-11-30 2013-06-18 Jedidiah Yueh Interfacing with a virtual database system
US8676762B2 (en) 2010-12-08 2014-03-18 International Business Machines Corporation Efficient backup and restore of a cluster aware virtual input/output server (VIOS) within a VIOS cluster
US8392378B2 (en) 2010-12-09 2013-03-05 International Business Machines Corporation Efficient backup and restore of virtual input/output server (VIOS) cluster
US9971656B2 (en) * 2010-12-13 2018-05-15 International Business Machines Corporation Instant data restoration
US8380955B1 (en) * 2010-12-23 2013-02-19 Netapp, Inc. Method and system for naming replicated storage
CN102063347B (zh) * 2010-12-28 2013-01-09 中国工商银行股份有限公司 一种磁带数据恢复方法及系统
US9430330B1 (en) * 2010-12-29 2016-08-30 Netapp, Inc. System and method for managing environment metadata during data backups to a storage system
US8635187B2 (en) * 2011-01-07 2014-01-21 Symantec Corporation Method and system of performing incremental SQL server database backups
US8738883B2 (en) * 2011-01-19 2014-05-27 Quantum Corporation Snapshot creation from block lists
US9311324B2 (en) * 2011-01-26 2016-04-12 Mitre Corporation Synchronizing data among a federation of servers with intermittent or low signal bandwidth
CN102622282B (zh) * 2011-01-28 2014-09-10 国际商业机器公司 一种虚拟主机中配置虚拟存储设备镜像的方法和系统
US8819190B2 (en) * 2011-03-24 2014-08-26 International Business Machines Corporation Management of file images in a virtual environment
JP5776267B2 (ja) * 2011-03-29 2015-09-09 日本電気株式会社 分散ファイルシステム
JP5501280B2 (ja) * 2011-03-31 2014-05-21 株式会社日立ソリューションズ 情報処理システム、バックアップ管理方法、及びプログラム
US10585766B2 (en) * 2011-06-06 2020-03-10 Microsoft Technology Licensing, Llc Automatic configuration of a recovery service
US10387267B2 (en) * 2011-06-08 2019-08-20 International Business Machines Corporation Fast copy using file system block mappings
US8745004B1 (en) * 2011-06-24 2014-06-03 Emc Corporation Reverting an old snapshot on a production volume without a full sweep
US8849777B1 (en) 2011-06-30 2014-09-30 Emc Corporation File deletion detection in key value databases for virtual backups
US9229951B1 (en) 2011-06-30 2016-01-05 Emc Corporation Key value databases for virtual backups
US9158632B1 (en) 2011-06-30 2015-10-13 Emc Corporation Efficient file browsing using key value databases for virtual backups
US9311327B1 (en) 2011-06-30 2016-04-12 Emc Corporation Updating key value databases for virtual backups
US8671075B1 (en) 2011-06-30 2014-03-11 Emc Corporation Change tracking indices in virtual machines
US8949829B1 (en) * 2011-06-30 2015-02-03 Emc Corporation Virtual machine disaster recovery
US8843443B1 (en) 2011-06-30 2014-09-23 Emc Corporation Efficient backup of virtual data
US8849769B1 (en) 2011-06-30 2014-09-30 Emc Corporation Virtual machine file level recovery
GB201111975D0 (en) 2011-07-13 2011-08-31 Centrix Software Ltd Modelling virtualized infrastructure
US8983915B2 (en) 2011-08-01 2015-03-17 Actifio, Inc. Successive data fingerprinting for copy accuracy assurance
US8832035B2 (en) 2011-08-30 2014-09-09 Netapp, Inc. System and method for retaining deduplication in a storage object after a clone split operation
US9063822B2 (en) 2011-09-02 2015-06-23 Microsoft Technology Licensing, Llc Efficient application-aware disaster recovery
US9092153B2 (en) * 2011-09-14 2015-07-28 Hitachi, Ltd. Method for creating clone file, and file system adopting the same
US9003139B1 (en) * 2011-09-15 2015-04-07 Symantec Corporation Systems and methods for recovering virtual machines after disaster scenarios
US8868860B2 (en) 2011-09-23 2014-10-21 International Business Machines Corporation Restore in cascaded copy environment
US9128973B1 (en) 2011-09-29 2015-09-08 Emc Corporation Method and system for tracking re-sizing and re-creation of volumes using modification time
US9959278B1 (en) * 2011-09-29 2018-05-01 EMC IP Holding Company LLC Method and system for supporting block-level incremental backups of file system volumes using volume pseudo devices
US9116633B2 (en) 2011-09-30 2015-08-25 Commvault Systems, Inc. Information management of virtual machines having mapped storage devices
US9461881B2 (en) 2011-09-30 2016-10-04 Commvault Systems, Inc. Migration of existing computing systems to cloud computing sites or virtual machines
US8719523B2 (en) 2011-10-03 2014-05-06 International Business Machines Corporation Maintaining multiple target copies
CN103428232B (zh) * 2012-05-16 2018-07-24 天津书生云科技有限公司 一种大数据存储系统
JP5735124B2 (ja) * 2011-10-28 2015-06-17 株式会社日立製作所 ストレージシステム、及びオブジェクト管理方法
EP2788875A2 (de) * 2011-12-05 2014-10-15 Persistent Telecom Solutions, Inc. Universelles einsteckbares notfallwiederherstellungssystem für clouds
US8776058B2 (en) * 2011-12-11 2014-07-08 International Business Machines Corporation Dynamic generation of VM instance at time of invocation
US9235589B2 (en) * 2011-12-13 2016-01-12 International Business Machines Corporation Optimizing storage allocation in a virtual desktop environment
US9471243B2 (en) * 2011-12-15 2016-10-18 Veritas Technologies Llc Dynamic storage tiering in a virtual environment
US9158828B1 (en) * 2011-12-19 2015-10-13 Emc Corporation Techniques using associated object properties
US9098452B2 (en) 2011-12-19 2015-08-04 International Business Machines Corporation Selecting files to backup in a block level backup
US8527479B2 (en) 2011-12-21 2013-09-03 International Business Machines Corporation Determining whether a selected backup set satisfies a retention policy
US9372910B2 (en) * 2012-01-04 2016-06-21 International Business Machines Corporation Managing remote data replication
US9208007B2 (en) * 2012-01-18 2015-12-08 International Business Machines Corporation Open resilience framework for simplified and coordinated orchestration of multiple availability managers
US8990164B1 (en) * 2012-02-01 2015-03-24 Symantec Corporation Systems and methods for performing incremental backups
US9311375B1 (en) 2012-02-07 2016-04-12 Dell Software Inc. Systems and methods for compacting a virtual machine file
US9043567B1 (en) * 2012-03-28 2015-05-26 Netapp, Inc. Methods and systems for replicating an expandable storage volume
US9069710B1 (en) 2012-03-28 2015-06-30 Netapp, Inc. Methods and systems for replicating an expandable storage volume
CN103365741B (zh) * 2012-03-30 2016-05-04 伊姆西公司 用于虚拟机集群的快照和恢复的方法和设备
US8639665B2 (en) 2012-04-04 2014-01-28 International Business Machines Corporation Hybrid backup and restore of very large file system using metadata image backup and traditional backup
US8966318B1 (en) * 2012-04-27 2015-02-24 Symantec Corporation Method to validate availability of applications within a backup image
AU2013277351A1 (en) 2012-06-18 2015-01-22 Actifio, Inc. Enhanced data management virtualization system
CN103514222B (zh) * 2012-06-29 2017-09-19 无锡江南计算技术研究所 虚拟机映像的存储方法、管理方法、存储管理装置及系统
JP5970984B2 (ja) 2012-07-03 2016-08-17 富士通株式会社 復元プログラムおよび復元装置
US20140019421A1 (en) * 2012-07-13 2014-01-16 Apple Inc. Shared Architecture for Database Systems
EP2891066A4 (de) * 2012-08-31 2016-04-20 Hewlett Packard Development Co Auswahl einer ressource zur verwendung in einer datensicherungs- oder datenwiederherstellungsoperation
US20140068040A1 (en) * 2012-09-04 2014-03-06 Bank Of America Corporation System for Enabling Server Maintenance Using Snapshots
US9697093B2 (en) 2012-09-05 2017-07-04 Veritas Technologies Llc Techniques for recovering a virtual machine
US9047108B1 (en) * 2012-09-07 2015-06-02 Symantec Corporation Systems and methods for migrating replicated virtual machine disks
US8805789B2 (en) 2012-09-12 2014-08-12 International Business Machines Corporation Using a metadata image of a file system and archive instance to backup data objects in the file system
US8914334B2 (en) 2012-09-12 2014-12-16 International Business Machines Corporation Using a metadata image of a file system and archive instance to restore data objects in the file system
US9063721B2 (en) 2012-09-14 2015-06-23 The Research Foundation For The State University Of New York Continuous run-time validation of program execution: a practical approach
WO2014049691A1 (ja) * 2012-09-25 2014-04-03 株式会社東芝 情報処理システム
US9069782B2 (en) 2012-10-01 2015-06-30 The Research Foundation For The State University Of New York System and method for security and privacy aware virtual machine checkpointing
US8788461B2 (en) 2012-10-04 2014-07-22 Delphix Corp. Creating validated database snapshots for provisioning virtual databases
US10346369B2 (en) 2012-10-11 2019-07-09 Delphix Corp. Retrieving point-in-time copies of a source database for creating virtual databases
US11126418B2 (en) * 2012-10-11 2021-09-21 Mcafee, Llc Efficient shared image deployment
US9372760B1 (en) * 2012-10-19 2016-06-21 Veritas Technologies Llc Systems and methods for securely storing backup data while facilitating fast failovers
US9354907B1 (en) 2012-10-26 2016-05-31 Veritas Technologies Llc Optimized restore of virtual machine and virtual disk data
US10635128B1 (en) * 2012-10-29 2020-04-28 Veritas Technologies Llc Storing backup data using snapshots
US9282166B2 (en) 2012-11-29 2016-03-08 International Business Machines Corporation Management infrastructure analysis for cloud migration
US9292330B2 (en) 2012-11-29 2016-03-22 International Business Machines Corporation Replacing virtual machine disks
US9742873B2 (en) 2012-11-29 2017-08-22 International Business Machines Corporation Adjustment to managed-infrastructure-as-a-service cloud standard
US9092837B2 (en) * 2012-11-29 2015-07-28 International Business Machines Corporation Use of snapshots to reduce risk in migration to a standard virtualized environment
US9110762B2 (en) * 2012-12-04 2015-08-18 Microsoft Technology Licensing, Llc Virtual machine-preserving host updates
US9563628B1 (en) * 2012-12-11 2017-02-07 EMC IP Holding Company LLC Method and system for deletion handling for incremental file migration
JP2014123183A (ja) 2012-12-20 2014-07-03 Fujitsu Ltd ストレージ装置、領域解放プログラム、および領域解放方法
US9286086B2 (en) 2012-12-21 2016-03-15 Commvault Systems, Inc. Archiving virtual machines in a data storage system
US20140181046A1 (en) 2012-12-21 2014-06-26 Commvault Systems, Inc. Systems and methods to backup unprotected virtual machines
US9378035B2 (en) 2012-12-28 2016-06-28 Commvault Systems, Inc. Systems and methods for repurposing virtual machines
US20140196039A1 (en) 2013-01-08 2014-07-10 Commvault Systems, Inc. Virtual machine categorization system and method
CN104937570A (zh) * 2013-01-29 2015-09-23 惠普发展公司，有限责任合伙企业 从原始图像备份数据恢复文件系统对象
US9002798B1 (en) * 2013-02-11 2015-04-07 Symantec Corporation Systems and methods for remedying corrupt backup images of host devices
US20140229695A1 (en) * 2013-02-13 2014-08-14 Dell Products L.P. Systems and methods for backup in scale-out storage clusters
KR101544899B1 (ko) 2013-02-14 2015-08-17 주식회사 케이티 가상화 환경 백업 시스템 및 그 방법
US20140250077A1 (en) * 2013-03-01 2014-09-04 Storagecraft Technology Corporation Deduplication vault storage seeding
US9430333B2 (en) * 2013-03-14 2016-08-30 Microsoft Technology Licensing, Llc Recovery of application from snapshot
JP2014191752A (ja) * 2013-03-28 2014-10-06 Fujitsu Ltd マイグレーション処理プログラム，マイグレーション方法及びクラウドシステム
US9786197B2 (en) 2013-05-09 2017-10-10 Rockwell Automation Technologies, Inc. Using cloud-based data to facilitate enhancing performance in connection with an industrial automation system
US9646067B2 (en) 2013-05-14 2017-05-09 Actifio, Inc. Garbage collection predictions
US10157107B2 (en) * 2013-07-03 2018-12-18 Catalogic Software, Inc. Data backup and progressive restoration using data chunks in cloud storage and a data cache
US9436556B2 (en) 2013-07-09 2016-09-06 Delphix Corp. Customizable storage system for virtual databases
JP6050917B2 (ja) * 2013-07-09 2016-12-21 デルフィクス コーポレーション 仮想データベースの巻き戻し
US10108685B2 (en) 2013-07-09 2018-10-23 Delphix Corp. Remote provisioning of virtual databases
US9354908B2 (en) 2013-07-17 2016-05-31 Veritas Technologies, LLC Instantly restoring virtual machines by providing read/write access to virtual disk before the virtual disk is completely restored
US9710386B1 (en) 2013-08-07 2017-07-18 Veritas Technologies Systems and methods for prefetching subsequent data segments in response to determining that requests for data originate from a sequential-access computing job
US9053216B1 (en) 2013-08-09 2015-06-09 Datto, Inc. CPU register assisted virtual machine screenshot capture timing apparatuses, methods and systems
US9092248B1 (en) * 2013-08-21 2015-07-28 Symantec Corporation Systems and methods for restoring distributed applications within virtual data centers
US10789136B1 (en) * 2013-08-23 2020-09-29 Acronis International Gmbh Granular recovery using hot-plug virtual disks
US20160048428A1 (en) * 2013-09-04 2016-02-18 DataGravity, Inc. Thin provisioned clone
US9939981B2 (en) 2013-09-12 2018-04-10 Commvault Systems, Inc. File manager integration with virtualization in an information management system with an enhanced storage manager, including user control and storage management of virtual machines
US10061653B1 (en) * 2013-09-23 2018-08-28 EMC IP Holding Company LLC Method to expose files on top of a virtual volume
GB2518452A (en) 2013-09-24 2015-03-25 Ibm Method for file recovery and client server system
US10614047B1 (en) * 2013-09-24 2020-04-07 EMC IP Holding Company LLC Proxy-based backup and restore of hyper-V cluster shared volumes (CSV)
US20150127770A1 (en) * 2013-11-06 2015-05-07 Pax8, Inc. Distributed Cloud Disk Service Provisioning and Management
US9665437B2 (en) 2013-11-18 2017-05-30 Actifio, Inc. Test-and-development workflow automation
US10157014B1 (en) 2013-12-16 2018-12-18 EMC IP Holding Company LLC Maintaining backup snapshots on deduplicated storage using continuous replication
US9377964B2 (en) * 2013-12-30 2016-06-28 Veritas Technologies Llc Systems and methods for improving snapshot performance
CN103713970B (zh) * 2013-12-31 2017-02-15 曙光云计算技术有限公司 一种基于虚拟机的磁盘镜像文件快照的制作方法和系统
US9354979B2 (en) 2014-02-07 2016-05-31 International Business Machines Corporation Server based disaster recovery by making use of dual write responses
US9720778B2 (en) 2014-02-14 2017-08-01 Actifio, Inc. Local area network free data movement
CN103780433B (zh) * 2014-02-18 2017-05-24 成都致云科技有限公司 自愈式虚拟资源配置管理数据架构
US10169121B2 (en) 2014-02-27 2019-01-01 Commvault Systems, Inc. Work flow management for an information management system
US20150269029A1 (en) * 2014-03-20 2015-09-24 Unitrends, Inc. Immediate Recovery of an Application from File Based Backups
US9348827B1 (en) * 2014-03-27 2016-05-24 Emc Corporation File-based snapshots for block-based backups
US9411821B1 (en) * 2014-03-27 2016-08-09 Emc Corporation Block-based backups for sub-file modifications
US9329889B2 (en) * 2014-03-31 2016-05-03 Vmware, Inc. Rapid creation and reconfiguration of virtual machines on hosts
US20150278032A1 (en) * 2014-04-01 2015-10-01 Ca, Inc. Providing services on system being recovered
US9811427B2 (en) 2014-04-02 2017-11-07 Commvault Systems, Inc. Information management by a media agent in the absence of communications with a storage manager
US10037204B2 (en) 2014-04-22 2018-07-31 Delphix Corp. Version control of applications
US10284645B1 (en) * 2014-05-06 2019-05-07 Veritas Technologies Llc Backup from network attached storage to sequential access media in network data management protocol environments
US9792187B2 (en) 2014-05-06 2017-10-17 Actifio, Inc. Facilitating test failover using a thin provisioned virtual machine created from a snapshot
US9454439B2 (en) 2014-05-28 2016-09-27 Unitrends, Inc. Disaster recovery validation
US9594636B2 (en) * 2014-05-30 2017-03-14 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
WO2015195834A1 (en) 2014-06-17 2015-12-23 Rangasamy Govind Resiliency director
US9607004B2 (en) 2014-06-18 2017-03-28 International Business Machines Corporation Storage device data migration
US9619342B2 (en) * 2014-06-24 2017-04-11 International Business Machines Corporation Back up and recovery in virtual machine environments
US9448834B2 (en) 2014-06-27 2016-09-20 Unitrends, Inc. Automated testing of physical servers using a virtual machine
US9600487B1 (en) * 2014-06-30 2017-03-21 EMC IP Holding Company LLC Self healing and restartable multi-steam data backup
US20160019317A1 (en) 2014-07-16 2016-01-21 Commvault Systems, Inc. Volume or virtual machine level backup and generating placeholders for virtual machine files
US9442715B2 (en) * 2014-07-28 2016-09-13 Microsoft Technology Licensing, Llc Patch process ensuring high availability of cloud application
JP5975473B2 (ja) 2014-08-29 2016-08-23 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ バックアップ方法、リストア方法、ストレージ・システムおよびプログラム
US10042710B2 (en) 2014-09-16 2018-08-07 Actifio, Inc. System and method for multi-hop data backup
US10379963B2 (en) 2014-09-16 2019-08-13 Actifio, Inc. Methods and apparatus for managing a large-scale environment of copy data management appliances
CN105573859A (zh) * 2014-10-15 2016-05-11 中兴通讯股份有限公司 一种数据库的数据恢复方法和设备
CN104503863B (zh) * 2014-11-07 2017-08-11 清华大学 用于虚拟容器系统容灾的内核态与用户态数据交换方法
US10776209B2 (en) 2014-11-10 2020-09-15 Commvault Systems, Inc. Cross-platform virtual machine backup and replication
US9983936B2 (en) 2014-11-20 2018-05-29 Commvault Systems, Inc. Virtual machine change block tracking
US10140188B2 (en) * 2014-11-26 2018-11-27 ArcServe (USA) LLC Snapshot management
US10445187B2 (en) 2014-12-12 2019-10-15 Actifio, Inc. Searching and indexing of backup data sets
US9880904B2 (en) * 2014-12-12 2018-01-30 Ca, Inc. Supporting multiple backup applications using a single change tracker
US9870289B2 (en) * 2014-12-12 2018-01-16 Ca, Inc. Notifying a backup application of a backup key change
US10101908B1 (en) * 2014-12-18 2018-10-16 EMC IP Holding Company LLC Dynamic staging model
US10289495B1 (en) * 2014-12-19 2019-05-14 EMC IP Holding Company LLC Method and system for performing an item level restore from a backup
WO2016115135A1 (en) 2015-01-12 2016-07-21 Xiangdong Zhang Disk group based backup
US10459802B2 (en) 2015-01-30 2019-10-29 Hewlett-Packard Development Company, L.P. Backup image restore
US9600193B2 (en) 2015-02-04 2017-03-21 Delphix Corporation Replicating snapshots from a source storage system to a target storage system
US10083196B2 (en) 2015-02-04 2018-09-25 Delphix Corporation Creating secure virtual databases storing masked data
US9990366B2 (en) 2015-03-13 2018-06-05 Delphix Corporation Virtual partitions in virtual databases
US11243505B2 (en) 2015-03-16 2022-02-08 Rockwell Automation Technologies, Inc. Cloud-based analytics for industrial automation
US10496061B2 (en) 2015-03-16 2019-12-03 Rockwell Automation Technologies, Inc. Modeling of an industrial automation environment in the cloud
US11513477B2 (en) 2015-03-16 2022-11-29 Rockwell Automation Technologies, Inc. Cloud-based industrial controller
US9940205B2 (en) * 2015-03-27 2018-04-10 EMC IP Holding Company LLC Virtual point in time access between snapshots
US10282201B2 (en) 2015-04-30 2019-05-07 Actifo, Inc. Data provisioning techniques
WO2016186617A1 (en) * 2015-05-15 2016-11-24 Hewlett-Packard Development Company, L.P. Data copying
US10084873B2 (en) 2015-06-19 2018-09-25 Commvault Systems, Inc. Assignment of data agent proxies for executing virtual-machine secondary copy operations including streaming backup jobs
US9563514B2 (en) 2015-06-19 2017-02-07 Commvault Systems, Inc. Assignment of proxies for virtual-machine secondary copy operations including streaming backup jobs
US9703641B1 (en) 2015-06-26 2017-07-11 EMC IP Holding Company LLC Unified protection of cluster suite
US10691659B2 (en) 2015-07-01 2020-06-23 Actifio, Inc. Integrating copy data tokens with source code repositories
US10613938B2 (en) 2015-07-01 2020-04-07 Actifio, Inc. Data virtualization using copy data tokens
WO2017027052A1 (en) * 2015-08-08 2017-02-16 Hewlett-Packard Development Company, L.P. Data restoration
US10558480B2 (en) * 2015-09-10 2020-02-11 Veritas Technologies Llc Optimizing access to production data
US10802928B2 (en) 2015-09-10 2020-10-13 International Business Machines Corporation Backup and restoration of file system
CN106547759B (zh) * 2015-09-17 2020-05-22 伊姆西Ip控股有限责任公司 用于选择增量备份方式的方法和装置
US10146631B1 (en) * 2015-09-30 2018-12-04 EMC IP Holding Company LLC Incremental forever backups for exchange
US10846195B2 (en) * 2015-10-05 2020-11-24 Unisys Corporation Configuring logging in non-emulated environment using commands and configuration in emulated environment
US9983933B2 (en) 2015-10-15 2018-05-29 International Business Machines Corporation Accelerating system dump capturing
US10127055B2 (en) * 2015-10-16 2018-11-13 Quanta Computer Inc. iSCSI based bare metal OS image deployment and diskless boot
US10157103B2 (en) 2015-10-20 2018-12-18 Veeam Software Ag Efficient processing of file system objects for image level backups
US10102138B2 (en) * 2015-10-22 2018-10-16 Western Digital Technologies, Inc. Division of data storage in single-storage device architecture
CN105260229A (zh) * 2015-10-28 2016-01-20 北京百度网讯科技有限公司 拉取虚拟机镜像文件的方法和装置
KR101643729B1 (ko) * 2015-10-28 2016-07-29 주식회사 인피니플럭스 시간 기반 데이터에 대한 백업, 리스토어, 및 마운트를 위한 데이터 관리 시스템 및 방법
WO2017095465A1 (en) * 2015-12-04 2017-06-08 Hewlett Packard Enterprise Development Lp Create snapshot of subset of data
CN105677509B (zh) * 2015-12-25 2019-03-01 北京奇虎科技有限公司 数据库中数据的恢复方法及装置
US10592128B1 (en) * 2015-12-30 2020-03-17 EMC IP Holding Company LLC Abstraction layer
CN105740049B (zh) * 2016-01-27 2019-05-28 新华三技术有限公司 一种控制方法及装置
US10528431B2 (en) * 2016-02-04 2020-01-07 International Business Machines Corporation Providing integrity for data sets backed-up from client systems to objects in a network storage
US10037201B2 (en) * 2016-02-26 2018-07-31 Dell Products L.P. Secure live media boot system
US10592350B2 (en) 2016-03-09 2020-03-17 Commvault Systems, Inc. Virtual server cloud file system for virtual machine restore to cloud operations
US10152246B1 (en) * 2016-03-28 2018-12-11 EMC IP Holding Company LLC Application aware AMQP durable messages backup and restore
CN105843709B (zh) * 2016-04-08 2019-01-25 杭州宏杉科技股份有限公司 差异数据扫描方法及装置
US10445298B2 (en) 2016-05-18 2019-10-15 Actifio, Inc. Vault to object store
CN107402839B (zh) * 2016-05-18 2021-03-09 深信服科技股份有限公司 一种备份数据的方法及系统
CN106095890A (zh) * 2016-05-30 2016-11-09 浙江协同数据系统有限公司 一种基于分布式虚拟化数据库服务的数据共享方法
US10476955B2 (en) 2016-06-02 2019-11-12 Actifio, Inc. Streaming and sequential data replication
US10346248B2 (en) 2016-06-23 2019-07-09 Red Hat Israel, Ltd. Failure resistant volume creation in a shared storage environment
US10417098B2 (en) 2016-06-28 2019-09-17 International Business Machines Corporation File level access to block level incremental backups of a virtual disk
US10216254B1 (en) 2016-06-29 2019-02-26 Altera Corporation Methods and apparatus for selectively extracting and loading register states
CN106250274B (zh) * 2016-08-16 2019-03-15 浪潮(北京)电子信息产业有限公司 一种虚拟机的备份方法及装置
CN106445732B (zh) * 2016-08-30 2018-04-24 华中科技大学附属中学 一种基于版本控制的在线快照管理方法和系统
CN106357778A (zh) * 2016-09-27 2017-01-25 山东浪潮商用系统有限公司 一种会话信息的共享方法、装置及系统
CN106407045B (zh) * 2016-09-29 2019-09-24 郑州云海信息技术有限公司 一种数据灾难恢复方法、系统及服务器虚拟化系统
US10417102B2 (en) 2016-09-30 2019-09-17 Commvault Systems, Inc. Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, including virtual machine distribution logic
US10162528B2 (en) 2016-10-25 2018-12-25 Commvault Systems, Inc. Targeted snapshot based on virtual machine location
US10678758B2 (en) 2016-11-21 2020-06-09 Commvault Systems, Inc. Cross-platform virtual machine data and memory backup and replication
US10884875B2 (en) * 2016-12-15 2021-01-05 Palantir Technologies Inc. Incremental backup of computer data files
US10310949B1 (en) * 2016-12-22 2019-06-04 EMC IP Holding Company LLC Disaster restore of big data application with near zero RTO
US10261719B2 (en) 2017-01-31 2019-04-16 Hewlett Packard Enterprise Development Lp Volume and snapshot replication
CN108572888B (zh) * 2017-03-14 2022-08-19 阿里巴巴集团控股有限公司 磁盘快照创建方法和磁盘快照创建装置
US10949308B2 (en) 2017-03-15 2021-03-16 Commvault Systems, Inc. Application aware backup of virtual machines
JP6489144B2 (ja) * 2017-03-23 2019-03-27 日本電気株式会社 情報処理装置
US10896100B2 (en) 2017-03-24 2021-01-19 Commvault Systems, Inc. Buffered virtual machine replication
CN106951345B (zh) * 2017-03-28 2020-03-13 上海爱数信息技术股份有限公司 一种虚拟机磁盘数据的一致性测试方法及装置
US11074140B2 (en) * 2017-03-29 2021-07-27 Commvault Systems, Inc. Live browsing of granular mailbox data
US10387073B2 (en) 2017-03-29 2019-08-20 Commvault Systems, Inc. External dynamic virtual machine synchronization
US10853195B2 (en) 2017-03-31 2020-12-01 Commvault Systems, Inc. Granular restoration of virtual machine application data
JP7289034B2 (ja) * 2017-03-31 2023-06-09 インターナショナル・ビジネス・マシーンズ・コーポレーション ストレージ非依存アプリケーション一貫性スナップショット及び複製
CN108733509B (zh) * 2017-04-17 2021-12-10 伊姆西Ip控股有限责任公司 用于在集群系统中备份和恢复数据的方法和系统
US10891201B1 (en) * 2017-04-27 2021-01-12 EMC IP Holding Company LLC Dynamic rule based model for long term retention
US10855554B2 (en) 2017-04-28 2020-12-01 Actifio, Inc. Systems and methods for determining service level agreement compliance
US10599524B2 (en) * 2017-04-28 2020-03-24 Veritas Technologies Llc Backup performance after backup failure
US10509646B2 (en) 2017-06-02 2019-12-17 Apple Inc. Software update rollbacks using file system volume snapshots
US11449389B2 (en) * 2017-06-02 2022-09-20 Apple Inc. Techniques for performing incremental data backups
US11301332B2 (en) * 2017-07-31 2022-04-12 Honeywell International Inc. Automatic firmware upgrade of an embedded node
KR102474582B1 (ko) * 2017-08-28 2022-12-05 삼성전자주식회사 가상화 클러스터 환경의 비바람직한 호스트 서버 상에서 더티 가상 머신의 실행을 방지하는 방법 및 시스템
US11099765B2 (en) * 2017-09-28 2021-08-24 Quantum Corporation Data protection of container persistent storage with changed block tracking
US11403178B2 (en) 2017-09-29 2022-08-02 Google Llc Incremental vault to object store
CN107943557B (zh) * 2017-11-18 2020-07-17 浙江网新恒天软件有限公司 一种基于云平台的虚拟机磁盘增量快照方法
US10664367B2 (en) * 2017-11-30 2020-05-26 International Business Machines Corporation Shared storage parity on RAID
US10540171B2 (en) * 2017-12-29 2020-01-21 Business Objects Software, Ltd. State capture and retrieval for rapid deployment environments
US11232001B2 (en) * 2018-01-29 2022-01-25 Rubrik, Inc. Creation of virtual machine packages using incremental state updates
US20210334003A1 (en) * 2018-02-14 2021-10-28 Commvault Systems, Inc. Private snapshots based on sparse files and data replication
US11163887B2 (en) 2018-02-14 2021-11-02 Microsoft Technology Licensing, Llc Clearance of bare metal resource to trusted state usable in cloud computing
US10740022B2 (en) * 2018-02-14 2020-08-11 Commvault Systems, Inc. Block-level live browsing and private writable backup copies using an ISCSI server
US10545834B1 (en) * 2018-03-02 2020-01-28 June B. Smith Server-assisted network data archiving
US10877928B2 (en) 2018-03-07 2020-12-29 Commvault Systems, Inc. Using utilities injected into cloud-based virtual machines for speeding up virtual machine backup operations
US10657068B2 (en) * 2018-03-22 2020-05-19 Intel Corporation Techniques for an all persistent memory file system
CN110309100B (zh) * 2018-03-22 2023-05-23 腾讯科技（深圳）有限公司 一种快照对象生成方法和装置
US10261865B1 (en) * 2018-04-27 2019-04-16 Cohesity, Inc. Fast and optimized restore using delta information
US11003372B2 (en) * 2018-05-31 2021-05-11 Portworx, Inc. Protecting volume namespaces from corruption in a distributed container orchestrator
US11176001B2 (en) 2018-06-08 2021-11-16 Google Llc Automated backup and restore of a disk group
CN108984342B (zh) * 2018-07-06 2019-07-19 无锡华云数据技术服务有限公司 改进的基于虚拟磁盘文件的流式增量备份方法及装置
US11126505B1 (en) * 2018-08-10 2021-09-21 Amazon Technologies, Inc. Past-state backup generator and interface for database systems
US11200124B2 (en) 2018-12-06 2021-12-14 Commvault Systems, Inc. Assigning backup resources based on failover of partnered data storage servers in a data storage management system
JP6881480B2 (ja) * 2019-01-28 2021-06-02 株式会社安川電機 産業機器管理システム、産業機器管理方法、及びプログラム
US10768971B2 (en) 2019-01-30 2020-09-08 Commvault Systems, Inc. Cross-hypervisor live mount of backed up virtual machine data
US11093347B2 (en) * 2019-04-16 2021-08-17 EMC IP Holding Company LLC File system restoration using block-based snapshots and file system consistency check
US10776041B1 (en) * 2019-05-14 2020-09-15 EMC IP Holding Company LLC System and method for scalable backup search
US11615001B2 (en) * 2019-06-27 2023-03-28 Netapp, Inc. Incremental restore of a virtual machine
US11809899B2 (en) 2019-06-28 2023-11-07 Intel Corporation Methods and apparatus for accelerating virtual machine migration
US11182254B2 (en) * 2019-07-31 2021-11-23 Rubrik, Inc. Streaming database backup using cluster live mounts
US11461122B2 (en) 2019-07-31 2022-10-04 Rubrik, Inc. Streaming database cloning using cluster live mounts
US11513917B2 (en) * 2019-07-31 2022-11-29 Rubrik, Inc. Streaming database recovery using cluster live mounts
US11977453B2 (en) 2019-09-12 2024-05-07 Restorvault, Llc Virtual replication of unstructured data
CA3151014A1 (en) * 2019-09-12 2021-03-18 Jesse Paul CHARFAUROS Virtual recovery and replication of unstructured data
US11816000B2 (en) 2019-09-12 2023-11-14 restor Vault, LLC Virtual recovery of unstructured data
US11467775B2 (en) 2019-10-15 2022-10-11 Hewlett Packard Enterprise Development Lp Virtual persistent volumes for containerized applications
US11068196B2 (en) * 2019-10-24 2021-07-20 EMC IP Holding Company LLC System and method for a restoration of on-premise backups to a cloud-based service
CN111078352A (zh) * 2019-10-31 2020-04-28 苏州浪潮智能科技有限公司 一种基于kvm虚拟化系统的双机热备部署方法及系统
US11237924B2 (en) 2019-12-11 2022-02-01 Commvault Systems, Inc. Dynamic resizing and re-distribution of destination data storage resources for bare metal restore operations in a data storage management system
US11194761B2 (en) * 2020-01-30 2021-12-07 Rubrik, Inc. Optimizing utilization of a tablespace for exporting from a foreign database recovery environment
US11360860B2 (en) 2020-01-30 2022-06-14 Rubrik, Inc. Exporting a database from a foreign database recovery environment
US11609828B2 (en) 2020-01-30 2023-03-21 Rubrik, Inc. Utilizing a tablespace to export to a native database recovery environment
US11467925B2 (en) 2020-01-30 2022-10-11 Rubrik, Inc. Exporting a database to a native database recovery environment
US11604761B2 (en) 2020-01-30 2023-03-14 Rubrik, Inc. Utilizing a tablespace to export from a foreign database recovery environment
WO2021155857A1 (en) * 2020-02-07 2021-08-12 Huawei Technologies Co., Ltd. Fast file snapshots and clones
US11467753B2 (en) 2020-02-14 2022-10-11 Commvault Systems, Inc. On-demand restore of virtual machine data
US11803593B2 (en) 2020-02-14 2023-10-31 Coupang Corp. Systems and methods for receiving and propagating efficient search updates in real time
US11442768B2 (en) 2020-03-12 2022-09-13 Commvault Systems, Inc. Cross-hypervisor live recovery of virtual machines
WO2021191110A1 (en) 2020-03-24 2021-09-30 Signify Holding B.V. A controller for providing uninterrupted control of a node in a lighting network and a method thereof
US11099956B1 (en) 2020-03-26 2021-08-24 Commvault Systems, Inc. Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations
US12079162B2 (en) 2020-03-30 2024-09-03 Pure Storage, Inc. Snapshot management in a storage system
US11704035B2 (en) 2020-03-30 2023-07-18 Pure Storage, Inc. Unified storage on block containers
US11687267B2 (en) 2020-04-14 2023-06-27 Hewlett Packard Enterprise Development Lp Containerized application manifests and virtual persistent volumes
US11243882B2 (en) * 2020-04-15 2022-02-08 International Business Machines Corporation In-array linked list identifier pool scheme
US11748143B2 (en) 2020-05-15 2023-09-05 Commvault Systems, Inc. Live mount of virtual machines in a public cloud computing environment
US11586489B2 (en) 2020-06-08 2023-02-21 Sungard Availability Services, Lp Automated disaster recovery test verification
US11693573B2 (en) 2020-06-18 2023-07-04 Hewlett Packard Enterprise Development Lp Relaying storage operation requests to storage systems using underlying volume identifiers
US11868213B2 (en) * 2020-06-26 2024-01-09 Netapp, Inc. Incremental backup to object store
US11960773B2 (en) * 2020-07-31 2024-04-16 Hewlett Packard Enterprise Development Lp Modifying virtual persistent volumes based on analysis of performance metrics
CN112000437A (zh) * 2020-08-21 2020-11-27 济南浪潮数据技术有限公司 一种灾备方法、装置、电子设备及存储介质
US11656951B2 (en) 2020-10-28 2023-05-23 Commvault Systems, Inc. Data loss vulnerability detection
CN112445780A (zh) * 2020-11-27 2021-03-05 上海上讯信息技术股份有限公司 一种基于快照的主从架构部署方法及设备
CN112363807A (zh) * 2020-11-27 2021-02-12 上海爱数信息技术股份有限公司 一种生产系统任意时间接管系统及其方法
CN112650447B (zh) * 2020-12-18 2024-02-13 北京浪潮数据技术有限公司 一种ceph分布式块存储的备份方法、系统及装置
CN113297159B (zh) * 2021-02-08 2024-03-08 阿里巴巴集团控股有限公司 数据存储方法以及装置
US11620070B2 (en) 2021-02-08 2023-04-04 Kyndryl, Inc. Cognitive control plane for application consistent datasets
US11816129B2 (en) 2021-06-22 2023-11-14 Pure Storage, Inc. Generating datasets using approximate baselines
CN116545845B (zh) * 2023-07-04 2023-09-08 四川万流数据服务有限责任公司 生产服务器冗余备份装置、系统及方法

Family Cites Families (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5410621A (en) * 1970-12-28 1995-04-25 Hyatt; Gilbert P. Image processing system having a sampled filter
JPS5829350B2 (ja) * 1981-04-16 1983-06-22 フイルマ・カ−ル・シユテイル・ゲゼルシヤフト・ミツト・ベシユレンクテル・ハフツング・ウント・コンパニ−・コマンデイ−トゲゼルシヤフト しやく熱コ−クスを乾式冷却するための装置
US5047923A (en) * 1987-08-21 1991-09-10 Siemens Aktiengesellschaft Modularly structured digital communication system for interconnecting terminal equipment and public networks
US5018097A (en) * 1987-08-21 1991-05-21 Siemens Aktiengesellschaft Modularly structured digital communications system for interconnecting terminal equipment and public networks, and having operation and reliability programs
US5018078A (en) * 1987-12-09 1991-05-21 Fuji Photo Film Co., Ltd. Apparatus and method for processing huge image information at high speed
US5163122A (en) * 1987-12-09 1992-11-10 Fuji Photo Film Co., Ltd. Image processing system
EP0326137A3 (de) * 1988-01-27 1991-10-02 Fuji Photo Film Co., Ltd. Bildverarbeitungssystem
US5155837A (en) * 1989-03-02 1992-10-13 Bell Communications Research, Inc. Methods and apparatus for software retrofitting
US5231636A (en) * 1991-09-13 1993-07-27 National Semiconductor Corporation Asynchronous glitchless digital MUX
WO1993009494A1 (en) 1991-10-28 1993-05-13 Digital Equipment Corporation Fault-tolerant computer processing using a shadow virtual processor
US5325520A (en) * 1992-01-03 1994-06-28 Amdahl Corporation Invoking hardware recovery actions via action latches
JP3016971B2 (ja) * 1992-09-29 2000-03-06 日本電気株式会社 ファイルシステム
US5963962A (en) * 1995-05-31 1999-10-05 Network Appliance, Inc. Write anywhere file-system layout
US5835953A (en) * 1994-10-13 1998-11-10 Vinca Corporation Backup system that takes a snapshot of the locations in a mass storage device that has been identified for updating prior to updating
SE504943C2 (sv) * 1994-12-09 1997-06-02 Ericsson Telefon Ab L M Synkroniseringsförfarande som tillåter tillståndsöverföring
JPH1153239A (ja) * 1997-08-04 1999-02-26 Nec Corp データベースのロールバック処理方法及び前記ロールバック処理方法の手順を記録した記録媒体
US6016553A (en) * 1997-09-05 2000-01-18 Wild File, Inc. Method, software and apparatus for saving, using and recovering data
US6795966B1 (en) * 1998-05-15 2004-09-21 Vmware, Inc. Mechanism for restoring, porting, replicating and checkpointing computer systems using state extraction
US20020049883A1 (en) * 1999-11-29 2002-04-25 Eric Schneider System and method for restoring a computer system after a failure
US6615365B1 (en) * 2000-03-11 2003-09-02 Powerquest Corporation Storing a computer disk image within an imaged partition
US7363633B1 (en) * 2000-04-24 2008-04-22 Microsoft Corporation Registering and storing dependencies among applications and objects in a computer system and communicating the dependencies to a recovery or backup service
JP2001312421A (ja) * 2000-04-28 2001-11-09 Toshiba Corp バックアップ方法および記録媒体
US6636954B2 (en) * 2000-06-02 2003-10-21 Fujitsu Limited Method and apparatus for inter-disk copy processing, and a computer product
JP2002055783A (ja) * 2000-06-02 2002-02-20 Fujitsu Ltd ディスク間の複写処理装置、複写処理方法、およびその方法をコンピュータに実行させるプログラム、並びにそのプログラムを記録したコンピュータ読み取り可能な記録媒体
BR0112170A (pt) * 2000-07-05 2004-07-27 Ernst & Young Llp Aparelho provendo um ou mais serviços de computador para diversos clientes, combinação de um primeiro aparelho e um segundo aparelho substancialmente idêntico ao citado primeiro aparelho, e, processos para prover um ou mais serviços de computador para diversos clientes, para operar um computador real em nome de diversos clientes, e para prover, para diversos clientes, um ou mais serviços de computador
US7313614B2 (en) * 2000-11-02 2007-12-25 Sun Microsystems, Inc. Switching system
US6931558B1 (en) * 2000-11-29 2005-08-16 Veritas Operating Corporation Computer restoration systems and methods
US6941490B2 (en) * 2000-12-21 2005-09-06 Emc Corporation Dual channel restoration of data between primary and backup servers
GB0112781D0 (en) * 2001-05-25 2001-07-18 Global Continuity Plc Method for rapid recovery from a network file server failure
US6832330B1 (en) * 2001-09-05 2004-12-14 Emc Corporation Reversible mirrored restore of an enterprise level primary disk
US7213065B2 (en) * 2001-11-08 2007-05-01 Racemi, Inc. System and method for dynamic server allocation and provisioning
US6948089B2 (en) * 2002-01-10 2005-09-20 Hitachi, Ltd. Apparatus and method for multiple generation remote backup and fast restore
US7043485B2 (en) * 2002-03-19 2006-05-09 Network Appliance, Inc. System and method for storage of snapshot metadata in a remote file
US7093086B1 (en) * 2002-03-28 2006-08-15 Veritas Operating Corporation Disaster recovery and backup using virtual machines
WO2003085526A1 (en) * 2002-04-03 2003-10-16 Powerquest Corporation Using disassociated images for computer and storage resource management
US7565517B1 (en) * 2002-04-03 2009-07-21 Symantec Corporation Retargeting a captured image to new hardware while in a pre-boot environment
US7778958B2 (en) * 2002-04-11 2010-08-17 Quantum Corporation Recovery of data on a primary data volume
US6944789B2 (en) * 2002-06-11 2005-09-13 Hitachi, Ltd. Method and apparatus for data backup and recovery
US7844577B2 (en) * 2002-07-15 2010-11-30 Symantec Corporation System and method for maintaining a backup storage system for a computer system
US6907505B2 (en) * 2002-07-31 2005-06-14 Hewlett-Packard Development Company, L.P. Immediately available, statically allocated, full-logical-unit copy with a transient, snapshot-copy-like intermediate stage
US7120270B2 (en) * 2002-09-18 2006-10-10 Bose Corporation Audio device heat transferring
WO2004034197A2 (en) * 2002-10-07 2004-04-22 Commvault Systems, Inc. System and method for managing stored data
US8209680B1 (en) * 2003-04-11 2012-06-26 Vmware, Inc. System and method for disk imaging on diverse computers
US7191299B1 (en) * 2003-05-12 2007-03-13 Veritas Operating Corporation Method and system of providing periodic replication
US7069402B2 (en) * 2003-06-02 2006-06-27 International Business Machines Corporation Host-independent incremental backup method, apparatus, and system
US20040268068A1 (en) * 2003-06-24 2004-12-30 International Business Machines Corporation Efficient method for copying and creating block-level incremental backups of large files and sparse files
JP2005038176A (ja) * 2003-07-15 2005-02-10 Nec Corp コンピュータシステムおよびファイル管理方法
WO2005017737A2 (en) * 2003-08-14 2005-02-24 Compellent Technologies Virtual disk drive system and method
JP4021823B2 (ja) * 2003-09-01 2007-12-12 株式会社日立製作所 リモートコピーシステム及びリモートコピーの方法
JP4508583B2 (ja) * 2003-09-05 2010-07-21 三洋電機株式会社 液晶表示制御装置
US7237056B2 (en) * 2003-11-17 2007-06-26 Hewlett-Packard Development Company, L.P. Tape mirror interface
US7529897B1 (en) * 2003-12-31 2009-05-05 Vmware, Inc. Generating and using checkpoints in a virtual computer system
US7322010B1 (en) * 2004-02-06 2008-01-22 Symantec Operating Corporation Graphical user interface for mapping computer resources
US7266655B1 (en) * 2004-04-29 2007-09-04 Veritas Operating Corporation Synthesized backup set catalog
US7769720B2 (en) * 2004-06-16 2010-08-03 Hewlett-Packard Development Company, L.P. Systems and methods for migrating a server from one physical platform to a different physical platform
US7254682B1 (en) * 2004-07-28 2007-08-07 Symantec Corporation Selective file and folder snapshot image creation
US7840963B2 (en) 2004-10-15 2010-11-23 Microsoft Corporation Marking and utilizing portions of memory state information during a switch between virtual machines to minimize software service interruption
US20060112219A1 (en) * 2004-11-19 2006-05-25 Gaurav Chawla Functional partitioning method for providing modular data storage systems
US8732182B2 (en) * 2004-12-02 2014-05-20 Desktopsites Inc. System and method for launching a resource in a network
US8195443B2 (en) * 2005-02-18 2012-06-05 Opnet Technologies, Inc. Application level interface to network analysis tools
JP2009506399A (ja) * 2005-06-24 2009-02-12 シンクソート インコーポレイテッド バックアップイメージを仮想化するシステム及び方法
US9378099B2 (en) * 2005-06-24 2016-06-28 Catalogic Software, Inc. Instant data center recovery

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103176868A (zh) * 2013-04-02 2013-06-26 浪潮电子信息产业股份有限公司 一种文件状态备份方法
CN103176868B (zh) * 2013-04-02 2017-07-28 浪潮电子信息产业股份有限公司 一种文件状态备份方法
WO2016064387A1 (en) * 2014-10-22 2016-04-28 Hewlett Packard Enterprise Development Lp Data restoration using block disk presentations
CN104375904A (zh) * 2014-10-30 2015-02-25 浪潮电子信息产业股份有限公司 一种基于快照差异化数据传输的容灾备份方法

Also Published As

Publication number Publication date
US8346726B2 (en) 2013-01-01
CN102117233A (zh) 2011-07-06
AU2006262045A1 (en) 2007-01-04
EP2713271B1 (de) 2015-08-12
US20100077160A1 (en) 2010-03-25
US9116847B2 (en) 2015-08-25
WO2007002398A2 (en) 2007-01-04
US20140325267A1 (en) 2014-10-30
CN101495970B (zh) 2013-07-17
US9329941B2 (en) 2016-05-03
JP5420242B2 (ja) 2014-02-19
JP5430711B2 (ja) 2014-03-05
HK1173805A1 (en) 2013-05-24
EP2477114A3 (de) 2012-10-24
HK1159285A1 (en) 2012-07-27
EP2713271A3 (de) 2014-04-16
AU2006262046B2 (en) 2011-05-12
CA2613419A1 (en) 2007-01-04
CA2613419C (en) 2014-12-02
EP1907935A4 (de) 2009-04-22
US20090222496A1 (en) 2009-09-03
DE602006019875D1 (de) 2011-03-10
EP1907972A2 (de) 2008-04-09
JP2012198918A (ja) 2012-10-18
EP1907935A2 (de) 2008-04-09
CA2954888A1 (en) 2007-01-04
CA2613359C (en) 2017-05-30
EP1907972A4 (de) 2011-04-20
EP2713271A2 (de) 2014-04-02
AU2006262046A1 (en) 2007-01-04
CN101243413A (zh) 2008-08-13
WO2007002397A3 (en) 2009-04-16
CN102117233B (zh) 2013-07-17
ATE555438T1 (de) 2012-05-15
WO2007002397A2 (en) 2007-01-04
US20130086347A1 (en) 2013-04-04
HK1119800A1 (en) 2009-03-13
AU2006262045B2 (en) 2011-11-03
JP2008547123A (ja) 2008-12-25
US8706992B2 (en) 2014-04-22
EP1907972B1 (de) 2012-04-25
EP2477114B1 (de) 2014-01-15
US20110218968A1 (en) 2011-09-08
CN101243413B (zh) 2013-08-14
EP1907935B1 (de) 2011-01-26
ATE497210T1 (de) 2011-02-15
WO2007002398A3 (en) 2007-06-21
CA2954888C (en) 2019-06-04
JP2013254513A (ja) 2013-12-19
JP2009506399A (ja) 2009-02-12
CN101495970A (zh) 2009-07-29
HK1136048A1 (en) 2010-06-18
CA2613359A1 (en) 2007-01-04
US8255651B2 (en) 2012-08-28
US7937547B2 (en) 2011-05-03
US20120297246A1 (en) 2012-11-22

Similar Documents

Publication Publication Date Title
US9116847B2 (en) System and method for high performance enterprise data protection
US7076685B2 (en) Information replication system mounting partial database replications
EP1540510B1 (de) Verfahren und vorrichtung zur verwaltung der datenintegrität von sicherungs- und katastrophen-wiederherstellungsdaten
US7672979B1 (en) Backup and restore techniques using inconsistent state indicators
US6978282B1 (en) Information replication system having automated replication storage
US6269381B1 (en) Method and apparatus for backing up data before updating the data and for restoring from the backups
US7971091B1 (en) Network configuration backup and restore operations using continuous data protection
US7509358B1 (en) Performing replication operations on continuous data protection systems using pseudosnapshots
US7584339B1 (en) Remote backup and restore operations for ISB protocol systems
US7725669B1 (en) Backup and restore operations using coherency groups for ISB protocol systems
US7765190B1 (en) Pseudosnapshot creation and implementation using continuous data protection
US7487310B1 (en) Rotation policy for SAN copy sessions of ISB protocol systems
US7587565B1 (en) Generating automated and scheduled SAN copy sessions for ISB protocol systems
CN112380050A (zh) 一种利用快照在系统备份中的方法
AU2012200446B2 (en) System and method for high performance enterprise data protection
WO2003003209A1 (en) Information replication system having enhanced error detection and recovery

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AC Divisional application: reference to earlier application

Ref document number: 1907972

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/00 20060101AFI20120920BHEP

Ipc: G06F 11/14 20060101ALI20120920BHEP

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1173805

Country of ref document: HK

17P Request for examination filed

Effective date: 20130424

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006040136

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0011000000

Ipc: G06F0011200000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/20 20060101AFI20130624BHEP

Ipc: G06F 11/14 20060101ALI20130624BHEP

INTG Intention to grant announced

Effective date: 20130722

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AC Divisional application: reference to earlier application

Ref document number: 1907972

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 650104

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006040136

Country of ref document: DE

Effective date: 20140227

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 650104

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140115

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140515

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1173805

Country of ref document: HK

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140515

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006040136

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

26N No opposition filed

Effective date: 20141016

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140623

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006040136

Country of ref document: DE

Effective date: 20141016

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140630

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140623

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140416

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20140115

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20060623

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20220630

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20220630

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20220722

Year of fee payment: 17

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20230701

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230701

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230630

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240527

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240528

Year of fee payment: 19

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230623