Granted Patent B2

US 12,591,700 · App. 18/410,903 · Granted Mar 31, 2026

Inventors: Deepanshu Verma (Bengaluru, IN); Hemanth Kumar Thummala (San Jose, CA); Manoj Premanand Naik (San Jose, CA); Saji Kumar Vijaya Kumari Rajendran Nair (Cupertino, CA); Shilpa Krishnareddy (Bengaluru, IN)

Assignee: Nutanix, Inc.

G06F21/6218G06F16/188

Abstract

Claims (68)

1 . A distributed file server comprising:

at least one processor;

non-transitory computer-readable storage media encoded with instructions which, when executed by the at least one processor, cause the file server manager to perform actions comprising:

scan a plurality of domains, including a domain the distributed file server is subscribed to and trusted domains of the plurality of domains;

identify a trusted domain of the plurality of domains, wherein the trusted domain is associated with one or more users, each of the one or more users having a respective security identifier;

allocate, to the trusted domain, a range of file server user identifiers (IDs);

store a mapping between security identifiers (SIDs) in the trusted domain, including each respective security identifier, to a respective file server user ID within the range of file server user IDs; and

provide the mapping to a replication target for the distributed file server.

2 . The distributed file server of claim 1 , wherein at least one domain serviced by the distributed file server.

3 . The distributed file server of claim 1 , wherein each file server user ID within the range of file server user IDs is a global identifier (GID).

4 . The distributed file server of claim 1 , wherein each SID associated with a respective user of the one or more users comprises a domain-specific portion and relative user identifier (RID) portion.

5 . The distributed file server of claim 1 , wherein the trusted domain is an active directory domain.

6 . The distributed file server of claim 1 , wherein the distributed file server is a virtualized file server.

7 . The distributed file server of claim 1 , wherein the replication target is a destination target, a disaster recovery target, or a combination thereof.

8 . The distributed file server of claim 1 , wherein providing the mapping to the replication target for the distributed file server occurs responsive to a failover event, a disaster recovery event, a replication event, or combinations thereof.

9 . The distributed file server of claim 1 , wherein the distributed file server is further configured to perform actions comprising:

determine that a number of SIDs associated with the trusted domain exceeds a number of file server user IDs allocated to the trusted domain in the range of file server user IDs;

dynamically allocate another range of file server user IDs to the trusted domain; and

store a mapping between the number of SIDs that exceed the number of file server user IDs allocated to the trusted domain, and the another range of file server user IDs.

10 . The distributed file server of claim 9 , wherein the another range of file server user IDs is dynamically added to the trusted domain on a per-file share basis.

11 . The distributed file server of claim 9 , wherein the another range of file server user IDs is dynamically added to the trusted domain on a per-file server basis.

12 . The distributed file server of claim 9 , wherein the mapping between the number of SIDs that exceed the number of file server user IDs allocated to the trusted domain, and the another range of file server user IDs, the mapping between security identifiers in the trusted domain, including each respective security identifier, to a respective file server user ID within the range of file server user IDs, or a combination thereof, are accessible to each trusted domain.

13 . The distributed file server of claim 1 , wherein the distributed file server is further configured to perform actions comprising:

assign a file server user ID included in the range of file server user IDs to a user of the one or more users of the trusted domain, wherein the user is associated with an assigned SID of the SIDs, and wherein the assigned SID comprises a trusted domain-specific portion and a relative identifier (RID) specific portion.

14 . A method comprising:

scanning one or more domains, including a domain a distributed file server is subscribed to and trusted domains of the one or more domains;

allocating a range of file server user identifier (IDs) to each of the one or more domains;

storing a mapping between security identifiers (SIDs) in each domain of the one or more domains to a respective file server user ID within each respective range of file server user IDs; and

providing the mapping to a replication target for the distributed file server.

15 . The method of claim 14 , wherein at least one of the one or more domains is an active directory domain.

16 . The method of claim 14 , wherein each of the one or more domains is a trusted domain.

17 . The method of claim 14 , wherein each file server user identifier of the file server user IDs is a global identifier (GID).

18 . The method of claim 16 , wherein each trusted domain is an active directory domain.

