IP Library Granted Patent US 11,698,838
Granted Patent B1
US 11,698,838 · App. 17/589,695 · Granted Jul 11, 2023

Data storage volume re-bind method

Inventor: Naruki Kurata (San Jose, CA)
Assignee: HITACHI, LTD.
G06F11/1469G06F3/065G06F3/067G06F3/0614G06F3/0644
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,698,838
App. No.
17/589,695
Granted
Jul 11, 2023
Kind
B1
Abstract

Disclosed herein is a technique to automatically re-bind applications and storage volumes during recovery from planned outage or platform failure and disaster recovery. Such implementations can involve managing volume management information that maps volume claim information with a logical volume identifier associated with persistent volume information; and for receipt of a request for a new volume, referencing the volume management information to retrieve an associated logical volume identifier and the persistent volume information based on the volume claim information associated with the request; and providing the retrieved persistent volume information to a volume provisioning function.

Claims (42)

1. A method, comprising:

managing volume management information that maps volume claim information with a logical volume identifier associated with persistent volume information; and

for receipt of a request for a new volume:

referencing the volume management information to retrieve an associated logical volume identifier and the persistent volume information based on volume claim information associated with the request; and

providing the retrieved persistent volume information to a volume provisioning function,

wherein the referencing the volume management information to retrieve the associated logical volume identifier and the persistent volume information based on the volume claim information associated with the request comprises:

determining whether a corresponding data exists in the volume management information associated with a claim name from the persistent volume information;

for a determination that the corresponding data exists, retrieving the associated persistent volume information comprising persistent volume identifier and persistent volume attributes, from the volume management information.

2. The method of claim 1 , wherein

for a determination that the corresponding data does not exist:

creating a new logical volume with a new logical volume identifier;

creating a new persistent volume identifier based on the new logical volume and the new logical volume identifier; and

adding a new data to the volume management information comprising the new logical volume identifier.

3. The method of claim 1 , further comprising, for the volume provisioning function creating new persistent volume metadata responsive to the retrieved persistent volume information:

during a deployment of the new persistent volume metadata:

executing a hook process to determine whether a corresponding data exists in the volume management information associated with a claim name from the persistent volume information;

for a determination that the corresponding data exists, retrieving the associated logical volume identifier and the persistent volume information comprising persistent volume identifier and persistent volume attributes, from the volume management information; and

overwriting persistent volume metadata attributes with the retrieved persistent volume attributes in the volume management information.

4. The method of claim 1 , further comprising, for the volume provisioning function creating new persistent volume metadata responsive to the retrieved persistent volume information:

during a binding of a persistent volume claim to the new persistent volume metadata:

executing a hook process to determine whether a corresponding data exists in the volume management information associated with a claim name from the persistent volume information;

for a determination that the corresponding data exists, retrieving the associated logical volume identifier and the persistent volume information comprising persistent volume identifier and persistent volume attributes, from the volume management information;

copying volume metadata from a previous logical volume associated with a previous persistent volume metadata to a new logical volume.

5. The method of claim 1 , further comprising, for the volume provisioning function creating new persistent volume metadata responsive to the retrieved persistent volume information:

during a binding of a persistent volume claim to the new persistent volume metadata:

executing a hook process to determine whether a corresponding data exists in the volume management information associated with a claim name from the persistent volume information;

for a determination that the corresponding data exists, retrieving the associated logical volume identifier and the persistent volume information comprising persistent volume identifier and persistent volume attributes, from the volume management information; and

copying data from a previous logical volume associated with a previous persistent volume metadata to a new logical volume.

6. The method of claim 1 , wherein the method is executed by one of a container orchestrator or a hypervisor.

7. A method, comprising:

managing volume management information that maps volume claim information with a logical volume identifier associated with persistent volume information;

for receipt of a request for a new volume:

providing temporary persistent volume information to a volume provisioning function, and

for the volume provisioning function deploying a persistent volume metadata responsive to the logical volume identifier and the persistent volume information:

during a deployment of a persistent volume;

referencing the volume management information to retrieve an associated logical volume identifier and the persistent volume information based on the volume claim information; and

overwrite persistent volume metadata attributes with retrieved persistent volume attributes in the volume management information.

8. A method, comprising:

managing volume management information that maps volume claim information with a logical volume identifier associated with persistent volume information;

generating a persistent volume metadata using the logical volume identifier and the persistent volume information in the volume management information prior to receipt of a request for a new volume, and

performing automatic binding of a persistent volume claim to the persistent volume metadata.

9. The method of claim 8 , wherein the method is executed by one of a container orchestrator or a hypervisor.

Assignments (2)
COMPANY SPLIT Recorded Aug 20, 2024
From: HITACHI, LTD.
To: HITACHI VANTARA, LTD.
Reel/Frame 069518/0761 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2022
From: KURATA, NARUKI
To: HITACHI, LTD.
Reel/Frame 058836/0615 →
Cited By (2)
US 12,561,078 US 12,705,107