International Business Machines Corporation

Elena Drobchenko

Shay Haim Akirav

Gil E Paz

Itay Maoz

Ofer Leneman

Tzafrir Z Taub

Aharon Lazar

Aviv Caro

Dov N Hepner

Yariv Bachar

Evgeny Budilovsky

Samuel Krikler

Dan Melamed

Asaf Ekshtein

Vadim Stotland

Asaf Levy

Lior Aronovich

Haim Bitner

Liran Loya

Shira Ben-Dor

Shiri Alexander

Neville Yates

Shira Bash

Joseph W Dain

Oren Bar

Ofer Lenaman

Methods, systems, and computer program product embodiments for cataloging data in a backup storage environment, by a processor device, are provided. In a storage system using tape library data replication between an originating site and one or more backup sites, data catalog data is replicated between the originating site and the backup site such that replicated data moved from the originating site to the backup site is placed into a catalog duplicative of the originating site.

Granular instant import of replicated VTL cartridge into a backup catalog

Exemplary method, system, and computer program product embodiments for protecting data segments by a processor device in a computing environment, are provided. In one embodiment, by way of example only, a history table is configured to accompany data segments for consultation during a replication operation. If the history table indicates an ownership conflict, the replication operation is inhibited.

Protecting data segments in a computing environment

Various embodiments for protecting data segments by a processor device in a computing environment, are provided. In one embodiment, a method comprises, if an error occurs during a replication operation from a source location to a destination location causing at least one of a plurality of data segments to be deleted in the source location, performing: executing a failback operation by a reverse replication process from the destination location to the source location, and regaining ownership of the data segments by the source location; and pursuant to the failback operation, performing: enabling the reverse replication process if an owner of the data segments is a designated one of the destination location, and adding an invalid owner notification in a history table, wherein the failback operation is identified for the designated one of the at least one destination location.

Subsequent to a storage operation performed on the source instance by a source component, a synchronization message is sent to a replicated component for the replicated instance. The synchronization message is stored locally in a persistent storage location associated with the source component along with an indicator representative of a time the storage operation was performed. Pursuant to receipt of the synchronization message by the replicated component, the replicated component is updated to a dirty state to indicate a lack of full synchronization between the source and replicated instances.

Synchronization of sequential access storage components with backup catalog

A calculated factoring ratio is determined as a weighted ratio of current nominal data to physical data. A maximal nominal estimated space in the computing storage environment is calculated. A remaining space, defined as the maximal nominal estimated space minus a current nominal space in the computing storage environment, is calculated. Data replication operations are accepted and stored in the computing storage environment if the remaining space is below a predetermined threshold of space for backup operations.

Space reservation in a deduplication system

Exemplary system and computer program product embodiments for protecting data segments by a processor device in a computing environment, are provided. In one embodiment, by way of example only, a history table is configured to accompany data segments for consultation during a replication operation. If the history table indicates an ownership conflict, the replication operation is inhibited.

A calculated factoring ratio is determined as a weighted ratio of current nominal data to physical data based on at least one storage capacity threshold and a used storage space currently physically consumed by one of backup and replication data. A maximal nominal estimated space in the computing storage environment is calculated. A remaining space, defined as the maximal nominal estimated space minus a current nominal space in the computing storage environment, is calculated.

Pursuant to execution of a predetermined failback policy, if a storage device is not preexistent in a source storage system operable in the computing environment, and an owner of the storage device is one of a DR storage system and a storage system having previously withdrawn from a replication grid, and the DR storage system has authorization to transfer ownership of the storage device by a replacement operation, and an instance of the storage device is replicated to the source storage system to generate a replicated instance of the storage device on the source storage system.

Disaster recovery failback

A deduplication storage capacity is estimated as a function of an expected deduplication ratio, the expected deduplication ratio being a combined average of a current deduplication ratio and a configured deduplication ratio, the current deduplication ratio depending on the data currently stored in the deduplication storage, and the configured deduplication ratio being an estimate made at a configuration stage of the deduplication computing storage environment.

Capacity management in deduplication storage systems

Visibility of a data storage entity on a first storage system is switched to a replicated data storage entity on a second storage system. Data from the data storage entity is replicated from the first storage system to the second storage system using a common serial number. The data storage entity is hidden from the first storage system by concealing the common serial number. An ejection of the data storage entity from the first storage system is automated, and the replicated data storage entity is introduced to the second storage system.

Switching visibility between virtual data storage entities

Various embodiments for synchronization of source and replicated instances of sequential access storage components in a computing environment by a processor device are provided. A replication synchronization table (RST) of a source instance is updated at a source component with the compacted information. Based on the RST of the source instance and the RST of the replicated instance, data representative of a most recent position on the source component from which data should be transmitted to a replicated component to achieve a full synchronization is determined.

Synchronization of replicated sequential access storage components

A replication synchronization table (RST) is configured for the source instance. The RST is adapted for recording compacted information for at least one of a truncate and an erase operation applied on the source instance. The RST of the source instance is updated at a source component with the compacted information. The updated RST is transmitted from the source instance to the replicated instance. Based on the RST of the source instance and the RST of the replicated instance, data representative of a most recent position on the source component from which data should be transmitted to a replicated component to achieve a full synchronization is determined.

Growing community of inventors

Raanana, Israel

Elena Drobchenko