19 . The method of claim 14 , wherein the distributed file server is a virtualized file server.

20 . The method of claim 14 , wherein the replication target is a destination target, a disaster recovery target, or a combination thereof.

21 . The method of claim 14 , wherein providing the mapping to the replication target occurs responsive to a failover event, a disaster recovery event, a replication event, or combinations thereof.

22 . The method of claim 14 , the method further comprising:

determining that a number of SIDs associated with a first domain of the one or more domains exceeds a number of file server user IDs allocated to the first domain in a first range;

dynamically allocating another range of file server user IDs to the first domain; and

storing another mapping between the SIDs that exceed the number of file server user IDs allocated to the first domain, and the another range of file server user IDs.

23 . The method of claim 22 , wherein the mapping between SIDs in each domain of the one or more domains, the another mapping between the SIDs that exceed the number of file server user IDs allocated to the first domain, and the another range of file server user IDs, or a combination thereof, are accessible to each trusted domain.

24 . The method of claim 14 , the method further comprising:

assigning to a first user of a first domain of the one or more domains, a file server user ID, wherein the first user is associated with an assigned SID, including a domain-specific portion and a relative identifier (RID) specific portion.

25 . At least one non-transitory computer-readable storage medium encoded with instructions which, when executed, cause a computing node to perform operations, the operations comprising:

scanning one or more domains, including a domain a distributed file server is subscribed to and trusted domains of the one or more domains;

determining at least one domain of the one or more domains scanned is a trusted domain;

allocating a range of global identifiers (GIDs) to the trusted domain;

storing a mapping between security identifiers (SIDs) in the trusted domain to a respective GID within the range of GIDs; and

providing the mapping to a replication target for the distributed file server.

26 . The non-transitory computer-readable storage medium of claim 25 , wherein the GID is a file server user identifier (ID).

27 . The non-transitory computer-readable storage medium of claim 25 , wherein the one or more domains are active directory domains.

28 . The non-transitory computer-readable storage medium of claim 25 , wherein the trusted domain is an active directory domain.

29 . The non-transitory computer-readable storage medium of claim 25 , wherein the distributed file server is a virtualized file server.

30 . The non-transitory computer-readable storage medium of claim 25 , wherein the replication target is a destination target, a disaster recovery target, or a combination thereof.

31 . The non-transitory computer-readable storage medium of claim 25 , wherein providing the mapping to the replication target occurs responsive to a failover event, a disaster recovery event, a replication event, or combinations thereof.

32 . The non-transitory computer-readable storage medium of claim 25 , the operations further comprising:

determining a number of SIDs associated with the trusted domain exceeds a number of GIDs allocated to the trusted domain within the range of GIDS;

allocating another range of GIDs to the trusted domain; and

storing another mapping between the SIDs that exceed the number of GIDs allocated to the trusted domain and the another range of GIDs.

33 . The non-transitory computer-readable storage medium of claim 32 , the operations further comprising:

scanning the one or more domains;

determining a second domain of the one or more domains is a second trusted domain, the second trusted domain subscribed to by the distributed file server;

allocating a second range of GIDs to the second trusted domain, wherein the second range of GIDs is different from the range of GIDs allocated to the trusted domain and the another range of GIDs allocated to the trusted domain;

storing a second mapping between SIDs in the second trusted domain to a respective GID within the second range of GIDs; and

providing the second mapping to a second replication target for the distributed file server.

34 . The non-transitory computer-readable storage medium of claim 33 , wherein the mapping between SIDs in the trusted domain to a respective GID within the range of GIDs, the another mapping between the SIDs that exceed the number of GIDs allocated to the trusted domain, the second mapping between SIDs in the second trusted domain to a respective GID within the second range of GIDs, or combinations thereof, are accessible to each trusted domain.

35 . The non-transitory computer-readable storage medium of claim 25 , the operations further comprising:

assigning, to a user of the trusted domain, a first GID within the range of GIDs allocated to the trusted domain, wherein the user is associated with an assigned SID, including a domain-specific portion and a relative identifier (RID) specific portion.

Assignments (2)

Priority Claims (1)

Continuity (1)

References Cited (400)