Backups of file system instances with root object encrypted by metadata encryption key

1. A system belonging to a cluster, the system comprising:

a processing resource; and

a machine readable medium storing instructions that, when executed by the processing resource, cause the processing resource to:

encrypt data objects of a file system instance to generate encrypted data objects using a data encryption key (DEK) specific to a security domain containing the file system instance, the DEK being wrapped by a key encryption key (KEK) shared exclusively within the cluster, and the file system instance hierarchically relating the encrypted data objects located at a leaf level to a first root object through references to signatures of the encrypted data objects,

encrypt the first root object using a first metadata encryption key (MEK),

create on a node a backup of the file system instance comprising at least some of the encrypted data objects, and

send the DEK and the first MEK to the node with the backup.

2. The system of claim 1 , wherein the first MEK is wrapped by the DEK and is specific to the first root object.

3. The system of claim 1 , wherein the machine readable medium stores instructions to cause the processing resource to:

create a second backup of the file system instance on the node, the second backup contained by the security domain and including additional encrypted data objects that are encrypted using the DEK and a second root object different from the root object, and

encrypt the second root object using a second MEK different from the first MEK.

4. The system of claim 1 , wherein backups of file system instances within the security domain are identified by respective root objects that are encrypted using different respective MEKs, and

the machine readable medium stores instructions that cause the processing resource to delete a selected MEK, from among the different respective MEKs, corresponding to a backup, from among the backups, selected for cryptographic erasure.

5. The system of claim 1 , wherein the data objects encrypted by the processing resource include an inode attribute data object or an inode extended attribute data object of the file system instance.

6. The system of claim 1 , wherein the instructions cause the processing resource to encrypt the data objects using the DEK and respective tweak values that are based on positions of the data objects in the file system instance, and

the signatures are calculated as hash-based message authentication codes of respective encrypted data objects using the positions of the respective encrypted data objects as a key.

7. The system of claim 5 , wherein the positions are based on at least one of an inode number, inode tree number, and an offset.

8. The system of claim 1 , wherein internal metadata objects within the file system instance are unencrypted.

9. A method comprising:

encrypting, by a processing resource of a node in a cluster, data objects of a file system instance to generate encrypted data objects using a data encryption key (DEK) specific to a security domain containing the file system instance, the DEK being wrapped by a key encryption key (KEK) shared exclusively within the cluster, and the file system instance hierarchically relating the encrypted data objects located at a leaf level to a first root object through references to signatures of the encrypted data objects;

encrypting, by the processing resource, the first root object using a first metadata encryption key (MEK) that is wrapped by the DEK and is specific to the first root object to generate an encrypted first root object;

creating, by the processing resource, a backup of the file system instance on another node comprising at least some of the encrypted data objects; and

sending the DEK and the first MEK to the other node with the backup.

10. The method of claim 9 , comprising:

creating a second backup file system instance on the other node, the second backup contained by the security domain and including additional encrypted data objects that are encrypted using the DEK and a second root object different from the first root object; and

encrypting the second root object using a second MEK different from the first MEK.

11. The method of claim 9 , wherein backups of file system instance within the security domain are identified by respective encrypted root objects that are encrypted using different respective MEKs, and

the method comprising deleting a selected MEK, from among the different respective MEKs, corresponding to a backup, from among the backups, selected for cryptographic erasure.

12. The method of claim 9 , comprising:

receiving, from the other node, an unencrypted reconstructed root object or a signature of the unencrypted reconstructed root object, wherein the other node is not a member of the cluster, and the unencrypted reconstructed root object is generated by the other node based on encrypted data objects of the backup;

verifying the unencrypted reconstructed root object against the first root object; and

responsive to the unencrypted reconstructed root object being verified, sending the encrypted first root object to the other node for persisting at the other node.

13. The method of claim 9 , wherein the encrypting data objects includes encrypting the data objects using the DEK and respective tweak values that are based on positions of the data objects in the file system instance, and

the signatures are calculated as hash-based message authentication codes of respective encrypted data objects using the positions of the respective encrypted data objects as a key.

14. The method of claim 13 , wherein the positions are based on an inode number, inode tree number, and an offset.

15. A non-transitory machine readable medium storing instructions executable by processing resource of a computing system, the non-transitory machine readable medium comprising:

instructions to encrypt data objects of a file system instance to generate encrypted data objects using a data encryption key (DEK) specific to a security domain containing the file system instance, the DEK being wrapped by a key encryption key (KEK) shared exclusively within a cluster to which the computing system belongs, and the file system instance hierarchically relating the encrypted data objects located at a leaf level to a first root object through references to signatures of the encrypted data objects;

instructions to encrypt the first root object using a first metadata encryption key (MEK) that is wrapped by the DEK and is specific to the first root object;

instructions to create a backup of the file system instance on another computing system comprising at least some of the encrypted data objects; and

instructions to send the DEK and the first MEK to the other computing system with the backup.

16. The non-transitory machine readable medium of claim 15 comprising:

instructions to generate a different MEK to encrypt a root object of each different file system instance being secured.

17. The non-transitory machine readable medium of claim 15 , wherein backups of the file system instances are identified by respective root objects that are encrypted using different respective MEKs, and

the non-transitory machine readable medium comprises instructions to delete a selected MEK, from among the different respective MEKs, corresponding to a backup, from among the backups, selected for cryptographic erasure.

18. The non-transitory machine readable medium of claim 15 , wherein the data objects encrypted to generate encrypted data objects includes inode attribute data objects and inode extended attribute data objects of the file system instance, and

wherein internal metadata objects within the file system instance are unencrypted.

19. The non-transitory machine readable medium of claim 15 , wherein the instructions to encrypt data objects causes the processing resource to encrypt the data objects using the DEK and respective tweak values that are based on positions of the data objects in the file system instance, and

the signatures are calculated as hash-based message authentication codes of respective encrypted data objects using the positions of the respective encrypted data objects as a key.

20. The non-transitory machine readable medium of claim 19 , wherein the positions are based on an inode number, inode tree number, and an offset.