# US 2021/0176513 A1 · Storage virtual machine relocation

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

- Number: US 2021/0176513 A1
- Document ID: US20210176513A1
- Status: Published application
- Kind: A1
- Application number: 17/182,576
- Filed: 2021-02-23
- Published: 2021-06-10
- Earliest claimed: 2015-10-15
- Assignees: NetApp, Inc.
- Applicants: NetApp Inc.
- Inventors: Balaji Ramani; Kazunobu Nishime; Pankti Vinay Majmudar; Prachi Bapurao Deshmukh; Susan M. Coatney; Vijay Singh
- Web page: https://patentgrep.com/patent/US20210176513A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/0647: {Migration mechanisms}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 11/14: Error detection or correction of the data by redundancy in operations (error detection or correction of the data by redundancy in hardware G06F11/16)
- G06F 11/16: Error detection or correction of the data by redundancy in hardware
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2033: {switching over of hardware resources}
- G06F 11/2092: {Techniques of failing over between control units}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/3034: {where the computing system component is a storage system, e.g. DASD based or network based (digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/3433: {for load management (allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029)}
- H04N 21/21805: {enabling multiple viewpoints, e.g. using a plurality of cameras}
- H04N 21/2187: Live feed
- H04N 21/23439: {for generating different versions}
- H04N 21/2387: Stream processing in response to a playback request from an end-user, e.g. for trick-play
- H04N 21/2393: {involving handling client requests (scheduling or organising the servicing of application requests H04L67/60)}
- H04N 21/2665: Gathering content from different sources, e.g. Internet and satellite
- H04N 21/2668: Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles {(information retrieval from the Internet by querying with filtering and personalisation G06F16/9535; arrangements for replacing or switching information during the broadcast H04H20/10; push services over packet-switching network H04L12/1859; adaptation of message content in packet-switching networks H04L51/063)}
- H04N 21/458: Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules {; time-related management operations (arrangements for replacing or switching information during the broadcast or during the distribution H04H20/10)}
- H04N 21/4622: {Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet (web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859)}
- H04N 21/47202: {for requesting content on demand, e.g. video on demand}
- H04N 21/6408: Unicasting
- H04N 21/8549: Creating video summaries, e.g. movie trailer {(retrieval in video databases by using presentations in form of a video summary G06F16/739)}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F 2201/815: Virtual
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

One or more techniques and/or devices are provided for storage virtual machine relocation (e.g., ownership change) between storage clusters. For example, operational statistics of a first storage cluster and a second storage cluster may be evaluated to identify a set of load balancing metrics. Ownership of one or more storage aggregates and/or one or more storage virtual machines may be changed (e.g., permanently changed for load balancing purposes or temporarily changed for disaster recovery purposes) between the first storage cluster and the second storage cluster utilizing zero-copy ownership change operations based upon the set of load balancing metrics. For example, if the first storage cluster is experiencing a relatively heavier load of client I/O operations and the second storage cluster has available resources, ownership of a storage aggregate and a storage virtual machine may be switched from the first storage cluster to the second storage cluster for load balancing.

## Claims

### Claim 1

A method, comprising:
hosting a storage virtual machine at a first cluster for providing clients with access to client data within a storage aggregate; and
implementing a relocation of the storage virtual machine from the first cluster to a second cluster, comprising:
switching ownership of the storage aggregate from being owned by the first cluster to being owned by the second cluster; and
switching ownership of the storage virtual machine from being owned by the first cluster to being owned by the second cluster, wherein the storage virtual machine owned by the second cluster provides the clients with access to the client data within the storage aggregate owned by the second cluster.

### Claim 2 (depends on 1)

The method of claim 1, comprising:
mirroring the client data within a storage device of the first cluster into a mirror storage device of the second cluster before implementation of the relocation.

### Claim 3 (depends on 2)

The method of claim 2, wherein the switching ownership of the storage aggregate comprises:
utilizing a zero-copy ownership change operation to switch ownership of the storage aggregate to the second cluster using replicated data within the mirror storage device of the second cluster.

### Claim 4 (depends on 3)

The method of claim 3, wherein switching ownership of the storage aggregate comprises:
configuring the storage virtual machine to access the client data of the storage aggregate through the mirror storage device.

### Claim 5 (depends on 1)

The method of claim 1, wherein the switching ownership of the storage virtual machine comprises:
utilizing a zero-copy ownership change operation to switch ownership of the storage aggregate from being owned by the first cluster to being owned by the second cluster.

### Claim 6 (depends on 1)

The method of claim 1, wherein a plurality of storage virtual machines, including the storage virtual machine, are owned by the first cluster, and wherein the method comprises:
switching ownership of the plurality of storage virtual machines from the first cluster to the second cluster.

### Claim 7 (depends on 1)

The method of claim 1, comprising:
maintaining non-disruptive client access to the client data through the storage aggregate during switchover of ownership of the storage aggregate and the storage virtual machine.

### Claim 8 (depends on 1)

The method of claim 1, comprising:
unmounting the storage aggregate for changing ownership of a storage device, associated with the storage aggregate, from the first cluster to the second cluster.

### Claim 9 (depends on 1)

The method of claim 1, comprising:
maintaining a replica storage virtual machine at the second cluster as a replica of the storage virtual machine.

### Claim 10 (depends on 1)

The method of claim 1, comprising:
switching ownership of the storage virtual machine and the aggregate based upon the first cluster failing.

### Claim 11 (depends on 1)

The method of claim 1, comprising:
switching ownership of the storage virtual machine and the aggregate based upon load balancing metrics.

### Claim 12 (depends on 1)

The method of claim 1, wherein the second cluster is designated as a temporary owner of the storage aggregate.

### Claim 13 (depends on 1)

The method of claim 1, wherein the second cluster is designated as a permanent owner of the storage aggregate.

### Claim 14 (depends on 1)

The method of claim 1, wherein switching ownership of the storage aggregate comprises:
onlining the storage aggregate to access mirrored client data within a mirrored storage device, wherein the mirrored client data corresponds to the client data that was mirrored from a storage device at the first cluster to the mirrored storage device at the second cluster while the first cluster owned the storage aggregate.

### Claim 15

A non-transitory machine readable medium having stored thereon instructions, which when executed by a machine, causes the machine to:
host a storage virtual machine at a first cluster for providing clients with access to client data within a storage aggregate; and
implement a relocation of the storage virtual machine from the first cluster to a second cluster, comprising:
switching ownership of the storage aggregate from being owned by the first cluster to being owned by the second cluster; and
switching ownership of the storage virtual machine from being owned by the first cluster to being owned by the second cluster, wherein the storage virtual machine owned by the second cluster provides the clients with access to the client data within the storage aggregate owned by the second cluster.

### Claim 16 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the instructions cause the machine to:
perform a zero-copy ownership change operation to online the storage aggregate to access mirrored client data within a mirrored storage device, wherein the mirrored client data corresponds to the client data that was mirrored from a storage device at the first cluster to the mirrored storage device at the second cluster while the first cluster owned the storage aggregate.

### Claim 17 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the instructions cause the machine to:
utilizing a zero-copy ownership change operation to switch ownership of the storage aggregate from being owned by the first cluster to being owned by the second cluster.

### Claim 18 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the instructions cause the machine to:
switch ownership of the storage virtual machine and the aggregate based upon the first cluster failing.

### Claim 19 (depends on 15)

The non-transitory machine readable medium of claim 15, wherein the instructions cause the machine to:
switch ownership of the storage virtual machine and the aggregate based upon load balancing metrics.

### Claim 20

A computing device comprising:
a memory comprising machine executable code; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
host a storage virtual machine at a first cluster for providing clients with access to client data within a storage aggregate; and
implement a relocation of the storage virtual machine from the first cluster to a second cluster, comprising:
switching ownership of the storage aggregate from being owned by the first cluster to being owned by the second cluster; and
switching ownership of the storage virtual machine from being owned by the first cluster to being owned by the second cluster, wherein the storage virtual machine owned by the second cluster provides the clients with access to the client data within the storage aggregate owned by the second cluster.
