Symantec Operating Corporation

Hewlett Packard Enterprise Development LP

Symantec Corporation

Dell Products Inc.

Quest Software Inc.

Veritas Operating Corporation

Symantec Operating Company

Michael E Root

Ronald S Karr

Goutham Rao

Vinod Jayaraman

Murali Bashyam

Abhijit Dinkar

Mark Taylor

Oleg Kiselev

Anand A Kekre

Gopal Sharma

Tomasz Barszczak

Kirubakaran Kaliannan

Charles Silvers

Naveen Bali

Arun M Rokade

John Colgrove

Niranjan Sanjiv Pendharkar

Angshuman Bezbaruah

Raghu Krishnamurthy

Vikas Gupta

Praveen Killamsetti

Deepak Tawri

Gurunatha Karaje

Anurag Choudhary

Kedar M Karmarkar

Randall K Shingai

Kevin Kauffman

Nguyen Truong

Ashish Agarwal

Cristian Medina Abkarian

Neha Siddha

Liam McArdle

Zaid Bin Tariq

Kati Rader

A technique includes causing an agent device to setup a replication partnership between a first storage node and a second storage. Causing the agent device to setup the replication partnership includes configuring a proxy server that is associated with the second storage node to establish a secure communication channel for the replication partnership over a public network. Configuring the proxy server includes storing in the proxy server credentials for authenticating the first storage node to use the secure communication channel; and establishing port translations to be used in the secure communication channel in communicating replication data between the first storage node and the second storage node. Causing the agent device to setup the replication partnership may also include communicating replication partnership information to the second node.

Replicating data over a public network

Techniques and mechanisms are provided for migrating data blocks around a cluster during node addition and node deletion. Migration requires no downtime, as a newly added node is immediately operational while the data blocks are being moved. Blockmap files and deduplication dictionaries need not be updated.

Data block migration

According to examples, an apparatus may include a processor and a non-transitory machine-readable storage medium comprising instructions executable by the processor to assign a first object identifier and a data identifier to a first volume, the first object identifier being assigned exclusively to the first volume. The instructions may also be executable by the processor to identify an identifier of a second volume, determined whether the identifier of the second volume matches the data identifier, and based on a determination that the identifier of the second volume matches the data identifier of the first volume, configure a replication relationship between the first volume and the second volume.

Assignment of a data identifier to first and second volumes

In some examples, with respect to pool partner based replication, a first pool may be generated for a first storage array and may include a first volume of data stored in a storage space of the first storage array. A second pool may be generated for a second storage array and may include a second volume to receive data replicated from the first volume. Based on the generation of the second pool, first and second pool partners respectively representing end points for communication with the first and second pools may be generated. A volume collection may be generated and may include identifications of the first pool partner and the second pool partner, and a first volume identification of the first volume. Based on the volume collection, replication of the first volume may be performed from the first pool to the second volume of the second pool.

Pool partner based replication

Techniques and mechanisms provide a storage optimization manager. Data may be optimized and maintained on various nodes in a cluster. Particular nodes may be overburdened while other nodes remain relatively unused. Techniques are provided to efficiently optimize data onto nodes to enhance operational efficiency. Data access requests for optimized data are monitored and managed to allow for intelligent maintenance of optimized data.

Storage optimization manager

A computer-implemented method for reclaiming storage space from deleted volumes on thin-provisioned disks may include: 1) identifying a deleted volume, 2) identifying storage space on a thin-provisioned disk that was allocated to the deleted volume, 3) saving information that identifies the storage space, 4) identifying a policy that specifies reclaiming the storage space asynchronously with respect to the deleted volume, and then 5) reclaiming the storage space asynchronously with respect to deletion of the volume in accordance with the policy. Various other methods, systems, and computer-readable media are also disclosed.

Systems and methods for reclaiming storage space from deleted volumes on thin-provisioned disks

