Comm Vault Systems, Inc.

Sumedh Pramod Degaonkar

Amit Mitkar

Paramasivam Kumarasamy

Rahul S Pawar

Sanjay Kumar

Henry Wallace Dornemann

Sri Karthik Bhagi

Satish Chandra Kilaru

Sunil Kumar Gutta

Jianwei Chen

Unmil Vinay Tambe

Gaurav Kumar Singh

Vikash Kumar

Shankarbabu Bhavanarushi

Rajesh Kumar Singh

Rahil Mohmed Husein Mansuri

Srikanth Hejamadi Tati

Shivam Garg

Gopikannan Venugopalsamy

Live mounting a virtual machine (VM) causes the VM to run off a backup copy or snapshot previously taken of a 'live' production VM. The live-mounted VM is generally intended for temporary use such as to validate the integrity and contents of the backup copy for disaster recovery validation, or to access some contents of the backup copy from the live-mounted VM without restoring all backed up files. These uses contemplate that changes occurring during live mount are not preserved after the live-mounted VM expires or is taken down. Thus, live mounting a VM is not a restore operation and usually does not involve access to every block of data in the backup copy. However, live mounting provides live VM service in the cloud sooner than waiting for all of the backup copy/snapshot to be restored.

Live recovery of virtual machines in a public cloud computing environment based on temporary live mount

A method and system for communicating with IoT devices to gather information related to device failure or error(s) is disclosed. The system makes a copy of at least a portion of the device's non-volatile memory and/or receives IoT device data (e.g., sensor data and/or log files etc.) from an IoT device that recently failed. The system determines which log files and/or sensor data, for example, the IoT device created before and/or after a failure. After gathering this information, the system stores the information in a database, sends it to the IoT device manufacturer, for further analysis and diagnostics to troubleshoot the failure and send a fix or software update to the IoT device.

Management of internet of things devices

Aspects of the present disclosure enable data protection operations including differential and incremental backups by performing changed-block tracking in network or cloud computing systems with architectures that do not natively support changed-block tracking or do not expose changed-block tracking functionality to an information management system. In certain aspects, an identity of changed blocks may be obtained by using a hypervisor configured to interface with the cloud computing architecture. The identified changed blocks may be used to generate a map of the changed blocks. The maps of the changed blocks can be used by a virtual server agent to extract the changed blocks from a copy of a virtual machine disk and backed up to perform a differential or incremental backup.

Systems and methods for change block tracking for backing up changed data

Live mount of virtual machines in a public cloud computing environment

A method and system for communicating with IoT devices connected to a vehicle to gather information related to device operation or performance is disclosed. The system makes a copy of at least a portion of the device's non-volatile memory and/or receives IoT device data (e.g., sensor data and/or log files etc.) from an IoT device that recently failed. The system determines which log files and/or sensor data, for example, the IoT device created before and/or after a failure. After gathering this information, the system stores the information, sends it to a storage destination for further analysis and diagnostics to troubleshoot the failure and send a fix or software update to the IoT device. The information can also be placed into secondary storage to comply with regulatory, insurance, or legal purposes.

Managing data from internet of things (IoT) devices in a vehicle

Illustrative embodiments represent a dynamic on-demand approach to configuring destination storage for bare metal restore (BMR) operations without operator intervention, including destination storage that is smaller than source storage devices. The illustrative operations rely on system state information collected concurrently with or shortly after source data is backed up, thereby capturing current actual storage metrics for the source data. The illustrative embodiments further rely on enhanced data agent components to collect and restore system state information as well as to restore backup data, thereby streamlining the configurations needed for the BMR operation to proceed. Additional business logic matches source mount points with suitable smaller destination storage resources and ensures that the BMR operation successfully completes with diverse and/or smaller storage destinations.

Dynamic resizing and re-distribution of destination data storage resources for bare metal restore operations in a data storage management system

Software, firmware, and systems are described herein that migrate functionality of a source physical computing device to a destination virtual machine. A non-production copy of data associated with a source physical computing device is created. A configuration of the source physical computing device is determined. A configuration for a destination virtual machine is determined based at least in part on the configuration of the source physical computing device. The destination virtual machine is provided access to data and metadata associated with the source physical computing device using the non-production copy of data associated with the source physical computing device.

Migration of existing computing systems to cloud computing sites or virtual machines

A 'backup services container' comprises 'backup toolkits,' which include scripts for accessing containerized applications plus enabling utilities/environments for executing the scripts. The backup services container is added to Kubernetes pods comprising containerized applications without changing other pod containers. For maximum value and advantage, the backup services container is &#x201c;over-equipped&#x201d; with toolkits. The backup services container selects and applies a suitable backup toolkit to a containerized application to ready it for a pending backup. Interoperability with a proprietary data storage management system provides features that are not possible with third-party backup systems. Some embodiments include one or more components of the proprietary data storage management within the illustrative backup services container. Some embodiments include one or more components of the proprietary data storage management system in a backup services pod configured in a Kubernetes node. All configurations and embodiments are suitable for cloud and/or non-cloud computing environments.

