Method for dynamic pseudofs creation and management in a network filesystem
One example method includes connecting to a fileserver of a data protection system, initiating, at a client, an operation that is associated with a master pseudofs of the fileserver, creating, at the client, a client-specific pseudofs based upon the master pseudofs, and the client-specific pseudofs includes only those nodes of the master pseudofs that the client is authorized to access, and performing the operation using the client-specific pseudofs.
1. A method, comprising performing the following operations:
connecting, by a client, to a fileserver of a data protection system;
initiating, by an application hosted at the client, a filesystem operation that is associated with a master pseudofs of the fileserver, and the master pseudofs comprises a non-virtual filesystem that is accessible by the client;
creating, at the client, and on an as-needed basis, a client-specific pseudofs that comprises only those nodes of the master pseudofs that the client is authorized to access, and the client-specific pseudofs comprises a virtual filesystem whose configuration is derived from a configuration of the non-virtual filesystem of the master pseudofs, wherein the nodes comprise respective path components, and the client-specific pseudofs provides a discrete view to the client that shows only those path components that the client is allowed to access; and
performing, at the client, the filesystem operation using the client-specific pseudofs.
2. The method as recited in claim 1 , wherein creating the client-specific pseudofs comprises traversing, by the client, a master tree associated with the master pseudofs and identifying, by the client, one or more nodes of the master tree that the client is authorized to access.
3. The method as recited in claim 1 , wherein a file in the client-specific pseudofs is represented by a discrete filehandle type that can be distinguished by the filesystem.
4. The method as recited in claim 1 , wherein the client-specific pseudofs does not exist separately from the master pseudofs.
5. The method as recited in claim 1 , wherein the filesystem operation performed at the client comprises one or more of a read operation, a write operation, a delete operation, or a restore operation.
6. The method as recited in claim 1 , further comprising automatically updating, by the client, the client-specific pseudofs to reflect a change involving an export that the client was previously authorized to access.
7. The method as recited in claim 1 , wherein information concerning a change to the master pseudofs is communicated automatically by the master pseudofs to the client-specific pseudofs at the client.
8. The method as recited in claim 7 , wherein the change to the master pseudofs concerns one or more of addition of an export, removal of an export, or a change to an export access control list (ACL).
9. The method as recited in claim 1 , further comprising allowing the client-specific pseudofs to age out.
10. The method as recited in claim 1 , further comprising validating, by the client, the client-specific pseudofs against the master pseudofs.
11. A non-transitory storage medium having stored therein instructions which are executable by one or more hardware processors to perform operations comprising:
connecting, by a client, to a fileserver of a data protection system;
initiating, by an application hosted at the client, a filesystem operation that is associated with a master pseudofs of the fileserver, and the master pseudofs comprises a non-virtual filesystem that is accessible by the client;
creating, at the client, and on an as-needed basis, a client-specific pseudofs that comprises only those nodes of the master pseudofs that the client is authorized to access, and the client-specific pseudofs comprises a virtual filesystem whose configuration is derived from a configuration of the non-virtual filesystem of the master pseudofs, wherein the nodes comprise respective path components, and the client-specific pseudofs provides a discrete view to the client that shows only those path components that the client is allowed to access; and
performing, at the client, the filesystem operation using the client-specific pseudofs.
12. The non-transitory storage medium as recited in claim 11 , wherein creating the client-specific pseudofs comprises traversing, by the client, a master tree associated with the master pseudofs and identifying, by the client, one or more nodes of the master tree that the client is authorized to access.
13. The non-transitory storage medium as recited in claim 11 , wherein a file in the client-specific pseudofs is represented by a discrete filehandle type that can be distinguished by the filesystem.
14. The non-transitory storage medium as recited in claim 11 , wherein the client-specific pseudofs does not exist separately from the master pseudofs.
15. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise automatically updating, by the client, the client-specific pseudofs to reflect a change involving an export that the client was previously authorized to access.
16. The non-transitory storage medium as recited in claim 11 , wherein information concerning a change to the master pseudofs is communicated automatically by the master pseudofs to the client-specific pseudofs at the client.
17. The non-transitory storage medium as recited in claim 16 , wherein the change to the master pseudofs concerns one or more of addition of an export, removal of an export, or a change to an export access control list (ACL).
18. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise allowing the client-specific pseudofs to age out.
19. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise validating, by the client, the client-specific pseudofs against the master pseudofs.