# US 2013/0254481 A1 · Presentation of a read-only clone lun to a host device as a snapshot of a parent lun

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254481 A1
- Document ID: US20130254481A1
- Status: Published application
- Kind: A1
- Application number: 13/784,194
- Filed: 2013-03-04
- Published: 2013-09-26
- Earliest claimed: 2010-01-08
- Assignees: Network Appliance, Inc.
- Applicants: Network Appliance, Inc.
- Inventors: Ameya Prakash Usgaonkar; Kamlesh Advani
- Web page: https://patentgrep.com/patent/US20130254481A1

## CPC

- G06F 3/065: {Replication mechanisms}
- G06F 3/0608: {Saving storage space on storage systems}
- G06F 3/0617: {in relation to availability}
- G06F 3/0641: {De-duplication techniques}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0683: {Plurality of storage devices}
- G06F 11/1435: {using file system or storage system metadata}
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method, apparatus, and system of presentation of a read-only clone Logical Unit Number (LUN) to a host device as a snapshot of a parent LUN are disclosed. In one embodiment, a method includes generating a read-write clone LUN of a parent LUN and coalescing an identical data instance of the read-write clone LUN and the parent LUN in a data block of a volume of a storage system. A block transfer protocol layer is modified to refer the read-write clone LUN as a read-only clone LUN, according to the embodiment. Furthermore, according to the embodiment, the read-only clone LUN is presented to a host device as a snapshot of the parent LUN.

## Claims

### Claim at position 1

1-23. (canceled)

### Claim 24

A machine implemented method comprising:
a processor of a storage system generating a read-write clone storage object of a parent storage object representing storage space for storing information at the storage system;
the processor modifying a data structure to refer to the read-write clone storage object as a read-only clone storage object; and presenting the read-only clone storage object as a snapshot of the parent storage object; and
the processor coalescing an identical data instance of the read-write clone storage object and the parent storage object.

### Claim 25 (depends on 24)

The method of claim 24, wherein the parent storage object is a parent logical unit number (LUN) that is presented by the storage system to a computing system, the read-write clone storage object is a read-write clone LUN and the read-onle clone storage object is a read-only clone LUN.

### Claim 26 (depends on 25)

The method of claim 25, further comprising:
modifying a Small Computer System Interface (SCSI) target to refer to the read-write clone LUN as the read-only clone LUN.

### Claim 27 (depends on 26)

The method of claim 26, further comprising:
differentiating the read-write clone LUN from the parent LUN with a SCSI inquiry data.

### Claim 28 (depends on 24)

The method of claim 24, wherein the data structure is at a block transfer layer level.

### Claim 29 (depends on 28)

The method of claim 28, further comprising:
revising the block transfer protocol layer to render the read-only clone storage object for presentation as the snapshot of the parent storage object.

### Claim 30 (depends on 24)

The method of claim 24, wherein the identical data instance of the read-write clone storage object and the parent storage object are coalesced in a data block of a storage volume of the storage system.

### Claim 31

A machine implemented method, comprising:
generating a read-write clone Logical Unit Number (LUN) of a parent LUN;
coalescing an identical data instance of the read-write clone LUN and the parent LUN;
modifying a data structure to refer to the read-write clone LUN as a read-only clone LUN;
presenting the read-only clone LUN as a snapshot of the parent LUN;
coalescing the identical data instance of the read-write clone LUN and the parent LUN; and
preventing a modification of the read-only clone LUN using a command that refers to the read-only clone LUN as the snapshot.

### Claim 32 (depends on 31)

The method of claim 31, wherein the data structure is at a block transfer protocol layer level.

### Claim 33 (depends on 32)

The method of claim 32, further comprising:
revising the block transfer protocol layer to render the read-only clone LUN for presentation to a host device as the snapshot of the parent LUN.

### Claim 34 (depends on 30)

The method of claim 30, wherein the identical data instance of the read-write clone LUN and the parent LUN are coalesced in a data block of a storage volume of the storage system.

### Claim 35 (depends on 31)

The method of claim 31, further comprising:
modifying a Small Computer System Interface (SCSI) target to refer to the read-write clone LUN as the read-only clone LUN.

### Claim 36 (depends on 35)

The method of claim 35, further comprising:
differentiating the read-write clone LUN from the parent LUN with a SCSI inquiry data.

### Claim 37

A system comprising:
a host device having an initiator that requests a snapshot of a parent Logical Unit Number (LUN); and
a storage system coupled to the host device is configured to generate a read-write clone LUN of the parent LUN; present a read-only clone LUN of the parent LUN to the host device as the snapshot of the parent LUN; and coalesce an identical data instance of the read-write clone LUN and the parent LUN.

### Claim 38 (depends on 37)

The system of claim 37, further comprising:
a target module of the storage system to modify a small computer system interface (SCSI) target to refer to the read-write clone LUN as read-only clone LUN.

### Claim 39 (depends on 37)

The system of claim 37, wherein the read-write clone LUN is differentiated from the parent LUN with a SCSI inquiry data.

### Claim 40 (depends on 37)

The system of claim 37, wherein the storage system implements a block sharing operation between the read-write clone LUN and the parent LUN.

### Claim 41 (depends on 37)

A system of claim 37, wherein a modification of the read-only clone LUN is prevented by a command that refers to the read-only clone LUN as the snapshot.

### Claim 42 (depends on 41)

The system of claim 41, wherein a block transfer protocol layer is revised to render the read-only clone LUN for presentation to the host device as the snapshot of the parent LUN.

### Claim 43 (depends on 37)

The system of claim 37, wherein the identical data instance of the read-write clone LUN and the parent LUN are coalesced such that unique data blocks of the parent LUN and the read-write clone LUN are stored in a volume of the storage system.

### Claim 44 (depends on 37)

The system of claim 37, wherein the storage system includes a processor executable module for coalescing the identical data instance of the read-write clone LUN and the parent LUN.