Preparing containerized applications for backup using a backup services container and a backup services container-orchestration pod

Live recovery generates a new 'recovery VM' that operates as an ongoing 'live' production platform. A previously created non-cloud-native backup copy is the data source for the recovery VM. Live recovery restores data blocks from the backup copy on backup media directly to cloud-based virtual disk(s) assigned to the recovery VM. As a result, the cloud-based recovery VM can become fully operational in the cloud computing environment on a going-forward basis. The advantage of live recovery over a traditional restore is that live recovery provides a cloud-based VM that begins operating well before the backup copy is fully restored. This is accomplished by temporarily mounting a &#x201c;temp-mounted VM&#x201d; in the cloud while the backup copy is methodically restored in the background. VM reads and writes begin issuing from the temp-mounted VM and writes are retained on completion. Downtime is minimized when switching from the temp-mounted VM to the recovery VM.

Live recovery of virtual machines in a public cloud computing environment

Illustrative systems and methods enable a virtual machine ('VM') to be powered up at any hypervisor regardless of hypervisor type, based on live-mounting VM data that was originally backed up into a hypervisor-independent format by a block-level backup operation. Afterwards, the backed up VM executes anywhere anytime without needing to find a hypervisor that is the same as or compatible with the original source VM's hypervisor. The backed up VM payload data is rendered portable to any virtualized platform. Thus, a VM can be powered up at one or more test stations, data center or cloud recovery environments, and/or backup appliances, without the prior-art limitations of finding a same/compatible hypervisor for accessing and using backed up VM data. An illustrative media agent maintains cache storage that acts as a way station for data blocks retrieved from an original backup copy, and stores data blocks written by the live-mounted VM.

Cross-hypervisor live mount of backed up virtual machine data

Hypervisor-independent block-level live browse is used for directly accessing backed up virtual machine (VM) data. Hypervisor-free file-level recovery (block-level pseudo-mount) from backed up VMs also is disclosed. Backed up virtual machine ('VM') data can be browsed without needing or using a hypervisor. Individual backed up VM files can be requested and restored to anywhere without a hypervisor and without the need to restore the rest of the backed up virtual disk. Hypervisor-agnostic VM backups can be browsed and recovered without a hypervisor and from anywhere, and individual backed up VM files can be restored to anywhere, e.g., to a different VM platform, to a non-VM environment, without restoring an entire virtual disk, and without a recovery data agent at the destination.

Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block- level pseudo-mount)

Certain embodiments described herein relate to an improved information management system that can perform platform-agnostic containerized application data protection. In one embodiment, the information management system receives a user's credentials to a container orchestrator along with an indication of whether or not to deploy a backup pod. Using the user credentials, the information management system accesses the container orchestrator, and if the user has requested deployment of a backup pod on the user's cluster, the information management system may do so using a backup pod specification and allow the backup pod to perform data protection operations, using a platform-agnostic interface (e.g., container storage interface), for application data accessible by the user applications on the user's pod on the user's cluster. Alternatively, if the user has not requested deployment of a backup pod, the information management system may perform data protection operations using provider-specific interface.

Platform-agnostic containerized application data protection

A data storage management system incorporates image recognition and classification features. The illustrative system generates thumbnail images to represent images detected in secondary copies. Subsequent image recognition and classification operations are based on the thumbnail images without need to access the secondary copies from which the thumbnails were derived. The system indexes thumbnail images and respective relationships to each other and to the source secondary copies. Metadata from the source secondary copies is extracted and preserved with the thumbnails. Thumbnail images, metadata, and related index data (collectively 'thumbnail data') are stored locally in an illustrative content index server, or in an enhanced storage manager, thus improving performance without interfering with ongoing storage management operations. Features are disclosed for searching within the system and performing storage management operations based on image criteria. Access to/from other systems is also possible, e.g., for importing images and/or thumbnails.

Data storage management operations in a secondary storage subsystem using image recognition and image-based criteria

Certain embodiments described herein relate to an improved information management system that can perform provider-specific data protection methods for cloud-stored data. In one embodiment, the information management system accesses a pod specification that indicates information usable to execute a containerized application on behalf of a user, and determines the cloud provider system configured to provide one or more computing resources for execution the containerized application. Using a provider-specific interface that is specific to the determined cloud provider system, the information management system creates a snapshot of a cloud storage volume associated with the containerized application and accesses the data inside the snapshot. The accessed data is stored onto a secondary storage device, and the snapshot is removed from the cloud provider system, thereby providing an efficient backup solution for the data used for executing the containerized application on the container orchestrator system.

Growing community of inventors

Surrey, Canada

Sumedh Pramod Degaonkar