The described embodiments set forth techniques for providing an improved backup progress estimate for a backup of a source file system volume (FSV). The techniques involve determining, for the source FSV, a backup size during performance of backup operations. The operations can include determining the backup size based on a number of files on the source FSV. Additionally, the operations can include copying files of the source FSV and/or propagating corresponding files of a destination FSV to a location of the backup of the source FSV on a destination storage device and updating one or more metrics using a number of files and/or a number of bytes copied and/or propagated to the backup. In this manner, a progress indication for the backup may be determined based on the one or more metrics responsive to files and/or directories of the source file system volume being stored on a destination storage device.

Back-up procedures for saving configuration data are provided, which enable the restoration of said configuration data on the device when it is reset to default, or on another device when the device is stolen or broken. Since configuration data are sensitive data, it is important to protect their confidentiality and their integrity throughout the back-up and restore process. Current solutions enable a secure back-up and restore process on the same device since the backed-up configuration data are encrypted using credentials that are only known to the device. In order to overcome these drawbacks, a solution is proposed for performing a secure back-up process which enables the restoration of the backed-up data to the same device or to a distinct device. This is made possible by using encryption keys that are common to a pool of devices. Those common encryption keys are provided during the manufacturing of the devices.

A semiconductor device includes a source/drain (S/D) region, a fin structure formed on the S/D region, and a gate structure formed on the fin structure so that a space is formed between the S/D region and the gate structure.

An executable utility is injected into cloud-based virtual machines (VMs) that are subject to backups by a data storage management system tasked with protecting the cloud-based VMs and their associated data. The utility is injected into a target VM which is “live” and operating. The utility analyzes the VM's live volume to discover data extents therein, and for each extent computes a respective checksum and determines whether the extent is a “hole.” Afterwards, checksums help identify changed data in successive snapshots of the live volume, so that only changed data will be read and backed up in incremental backups. Time is saved in performing the backup operation first by pre-warming the backup's source volume in parallel with the utility analyzing the live volume, and second by skipping read operations for extents unchanged since a preceding backup. The resulting incremental backup operation is sped up as compared to prior art approaches.

A device having a function of simultaneously charging and backing up data is provided. The device includes a transmission interface, a power supply circuit, a storage circuit, and a main control circuit. The transmission interface is connected to an electronic device. The power supply circuit is configured to supply power to the electronic device to charge the electronic device. The storage circuit is configured to access data of the electronic device, or to provide data stored in the storage circuit to the electronic device. The main control circuit is connected to the transmission interface, the power supply circuit and the storage circuit. The main control circuit is configured to control the power supply circuit to supply the power to the electronic device and the storage circuit to back up the data simultaneously.

A first cloud vendor is registered by a backup application. A file is moved from backup storage of the backup application to the first cloud vendor. A reference is maintained at the backup storage to the first file residing at the first cloud vendor. A second cloud vendor is registered by the backup application. The backup application directs a migration of the file from the first cloud vendor to the second cloud vendor without recalling the file to the backup storage. A reference maintained at the backup storage is updated to refer to the file now residing at the second cloud vendor. The updated reference is maintained at the backup storage.

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.

Information technology resource forecasting based on time series analysis is described. A system creates multiple forecasts for an information technology resource by applying corresponding multiple time series models to first data associated with the information technology resource. The system selects a model of the multiple time series models by comparing the multiple forecasts for the information technology resource to second data associated with the information technology resource. The system outputs a forecast that is created by applying the selected model to third data associated with the information technology resource.

Techniques described herein relate to a method for managing data protection services for data clusters. The method includes identifying, by a data protection manager, a migration event associated with a first data cluster; in response to identifying the migration event: identifying a second data cluster capable of hosting the first data cluster using data cluster topology information and data cluster component inventory information associated with the first data cluster; generating a dependency map associated with the second data cluster based on the first data cluster; identifying a migration sequence based on the dependency map; initiating data cluster components of the second data cluster to perform migration of the first data cluster; and migrating the first data cluster to the second data cluster.

An illustrative method includes a data protection system determining an encryption indicator for a first recovery dataset associated with a storage system, the encryption indicator representative of a likelihood that a threshold amount of data associated with the first recovery dataset is encrypted; and performing, based on the encryption indicator for the first recovery dataset, an action with respect to a second recovery dataset associated with the storage system.