Patent classifications
G06F11/1458
BACKUP OF CONTAINERIZED APPLICATIONS USING A BACKUP SERVICES CONTAINER AND A BACKUP SERVICES CONTAINER-ORCHESTRATION POD
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.
SNAPSHOT RETENTION LOCK AT FILE SYSTEM, FILE SET/DIRECTORY LEVEL TO INSTANTLY LOCK ALL FILES
A snapshot is taken of at least a portion of a file system having a set of files to retain over a retention duration. The snapshot is taken at a level of the file system or a directory of the file system. A retention lock is applied to the snapshot to block, over the retention duration, operations involving deletion of the snapshot. The retention lock is not applied to the set of files.
System and method for distributed-agent backup of virtual machines
A distributed agent for backup and restoration of virtual machines collects backup data and meta-data. The distributed agent includes an agent inside a virtual machine and an agent outside the virtual machine. The two kinds of agents communicate with each other to collect data of different types used to backup and restore virtual machines.
METHOD, ELECTRONIC DEVICE AND COMPUTER PROGRAM PRODUCT FOR STORAGE MANAGEMENT
Embodiments of the present disclosure relate to a method for storage management, an electronic device, and a computer program product. According to an example implementation of the present disclosure, a method for storage management is provided, which comprises receiving an access request for target metadata from a user at a node among a plurality of nodes included in a data protection system, wherein the access request includes an identification of the target metadata; based on the identification, acquiring target access information corresponding to the identification from a set of access information for the user, wherein the target access information records information related to access to the target metadata; and if the target access information is acquired, determining the target metadata based on the target access information.
Method, electronic device and computer program product for storage management
Techniques involve: acquiring a first source snapshot for a source storage object stored in a source storage device; determining first difference data between the first source snapshot and the source storage object or a second source snapshot for the source storage object, creation time of the first source snapshot being associated with creation time of the second source snapshot; and sending the first difference data to a destination storage device to enable the destination storage device to create a first destination snapshot for a destination storage object stored in the destination storage device based on the first difference data. Such techniques can migrate snapshots more efficiently to improve storage management efficiency.
Orchestrator for orchestrating operations between a computing environment hosting virtual machines and a storage environment
Techniques are provided for orchestrating operations between a storage environment and a computing environment hosting virtual machines. A virtual machine proxy, associated with a computing environment hosting a virtual machine, is accessed by an orchestrator to identify the virtual machine and properties of the virtual machine. A storage proxy, associated with a storage environment comprising a volume within which snapshots of the virtual machine are to be stored, is accessed by the orchestrator to initialize a backup procedure. The orchestrator utilizes the virtual machine proxy to create a snapshot of the virtual machine. The orchestrator utilizes the storage proxy to back up the snapshot to the volume using the backup procedure.
SECURE DATA BACKUP AND RECOVERY FROM CYBERATTACKS
Aspects of the present disclosure provide systems, methods, and computer-readable storage media that support providing secure backup and recovery of files from edge devices during ransomware attacks or other cyberattacks. Secure data, such as medical records, may be stored at one or more networked storage nodes and backup images (e.g., snapshots) may be stored at a disconnected storage node (e.g., an air-gapped storage node) that is isolated from the networked storage nodes. Application programming interface (API) calls may be managed and monitored to detect an alarm state (e.g., a ransomware attack), and based on the alarm state, storage and retrieval from the networked storage nodes may be stopped. Additionally, a recent backup image from the disconnected storage node may be retrieved for use in performing system recovery operations.
MULTIPLE OPERATION MODES IN BACKUP OPERATOR
Some embodiments include a system, method, and non-transitory medium, with the system including a plurality of database services; and a stateless backup operator to perform a first mode for each database service to reconfigure a current backup state of each database service with an associated desired backup state information for the respective database service and the stateless backup operator to switch to and perform a second mode for a specific one of the plurality of database services in response to a request execute a first backup operation for the specific database service.
Dynamic resizing and re-distribution of destination data storage resources for bare metal restore operations in a data storage management system
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.
INTEGRATION OF DATABASE WITH DISTRIBUTED STORAGE SYSTEM
Methods, systems, and computer programs are presented for providing backup services to a database. One method includes operations for installing a backup agent in a first database, receiving information about the first database, and executing, by the backup agent, queries to the first database to determine a topology of the first database. Further, the method includes configuring, based on the topology, a receiver service of a second database for backing up the first database in the second database. The backup agent configures an interface module of the first database to back up the first database to the second database. The configuration includes an interface to the receiver service of the second database and connection information for storing data in one or more nodes of the second database. The interface module streams updates from the first database to the second database based on the configuration of the interface module.