Methods and apparatus for protecting data. Backup copies of data are created in real time and restoration of this backup data is enabled. For example, backup repositories of files stored in a primary storage device of a computer system may be created by examining information concerning the files to determine critical fields therein, and storage of the critical fields to a critical storage device and of non-critical fields and tags that are substituted for the critical fields to a context storage device effected. Following compromise of the files stored in the primary storage device, accesses by applications may be directed to the context storage device, e.g., as a means of rapid failover, and/or for each file stored in the context storage device, record-by-record copying of such files to the primary storage device may be effected to restore the contents of the primary storage device.

Due to the threat of virus attacks and ransom ware, an apparatus and methods for protecting backup storage devices from malicious software virus attacks is explored. An independent backup storage system is connected to a primary storage server over an undiscoverable communications line. The backup storage system is a read-only backup storage system most of the time buffering the backup storage system from a virus or attack on the primary storage server. The backup storage system changes from a read-only backup storage system to a read/write backup storage system only during a backup window of time where data is backed up to the backup storage system. A snapshot of the backup data is maintained in the backup storage system and can be made available at numerous points of time in the past if the data primary storage server becomes corrupted.

Ensuring resiliency to storage device failures in a storage system, including: determining a number of storage device failures within a particular write group that are to be tolerated by the storage system; for a plurality of datasets stored within the storage system, writing each dataset to at least a predetermined number of storage devices within the particular write group, wherein the predetermined number of storage devices is greater than the number of storage device failures within the particular write group that are to be tolerated by the storage system; and responsive to recovering from a system interruption: determining a number of readable storage devices that contain a copy of the dataset; and if the number of readable storage devices that contain a copy of the dataset is not greater than the number of failures that are to be tolerated, writing the dataset to one or more additional storage devices.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

Techniques are disclosed relating to archive operations for database systems. In some embodiments, a database system initiates one or more archive operations to archive one or more data extents for a database maintained by the database system. The system may halt archive activity for the database, in response to determining that archive operations for a threshold amount of data extents are initiated but not completed. The system may cancel at least one of the one or more archive operations. The system may determine to resume activity for the database based on determining that a threshold timer interval has elapsed and determining that a threshold amount of storage space is available for the database system. Disclosed embodiments may improve database availability, relative to traditional techniques.

Embodiments for a method performing data migration such as backups and restores in a network by identifying characteristics of data in a data saveset to separate the data into defined types based on respective characteristics, assigning a data label to each defined type by receiving user selection or automatically merging or selecting a priority label, from among many labels associated with a file, defining migration rules for each data label, discovering assigned labels during a migration operation; and applying respective migration rules to labeled data in the data saveset. The migration rules can dictate storage location, access rights, replication periods, retention periods, and similar parameters.

Embodiments of the present disclosure relate to a method for data backup. The method includes obtaining an attribute value associated with a backup task to be run, the backup task being used for backing up data on a client terminal to a server through a network, the attribute value including a value of at least one of an attribute of the client terminal, an attribute of the server, and an attribute of the network; determining, based on the attribute value, the number of threads to be used to perform the backup task on the client terminal; and causing the client terminal to perform the backup task using the number of threads to back up the data.

Example implementations relate to virtual persistent volumes for containerized applications. In an example, a plurality of different storage mounts are acquired from a mix of storage types. A containerized storage virtualization system creates and manages a virtual persistent volume that aggregates the acquired storage mounts. A mount point of the virtual persistent volume is provided to the containerized application. The virtual persistent volume includes a hierarchical structure that relates data objects of the containerized application by content-based signatures to a root object.

A backup manager for providing backup services includes storage and a backup orchestrator. The persistent storage stores prediction models. The backup orchestrator obtains a computing resource availability for a client; generates a prediction model of the prediction models using the computing resource availability for the client; predicts, using the prediction model and live data, a future computing resource availability for the client; and initiates generation of a backup for the client at an unscheduled time that is based, at least in part, on the future computing resource availability.

A data management and storage (DMS) cluster of peer DMS nodes manages data of a compute infrastructure by generating snapshots of partitions of a fileset of the compute infrastructure and providing a passthrough for storing the snapshots in a data storage separate from the DMS cluster, such as a cloud computing system. In one approach, the DMS nodes determine partitions of a fileset using fileset metadata, generates snapshots of the partitions, and stores the snapshots in the data storage. Each DMS node may include a local storage which is used to facilitate creation of a snapshot of a partition. The snapshot may be removed from the local storage after being sent to the data storage. Rather than storing the snapshot, the DMS cluster stores fileset metadata that is referenced to retrieve the snapshot from the data storage. The snapshot is deployed to retrieve a file stored in the partition.