# US 2023/0273753 A1 · Reducing potential data-loss scenarios when using ephemeral storage as backing storage for journaling by a virtual storage system

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

- Number: US 2023/0273753 A1
- Document ID: US20230273753A1
- Status: Published application
- Kind: A1
- Application number: 18/168,844
- Filed: 2023-02-14
- Published: 2023-08-31
- Earliest claimed: 2022-02-25
- Assignees: NetApp, Inc.
- Applicants: NetApp, Inc.
- Inventors: Sangramsinh Pandurang Pawar; Per Olov Wahlstrom; William Derby Dallas; Houze Xu; Ruitao Duan; Rajesh Rajaraman
- Web page: https://patentgrep.com/patent/US20230273753A1

## CPC

- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 11/1451: {by selection of backup contents}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/061: {Improving I/O performance}
- G06F 3/0647: {Migration mechanisms}
- G06F 3/0656: {Data buffering arrangements}
- G06F 3/0662: {Virtualisation aspects}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 11/07: Responding to the occurrence of a fault, e.g. fault tolerance
- G06F 11/1456: {Hardware arrangements for backup}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for flushing an operation log journal to both ephemeral storage and persistent storage during a shutdown sequence of a virtual storage system to minimize data-loss scenarios are provided. According to one embodiment, the shutdown or reboot scenarios that result in loss of data are minimized by using persistent storage as a backup to ephemeral storage when the scenario results in rehosting of virtual storage system. For example, responsive to an event indicative of an imminent shutdown or reboot of the virtual storage system, vNVRAM memory may be flushed to both ephemeral storage and persistent storage (e.g., a boot disk). In this manner, when the virtual storage system is rehosted after an unplanned shutdown or reboot resulting from an unrecoverable host error (other than an unrecoverable hardware failure), the operation log journal may be recovered from persistent storage to facilitate vNVRAM replay and avoid data loss.

## Claims

### Claim 1

A method comprising:
after receiving an event indicative of an imminent shutdown or reboot of a compute instance of a cloud environment in which a virtual storage system is operating, flushing, by the virtual storage system, an operation log maintained by the virtual storage system within a local memory of a host on which the compute instance is running to both ephemeral storage associated with the compute instance and persistent storage; and
during subsequent boot processing of the virtual storage system, facilitating replay of the operation log by:
determining whether the virtual storage system has been rehosted;
responsive to an affirmative determination that the virtual storage system has been rehosted, loading the operation log from the persistent storage; and
responsive to a negative determination that the virtual storage system has been rehosted, loading the operation log from the ephemeral storage.

### Claim 2 (depends on 1)

The method of claim 1, wherein determination regarding whether the virtual storage system has been rehosted is based on a unique identifier associated with the ephemeral storage.

### Claim 3 (depends on 1)

The method of claim 1, wherein after a recoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on the host.

### Claim 4 (depends on 1)

The method of claim 1, wherein after an unrecoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on a new host within the cloud environment.

### Claim 5 (depends on 1)

The method of claim 1, wherein the persistent storage comprises a boot disk on which boot image files associated with the virtual storage system are stored.

### Claim 6 (depends on 1)

The method of claim 1, wherein the compute instance comprises a virtual machine.

### Claim 7 (depends on 1)

The method of claim 1, wherein the compute instance comprises a container.

### Claim 8

A virtual storage system comprising:
a processing resource; and
instructions that when executed by the processing resource cause the virtual storage system to:
after receiving an event indicative of an imminent shutdown or reboot of a compute instance of a cloud environment in which the virtual storage system is operating, flush an operation log maintained by the virtual storage system within a local memory of a host on which the compute instance is running to both ephemeral storage associated with the compute instance and persistent storage; and
during subsequent boot processing of the virtual storage system, facilitate replay of the operation log by:
determining whether the virtual storage system has been rehosted;
responsive to an affirmative determination that the virtual storage system has been rehosted, loading the operation log from the persistent storage; and
responsive to a negative determination that the virtual storage system has been rehosted, loading the operation log from the ephemeral storage.

### Claim 9 (depends on 8)

The virtual storage system of claim 8, wherein after a recoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on the host.

### Claim 10 (depends on 8)

The virtual storage system of claim 8, wherein after an unrecoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on a new host within the cloud environment.

### Claim 11 (depends on 8)

The virtual storage system of claim 8, wherein the persistent storage comprises a boot disk on which boot image files associated with the virtual storage system are stored.

### Claim 12 (depends on 8)

The virtual storage system of claim 8, wherein the compute instance comprises a virtual machine.

### Claim 13 (depends on 8)

The virtual storage system of claim 8, wherein the compute instance comprises a container.

### Claim 14

A non-transitory machine readable medium storing instructions, which when executed by a processing resource of a virtual storage system deployed within a compute instance of a cloud environment, cause the virtual storage system to:
after receiving an event indicative of an imminent shutdown or reboot, flush an operation log maintained by the virtual storage system within a local memory of a host on which the compute instance is running to both ephemeral storage associated with the compute instance and persistent storage; and
during subsequent boot processing of the virtual storage system, facilitate replay of the operation log by:
determining whether the virtual storage system has been rehosted;
responsive to an affirmative determination that the virtual storage system has been rehosted, loading the operation log from the persistent storage; and
responsive to a negative determination that the virtual storage system has been rehosted, loading the operation log from the ephemeral storage.

### Claim 15 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein determination regarding whether the virtual storage system has been rehosted is based on a unique identifier associated with the ephemeral storage.

### Claim 16 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein after a recoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on the host.

### Claim 17 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein after an unrecoverable failure associated with the host, a cloud provider operating the cloud environment brings up the virtual storage system within a new compute instance on a new host within the cloud environment.

### Claim 18 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the persistent storage comprises a boot disk on which boot image files associated with the virtual storage system are stored.

### Claim 19 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the compute instance comprises a virtual machine.

### Claim 20 (depends on 14)

The non-transitory machine readable medium of claim 14, wherein the compute instance comprises a container.
