Abstract: Embodiments for managing access to Mtrees using a mechanism through the use of net groups that contain a pool of IP addresses with configuration information that is automatically propagated to new nodes as they are added to a defined net group to facilitate zero configuration when scaling a network. Using net groups, access to an Mtree across nodes in a data center or similar network can be managed with a group of IP addresses spread across all the nodes in the cluster as a single net group entity. The net group provides flexibility to create multiple net groups that can be used to manage the appliance in management, diagnostic, data, and interconnect domains. It allows flexibility to manage the access to Mtree from different networks and security domains, and allows a user to configure the network attributes of all the IP addresses as a single entity.

Abstract: Embodiments for managing access to Mtrees using a mechanism through the use of net groups that contain a pool of IP addresses with configuration information that is automatically propagated to new nodes as they are added to a defined net group to facilitate zero configuration when scaling a network. Using net groups, access to an Mtree across nodes in a data center or similar network can be managed with a group of IP addresses spread across all the nodes in the cluster as a single net group entity. The net group provides flexibility to create multiple net groups that can be used to manage the appliance in management, diagnostic, data, and interconnect domains. It allows flexibility to manage the access to Mtree from different networks and security domains, and allows a user to configure the network attributes of all the IP addresses as a single entity.

Abstract: A first request is received from a first user to access a first file system management objects (FSMOs) of a first tenant unit (TU), the first TU being one of a plurality of TUs. The first FSMO is one of a plurality of FSMOs, each FSMO containing namespace information of a particular tenant. In response to the first request, it is determined whether the first user is authorized to access the first FSMO, including identifying TUs that are associated with the first user, determining whether the first TU is included in the TUs, and if so, determining whether the first FSMO is included in FSMOs associated with the first TU. In response to determining that the first FSMO is included in a set of one or more FSMOs that are associated with the first TU, the first user to access the first FSMO is allowed.

Abstract: A first request is received from a first user to access a first file system management objects (FSMOs) of a first tenant unit (TU), the first TU being one of a plurality of TUs. The first FSMO is one of a plurality of FSMOs, each FSMO containing namespace information of a particular tenant. In response to the first request, it is determined whether the first user is authorized to access the first FSMO, including identifying TUs that are associated with the first user, determining whether the first TU is included in the TUs, and if so, determining whether the first FSMO is included in FSMOs associated with the first TU. In response to determining that the first FSMO is included in a set of one or more FSMOs that are associated with the first TU, the first user to access the first FSMO is allowed.

Abstract: Exemplary methods for providing secure multi-tenancy in a Purpose Built Backup Appliance include creating a set of tenant-units (TUs), associating file system management objects (FSMOs) and users with the TUs. The methods further include maintaining a protocol config-metadata store based on the association of the FSMOs and users with the TUs. In one embodiment, in response to a first request from a first user to access a first FSMO of a first TU, the methods include determining whether the first user is authorized to access the first FSMO based on information of the protocol config-metadata store, and in response to the protocol config-metadata store indicating the first user is authorized to access the first FSMO, allowing the first user to access the first FSMO.

Abstract: Exemplary methods for providing secure multi-tenancy in a Purpose Built Backup Appliance include creating a set of tenant-units (TUs), associating file system management objects (FSMOs) and users with the TUs. The methods further include maintaining a protocol config-metadata store based on the association of the FSMOs and users with the TUs. In one embodiment, in response to a first request from a first user to access a first FSMO of a first TU, the methods include determining whether the first user is authorized to access the first FSMO based on information of the protocol config-metadata store, and in response to the protocol config-metadata store indicating the first user is authorized to access the first FSMO, allowing the first user to access the first FSMO.

Abstract: A system and method for managing software upgrades in a distributed computing system. The distributed computing system may include a plurality of nodes which provide one or more fault-tolerant services. The system and method perform software upgrades in a sequential or “rolling” manner (e.g., node by node). The rolling upgrade process allows all services and data of the distributed computing system to remain operable and available throughout the upgrade process.

Abstract: A system and method for managing software upgrades in a distributed computing system. The distributed computing system may include a plurality of nodes which provide one or more fault-tolerant services. The system and method perform software upgrades in a sequential or “rolling” manner (e.g., node by node). The rolling upgrade process allows all services and data of the distributed computing system to remain operable and available throughout the upgrade process.

Abstract: According to one embodiment, a dynamic server directory (DSD) (300) may include a number of relational tables (302 to 314) having a number of entries. Entries of selected tables (304 to 306) may include information for a server in a distributed computing system. Such information may include a server identification, host machine identification, and server status information. Entries of another table (308) may include host route information. According to one embodiment, dynamic server directory agents (DSDAs), residing on the same machine as a client process, may cache tables of a DSD (300). For a given client request, a client may query a local DSDA to determine which server(s) may service the client request. The local DSDA may then return the route to one or more servers that are available to service the request. Server information in a DSD (300) may be changed in response to changes in server status. Such changes may then be forwarded to DSDAs.