IP Library Granted Patent US 12,608,494
Granted Patent B2
US 12,608,494 · App. 18/596,785 · Granted Apr 21, 2026

Storage and data protection method of storage

Inventors: Akira Deguchi (Tokyo, JP); Yusuke Yamaga (Tokyo, JP)
Assignee: HITACHI VANTARA, LTD.
G06F21/62G06F11/1451G06F11/1464G06F2201/825G06F2201/84
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 12,608,494
App. No.
18/596,785
Granted
Apr 21, 2026
Kind
B2
Abstract

To safely store data. A storage 200 connected to another storage 400 via a network, the storage 200 including: a processor 216 configured to process data to be stored in a storage device 220 , in which the processor 216 is configured to acquire a first snapshot for a volume generated using a storage area of the storage device, compare a second snapshot, which is a previously acquired snapshot, with the first snapshot to retrieve incremental data, transfer the incremental data to the other storage and store the incremental data as backup data, and set lock of the backup data stored in the other storage.

Claims (55)

1 . A storage connected to another storage via a network, the storage comprising:

a processor configured to process data to be stored in a storage device, wherein

the processor is configured to:

acquire a first snapshot for a volume generated using a storage area of the storage device,

compare a second snapshot, which is a previously acquired snapshot, with the first snapshot to retrieve incremental data,

transfer the incremental data to the other storage and store the incremental data as backup data,

set a lock of the backup data stored in the other storage,

set a lock for the first snapshot and the second snapshot at the time of acquiring the first snapshot and the second snapshot, and

calculate, based on schedule information of a backup set by a user, a period of a lock set for the first snapshot at the time of acquiring the first snapshot, and

wherein the lock of the first snapshot prohibits deletion and overwriting of data to be locked.

2 . The storage according to claim 1 , wherein

the processor is configured to calculate and determine a period of the lock set for the backup data, based on a lock period designated by a user or a holding number of backups and a backup frequency set by the user.

3 . The storage according to claim 1 , wherein

the processor is configured to determine, based on a lock target designated by a user regarding the lock for the first snapshot and the lock for the backup data, whether to set the lock.

4 . The storage according to claim 1 , wherein

the processor is configured to:

calculate a total transfer amount of the data transferred to the other storage,

acquire a storage amount of the transferred data in the other storage, and

detect that there is a cyber attack when the total transfer amount and the storage amount are inconsistent.

5 . The storage according to claim 4 , wherein

the processor is configured to extend a lock period of the backup data transferred to the other storage when the cyber attack is detected.

6 . The storage according to claim 1 , wherein

the other storage is a storage disposed in a cloud, and

the storage connected to the other storage is a storage disposed in an on-premises.

7 . A storage connected to another storage via a network, the storage comprising:

a processor configured to process data to be stored in a storage device, wherein

the processor is configured to:

acquire a first snapshot for a volume generated using a storage area of the storage device,

compare a second snapshot, which is a previously acquired snapshot, with the first snapshot to retrieve incremental data,

transfer the incremental data to the other storage and store the incremental data as backup data,

set a lock of the backup data stored in the other storage,

set a lock for the first snapshot and the second snapshot at the time of acquiring the first snapshot and the second snapshot, and issue an alert when the first snapshot and the second snapshot are not locked,

wherein the lock of the first snapshot and the second snapshot prohibits deletion and overwriting of data to be locked.

8 . A storage connected to another storage via a network, the storage comprising:

a processor configured to process data to be stored in a storage device, wherein

the processor is configured to:

acquire a first snapshot for a volume generated using a storage area of the storage device,

compare a second snapshot, which is a previously acquired snapshot, with the first snapshot to retrieve incremental data,

transfer the incremental data to the other storage and store the incremental data as backup data,

set a lock of the backup data stored in the other storage, and

set, for the backup data, a lock period shorter than a requested lock period, which is a lock period designated by a user, and in a case where the already-set lock period is within a predetermined range before expiration and determining, based on predetermined criteria, to extend the lock period when the expiration of the lock period is earlier than expiration of the requested lock period.

9 . A storage connected to another storage via a network, the storage comprising:

a processor configured to process data to be stored in a storage device,

wherein

the processor is configured to:

acquire a first snapshot for a volume generated using a storage area of the storage device,

compare a second snapshot, which is a previously acquired snapshot, with the first snapshot to retrieve incremental data,

transfer the incremental data to the other storage and store the incremental data as backup data,

set a lock of the backup data stored in the other storage, and

after completing transfer of the backup data to the other storage, delete the data after waiting for a lock release of backup data older than transferred backup data.

10 . The storage according to claim 9 , wherein

upon receiving a deletion instruction of the backup data, the other storage is configured to

identify and record an object,

monitor release of a lock of the identified object, and

delete the object when the lock of the identified object is released.

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 Mar 6, 2024
From: DEGUCHI, AKIRA; YAMAGA, YUSUKE
To: HITACHI, LTD.
Reel/Frame 066662/0960 →
Priority Claims (1)
JP 2023-137013 · Aug 25, 2023 · national
Continuity (1)
Related Publication 20250068749A1 · Feb 27, 2025
References Cited (20)
US 10078641B1 · Redko · 2018 [cited by examiner]
US 20080114771A1 · Welingkar · 2008 [cited by examiner]
US 20090125577A1 · Kodama · 2009 [cited by examiner]
US 20170054803A1 · Kato · 2017 [cited by examiner]
US 20170180394A1 · Crofton · 2017 [cited by examiner]
US 20190342330A1 · Wu · 2019 [cited by examiner]
US 20200226256A1 · Gaurav · 2020 [cited by examiner]
US 20210294701A1 · Satoyama et al. · 2021 [cited by applicant]
US 20210336970A1 · Woo · 2021 [cited by applicant]
US 20220138169A1 · Yelheri · 2022 [cited by examiner]
US 20220405237A1 · Matsushita et al. · 2022 [cited by applicant]
US 20230103474A1 · Gunda · 2023 [cited by examiner]
US 20240160605A1 · Katuri · 2024 [cited by examiner]
US 20240211598A1 · Zhang · 2024 [cited by examiner]
US 20240248985A1 · Vokaliga · 2024 [cited by examiner]
US 20240273186A1 · George · 2024 [cited by examiner]
JP 2021149773A · 2021 [cited by applicant]
JP 20231471A · 2023 [cited by applicant]
JP 2023503760A · 2023 [cited by applicant]
Japanese Office Action received in corresponding Japanese Application No. 2023-137013 dated Aug. 19, 2025. [cited by applicant]