Granted Patent B2

US 11,947,427 · App. 16/871,846 · Granted Apr 2, 2024

Inventors: Simon Yuting Zhang (Chengdu, CN); Yizhou Zhou (Chengdu, CN); Aaron Chao Lin (Chengdu, CN)

Assignee: EMC IP HOLDING COMPANY LLC

G06F11/1464G06F11/1451G06F11/1461G06F11/1469G06F16/2322G06F21/602G06F21/78G06F21/88

Abstract

Claims (102)

1. A method for storage management, comprising:

acquiring a lock attribute record in a lock attribute record blockchain from a data protection network for backing up data, the data protection network including a plurality of data protection servers that reach a consensus on the lock attribute record blockchain, the lock attribute record comprising a first attribute value of an attribute of a lock operation, the lock operation being used for preventing a backup of the data stored in a storage server from being tampered with, the lock attribute record being a block in the lock attribute record blockchain, the first attribute value comprising a first retention time of the lock operation, the first retention time generated by one the plurality of data protection servers;

acquiring, based on the lock attribute record, a second attribute value of the attribute of the lock operation from the storage server, the second attribute value comprising a second retention time of the lock operation; and

generating, based on determining that the first retention time does not match the second retention time, an alarm indicating that the backup is tampered with;

wherein the attribute comprises a timestamp representing a time at which the lock attribute record is created; and

wherein acquiring the lock attribute record comprises:

acquiring a plurality of candidate lock attribute records for the backup in the lock attribute record blockchain from the data protection network, and

determining a candidate lock attribute record with the time indicated by the timestamp exceeding a time threshold among the plurality of candidate lock attribute records as the lock attribute record.

2. The method according to claim 1 , wherein the attribute further comprises at least one of following items:

a data protection server identifier representing an identifier of a data protection server that initiates the backup among the plurality of data protection servers;

a lock role representing a role that executes the lock operation;

a backup identifier representing an identifier of the backup;

a backup hash value representing a value obtained by hashing the backup;

a storage identifier representing an identifier of the storage server;

a lock mode representing a mode used by the lock operation;

a last lock attribute record representing an address of a lock attribute record of a last lock operation for the backup; and

an illegality tag indicating whether the lock operation is illegal, the illegality tag comprising a retention time being shortened relative to the last lock operation.

3. The method according to claim 2 , wherein acquiring the second attribute value comprises:

extracting the data protection server identifier and the backup identifier of the backup and the storage identifier of the storage server from the lock attribute record; and

acquiring the second attribute value of the attribute of the lock operation for the backup from the storage server based on the data protection server identifier, the backup identifier, and the storage identifier.

4. The method according to claim 1 , further comprising:

determining information associated with an attempted illegal lock operation from a candidate lock attribute record indicated by an illegality tag to be illegal among the plurality of candidate lock attribute records.

5. The method according to claim 1 , wherein the attribute further comprises at least one of following items:

a data protection server identifier representing an identifier of a data protection server that initiates the backup among the plurality of data protection servers;

a lock role representing a role that executes the lock operation; and

a backup identifier representing an identifier of the backup.

6. The method according to claim 1 , wherein the attribute further comprises at least one of following items:

a backup hash value representing a value obtained by hashing the backup; and

a storage identifier representing an identifier of the storage server.

7. The method according to claim 1 , wherein the attribute further comprises at least one of following items:

a lock mode representing a mode used by the lock operation; and

a last lock attribute record representing an address of a lock attribute record of a last lock operation for the backup.

8. A method for storage management, comprising:

receiving, at a first data protection server among a plurality of data protection servers of a data protection network for backing up data, a first lock request for a first backup of a first piece of data stored in a storage server from a second data protection server among the plurality of data protection servers, the first lock request being used for requesting execution of a lock operation preventing the first backup from being tampered with and comprising an attribute value of an attribute of the lock operation, the attribute value comprising a retention time of the lock operation;

creating a lock attribute record based on the first lock request, the plurality of data protection servers reaching a consensus on the lock attribute record, the lock attribute record comprising the retention time of the lock operation; and

sending a response that is for the first lock request and is associated with the lock attribute record to the second data protection server;

wherein the attribute comprises at least a timestamp representing a time at which the lock attribute record is created; and

wherein creating the lock attribute record comprises:

determining whether a last lock attribute record of a last lock operation for the first backup already exists in a lock attribute record blockchain which is stored at the first data protection server and on which the plurality of data protection servers reaches a consensus, and

creating the lock attribute record based on the first lock request based on determining that the last lock attribute record does not exist.

9. The method according to claim 8 , wherein the attribute further comprises at least one of following items:

a data protection server identifier representing an identifier of a data protection server that initiates the first backup among the plurality of data protection servers;

a lock role representing a role that executes the lock operation;

a backup identifier representing an identifier of the first backup;

a backup hash value representing a value obtained by hashing the first backup;

a storage identifier representing an identifier of the storage server storing the first backup; and

a lock mode representing a mode used by the lock operation.

10. The method according to claim 8 , further comprising:

determining, based on determining that the last lock attribute record exists, whether an illegality tag of the last lock attribute record indicates that the last lock operation is illegal; and

creating, based on determining that the last lock operation is illegal, the lock attribute record based on the first lock request and the last lock attribute record, so that an attribute related to the last lock attribute record of the lock attribute record indicates an address of the last lock attribute record.

11. The method according to claim 10 , further comprising:

