An approach is provided for autonomous and optimal cloning, reinstating, and archiving of a containerized application. Application metadata is obtained from a catalog. Cloning rules specifying cloning an application are obtained. Application components are selected for cloning and the cloning is determined to be compliant with the cloning rules. The application components are cloned and data for the clone is saved to a clone repository. The catalog is updated with specifications of the cloned application components. Reinstating rules specifying reinstating a clone of the application are obtained. Reinstating the clone is determined to be compliant with the reinstating rules. The catalog is updated with specifications of the reinstated clone. In one embodiment, the catalog is updated with inferred associations among applications and identified rules associated with the application, where the inferred associations and identified rules are generated by a trained machine learning-based classifier.

Embodiments of the disclosure provide a method and apparatus for upgrading a system version of a system. The method can include: acquiring, using circuitry, from a first storage space a current system version identification corresponding to a current system version; acquiring, using circuitry, from a second storage space a backup system version identification corresponding to a backup system version; comparing, using circuitry, the current system version identification with the backup system version identification; and configuring the system based on the comparison.

Techniques described herein relate to a method for generating backups of virtual machines. The method may include, in response to identifying a backup generation event associated with virtual machines: obtaining, by a backup agent, virtual machine metadata associated with the virtual machines; identifying groups of virtual machines based on the virtual machine metadata; provisioning resources to generate backups of the virtual machines based on the groups of virtual machines; and generating a backup of the virtual machines based on the groups of virtual machines using the provisioned resources associated with the groups of virtual machines.

A system including: one or more processors; a memory storing instructions that, when executed by the one or more processors are configured to cause the system to: scan a plurality of distributed cloud servers to identify a plurality of distributed cloud applications comprising a scheduler configuration file; determine whether each identified distributed cloud application includes a standard or nonstandard environment; shutdown each distributed cloud application of having a standard environment based on a shutdown schedule; reinitialize each distributed cloud application having a standard cloud environment based on the shutdown schedule; create a restore point for each distributed application having a nonstandard environment; convert the nonstandard environments into standard environments; shut down each distributed cloud application having a nonstandard environment, reinitialize each distributed cloud application having a nonstandard environment, and restore the nonstandard cloud environment based on the created restore points.

A device includes a host including a main memory, and semiconductor memory including a nonvolatile semiconductor memory, memory unit, and controller. The nonvolatile semiconductor memory stores first address information. The memory unit stores second address information as part of the first address information. The controller accesses the nonvolatile semiconductor memory based on the second address information. Third address information is stored in the main memory, and is part or all of the first address information. The controller uses the third address information when accessing the nonvolatile semiconductor memory if address information to be referred is not stored in the second address information.

A backup recovery system for a modern application includes a modern application module and a backup module. The modern application module includes a service unit, an object storage gateway, a database, and an object storage. The service unit is configured to generate a large object, small objects, and service metadata, send the large object and the small objects to an object storage gateway, and store the service metadata in a database. The object storage gateway is configured to store the large object and the small objects in the object storage, merge the small objects into a large object, store the merged large object in the object storage, generate object metadata, and store the object metadata in the database. The backup module includes a metadata backup unit configured to back up the database and an object storage backup unit configured to back up large objects.

For accessing files from block-level backups of a virtual disk, an apparatus is disclosed. The apparatus includes a changed block module that obtains a list of changed blocks between a previous and a current backup of a virtual disk. The apparatus includes a mapping module that maps logical clusters of the virtual disk to the changed blocks and identifies files corresponding to the logical clusters. The apparatus further includes a changed file module that designates the files corresponding to the logical clusters as changed files, unless current attributes of the files for the current backup match attributes of the files in a backup file index corresponding to the previous backup of the virtual disk. The changed file module further stores the current attributes and extents for the changed files within blocks of a backup storage device for updating in the backup file index.

A changed block tracking (CBT) driver at a production host tracks, in a bitmap, changes made to a source volume of the production host since a last backup. A command is received to perform a differential backup of the source volume. A request is issued to a copy service to take a snapshot of the source volume. The bitmap is embedded into the snapshot. The snapshot is mounted on a backup proxy, different from the production host. The backup proxy retrieves the bitmap from the snapshot and conducts the differential backup of the source volume to secondary storage, thereby backing up the changes made to the source volume since the last backup according to the bitmap.

An incremental backup is made of a source volume on a production host to on premise secondary storage. The incremental backup includes a bitmap specifying locations of blocks that have changed since a last backup of the source volume, and data of the changed blocks. First checksums are calculated from data of the changed blocks. The incremental backup, including the changed blocks and the bitmap, are moved to cloud storage. The changed blocks are merged, at the cloud storage, with the last backup of the source volume to generate a synthetic full backup of the source volume. The bitmap is consulted to identify locations of the changed blocks. Second checksums are calculated from data written to the locations on the synthetic full backup. The first and second checksums are compared. If the first and second checksums do not match, an indication is generated that the synthetic full backup is corrupt.

A configuration file specifies a percentage value of data to validate. A synthetic full backup image of a source volume on cloud storage is accessed. The synthetic full backup is created by merging changed blocks of an incremental backup with another previous backup. A bitmap specifying locations of the changed blocks is examined. A region on the synthetic full backup beginning at a location corresponding to an initial changed block and ending at a location corresponding to a last changed block according to the bitmap is identified. The region is partitioned into a set of portions. Each portion is validated by randomly selecting blocks in a respective portion to validate. The validating of the respective portion continues until an amount of data validated in the respective portion reaches a size equal to the percentage value of a size of the incremental backup divided by a number of portions.