Cloning a virtual disk in a storage platform

• US 9,798,489 B2
• Filed: 07/02/2014
• Issued: 10/24/2017
• Est. Priority Date: 07/02/2014
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: Hedvig Inc. (CommVault Systems Incorporated)
• Inventors: Lakshman, Avinash, Lakshman, Srinivas
• Primary Examiner(s): Thai, Tuan
• Assistant Examiner(s): Gossage, Glenn
• Application Number:
  US14/322,867
• Publication Number:
  US 20160004449A1
• Time in Patent Office: 1,210 Days
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0664 at device level, e.g. emulation of a storage device or system
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

An administrator provisions a virtual disk in a remote storage platform and defines policies for that virtual disk. A virtual machine writes to and reads from the storage platform using any storage protocol. Virtual disk data within a failed storage pool is migrated to different storage pools while still respecting the policies of each virtual disk. Snapshot and revert commands are given for a virtual disk at a particular point in time and overhead is minimal. A virtual disk is cloned utilizing snapshot information and no data need be copied. Any number of Zookeeper clusters are executing in a coordinated fashion within the storage platform, thus increasing overall throughput. A timestamp is generated that guarantees a monotonically increasing counter, even upon a crash of a virtual machine. Any virtual disk has a “hybrid cloud aware” policy in which one replica of the virtual disk is stored in a public cloud.

Claims

1. A method of cloning a virtual disk within a storage platform, said method comprising:

storing data for said virtual disk onto computer nodes of said storage platform, said stored data stored as blocks of data wherein each block of data has an associated version number, said virtual disk having a plurality of first policies regarding how said blocks of data are stored on said storage platform;

issuing a clone command for said virtual disk having a current version without copying contents of said virtual disk, said clone command indicating a prior version of said virtual disk from which a clone virtual disk should be created and including at least one second policy;

provisioning said clone virtual disk within said storage platform using said at least one second policy of said clone virtual disk different from said first policies regarding how data of said clone virtual disk is stored on said storage platform;

writing first data from a software application on a computer server remote from said storage platform onto said clone virtual disk, said data being written onto storage disks of said storage platform using said at least one second policy; and

reading second data from said clone virtual disk by walking a version tree of said virtual disk from said prior version to a root to obtain version numbers for a read request, and then performing said read request to read said second data from said virtual disk using said version numbers.

2. A method as recited in claim 1 wherein said clone virtual disk is created after said issuing said clone command without copying contents of said virtual disk and without allocating disk space in said storage platform.

3. The method as recited in claim 1 further comprising:

recording, on a metadata computer node within said storage platform, said current version of said virtual disk and said version tree of said virtual disk indicating from which version of said virtual disk a later version originates.

4. A method as recited in claim 1 wherein said at least one second policy includes at least one of replication factor, residence, compressed, de-duplication, replication policy, and cache enabled.

5. A method as recited in claim 1 wherein said read request is sent by a controller virtual machine of said computer server to said computer nodes, and the obtained version numbers are sent by the controller virtual machine when the read request is sent.

6. A method as recited in claim 1 further comprising:

using said version numbers by only reading said second data that includes one of said version numbers.