determining, based on determining that the last lock operation is non-illegal, whether a retention time of the last lock attribute record is longer than the retention time included in the first lock request; and

creating, based on determining that the retention time of the last lock attribute record is shorter than the retention time included in the first lock request, the lock attribute record based on the first lock request and the last lock attribute record, so that the attribute related to the last lock attribute record of the lock attribute record indicates the address of the last lock attribute record.

12. The method according to claim 11 , further comprising:

creating, based on determining that the retention time of the last lock attribute record is longer than the retention time included in the first lock request, the lock attribute record based on the first lock request and the last lock attribute record, so that the attribute related to the last lock attribute record of the lock attribute record indicates the address of the last lock attribute record, and an attribute of the lock attribute record related to the illegality tag indicates illegality.

13. The method according to claim 8 , further comprising:

sending a second lock request for a second backup of a second piece of data stored in the storage server to a third data protection server among the plurality of data protection servers;

determining, based on determining that a response for the second lock request is received from the third data protection server, whether the second lock request is successful and non-illegal; and

causing, based on determining that the second lock request is successful and non-illegal, the storage server to execute a second lock operation on the second backup.

14. The method according to claim 8 , further comprising:

adding the lock attribute record into the lock attribute record blockchain.

15. An electronic device, comprising:

at least one processing unit; and

at least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions, which when executed by the at least one processing unit, cause the at least one processing unit to perform an action, the action comprising:

acquiring a lock attribute record in a lock attribute record blockchain from a data protection network for backing up data, the data protection network including a plurality of data protection servers that reach a consensus on the lock attribute record blockchain, the lock attribute record comprising a first attribute value of an attribute of a lock operation, the lock operation being used for preventing a backup of the data stored in a storage server from being tampered with, the lock attribute record being a block in the lock attribute record blockchain, the first attribute value comprising a first retention time of the lock operation, the first retention time generated by one the plurality of data protection servers;

acquiring, based on the lock attribute record, a second attribute value of the attribute of the lock operation from the storage server, the second attribute value comprising a second retention time of the lock operation; and

generating, based on determining that the first retention time does not match the second retention time, an alarm indicating that the backup is tampered with

wherein the attribute comprises at least a timestamp representing a time at which the lock attribute record is created; and

wherein acquiring the lock attribute record comprises:

acquiring a plurality of candidate lock attribute records for the backup in the lock attribute record blockchain from the data protection network, and

determining a candidate lock attribute record with the time indicated by the timestamp exceeding a time threshold among the plurality of candidate lock attribute records as the lock attribute record.

16. The device according to claim 15 , wherein the attribute further comprises at least one of following items:

a data protection server identifier representing an identifier of a data protection server that initiates the backup among the plurality of data protection servers;

a lock role representing a role that executes the lock operation;

a backup identifier representing an identifier of the backup;

a backup hash value representing a value obtained by hashing the backup;

a storage identifier representing an identifier of the storage server;

a lock mode representing a mode used by the lock operation;

a last lock attribute record representing an address of a lock attribute record of a last lock operation for the backup; and

an illegality tag indicating whether the lock operation is illegal, the illegality tag comprising a retention time being shortened relative to the last lock operation.

17. The device according to claim 15 , wherein the action further comprises:

determining information associated with an attempted illegal lock operation from a candidate lock attribute record indicated by an illegality tag to be illegal among the plurality of candidate lock attribute records.

18. The device according to claim 16 , wherein acquiring the second attribute value comprises:

extracting the data protection server identifier and the backup identifier of the backup and the storage identifier of the storage server from the lock attribute record; and

acquiring the second attribute value of the attribute of the lock operation for the backup from the storage server based on the data protection server identifier, the backup identifier, and the storage identifier.

19. An electronic device, comprising:

at least one processing unit; and

at least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions, which when executed by the at least one processing unit, cause the at least one processing unit to perform an action, the action comprising:

receiving, at a first data protection server among a plurality of data protection servers of a data protection network for backing up data, a first lock request for a first backup of a first piece of data stored in a storage server from a second data protection server among the plurality of data protection servers, the first lock request being used for requesting execution of a lock operation preventing the first backup from being tampered with and comprising an attribute value of an attribute of the lock operation, the attribute value comprising a retention time of the lock operation;

creating a lock attribute record based on the first lock request, the plurality of data protection servers reaching a consensus on the lock attribute record, the lock attribute record comprising the retention time of the lock operation; and

sending a response that is for the first lock request and is associated with the lock attribute record to the second data protection server;

wherein the attribute comprises at least a timestamp representing a time at which the lock attribute record is created; and

wherein creating the lock attribute record comprises:

determining whether a last lock attribute record of a last lock operation for the first backup already exists in a lock attribute record blockchain which is stored at the first data protection server and on which the plurality of data protection servers reaches a consensus, and

creating the lock attribute record based on the first lock request based on determining that the last lock attribute record does not exist.

20. The device according to claim 19 , wherein the attribute further comprises at least one of following items:

a data protection server identifier representing an identifier of a data protection server that initiates the first backup among the plurality of data protection servers;

a lock role representing a role that executes the lock operation;

a backup identifier representing an identifier of the first backup;

a backup hash value representing a value obtained by hashing the first backup;

a storage identifier representing an identifier of the storage server storing the first backup; and

a lock mode representing a mode used by the lock operation.

Assignments (9)

Priority Claims (1)

Continuity (1)