Managing data using network attached storage (NAS) cluster
First Claim
1. A method of managing data storage, the method comprising:
- operating multiple physical computing machines in a NAS (network attached storage) cluster, the physical computing machines interconnected by a computer network and having access to block storage;
operating a NAS server from a first physical computing machine in the NAS cluster, the NAS server including a dedicated FSDB (file system database) that identifies a set of file systems that belong to the NAS server, the set of file systems backed by a set of LUNs (Logical UNits) hosted by the block storage; and
in response to a second physical computing machine in the NAS cluster receiving a request to take over operation of the NAS server, (i) accessing, by the second physical computing machine, the FSDB of the NAS server to identify each of the set of file systems and (ii) providing, by the second physical computing machine, host access to each of the set of file systems identified in the FSDB,wherein, prior to receiving the request to take over operation of the NAS server, the method further comprises the first physical computing machine running a first NAS data node manager as a first userspace process over a first kernel, the first kernel (i) discovering a first device based on a LUN in block storage that backs a file system that belongs to the NAS server and (ii) expressing the first device as a first kernel-resident block device accessible from userspace, the first kernel-resident block device having a unique device ID (identifier) within the NAS cluster, andwherein the second physical computing machine runs a second NAS data node manager as a second userspace process over a second kernel, the second kernel not running within the second userspace process.
7 Assignments
0 Petitions
Accused Products
Abstract
A technique for managing data storage provides multiple physical computing machines and block storage arranged in a NAS (network attached storage) cluster. The physical computing machines run NAS servers, with each NAS server including an FSDB (file system database) that identifies a set of file systems that belong to the NAS server. LUNs (Logical UNits) in the block storage provide backing store for the set of file systems of each NAS server. In response to a request to move operation of a NAS server from a first physical computing machine to a second physical computing machine, the second physical computing machine accesses the FSDB of the NAS server, identifies the set of file systems that belong to that NAS server, and acts to provide host access to the identified set of file systems.
30 Citations
22 Claims
-
1. A method of managing data storage, the method comprising:
-
operating multiple physical computing machines in a NAS (network attached storage) cluster, the physical computing machines interconnected by a computer network and having access to block storage; operating a NAS server from a first physical computing machine in the NAS cluster, the NAS server including a dedicated FSDB (file system database) that identifies a set of file systems that belong to the NAS server, the set of file systems backed by a set of LUNs (Logical UNits) hosted by the block storage; and in response to a second physical computing machine in the NAS cluster receiving a request to take over operation of the NAS server, (i) accessing, by the second physical computing machine, the FSDB of the NAS server to identify each of the set of file systems and (ii) providing, by the second physical computing machine, host access to each of the set of file systems identified in the FSDB, wherein, prior to receiving the request to take over operation of the NAS server, the method further comprises the first physical computing machine running a first NAS data node manager as a first userspace process over a first kernel, the first kernel (i) discovering a first device based on a LUN in block storage that backs a file system that belongs to the NAS server and (ii) expressing the first device as a first kernel-resident block device accessible from userspace, the first kernel-resident block device having a unique device ID (identifier) within the NAS cluster, and wherein the second physical computing machine runs a second NAS data node manager as a second userspace process over a second kernel, the second kernel not running within the second userspace process. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A NAS (network attached storage) cluster, comprising:
multiple physical computing machines interconnected via a computer network and having access to block storage, the physical computing machines including control circuitry constructed and arranged to; operate the physical computing machines in the NAS cluster; operate a NAS server from a first physical computing machine in the NAS cluster, the NAS server including a dedicated FSDB (file system database) that identifies a set of file systems that belong to the NAS server, the set of file systems backed by a set of LUNs (Logical UNits) hosted by the block storage; and in response to a second physical computing machine in the NAS cluster receiving a request to take over operation of the NAS server, (i) access, by the second physical computing machine, the FSDB of the NAS server to identify each of the set of file systems and (ii) provide, by the second physical computing machine, host access to each of the set of file systems identified in the FSDB, wherein, prior to receipt of the request to take over operation of the NAS server, the first physical computing machine is configured to run a first NAS data node manager as a first userspace process over a first kernel, the first kernel configured to (i) discover a first device based on a LUN in block storage that backs a file system that belongs to the NAS server and (ii) express the first device as a first kernel-resident block device accessible from userspace, the first kernel-resident block device having a unique device ID (identifier) within the NAS cluster, and wherein the second physical computing machine is configured to run a second NAS data node manager as a second userspace process over a second kernel, the second kernel not running within the second userspace process.
-
22. A computer program product including a set of non-transitory, computer-readable media having instructions which, when executed by control circuitry of a NAS (network attached storage) cluster, cause the control circuitry to perform a method for managing data storage, the method comprising:
-
operating multiple physical computing machines in the NAS cluster, the physical computing machines interconnected by a computer network and having access to block storage; operating a NAS server from a first physical computing machine in the NAS cluster, the NAS server including a dedicated FSDB (file system database) that identifies a set of file systems that belong to the NAS server, the set of file systems backed by a set of LUNs (Logical UNits) hosted by the block storage; and in response to a second physical computing machine in the NAS cluster receiving a request to take over operation of the NAS server, (i) accessing, by the second physical computing machine, the FSDB of the NAS server to identify each of the set of file systems and (ii) providing, by the second physical computing machine, host access to each of the set of file systems identified in the FSDB, wherein, prior to receiving the request to take over operation of the NAS server, the method further comprises the first physical computing machine running a first NAS data node manager as a first userspace process over a first kernel, the first kernel (i) discovering a first device based on a LUN in block storage that backs a file system that belongs to the NAS server and (ii) expressing the first device as a first kernel-resident block device accessible from userspace, the first kernel-resident block device having a unique device ID (identifier) within the NAS cluster, and wherein the second physical computing machine runs a second NAS data node manager as a second userspace process over a second kernel, the second kernel not running within the second userspace process.
-
Specification