Systems and methods for information storage replication are presented. In one embodiment a storage flow control method includes receiving a memory operation indication; performing a pre-reserve allocation process before proceeding with the memory operation, wherein the pre-reserve allocation process includes converting available unallocated memory space to allocated memory space if there is sufficient available unallocated memory space to perform the memory operation; executing the memory operation if the pre-reserve allocation process returns an indication there is sufficient memory space allocated to perform the memory operation; and aborting the memory operation if the pre-reserve allocation process returns an indication there is sufficient memory space allocated to perform the memory operation. In one embodiment, the memory operation is a write operation. The memory operation can be a write operation.

Storage systems and methods with pre-reserve allocation

A computer-implemented method for reclaiming storage space on striped volumes may include: 1) identifying a volume striped across a set of storage devices, 2) identifying a reclamation request to reclaim storage space allocated to the striped volume and then, for at least one device in the set of storage devices, 3) identifying stripes of storage on the device that are covered by the reclamation request, 4) creating a consolidated reclamation request for the device that identifies each stripe of storage on the device that is covered by the reclamation request, and then 5) issuing the consolidated reclamation request to the device. Various other methods, systems, and computer-readable media are also disclosed.

Systems and methods for reclaiming storage space on striped volumes

Various embodiments of a system and method for enabling multiple computers to mount a file system are described herein. The file system may be mounted on one computer, and a snapshot copy of the file system may be created and mounted on a second computer. Data for a particular file in the file system may be stored at particular storage locations on a storage device. In response to a read request to access data for the particular file through the file system, the data stored at the particular storage locations may be read and returned. Similarly, in response to a read request to access data for the particular file through the snapshot copy of the file system, the data stored at the particular storage locations may be read and returned.

System and method for mounting a file system on multiple host computers

A system for volume replication in a distributed block virtualization environment includes a first and a second set of one or more physical block devices, a first and a second volume server, one or more volume clients, and a replication manager. The first volume server may be configured to aggregate storage in the first set of one or more physical block devices into one or more logical volumes, and to make the one or more logical volumes accessible to the one or more volume clients. The replication manager may be configured to operate in cooperation with the first and second volume servers and the one or more volume clients to maintain a replica of at least a subset of the one or more logical volumes at the second set of one or more physical block devices.

System and method for volume replication in a storage environment employing distributed block virtualization

A method, system, computer system and computer program product to synchronize data and a snapshot of the data taken at a given point in time. Persistent data change maps are used to track changes made to data after a snapshot of the data is taken. Changes to the data are tracked using a persistent accumulator map, and changes to the data with respect to a second set of data are tracked using a persistent volume map. The persistent accumulator map is updated with each update of the data. Persistent volume maps are updated when a subsequent snapshot of the data is taken. Only changes to the data made after the snapshot was taken are applied to synchronize the snapshot with the data so that all of the data is not copied. Snapshots can be located in a physically separate location from the data itself.

Maintaining persistent data change maps for fast data synchronization and restoration

A method and apparatus for improving the boot sequence of a computer clone. The kernel within an operating system is designed to always access special devices within the computer's memory using a mount path that is hard coded into the kernel for each of the special devices. When the computer is cloned, the special devices are copied to a second computer without the need for subsequent alteration of the filesystem.

Method and apparatus for improving a computer boot sequence

A method, computer program product, computer system and system that enable symmetrical data change tracking with respect to a set of data and a copy of the set of data, referred to as a snapshot or a second set of data. The data and the copy may be independently updated after the two sides are 'split.' A join may be performed of the two sides of the split to resynchronize the data. For the first set of data, an accumulator map tracks changes to the first set of data and a volume map tracks changes to the first set of data with respect to a second set of data. For the second set of data (the snapshot), a second accumulator map tracks changes to the second set of data and a second volume map tracks changes to the second set of data with respect to the first set of data.

Symmetrical data change tracking

Growing community of inventors

San Jose, CA, United States of America

Michael E Root