Comm Vault Systems, Inc.

Sumedh Pramod Degaonkar

Amit Mitkar

Sanjay Kumar

Manas Bhikchand Mutha

Vikash Kumar

Shankarbabu Bhavanarushi

Rahul S Pawar

Paramasivam Kumarasamy

Henry Wallace Dornemann

Satish Chandra Kilaru

Unmil Vinay Tambe

Gaurav Kumar Singh

Rahil Mohmed Husein Mansuri

Srikanth Hejamadi Tati

Rajesh Kumar Singh

Shivam Garg

Data protection resources are automatically scaled to the needs of data source(s) in an application orchestrator computing environment, such as a cluster in a Kubernetes deployment. The approach is adaptable to data sources in production clusters or application suites that are not application orchestrator deployments, such as a cloud-based database-as-a-service (DBaaS). A data storage management system protects cluster-based data with an elastic number of data protection resources (e.g., data agents, media agents), which are deployed on demand. The number of data protection resources deployed for a particular job are appropriate to the workload(s) at present and depend on a variety of scaling factors. In some embodiments, data protection resources are deployed within the same cluster as the data sources. In other embodiments, a separate infrastructure cluster provides the data protection resources on demand, and connects to any number and types of data sources, whether cloud-based or otherwise, without limitation.

Scaled deployment of data protection resources for data originating in an application orchestrator

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 “over-equipped” 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.

Backup of containerized applications using a backup services container and a backup services container-orchestration pod

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

A method and system for communicating with IoT devices 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. The system determines which log files and/or sensor data, for example, the IoT device created. After gathering this information, the system stores the information, or may send it to a storage destination for further analysis. The information may also be placed into secondary storage to comply with regulatory, insurance, or legal purposes.

Managing data from internet of things (IoT) devices

Using an application orchestrator computing environment for automatically scaled deployment of data protection resources needed for data in a production cluster distinct from the application orchestrator or in another application orchestrator computing environment

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

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

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

Growing community of inventors

Sammamish, WA, United States of America

Sumedh Pramod Degaonkar