Emc IP Holding Company LLC

Luay Al-Alem

Antony Bett

Assaf Natanzon

Michael Rhodes

Systems and methods for performing data protection operations in a containerized application. A sidecar application is associated with or attached to a main application. The sidecar application has access to the resources of the main application. Backup requests are handled by the sidecar so that the application, which may be stateful, can be placed in a consistent state prior to performing the backup operation. The backup operation is then performed on the consistent application or on the data that is quiesced.

Application consistent snapshots as a sidecar of a containerized application

Methods and systems for backing up and restoring data on a worker node are described. According to some embodiments, the method includes using a job controller to spin up one or more backup jobs in the worker node. The method further includes utilizing, by the backup jobs, mount propagation to access one or more persistent volumes of a pod on the worker node. The method further includes performing, by the backup jobs, backup tasks on the persistent volumes. The method further includes applying a set of rules used by a scheduler to determine a location of the pod in order to ensure the backup jobs are scheduled on a same worker node. The method further includes storing, by the backup jobs, backup artifacts generated by the backup tasks, wherein the backup artifacts include deduplicated data.

Systems and methods for backup and restore of container-based persistent volumes

A containerized environment and application that are configured for component specific continuous replication and granular application level application. A key value store, which stores key values related to configuration data of the containerized application, is replicated continuously to a replicated key value store at a replica site. Persistent volumes may also be replicated to a replica site. The replication can be performed to multiple replica sites in an application specific manner.

Continuous replication and granular application level replication

One example method includes discovering an application topology, discovering relationships between microservices that are elements of the application topology, ranking the microservices, identifying one or more of the microservices as a persistency microservice, selecting one or more persistency microservices for backup, and defining a backup policy based on the microservice relationships, the microservice rankings, and the selected persistent microservices. A backup operation is then performed that includes backing up persistent data and/or persistent metadata generated and/or modified by one or more of the persistency microservices.

Smart dynamic restore for Kubernetes based applications

A method and system for enabling agentless backup and restore operations on a container orchestration platform. Specifically, the method and system disclosed herein may entail facilitating the implementation of backup (or restore) workloads in a containerized environment without the co-execution of secondary storage agents therein, which traditionally manage these backup (or restore) operations.

Method and system for enabling agentless backup and restore operations on a container orchestration platform

One example method includes identifying a group of microservices that form respective portions of an application, capturing any relations among microservices in the group of microservices, generating one or more restore policies for the application, based on identified relations among the microservices in the group of microservices, and configuring one of the restore policies so that such restore policy specifies restoring, together, a microservice that was identified as a partial cause of a problem, and any other microservices that are dependent on that microservice.

Automatically setting a dynamic restore policy in a native cloud environment

Systems and methods for discovering applications. An application may be discovered by determining a topology of the application in a containerized platform. Discovering the topology may include determining the components of the application and then determining relationships between the components. The relationships may include whether a component (e.g., a microservice) is user facing and may be based on traffic patterns between the components. The components or microservices may be prioritized or ranked based on the topology. The topology can be used when performing a data protection operation such as a restore operation.

Prioritizing microservices on a container platform for a restore operation

Systems and methods for performing data protection operation on an application in a manner that is integrated with the environment of the application being protected. A dynamic policy is associated with the data protection application so that a data protection operation can be performed whenever the policy is triggered.

Automatically setting a dynamic backup policy in a cloud environment

One example method includes receiving an indication that an application has experienced a problem, where the application comprises a plurality of microservices, discovering that one of the microservices is a partial cause of the problem, identifying one or more connections among the microservices, where one or more of the connections indicates a dependency, or lack of dependency, among two or more microservices, and restoring the microservice that is a partial cause of the problem, and also restoring any other microservices that are dependent on that microservice.

Growing community of inventors

Lynnfield, MA, United States of America

Luay Al-Alem