ACCESS AUTHORIZATION FOR REPORT DATA IN A MULTI-TENANCY DATA MANAGEMENT SYSTEM

Methods, systems, and devices for data management are described. A multi-tenancy data management system (DMS) may include multiple computing objects organized as a hierarchy of computing objects. The DMS may receive a request for report data associated with a first set of computing objects of the DMS. The DMS may identify context information for a log-in session associated with the request. The context information may include a tenant identifier (ID) for a tenant associated with the request. The DMS may apply a filter to the first set of computing objects. The filter may be based on a second set of computing objects to which the tenant has access within the hierarchy of computing objects. The DMS may output the report data for at least one computing object of the first set based on the at least one computing object being included in the second set of computing objects.

FIELD OF TECHNOLOGY

The present disclosure relates generally to data management, including techniques for access authorization for report data in a multi-tenancy data management system (DMS).

BACKGROUND

A data management system (DMS) may be employed to manage data associated with one or more computing systems. The data may be generated, stored, or otherwise used by the one or more computing systems, examples of which may include servers, databases, virtual machines, cloud computing systems, file systems (e.g., network-attached storage (NAS) systems), or other data storage or processing systems. The DMS may provide data backup, data recovery, data classification, or other types of data management services for data of the one or more computing systems. Improved data management may offer improved performance with respect to reliability, speed, efficiency, scalability, security, or ease-of-use, among other possible aspects of performance.

DETAILED DESCRIPTION

A multi-tenancy data management system (DMS) may provide backup services for multiple tenants (e.g., organizations or business units). A multi-tenancy DMS also may have resources across cloud platforms and on-premise data centers. In multi-tenant scenarios, multiple tenants (e.g., organizations or business units) may share data management resources. Some multi-tenant scenarios may be multi-level, with multiple hierarchical levels of tenants. For example, resources of a backup and recovery system may be shared among multiple higher-level tenants, and at least some of the higher-level tenants may be associated with one or more levels of lower-level tenants (e.g., subtenants), with resources associated with a higher-level tenant being shared by multiple subtenants of that tenant.

As one such example, which may be referred to as an enterprise scenario, an information technology (IT) services unit of a business (e.g., of a corporation) may be a tenant of a DMS, and multiple other business units of the same business (e.g., within the same corporation) may be subtenants of the IT services unit, and accordingly, may share the same data management services. As another such example, some tenants of a DMS may be multi-service providers (MSPs). An MSP may be a higher-level tenant of a backup and recovery system and may provide IT and data management services to multiple distinct customers, which may be separate businesses that are subtenants of the MSPs. For example, the MSP may subscribe to data management services and resources from the d DMS, and the MSP may use those services and resources to in turn provide data management service to the MSP's subtenants (e.g., an MSP subtenant may not directly subscribe to the DMS, such as due to a lack of internal expertise in configuring or managing the resources or services of the DMS, and thus the MSP subtenant may instead be customer of the MSP, which may directly subscribe to the DMS and use the MSP's subscription to offer data management services to the MSP subtenant).

There may be many tenants of the DMS, and some or all of the tenants may have any number of subtenants. The tenants of the DMS may be enterprise tenants, MSP tenants, other types of entities, or any combination thereof. Further, an entity that is a subtenant of a higher-level tenant may itself have one or more subtenants. That is, there may be three or more levels of tenants—in general, any quantity of levels may exist.

In some examples, a DMS may obtain and store report data for computing objects in the multi-tenant system, the computing objects being resources or other entities within the DMS (e.g., clusters or portions of clusters). The report data may include, for example, a status of the computing objects, such as a compliance status, a size, a status or history of one or more tasks related to the computing objects, or any combination thereof.

Techniques, systems, and devices described herein provide for a DMS to determine whether a user has permission to access report data for a given computing object based on the tenant associated with a given log-in session by the user. Computing objects within the DMS may be organized as part of an object hierarchy. If a tenant is granted access to one object within the object hierarchy, the tenant automatically also has access to any other object that is below that object within the object hierarchy. The user may log in to establish a session with the DMS. During the session, the user (e.g., an administrator for a given tenant, or some other user of the tenant) may request to access report data for a first set of one or more computing objects. In response to the request, the DMS may determine an identifier (ID) of the user and an ID of the tenant to which the user is logged in based on context information associated with the user's log-in session via which the request is sent. The tenant may have access to (e.g., permission or authorization to access) a second set of computing objects within the object hierarchy. The DMS may filter through the first set of computing objects associated with the requested report data by filtering out or omitting computing objects that are not in the second set of computing objects to which the tenant has access. The DMS may determine that the user has permission to access the requested report data for the remaining computing objects that are included in the second set of objects (e.g., are assigned to or accessible by the tenant) and may output such report data to the user accordingly.

In some examples, when the DMS generates and stores the report data for a given computing object, the DMS may add a field in the report data that indicates an ID of the corresponding computing object. The DMS may generate a mapping table for mapping object IDs to corresponding tenants that have access to the objects based on the computing object hierarchy. Accordingly, higher-level tenants may be able to request that the DMS display report data that is filtered by subtenants. For example, if a tenant requests to view all report data associated with a first subtenant, the DMS may scan the mapping table using a tenant ID of the first subtenant to determine computing object IDs of computing objects that the first subtenant has access to in the computing object hierarchy. The DMS may filter through a database of report data stored at the DMS using the identified computing object IDs. The DMS may output, to a user of the tenant that requested the report data for the first subtenant, all of the report data that includes the computing object IDs. The described techniques may thereby provide for the DMS to retrieve and provide report data with improved reliability, security, and efficiency.

FIG.1illustrates an example of a computing environment100that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The computing environment100may include a computing system105, a DMS110, and one or more computing devices115, which may be in communication with one another via a network120. The computing system105may generate, store, process, modify, or otherwise use associated data, and the DMS110may provide one or more data management services for the computing system105. For example, the DMS110may provide a data backup service, a data recovery service, a data classification service, a data transfer or replication service, one or more other data management services, or any combination thereof for data associated with the computing system105.

The network120may allow the one or more computing devices115, the computing system105, and the DMS110to communicate (e.g., exchange information) with one another. The network120may include aspects of one or more wired networks (e.g., the Internet), one or more wireless networks (e.g., cellular networks), or any combination thereof. The network120may include aspects of one or more public networks or private networks, as well as secured or unsecured networks, or any combination thereof. The network120also may include any quantity of communications links and any quantity of hubs, bridges, routers, switches, ports or other physical or logical network components.

A computing device115may be used to input information to or receive information from the computing system105, the DMS110, or both. For example, a user of the computing device115may provide user inputs via the computing device115, which may result in commands, data, or any combination thereof being communicated via the network120to the computing system105, the DMS110, or both. Additionally or alternatively, a computing device115may output (e.g., display) data or other information received from the computing system105, the DMS110, or both. A user of a computing device115may, for example, use the computing device115to interact with one or more user interfaces (e.g., graphical user interfaces (GUIs)) to operate or otherwise interact with the computing system105, the DMS110, or both. Though one computing device115is shown inFIG.1, it is to be understood that the computing environment100may include any quantity of computing devices115.

A computing device115may be a stationary device (e.g., a desktop computer or access point) or a mobile device (e.g., a laptop computer, tablet computer, or cellular phone). In some examples, a computing device115may be a commercial computing device, such as a server or collection of servers. And in some examples, a computing device115may be a virtual device (e.g., a virtual machine). Though shown as a separate device in the example computing environment ofFIG.1, it is to be understood that in some cases a computing device115may be included in (e.g., may be a component of) the computing system105or the DMS110.

The computing system105may include one or more servers125and may provide (e.g., to the one or more computing devices115) local or remote access to applications, databases, or files stored within the computing system105. The computing system105may further include one or more data storage devices130. Though one server125and one data storage device130are shown inFIG.1, it is to be understood that the computing system105may include any quantity of servers125and any quantity of data storage devices130, which may be in communication with one another and collectively perform one or more functions ascribed herein to the server125and data storage device130.

A data storage device130may include one or more hardware storage devices operable to store data, such as one or more hard disk drives (HDDs), magnetic tape drives, solid-state drives (SSDs), storage area network (SAN) storage devices, or network-attached storage (NAS) devices. In some cases, a data storage device130may comprise a tiered data storage infrastructure (or a portion of a tiered data storage infrastructure). A tiered data storage infrastructure may allow for the movement of data across different tiers of the data storage infrastructure between higher-cost, higher-performance storage devices (e.g., SSDs and HDDs) and relatively lower-cost, lower-performance storage devices (e.g., magnetic tape drives). In some examples, a data storage device130may be a database (e.g., a relational database), and a server125may host (e.g., provide a database management system for) the database.

A server125may allow a client (e.g., a computing device115) to download information or files (e.g., executable, text, application, audio, image, or video files) from the computing system105, to upload such information or files to the computing system105, or to perform a search query related to particular information stored by the computing system105. In some examples, a server125may act as an application server or a file server. In general, a server125may refer to one or more hardware devices that act as the host in a client-server relationship or a software process that shares a resource with or performs work for one or more clients.

A server125may include a network interface140, processor145, memory150, disk155, and computing system manager160. The network interface140may enable the server125to connect to and exchange information via the network120(e.g., using one or more network protocols). The network interface140may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor145may execute computer-readable instructions stored in the memory150in order to cause the server125to perform functions ascribed herein to the server125. The processor145may include one or more processing units, such as one or more central processing units (CPUs), one or more graphics processing units (GPUs), or any combination thereof. The memory150may comprise one or more types of memory (e.g., random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), read-only memory ((ROM), electrically erasable programmable read-only memory (EEPROM), Flash, etc.). Disk155may include one or more HDDs, one or more SSDs, or any combination thereof. Memory150and disk155may comprise hardware storage devices. The computing system manager160may manage the computing system105or aspects thereof (e.g., based on instructions stored in the memory150and executed by the processor145) to perform functions ascribed herein to the computing system105. In some examples, the network interface140, processor145, memory150, and disk155may be included in a hardware layer of a server125, and the computing system manager160may be included in a software layer of the server125. In some cases, the computing system manager160may be distributed across (e.g., implemented by) multiple servers125within the computing system105.

In some examples, the computing system105or aspects thereof may be implemented within one or more cloud computing environments, which may alternatively be referred to as cloud environments. Cloud computing may refer to Internet-based computing, wherein shared resources, software, and/or information may be provided to one or more computing devices on-demand via the Internet. A cloud environment may be provided by a cloud platform, where the cloud platform may include physical hardware components (e.g., servers) and software components (e.g., operating system) that implement the cloud environment. A cloud environment may implement the computing system105or aspects thereof through Software-as-a-Service (SaaS) or Infrastructure-as-a-Service (IaaS) services provided by the cloud environment. SaaS may refer to a software distribution model in which applications are hosted by a service provider and made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120). IaaS may refer to a service in which physical computing resources are used to instantiate one or more virtual machines, the resources of which are made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120).

In some examples, the computing system105or aspects thereof may implement or be implemented by one or more virtual machines. The one or more virtual machines may run various applications, such as a database server, an application server, or a web server. For example, a server125may be used to host (e.g., create, manage) one or more virtual machines, and the computing system manager160may manage a virtualized infrastructure within the computing system105and perform management operations associated with the virtualized infrastructure. The computing system manager160may manage the provisioning of virtual machines running within the virtualized infrastructure and provide an interface to a computing device115interacting with the virtualized infrastructure. For example, the computing system manager160may be or include a hypervisor and may perform various virtual machine-related tasks, such as cloning virtual machines, creating new virtual machines, monitoring the state of virtual machines, moving virtual machines between physical hosts for load balancing purposes, and facilitating backups of virtual machines. In some examples, the virtual machines, the hypervisor, or both, may virtualize and make available resources of the disk155, the memory, the processor145, the network interface140, the data storage device130, or any combination thereof in support of running the various applications. Storage resources (e.g., the disk155, the memory150, or the data storage device130) that are virtualized may be accessed by applications as a virtual disk.

The DMS110may provide one or more data management services for data associated with the computing system105and may include DMS manager190and any quantity of storage nodes185. The DMS manager190may manage operation of the DMS110, including the storage nodes185. Though illustrated as a separate entity within the DMS110, the DMS manager190may in some cases be implemented (e.g., as a software application) by one or more of the storage nodes185. In some examples, the storage nodes185may be included in a hardware layer of the DMS110, and the DMS manager190may be included in a software layer of the DMS110. In the example illustrated inFIG.1, the DMS110is separate from the computing system105but in communication with the computing system105via the network120. It is to be understood, however, that in some examples at least some aspects of the DMS110may be located within computing system105. For example, one or more servers125, one or more data storage devices130, and at least some aspects of the DMS110may be implemented within the same cloud environment or within the same data center.

Storage nodes185of the DMS110may include respective network interfaces165, processors170, memories175, and disks180. The network interfaces165may enable the storage nodes185to connect to one another, to the network120, or both. A network interface165may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor170of a storage node185may execute computer-readable instructions stored in the memory175of the storage node185in order to cause the storage node185to perform processes described herein as performed by the storage node185. A processor170may include one or more processing units, such as one or more CPUs, one or more GPUs, or any combination thereof. The memory150may comprise one or more types of memory (e.g., RAM, SRAM, DRAM, ROM, EEPROM, Flash, etc.). A disk180may include one or more HDDs, one or more SDDs, or any combination thereof. Memories175and disks180may comprise hardware storage devices. Collectively, the storage nodes185may in some cases be referred to as a storage cluster or as a cluster of storage nodes185.

The DMS110may provide a backup and recovery service for the computing system105. For example, the DMS110may manage the extraction and storage of snapshots135associated with different point-in-time versions of one or more target data sources within the computing system105. A snapshot135of a data source (e.g., a virtual machine, a database, a filesystem, a virtual disk, a virtual desktop, or other type of computing system or storage system) may be a file (or set of files) that represents a state of the data source (e.g., the data thereof) as of a particular point in time. A snapshot135may also be used to restore (e.g., recover) the corresponding data source as of the particular point in time corresponding to the snapshot135. A data source of which a snapshot135may be generated may be referred to as snappable. Snapshots135may be generated at different times (e.g., periodically or on some other scheduled or configured basis) in order to represent the state of the computing system105or aspects thereof as of those different times. In some examples, a snapshot135may include metadata that defines a state of the data source as of a particular point in time. For example, a snapshot135may include metadata associated with (e.g., that defines a state of) some or all data blocks included in (e.g., stored by or otherwise included in) the data source. Snapshots135(e.g., collectively) may capture changes in the data blocks over time. Snapshots135generated for the target data sources within the computing system105may be stored in one or more storage locations (e.g., the disk155, memory150, the data storage device130) of the computing system105, in the alternative or in addition to being stored within the DMS110, as described below.

To obtain a snapshot135of a target data source associated with the computing system105(e.g., of the entirety of the computing system105or some portion thereof, such as one or more databases, virtual machines, or filesystems within the computing system105), the DMS manager190may transmit a snapshot request to the computing system manager160. In response to the snapshot request, the computing system manager160may set the target data source into a frozen state (e.g. a read-only state). Setting the target data source into a frozen state may allow a point-in-time snapshot135of the target data source to be stored or transferred.

In some examples, the computing system105may generate the snapshot135based on the frozen state of the data source. For example, the computing system105may execute an agent of the DMS110(e.g., the agent may be software installed at and executed by one or more servers125), and the agent may cause the computing system105to generate the snapshot135and transfer the snapshot to the DMS110in response to the request from the DMS110. In some examples, the computing system manager160may cause the computing system105to transfer, to the DMS110, data that represents the frozen state of the target data source, and the DMS110may generate a snapshot135of the target data source based on the corresponding data received from the computing system105.

Once the DMS110receives, generates, or otherwise obtains a snapshot135, the DMS110may store the snapshot135at one or more of the storage nodes185. The DMS110may store a snapshot135at multiple storage nodes185, for example, for improved reliability. Additionally or alternatively, snapshots135may be stored in some other location connected with the network120. For example, the DMS110may store more recent snapshots135at the storage nodes185, and the DMS110may transfer less recent snapshots135via the network120to a cloud environment (which may include or be separate from the computing system105) for storage at the cloud environment, a magnetic tape storage device, or another storage system separate from the DMS110.

Updates made to a target data source that has been set into a frozen state may be written by the computing system105to a separate file (e.g., an update file) or other entity within the computing system105while the target data source is in the frozen state. After the snapshot135(or associated data) of the target data source has been transferred to the DMS110, the computing system manager160may release the target data source from the frozen state, and any corresponding updates written to the separate file or other entity may be merged into the target data source.

In response to a restore command (e.g., from a computing device115or the computing system105), the DMS110may restore a target version (e.g., corresponding to a particular point in time) of a data source based on a corresponding snapshot135of the data source. In some examples, the corresponding snapshot135may be used to restore the target version based on data of the data source as stored at the computing system105(e.g., based on information included in the corresponding snapshot135and other information stored at the computing system105, the data source may be restored to its state as of the particular point in time). Additionally or alternatively, the corresponding snapshot135may be used to restore the data of the target version based on data of the data source as included in one or more backup copies of the data source (e.g., file-level backup copies or image-level backup copies). Such backup copies of the data source may be generated in conjunction with or according to a separate schedule than the snapshots135. For example, the target version of the data source may be restored based on the information in a snapshot135and based on information included in a backup copy of the target object generated prior to the time corresponding to the target version. Backup copies of the data source may be stored at the DMS110(e.g., in the storage nodes185) or in some other location connected with the network120(e.g., in a cloud environment, which in some cases may be separate from the computing system105).

In some examples, the DMS110may restore the target version of the data source and transfer the data of the restored data source to the computing system105. And in some examples, the DMS110may transfer one or more snapshots135to the computing system105, and restoration of the target version of the data source may occur at the computing system105(e.g., as managed by an agent of the DMS110, where the agent may be installed and operate at the computing system105).

In response to a mount command (e.g., from a computing device115or the computing system105), the DMS110may instantiate data associated with a point-in-time version of a data source based on a snapshot135corresponding to the data source (e.g., along with data included in a backup copy of the data source) and the point-in-time. The DMS110may then allow the computing system105to read or modify the instantiated data (e.g., without transferring the instantiated data to the computing system). In some examples, the DMS110may instantiate (e.g., virtually mount) some or all of the data associated with the point-in-time version of the data source for access by the computing system105, the DMS110, or the computing device115.

In some examples, the DMS110may store different types of snapshots, including for the same data source. For example, the DMS110may store both base snapshots135and incremental snapshots135. A base snapshot135may represent the entirety of the state of the corresponding data source as of a point in time corresponding to the base snapshot135. An incremental snapshot135may represent the changes to the state-which may be referred to as the delta—of the corresponding data source that have occurred between an earlier or later point in time corresponding to another snapshot135(e.g., another base snapshot135or incremental snapshot135) of the data source and the incremental snapshot135. In some cases, some incremental snapshots135may be forward-incremental snapshots135and other incremental snapshots135may be reverse-incremental snapshots135. To generate a full snapshot135of a data source using a forward-incremental snapshot135, the information of the forward-incremental snapshot135may be combined with (e.g., applied to) the information of an earlier base snapshot135of the data source along with the information of any intervening forward-incremental snapshots135, where the earlier base snapshot135may include a base snapshot135and one or more reverse-incremental or forward-incremental snapshots135. To generate a full snapshot135of a data source using a reverse-incremental snapshot135, the information of the reverse-incremental snapshot135may be combined with (e.g., applied to) the information of a later base snapshot135of the data source along with the information of any intervening reverse-incremental snapshots135.

In some examples, the DMS110may provide a data classification service, a malware detection service, a data transfer or replication service, backup verification service, or any combination thereof, among other possible data management services for data associated with the computing system105. For example, the DMS110may analyze data included in one or more data sources of the computing system105, metadata for one or more data sources of the computing system105, or any combination thereof, and based on such analysis, the DMS110may identify locations within the computing system105that include data of one or more target data types (e.g., sensitive data, such as data subject to privacy regulations or otherwise of particular interest) and output related information (e.g., for display to a user via a computing device115). Additionally or alternatively, the DMS110may detect whether aspects of the computing system105have been impacted by malware (e.g., ransomware). Additionally or alternatively, the DMS110may relocate data or create copies of data based on using one or more snapshots135to restore the associated data source within its original location or at a new location (e.g., a new location within a different computing system105). Additionally or alternatively, the DMS110may analyze backup data to ensure that the underlying data (e.g., user data or metadata) has not been corrupted. The DMS110may perform such data classification, malware detection, data transfer or replication, or backup verification, for example, based on data included in snapshots135or backup copies of the computing system105, rather than live contents of the computing system105, which may beneficially avoid adversely affecting (e.g., infecting, loading, etc.) the computing system105.

In some examples, the DMS110may be a multi-tenancy DMS110that may provide backup services for multiple tenants (e.g., organizations or business units). The tenants may be organized into a hierarchy of tenants. For example, resources of the DMS110may be shared among multiple higher-level tenants, and at least some of the higher-level tenants may be associated with one or more levels of lower-level tenants (e.g., subtenants), with resources associated with a higher-level tenant being shared by multiple subtenants of that tenant. The DMS110may obtain and store report data for computing objects in the multi-tenant system, the computing objects being resources or other entities within the DMS110(e.g., clusters, storage nodes185, or portions of clusters or storage nodes185). The report data may include, for example, a status of the computing objects, such as a compliance status, a size, a status or history of one or more tasks related to the computing objects, or any combination thereof.

Techniques, systems, and devices described herein provide for the DMS110to determine whether a user has permission to access report data for a given computing object based on the tenant associated with a given log-in session by the user. Computing objects within the DMS110may be organized as part of an object hierarchy. If a tenant is granted access to one object within the object hierarchy, the tenant automatically also has access to any other object that is below that object within the object hierarchy. The user may log in to establish a session with the DMS110. During the session, the user (e.g., an administrator for a given tenant, or some other user of the tenant) may request to access report data for a first set of one or more computing objects. In response to the request, the DMS110may determine an ID of the user and an ID of the tenant to which the user is logged in based on context information associated with the user's log-in session via which the request is sent. The tenant may have access to (e.g., permission or authorization to access) a second set of computing objects within the object hierarchy. The DMS110may filter through the first set of computing objects associated with the requested report data by filtering out or omitting computing objects that are not in the second set of computing objects to which the tenant has access. The DMS110may determine that the user has permission to access the requested report data for the remaining computing objects that are included in the second set of objects (e.g., are assigned to or accessible by the tenant) and may output such report data to the user accordingly.

In some examples, when the DMS110generates and stores the report data for a given computing object, the DMS110may add a field in the report data that indicates an ID of the corresponding computing object. The DMS110may generate a mapping table for mapping object IDs to corresponding tenants that have access to the objects based on the computing object hierarchy. Accordingly, higher-level tenants may be able to request that the DMS110display report data that is filtered by subtenants. For example, if a tenant requests to view all report data associated with a first subtenant, the DMS110may scan the mapping table using a tenant ID of the first subtenant to determine computing object IDs of computing objects that the first subtenant has access to in the computing object hierarchy. The DMS110may filter through a database of report data stored at the DMS110using the identified computing object IDs. The DMS110may output, to a user of the tenant that requested the report data for the first subtenant, all of the report data that includes the computing object IDs. The described techniques may thereby provide for the DMS110to retrieve and provide report data with improved reliability, security, and efficiency.

FIG.2illustrates an example of a multi-tenancy system200that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The multi-tenancy system200may implement or be implemented by aspects of the computing environment100described with reference toFIG.1. For example, a DMS110may provide backup and recovery protection for data sources for multiple tenants and/or subtenants.

As described herein, a global organization (e.g., a tenant205) may provide IT services, including backup and recovery protection via a DMS110, to multiple tenants (e.g., tenant210-aand tenant210-b). Additionally, each tenant may further have subtenants. For example, the tenant210-amay have a subtenant215-aand a subtenant215-b. For example, the tenant205may be the IT services unit of an organization, and the tenant210-aand the tenant210-bmay be business units of or teams within the organization. The subtenant215-aand the subtenant215-bmay be sub-business units or sub-teams of the business unit corresponding to the tenant210)-a (e.g., working groups within the business unit). The subtenant215-csimilarly may be a sub-business unit or sub-teams of the business unit corresponding to the tenant210-b. As another example, the tenant205may be an MSP, and the tenant210-aand the tenant210-bmay be different enterprises/customers (e.g., organizations) of the MSP. The subtenant215-a, the subtenant215-b, and the subtenant215-cmay be business units and/or working groups/entities/teams of the enterprises/customers corresponding to the tenant210-aand the tenant210-b.

In some examples, the tenant205corresponds to a DMS110that controls backup and recovery resources that are used to provide backup and recovery protection to the various tenants210-aand sub tenants215of the organization. An administrative user of the tenant205may access the DMS110to configure and allocate resources (e.g., computing objects) that are used to support backup and recovery for data sources associated with the various tenants and subtenants. For example, the user may access a user interface of the DMS110to create the tenants210-aand210-band to assign the respective backup and recovery resources to the created tenants210-aand210-b. Assignment of resources to a tenant may include updating metadata (e.g., RBAC metadata) associated with the respective resources to indicate respective tenant or subtenant assignments. In some cases, the administrative user may assign, to a tenant or subtenant using the user interface of the DMS110, a data source that is to be backed-up using a respective resource, a backup or recovery procedure that may be performed using the respective resource, and/or a storage capacity for the backup and recovery resource. Assignment of a data source, procedure, or capacity may include updating the metadata (e.g., RBAC metadata) associated with the backup and recovery resource (e.g., computing object) that is to be used by the tenant or subtenant.

In some cases, the administrative user may access the user interface of the DMS110to assign users to the tenants210or subtenants215. For example, the administrative user of the tenant205may assign a second administrative user to the tenant210-asuch that the second administrative user may access the platform for backup and recovery management, as well as further subtenant creation and resource assignment, data source assignment, procedure assignment, and capacity assignment. A third demonstrative user may be similarly assigned to the tenant210-b. User assignment may be restricted or controlled based on hierarchical techniques, as described herein with respect to computing object assignment.

As described herein, users may access a user interface associated the DMS110to control various backup and recovery aspects related to a tenant205or210or subtenant215. In some examples, the user interface may be supported by a platform or application that is used to manage multiple DMSs110, multiple tenants205, subtenants215, etc. In some examples, an authorized user may access the platform or application to control backup and recovery procedures, as well as tenant or subtenant creation and assignment. Each tenant205or210or subtenant215may be associated with a “context” of the platform or application. An application context refers to a state of an application that allows a user to manage to control aspects of backup and recovery associated with a particular tenant205or210or subtenant215. Thus, a user may access an application context associated with the tenant210-aand the user may view resources, procedures, etc. that are assigned to the tenant210-aas well as create subtenants of the tenant210-a(e.g. subtenants215-aand215-b) and assign subsets of resources to the created subtenants. Thus, when discussing a user accessing a user interface of the DMS110herein, the user may access the application context associated with a tenant or subtenant to perform various functions and procedures described herein.

The DMS110may provide for an RBAC scheme such that users associated with each tenant/subtenant may access only the computing objects assigned to the given tenant/subtenant. Accordingly, the tenants210and subtenants215may share a single DMS110and/or a single data management cluster without unauthorized access by any tenant210or subtenant215to computing objects or files assigned to a different tenant210or subtenant215. For example, one business unit of an enterprise may not access computing objects or files assigned to a different business unit of the enterprise. As another example, one customer of an MSP may not access computing objects or files assigned to a different customer of the MSP.

In accordance with aspects of the present disclosure, the DMS110may receive, at a user interface associated with the DMS110, a request, by a user of the DMS110, to access report data for a first set of one or more computing objects of the DMS110. In response to the request, the DMS110may determine an ID of the user and an ID of the tenant210to which the user is logged in based on context information associated with the user's log-in session via which the request is sent. The tenant210may have access to (e.g., permission or authorization to access) a second set of computing objects within an object hierarchy of the DMS110. The DMS110may filter through the first set of computing objects associated with the requested report data by filtering out or omitting computing objects that are not in the second set of computing objects to which the tenant210has access. The DMS110may determine that the user has permission to access the requested report data for the remaining computing objects that are included in the second set of objects (e.g., are assigned to or accessible by the tenant) and may output such report data to the user accordingly.

In some examples, when the DMS110generates and stores the report data for a given computing object, the DMS110may add a field in the report data that indicates an ID of the corresponding computing object. The DMS110may generate a mapping table for mapping object IDs to corresponding tenants210that have access to the objects based on the computing object hierarchy. Accordingly, higher-level tenants210, such as the tenant210-a, may be able to request that the DMS110display report data that is filtered by subtenants215, such as the subtenant215-a, the subtenant215-b, or both. For example, if the tenant210-arequests to view all report data associated with the subtenant215-a, the DMS110may scan the mapping table using a tenant ID of the subtenant215-ato determine computing object IDs of computing objects that the subtenant215-ahas access to in the computing object hierarchy. The DMS110may filter through a database of report data stored at the DMS110using the identified computing object IDs. The DMS110may output, to a user of the tenant210-athat requested the report data for the subtenant215-a, all of the report data that includes the computing object IDs. In some examples, the user of the tenant210-amay request to view all report data for a group or set of two or more subtenants215of the tenant210-a, and the DMS110may filter the report data accordingly. The described techniques may thereby provide for the DMS110to retrieve and provide report data with improved reliability, security, and efficiency.

FIG.3illustrates an example of a computing object hierarchy300that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The computing object hierarchy300may implement or be implemented by aspects of the computing environment100described with reference toFIG.1. For example, a DMS110may provide backup and recovery protection for data sources for multiple tenants and/or subtenants via one or more data management clusters. For example,FIG.3illustrates a first data management cluster315-aand a second data management cluster315-b, which may provide protection for data sources associated with a first tenant305-a, a second tenant305-b, and a third tenant305-c.

Each of the first data management cluster315-aand the second data management cluster315-bmay include a set of computing objects (e.g., resources such as virtual machines or databases) which may be organized according to a hierarchical relationship. For example, the first data management cluster315-amay include the computing object310-a, which has as descendants the computing object310-band the computing object310-e. The computing object310-bhas as descendants the computing object310-cand the computing object310-d, and the computing object310-dfurther has as a descendant the computing object310-g. The computing object310-ehas as a descendent the computing object310-f.

The second data management cluster315-bmay include the computing object310-h, which has as descendants the computing object310-iand the computing object310-1. The computing object310-ihas as a descendant the computing object310-j, and the computing object310-jfurther has as a descendant the computing object310-k. The computing object310-1has as a descendent the computing object310-m.

As described herein, the multiple tenants (the first tenant305-a, the second tenant305-b, and the third tenant305-c) may share data management resources. More specifically, multiple tenants of a DMS110may share computing objects310of a same data management clusters315. For example, the first tenant305-aand the second tenant305-bmay both be assigned computing objects310within the first data management cluster315-a, and the first tenant305-aand the third tenant305-cmay both be assigned computing objects310within the second data management cluster315-b. The assignment of computing objects310of the data management clusters315may respect the hierarchical relationship among the computing objects310. For example, assignment of a top-level computing object such as the computing object310-bto the first tenant305-amay result in assignment of (e.g., an implicit assignment of) the computing object310-c, the computing object310-d, and the computing object310-gto the first tenant305-a, as the computing object310-c, the computing object310-d, and the computing object310-gare descendants of the computing object310-bwithin the computing object hierarchy of the first data management cluster315-a. Similarly, assignment of the computing object310-eto the second tenant305-bmay result in assignment of the computing object310-fto the second tenant305-b. As another example, assignment of the computing object310-ito the first tenant305-amay result in assignment of the computing object310-jand the computing object310-kto the first tenant305-a. As another example, assignment of the computing object310-1to the third tenant305-cmay result in assignment of the computing object310-mto the third tenant305-c. Such implicit assignment of resources based on the computing object hierarchy may simplify management of the DMS110for an administrator (e.g., an IT services unit or an MSP). For example, an MSP may assign a full data management cluster315to a tenant to achieve assignment of all backup computing objects from that data management cluster315to the tenant. As another example, an MSP may assign a Vcenter from a data management cluster315to assign all of the virtual machines from that Vcenter to the tenant.

As described herein, the DMS110may provide for a multi-tenancy RBAC scheme such that users associated with each tenant/subtenant may access only the computing objects assigned to the given tenant/subtenant. Multi-tenancy RBAC supports in-depth computing object level access control granularity for data management systems such as the DMS110with multiple data management clusters. Multi-tenancy RBAC supports both authorizing a full data management cluster315to a tenant (e.g., assigning all of the computing objects310of a given data management cluster315to a given tenant), and assignment of specific computing objects310of a data management cluster315to a given tenant. A user associated with the first tenant305-amay not access computing objects assigned to the second tenant305-bor the third tenant305-c, a user associated with the second tenant305-bmay not access computing objects assigned to the first tenant305-aor the third tenant305-c, and a user associated with the third tenant305-cmay not access computing objects assigned to the first tenant305-aor the second tenant305-b. For example, a tenant dashboard (e.g., a user interface view for a tenant account at a computing device115) may show relevant statistics and information regarding authorized computing objects310for that tenant, and the tenant may only manage data backup for the authorized computing objects310. The multi-tenancy RBAC may prevent information leakage across tenants via enforcing access control at all user interfaces, events, audits, reports, etc., for a tenant, such that a tenant is not able to view or access direct or aggregated information about computing objects310that are not assigned to that tenant. A tenant may not bypass the access control enforcement in either the control plane or the cluster side via federated login.

As an example, an MSP account with multiple cloud accounts or on-premise data management clusters (e.g., the first data management cluster315-amay be a first cloud account or on-premise data management cluster of the MSP and the second data management cluster315-bmay be a second cloud account or on-premise data management cluster of the MSP), and the MSP may assign a specific computing object310within the multiple cloud accounts or on-premise data management clusters of the MSP to a given tenant (e.g., customer) of the MSP. Further, multi-tenancy RBAC may authorize different permissions (e.g., read-only, read-write) on different computing objects310. For example, a tenant (e.g., the first tenant305-a) may have read-only access to a virtual machine (e.g., the computing object310-c) but read-write access to a MSSQL database (e.g., the computing object310-d).

Techniques, systems, and devices described herein provide for the DMS110to determine whether a user has permission to access report data for a given computing object310based on the tenant305associated with a given log-in session by the user. The user may log in to establish a session with the DMS110. During the session, the user (e.g., an administrator for a given tenant305, or some other user of the tenant305) may request to access report data for a first set of one or more computing objects310. In response to the request, the DMS110may determine an ID of the user and an ID of the tenant305to which the user is logged in based on context information associated with the user's log-in session via which the request is sent. The tenant305may have access to (e.g., permission or authorization to access) a second set of computing objects310within the object hierarchy. The DMS110may filter through the first set of computing objects310associated with the requested report data by filtering out or omitting computing objects310that are not in the second set of computing objects310to which the tenant305has access. The DMS110may determine that the user has permission to access the requested report data for the remaining computing objects310that are included in the second set of computing objects310(e.g., are assigned to or accessible by the tenant) and may output such report data to the user accordingly.

For example, if the user is logged in to the tenant305-a(Tenant1), the second set of computing objects310to which the tenant305-ahas access within the computing object hierarchy300may include the computing objects310-b,310-c,310-d,310-g,310-i,310-j, and310-k. If the user requests to access report data for a first set of computing objects310including computing objects310-a,310-b,310-c,310-d,310-e, and310-f, the DMS110may determine that the user is authorized to access a subset of the requested report data and the DMS110may output the report data associated with the computing objects310-b,310-c, and310-daccordingly.

In some examples, when the DMS110generates and stores the report data for a given computing object310, the DMS110may add a field in the report data that indicates an ID of the corresponding computing object310. The DMS110may generate a mapping table for mapping object IDs to corresponding tenants305that have access to the objects based on the computing object hierarchy300. Accordingly, higher-level tenants305may be able to request that the DMS110display report data that is filtered by subtenants. For example, if a tenant305requests to view all report data associated with a first subtenant, the DMS110may scan the mapping table using a tenant ID of the first subtenant to determine computing object IDs of computing objects310that the first subtenant has access to in the computing object hierarchy. The DMS110may filter through a database of report data stored at the DMS110using the identified computing object IDs. The DMS110may output, to a user of the tenant305that requested the report data for the first subtenant, all of the report data that includes the computing object IDs. The described techniques may thereby provide for the DMS110to retrieve and provide report data with improved reliability, security, and efficiency.

FIG.4illustrates an example of a computing environment400that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The computing environment400may implement or be implemented by aspects of the computing environment100, the multi-tenancy system200, and the computing object hierarchy300described with reference toFIGS.1-3. For example, the computing environment400includes a DMS410and a computing device415, which may be in communication with one another via a network420, as described with reference toFIG.1. The DMS410may provide backup services for multiple tenants (e.g., organizations or business units). The tenants of the DMS410may be organized in a hierarchical structure, as described with reference toFIG.2. In this example, the DMS410may determine whether a user has permission to access report data for a given computing object440based on a tenant associated with a log-in session by the user.

The DMS410may provide backup services for data sources of multiple tenants. The data sources that are to be backed up may be stored within one or more computing systems105(not pictured inFIG.4). The DMS410may include or be coupled with a central manager425. The central manager425may be a component of the DMS410that manages or facilitates tasks performed by the DMS410. In this example, the central manager425may manage access authorization and filtering for report data in a multi-tenancy system.

The DMS410may include multiple computing objects440(e.g., N computing objects440), which may be resources or other entities within the DMS410. In some examples, the DMS410may include one or more clusters (e.g., storage clusters or storage nodes), and the computing objects440may represent examples of a cluster or a portion of a cluster of the DMS410, as described in further detail elsewhere herein, including with reference toFIG.3. The computing objects440may be, for example, virtual machines, folders, filesets, databases, other computing objects, or any combination thereof. Each computing object440of the DMS410may be associated with or identified by a respective object ID (e.g., a unique ID). The computing objects440may be stored at the DMS410, at the central manager425, at one or more other servers or databases associated with or coupled to the DMS410, or any combination thereof.

The DMS410may obtain report data for the computing objects440. The report data may be general information (e.g., application-related information) related to the computing objects440, such as a backup status of a computing object440, a status of a task (e.g., a protection task report related to all protection tasks performed for a computing object440, or some other type of task) or job performed on the computing object440(e.g., a time until completion of the task, a starting time of the task, a success or failure of the task, or any combination thereof), a compliance status of a computing object440(e.g., whether the computing object is complying with or following a service level agreement domain), a size of the computing object440(e.g., an object capacity, a logical size, other size information, or any combination thereof), or any combination thereof. The DMS410may generate the report data and store the report data in a report data storage430) (e.g., a database or other storage location at the DMS410, at the central manager425, at one or more other storage locations, or any combination thereof). A client of the DMS410may access a report page of a user interface to view the report data for computing objects440of the client.

As described herein, when the DMS410generates report data for a given computing object440, the DMS410may determine an object ID of the corresponding computing object. The DMS410may store the object ID with the report data in the report data storage430. For example, each section or portion of report data (e.g., report data for each generated report) may be indexed by a respective object ID associated with a computing object440on which the report was performed. By storing the object ID with the report data in the report data storage430, the DMS410may efficiently and reliably determine which computing object440is associated with the report data, which may improve security and reduce latency associated with backup and management of data by the DMS410.

In some examples, the DMS410may store the report data in a table format in the report data storage430. For example, the DMS410may store the report data in one or more rows, where each row may include a respective type or portion of report data for a respective computing object440. In some examples, multiple rows of report data may be stored for a same computing object440if, for example, the report data includes a relatively large quantity of information, or the report data includes multiple types of report data (e.g., a size of the computing object440and a compliance status of the computing object440, or other types of report data). In the example illustrated inFIG.4, a first row of the report data storage430may include report data associated with a first computing object440having an object ID #1. A second row and a third row may include report data associated with a second computing object440having an object ID #2. The report data in the second row may, for example, indicate a size of the second computing object440at a given time, and the report data in the third row may, for example, indicate a status of a task performed on the computing object440at a given time, or some other type of report data. Other rows of report data may include other report data for the first and second computing objects440or other computing objects440of the DMS410.

In some examples, a user of the DMS410may request to view report data for one or more computing objects440. The user may be logged in to the DMS410via a tenant of the multiple tenants supported by the DMS410. For example, the user may be an administrator or other user of a tenant. As part of the log-in session with the DMS410, the user may output (e.g., send, transmit) a report data request445to the DMS410. The user may utilize a computing device415to log in to the DMS410and access a user interface that displays account settings and information associated with the user's log-in session. The user may send the report data request445via the user interface and the network420to the DMS410. The report data request445may indicate a request for the user to view or access report data and may indicate one or more computing objects associated with the requested report data. For example, the user may request to view a compliance status or size associated with one or more of the computing objects440of the DMS410that pertain to the users' data.

Techniques, systems, and devices described herein provide for the DMS410to determine whether the user that sends the report data request445has permission to access the report data for the requested computing object(s)440) based on a tenant associated with the log-in session by the user. In response to receiving the report data request445, the DMS410may determine an ID of the user and an ID of the tenant to which the user is logged in based on context information for the log-in session of the user via which the report data request445is sent. The context information may include information that defines or identifies the log-in session of the user, including the user ID, the tenant ID, other context information, or any combination thereof.

After determining the tenant ID associated with the report data request445, the DMS410(e.g., the central manager425) may apply a filter to the one or more computing objects440indicated via the report data request445. The DMS410may filter through the one or more computing objects440associated with the report data request445by filtering out or omitting computing objects440that the tenant does not have access to in a computing object hierarchy of the DMS410(such as the computing object hierarchy300described with reference toFIG.3).

As described with reference toFIG.3, the computing objects440of the DMS410may be organized as part of an object hierarchy, and if a tenant is granted access to one computing object440within the object hierarchy, the tenant automatically also has access to any other computing object440that is below that computing object440within the object hierarchy. Accordingly, the DMS410may scan the object hierarchy using the tenant ID associated with the report data request445to determine which node (e.g., computing object440) the tenant has authorization or permission to access. The DMS410may determine that the node and all computing objects440below the node in the object hierarchy are included in a set of one or more computing objects440to which the tenant has access. When applying the filter to the one or more computing objects440associated with the report data request445, the DMS410may determine which of the requested computing objects440are included in the set of one or more computing objects440to which the tenant has access. In some examples, the DMS410may compare object IDs of the computing objects440, and the DMS410may filter out or omit any computing objects440indicated via the report data request445that have object IDs that do no match any object IDs of the set of one or more computing objects440to which the tenant has access.

After filtering out any computing objects440to which the tenant does not have access, the DMS410may determine that remaining computing objects440indicated via the report data request445are accessible by the tenant. That is, the DMS410may determine that the user has permission to access the requested report data for the remaining computing objects440that are indicated via the report data request445and are included in the set of one or more computing objects440to which the tenant has access in the object hierarchy. The DMS410may output the report data for such computing objects440to the user. For example, the DMS410may output the computing objects440or access to the computing objects (e.g., the DMS410may export or mount the computing objects440) to the computing device415(e.g., as part of the user interface) via the network420. The DMS410may similarly verify authorization for any report data request445received from any other user of the DMS410, which may improve security and reliability of the services performed by the DMS410.

In some examples, a user of the DMS410may request to filter report data by one or more parameters, such as object size, compliance status, computing object440, tenant, or some other filtering criteria. As described herein, the DMS410may use the object IDs stored in the report data storage430to support filtering the report data in the report data storage430(e.g., a database of report data) per computing object440or per tenant. In some examples, a user of a relatively high level tenant (e.g., an administrator of a global organization, MSP, or other tenant that has authorization over at least one subtenant) may request to view report data for one or more subtenants. After establishing or initiating a log-in session with the DMS410via the tenant, the user may access a user interface via the computing device415. The user may perform a search or other request in the user interface to view report data for one or more subtenants. The DMS410may receive the filtering request450via the network420. The filtering request450may indicate an ID of the subtenant(s) for which the user requests to view report data.

In response to receiving the filtering request450to view report data for a given subtenant, the DMS410may filter the report data in the report data storage430per tenant. As described herein, the DMS410may utilize a mapping table435to perform the filtering of report data per tenant. The mapping table435may represent a database of information stored at the DMS410, the central manager425, or some other storage location included in or coupled with the DMS410. The mapping table435may include mapping information for the computing objects440of the DMS410. The mapping information for a given computing object440may be stored in a row of the mapping table435. That is, each row of the mapping table435may be associated with a respective computing object440and may be indexed by a respective object ID. The mapping information in each row may include the object ID and one or more tenant IDs of tenants that have access to the object ID in the object hierarchy of the DMS410.

In the example illustrated inFIG.4, the mapping table435may include N rows indexed by object IDs #1. #2, #3, through #N. A first row for the object ID #1 may include a first tenant ID #1 and may indicate a first tenant having the tenant ID #1 has access to the computing object440with object ID #1 in the object hierarchy. The same tenant may also have access to a computing object440with object ID #N, as shown by a final row in the mapping table435(e.g., the object IDs #1 and #N may be under a same node in the object hierarchy, and the tenant may have access to that node). A second tenant with tenant ID #2 may have access to a second computing object440with object ID #2 and a third tenant with tenant ID #3 may have access to a third computing object440with object ID #3. Although a single tenant ID is shown in each row of the mapping table435illustrated inFIG.4, it is to be understood that one or more tenant IDs may be included in each row, because a single computing object440) may be assigned to one or more tenants, in some examples.

The DMS410(e.g., the central manager425or some other component of the DMS410) may update the mapping table435dynamically based on the computing object hierarchy and tenant access grants. In some examples, a backend job (referred to as a mapping job in some examples herein) may be executed to maintain the mapping table435. Generating and updating the mapping information in the mapping table435may be referred to as flattening the computing object hierarchy, in some examples. For example, the mapping job may be operable to review tenant assignments in the computing object hierarchy (e.g., which tenant is assigned to which node in the object hierarchy) and generate mapping information that flattens the tenant assignments. The mapping job may be executed periodically or according to a schedule and may scan the object hierarchy to determine if any tenant assignments are changed or newly created. If a tenant was previously assigned to a first node, and the tenant assignment changed so the tenant is no longer assigned to a node, the mapping job may, for example, remove the tenant ID from the mapping table435. If a tenant is assigned to a new node in the object hierarchy, the mapping job may determine a set of computing objects440) that are below the node and include the node, and the mapping job may update the mapping table435to include the tenant ID in each row of the mapping table that is indexed by an object ID of a computing object440of the set of computing objects440. The DMS410may thereby execute one or more mapping jobs to generate and maintain the mapping table435, which may assist with filtering report data per tenant.

To filter the data per tenant in response to the filtering request450, the DMS410may scan the mapping table435using the tenant ID of the subtenant(s) indicated via the filtering request450. The DMS410may identify or select a set of computing object IDs from among all of the computing object IDs in the mapping table435based on the mapping information for the set of computing object IDs including the tenant ID of the subtenant. For example, if the filtering request450requests to view report data for a first subtenant having the tenant ID #1, the DMS410may scan the mapping table435using the tenant ID #1. The DMS410may determine a set of computing object IDs, such as the object IDs #1 and #N, that correspond to mapping information including the tenant ID #1 in the mapping table435.

The DMS410may subsequently identify report data in the report data storage430(e.g., report data that has been previously obtained and stored by the DMS410) that includes the set of object IDs selected from the mapping table435. For example, if the DMS410determined, based on scanning the mapping table435, that the object IDs #1 and #N are assigned to the subtenant, the DMS410may scan the report data storage430to find any report data that includes the object IDs #1 and #N. The DMS410may determine that the identified report data includes all of the report data for the requested subtenant. The DMS410may output (e.g., transmit, send, export, or mount), the identified report data for the subtenant to the user via the user interface in response to the filtering request450. In some examples, the DMS410may display the report data in a list or other organized format. By storing object IDs with report data and maintaining a mapping table435, the DMS410may thereby provide filtered report data to a user of the DMS410.

In some examples, the DMS410may verify authorization of the user to access the report data before outputting the filtered report data. For example, the DMS410may use the tenant ID of the tenant associated with the user to determine whether the tenant is authorized to access the subtenant and corresponding computing objects in the hierarchy. If the tenant is not authorized to access the computing objects, the subtenant, or both, the DMS410may refrain from outputting the filtered report data to the user. If the tenant is authorized to access the computing objects and the subtenant, the DMS410may output the filtered report data to the user.

The DMS410described herein may thereby obtain and store report data for multiple computing objects440of the DMS410while managing client data for multiple tenants. By using the described techniques for authorizing access to report data and filtering report data, the DMS410may support efficient, secure, and reliable management of report data in a multi-tenant system.

FIG.5illustrates an example of a process flow500that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The process flow500may implement or be implemented by aspects of the computing environments100and400, the multi-tenancy system200, and the computing object hierarchy300, as described with reference toFIGS.1-4. For example, the process flow500may be implemented by a user505, which may be logged in to a tenant515(e.g., an administrator for the tenant515, or some other user505of the tenant515) and one or more components of a DMS510, which may represent examples of corresponding devices and components as described with reference toFIGS.1-4. In some examples, the user505may represent an example of a computing device that may communicate with the DMS510via a user interface, such as the computing devices115or415described with reference toFIGS.1and2. In this example, the DMS510may determine whether the user505has permission to access report data for a given computing object based on the tenant515associated with a log-in session of the user505.

In some aspects, the operations illustrated in the process flow500may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code (e.g., software or firmware) executed by a processor, or any combination thereof. For example, aspects of the process flow500may be implemented or managed by a DMS, a report data access component, or some other software or application within a DMS510that is configured to manage backup and restoration of data and other computing resources for multiple tenants.

Although the user505and the DMS510are illustrated inFIG.5, it is to be understood that the process to authorize access for report data in a multi-tenancy system as described herein may be performed by any one or more components of a DMS510, including components not shown inFIG.5. For example, the DMS510may include or be coupled with a central manager, one or more other components, or any combination thereof (not pictured inFIG.5) that may be configured to facilitate or manage any one or more of the processes illustrated inFIG.5. Additionally, or alternatively, one or more components may perform tasks or may be configured to function in a different manner than illustrated inFIG.5. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, further steps may be added, or different components may perform the steps.

At520, in some examples, the DMS510may generate report data for one or more computing objects. The DMS510may generate the report data periodically, at one or more scheduled time instances, or dynamically based on one or more conditions or triggers associated with the computing objects. The report data for a given computing object may include a compliance status of the computing object, a size of the computing object, a status of one or more tasks being performed using or on the computing object, one or more other types of data associated with the computing object, or any combination thereof.

At525, in some examples, the DMS510may store the report data for the one or more computing objects based on generating the report data. The DMS510may store, with the report data, one or more object IDs for the one or more computing objects. For example, the DMS510may store a respective object ID for each portion of report data, as described in further detail elsewhere herein, including with reference toFIG.4. The DMS510may store the report data and one or more object IDs at the DMS510(e.g., in a report data database or storage location) or in some other storage location associated with the DMS510.

At530, the user505may send (e.g., output, transmit) a request, to the DMS510via a user interface, to access report data associated with a first set of one or more computing objects. The first set of one or more computing objects may include some or all of multiple computing objects of the DMS510. The computing objects of the DMS510may represent examples of resources or other entities within the DMS510(e.g., clusters or portions of clusters) and may be organized into a hierarchy of computing objects, as described in further detail elsewhere herein, including with reference toFIG.3.

At535, the DMS510may identify context information for a log-in session associated with the request to access the report data. For example, the user505may log in to the DMS510to initiate the log-in session. The user505may transmit the request as part of the log-in session. The user505may log in to the DMS510as a user505of the tenant515(e.g., an administrator or other user505of the tenant515). The context information for the log-in session may include a tenant ID of the tenant515. The Tenant ID may identify or distinguish the tenant515from among multiple tenants of the multi-tenancy DMS510.

At540, the DMS510may apply a filter to the first set of one or more computing objects associated with the requested report data. The DMS510may access the requested report data in a report data storage location of the DMS510in response to the request. The DMS510may identify one or more object IDs that are stored in or included in the requested report data. The one or more object IDs may identify the first set of one or more computing objects. The filter may be based on a second set of one or more computing objects to which the tenant515associated with the request (e.g., the tenant515to which the user505is logged in) has access within the hierarchy of computing objects. For example, filtering the first set of one or more computing objects may include the DMS510determining whether each computing object ID of the one or more computing object IDs for the first set of one or more computing objects associated with the requested report data matches a computing object ID of the second set of one or more computing objects to which the tenant515has access.

At545, the DMS510may output (e.g., send, transmit), in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects. The DMS510may output the at least one computing object based on that computing object being included in the second set of computing objects (e.g., an object ID of the at least one computing object matches an object ID of at least one second computing object of the second set). In some examples, the DMS may output all of the first set of one or more computing objects if all of the first set of one or more computing objects are included in the second set of one or more computing objects (e.g., if the tenant515has access to all of the first set of one or more computing objects). Additionally, or alternatively, the DMS510may output a subset of one or more computing objects that the tenant515has access to.

In some examples, the DMS510may refrain from outputting second report data for a second computing object of the first set of one or more computing objects based on the second computing object being absent from (e.g., not included in or excluded from) the second set of one or more computing objects. For example, if the DMS510determines that an object ID of the second computing object does not match or is not the same as an object ID of any of the second set of one or more computing objects, the DMS510may refrain from outputting report data for the second computing object to the first user505because the first user505may not be authorized to access the report data.

The DMS510may thereby facilitate secure and reliable exchanges of report data with customers or users505of the DMS510. The DMS510may use context information associated with a log-in session of a user505to determine a tenant515to which the user505is logged in. The DMS510may use a tenant ID of the tenant515to determine whether the tenant515is authorized or permitted to access the computing objects associated with requested report data. The DMS510may thereby support multiple tenants while maintaining reliable and secure data management services for each tenant515separately.

FIG.6illustrates an example of a process flow600that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The process flow600may implement or be implemented by aspects of the computing environments100and400, the multi-tenancy system200, the computing object hierarchy300, and the process flow500, as described with reference toFIGS.1-5. For example, the process flow600may be implemented by a user605, which may be logged in to a first tenant615(e.g., an administrator for the first tenant615, or some other user605of the first tenant615) and one or more components of a DMS610, which may represent examples of corresponding devices and components as described with reference toFIGS.1-5. In some examples, the user605may represent an example of a computing device that may communicate with the DMS610via a user interface, such as the computing devices115or415described with reference toFIGS.1and2. In this example, the DMS may generate and store report data for computing objects associated with multiple tenants, and the user605may request the DMS610to filter report data per tenant.

In some aspects, the operations illustrated in the process flow600may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components), code (e.g., software or firmware) executed by a processor, or any combination thereof. For example, aspects of the process flow600may be implemented or managed by a DMS610, a report data access component, or some other software or application within a DMS610that is configured to manage backup and restoration of data and other computing resources for multiple tenants.

Although the user605and the DMS610are illustrated inFIG.6, it is to be understood that the process to authorize access for report data in a multi-tenancy system as described herein may be performed by any one or more components of a DMS610, including components not shown inFIG.6. For example, the DMS610may include or be coupled with a central manager, one or more other components, or any combination thereof (not pictured inFIG.6) that may be configured to facilitate or manage any one or more of the processes illustrated inFIG.6. Additionally, or alternatively, one or more components may perform tasks or may be configured to function in a different manner than illustrated inFIG.6. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, further steps may be added, or different components may perform the steps.

At620, the user605may output (e.g., transmit, send) a request to view report data associated with one or more other tenants of multiple tenants supported by the DMS610(not pictured inFIG.6). For example, the user605may be an administrator or some other user605of the first tenant615, and the first tenant615may be a higher level tenant within a hierarchy of the multiple tenants supported by the DMS610(e.g., a global organization, an MSP, or some other higher level tenant). The one or more other tenants may be subtenants of the first tenant615. In some examples, the user605may request to view all report data previously obtained by and stored by the DMS610that relates to any combination of one or more tenants that are assigned to or below the first tenant615in the tenant hierarchy. In some examples, the user605may access a user interface of the DMS610and perform a search within the user interface. If the user605searches for a given organization or subtenant, the search may correspond to or trigger the request for report data associated with the given organization or subtenant. For example, the user605may request to view a display on the user interface of the report data for the given subtenant.

At625, the DMS610may filter a database of report data stored by the DMS610. The DMS610may filter the report data per tenant and in response to the request from the user605, one or more other requests from other users of the DMS610, or any combination thereof.

As part of filtering the database of report data for the second tenant in response to the request, at630, the DMS610may access a mapping table that includes mapping information for the computing objects of the DMS610. The mapping information for a given computing object may map that computing object to at least one tenant that has access to the computing object in the hierarchy of computing objects. The mapping table may represent an example of the mapping table435, as described with reference toFIG.4. At435, the DMS may select, from among all of the computing objects of the DMS610based on accessing the mapping table, one or more object IDs for a third set of one or more computing objects to which the one or more other tenants have access within the hierarchy of computing objects. For example, the DMS610may scan the mapping table to identify rows that include the tenant IDs of the one or more other tenants. Each row of the mapping table may be indexed by a respective object ID, and the DMS610may select the object IDs of each row that includes the tenant IDs of the one or more other tenants. That is, mapping information for the third set of one or more computing objects in the mapping table may include the tenant IDs of the one or more other tenants.

At640, as part of filtering the database of report data for the one or more other tenants, the DMS610may identify second report data that is stored within the database of report data generated by the DMS610based on the selected object IDs of the third set of one or more computing objects. For example, the report data in the database at the DMS610may be stored with respective object IDs. The DMS610may scan the report data database to identify report data that includes the object IDs associated with the third set of one or more computing objects. The identified report data may include all of the report data associated with the one or more other tenants. Thus, the DMS610may filter out the report data associated with the one or more other tenants from among the database of report data in response to the request. The DMS610may similarly filter out report data for any other tenant or combination of one or more tenants of the DMS610.

At645, after filtering the report data for the one or more other tenants from among the database of report data at the DMS610, the DMS may output (e.g., transmit, send), to the user605and in response to the request, the report data associated with the one or more other tenants based on the filtering. In some examples, the DMS610may display the report data for the one or more other tenants as a list or set via a user interface. In some examples, before outputting the report data, the DMS610may determine whether the user605is authorized to access the requested report data based on an ID of the first tenant615to which the user605is logged in, as described in further detail elsewhere herein, including with reference toFIG.5.

By storing object IDs with corresponding report data, the DMS610may thereby support filtering report data per tenant as described herein. The described techniques may improve security, reliability, and customer satisfaction with the multi-tenancy DMS610.

FIG.7illustrates a block diagram700of a system705that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The system705may be an example of aspects of a DMS as described herein. The system705may include an input interface710, an output interface715, and a report data access component720. The system705may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The input interface710may manage input signaling for the system705. For example, the input interface710may receive input signaling (e.g., messages, packets, data, instructions, commands, or any other form of encoded information) from other systems or devices. The input interface710may send signaling corresponding to (e.g., representative of or otherwise based on) such input signaling to other components of the system705for processing. For example, the input interface710may transmit such corresponding signaling to the report data access component720to support access authorization for report data in a multi-tenancy DMS. In some cases, the input interface710may be a component of a network interface1025as described with reference toFIG.10.

The output interface715may manage output signaling for the system705. For example, the output interface715may receive signaling from other components of the system705, such as the report data access component720, and may transmit such output signaling corresponding to (e.g., representative of or otherwise based on) such signaling to other systems or devices. In some cases, the output interface715may be a component of a network interface1025as described with reference toFIG.10.

The report data access component720, the input interface710, the output interface715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of access authorization for report data in a multi-tenancy DMS as described herein. For example, the report data access component720, the input interface710, the output interface715, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

Additionally, or alternatively, in some examples, the report data access component720, the input interface710, the output interface715, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the report data access component720, the input interface710, the output interface715, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the report data access component720may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input interface710, the output interface715, or both. For example, the report data access component720may receive information from the input interface710, send information to the output interface715, or be integrated in combination with the input interface710, the output interface715, or both to receive information, transmit information, or perform various other operations as described herein.

For example, the report data access component720may be configured as or otherwise support a means for receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The report data access component720may be configured as or otherwise support a means for identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The report data access component720may be configured as or otherwise support a means for applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The report data access component720may be configured as or otherwise support a means for outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

By including or configuring the report data access component720in accordance with examples as described herein, the system705(e.g., a processor controlling or otherwise coupled with the input interface710, the output interface715, the report data access component720, or a combination thereof) may support techniques for improved data management reliability, improved DMS performance and compliance for applications and systems that use objects managed by the system705, reduced power consumption, reduced processing complexity.

FIG.8illustrates a block diagram800of a system805that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. In some examples, the system805may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110. The system805may be an example of aspects of a system705or a DMS110as described herein. The system805may include an input interface810, an output interface815, and a report data access component820. The system805may also include one or more processors. Each of these components may be in communication with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The input interface810may manage input signaling for the system805. For example, the input interface810may receive input signaling (e.g., messages, packets, data, instructions, commands, or any other form of encoded information) from other systems or devices. The input interface810may send signaling corresponding to (e.g., representative of or otherwise based on) such input signaling to other components of the system805for processing. For example, the input interface810may transmit such corresponding signaling to the report data access component820to support access authorization for report data in a multi-tenancy DMS. In some cases, the input interface810may be a component of a network interface1025as described with reference toFIG.10.

The output interface815may manage output signaling for the system805. For example, the output interface815may receive signaling from other components of the system805, such as the report data access component820, and may transmit such output signaling corresponding to (e.g., representative of or otherwise based on) such signaling to other systems or devices. In some cases, the output interface815may be a component of a network interface1025as described with reference toFIG.10.

The system805, or various components thereof, may be an example of means for performing various aspects of access authorization for report data in a multi-tenancy DMS as described herein. For example, the report data access component820may include a report data request component825, a context information component830, an access authorization component835, a report data component840, or any combination thereof. The report data access component820may be an example of aspects of a report data access component720as described herein. In some examples, the report data access component820, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input interface810, the output interface815, or both. For example, the report data access component820may receive information from the input interface810, send information to the output interface815, or be integrated in combination with the input interface810, the output interface815, or both to receive information, transmit information, or perform various other operations as described herein.

The report data request component825may be configured as or otherwise support a means for receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The context information component830may be configured as or otherwise support a means for identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The access authorization component835may be configured as or otherwise support a means for applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The report data component840may be configured as or otherwise support a means for outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

FIG.9illustrates a block diagram900of a report data access component920that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The report data access component920may be an example of aspects of a report data access component720, a report data access component820, or both, as described herein. The report data access component920, or various components thereof, may be an example of means for performing various aspects of access authorization for report data in a multi-tenancy DMS as described herein. For example, the report data access component920may include a report data request component925, a context information component930, an access authorization component935, a report data component940, an object ID component945, a hierarchy component950, a report data storage component955, a report data filtering component960, a mapping component965, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The report data request component925may be configured as or otherwise support a means for receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The context information component930may be configured as or otherwise support a means for identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The access authorization component935may be configured as or otherwise support a means for applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The report data component940may be configured as or otherwise support a means for outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

In some examples, the object ID component945may be configured as or otherwise support a means for identifying, in response to the request, one or more first object IDs for the first set of one or more computing objects, the one or more first object IDs included in the requested report data. In some examples, the hierarchy component950) may be configured as or otherwise support a means for accessing, based on the tenant ID of the tenant associated with the request, a database including hierarchical information associated with the hierarchy of computing objects. In some examples, the object ID component945may be configured as or otherwise support a means for identifying, based on the hierarchical information, one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. In some examples, to apply the filter, the access authorization component935may be configured as or otherwise support a means for determining whether the one or more first object IDs included in the requested report data match the one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects.

In some examples, the hierarchical information includes a set of multiple rows of information. In some examples, a row of the set of multiple rows includes the tenant ID of the tenant associated with the request and further includes the one or more second object IDs for the second set of one or more computing objects to which the tenant has access within the hierarchy of computing objects.

In some examples, the report data component940may be configured as or otherwise support a means for generating the report data for the first set of one or more computing objects. In some examples, the report data storage component955may be configured as or otherwise support a means for storing, at the DMS based on the generating, the report data for the first set of one or more computing objects and one or more object IDs for the first set of one or more computing objects, where applying the filter is based on the one or more stored object IDs for the first set of one or more computing objects.

In some examples, to support storing the one or more object IDs for the first set of one or more computing objects, the report data storage component955may be configured as or otherwise support a means for storing a first object ID for a first computing object of the first set of one or more computing objects in a first field of the report data, where the first field is included in a first row that includes report data associated with the first computing object. In some examples, to support storing the one or more object IDs for the first set of one or more computing objects, the report data storage component955may be configured as or otherwise support a means for storing a second object ID for a second computing object of the first set of one or more computing objects in a second field of the report data, where the second field is included in a second row that includes report data associated with the second computing object.

In some examples, the report data request component925may be configured as or otherwise support a means for receiving a second request to view second report data associated with one or more other tenants of the set of multiple tenants of the DMS, where the second request is associated with the log-in session and the tenant, and where the one or more other tenants are one or more subtenants of the tenant within a tenant hierarchy associated with the set of multiple tenants. In some examples, the report data filtering component960may be configured as or otherwise support a means for filtering, per tenant and in response to the second request, a database of report data stored by the DMS. In some examples, the report data filtering component960may be configured as or otherwise support a means for outputting, to a user of the tenant via a user interface and in response to the second request, the second report data associated with the one or more other tenants based on the filtering and the one or more other tenants being one or more subtenants of the tenant within the tenant hierarchy.

In some examples, the mapping component965may be configured as or otherwise support a means for accessing, based on the second request, a mapping table that includes mapping information for a set of multiple computing objects of the DMS, where the mapping information for a computing object of the set of multiple computing objects indicates at least one tenant that has access to the computing object within the hierarchy of computing objects. In some examples, the object ID component945may be configured as or otherwise support a means for selecting, from among the set of multiple computing objects of the DMS based on accessing the mapping table, one or more object IDs for a third set of one or more computing objects to which the one or more other tenants have access within the hierarchy of computing objects, where selecting the one or more object IDs for the third set of one or more computing objects is based on mapping information for the third set of one of more computing objects in the mapping table including one or more tenant IDs for the one or more other tenants. In some examples, the report data component940may be configured as or otherwise support a means for identifying, after selecting the one or more object IDs of the third set of one or more computing objects, the second report data from among the database of report data based on the second report data including the one or more object IDs for the third set of one or more computing objects, where filtering the database of report data for the second tenant is based on the identifying.

In some examples, the hierarchy component950may be configured as or otherwise support a means for identifying the third set of one or more computing objects to which the one or more other tenants have access within the hierarchy of computing objects. In some examples, the mapping component965may be configured as or otherwise support a means for storing the one or more tenant IDs of the one or more other tenants in a set of one or more rows of the mapping table, the set of one or more rows indexed by the one or more object IDs for the third set of one or more computing objects.

In some examples, the access authorization component935may be configured as or otherwise support a means for refraining from outputting second report data for a second computing object of the first set of one or more computing objects based on the second computing object being absent from the second set of one or more computing objects.

In some examples, the report data for the first set of one or more computing objects includes a compliance status, a size, a status of one or more tasks, or any combination thereof associated with at the least one computing object of the first set of one or more computing objects.

FIG.10illustrates a block diagram1000of a system1005that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The system1005may be an example of or include the components of a system705, a system805, or a DMS as described herein. The system1005may include components for data management, including components such as a report data access component1020, an input information1010, an output information1015, a network interface1025, a memory1030, a processor1035, and a storage1040. These components may be in electronic communication or otherwise coupled with each other (e.g., operatively, communicatively, functionally, electronically, electrically: via one or more buses, communications links, communications interfaces, or any combination thereof). Additionally, the components of the system1005may include corresponding physical components or may be implemented as corresponding virtual components (e.g., components of one or more virtual machines). In some examples, the system1005may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110.

The network interface1025may enable the system1005to exchange information (e.g., input information1010, output information1015, or both) with other systems or devices (not shown). For example, the network interface1025may enable the system1005to connect to a network (e.g., a network120as described herein). The network interface1025may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. In some examples, the network interface1025may be an example of may be an example of aspects of one or more components described with reference toFIG.1, such as one or more network interfaces165.

Memory1030may include RAM, ROM, or both. The memory1030may store computer-readable, computer-executable software including instructions that, when executed, cause the processor1035to perform various functions described herein. In some cases, the memory1030may contain, among other things, a basic input/output system (BIOS), which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some cases, the memory1030may be an example of aspects of one or more components described with reference toFIG.1, such as one or more memories175.

The processor1035may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, a field programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). The processor1035may be configured to execute computer-readable instructions stored in a memory1030to perform various functions (e.g., functions or tasks supporting access authorization for report data in a multi-tenancy DMS). Though a single processor1035is depicted in the example ofFIG.10, it is to be understood that the system1005may include any quantity of one or more of processors1035and that a group of processors1035may collectively perform one or more functions ascribed herein to a processor, such as the processor1035. In some cases, the processor1035may be an example of aspects of one or more components described with reference toFIG.1, such as one or more processors170.

Storage1040may be configured to store data that is generated, processed, stored, or otherwise used by the system1005. In some cases, the storage1040may include one or more HDDs, one or more SDDs, or both. In some examples, the storage1040may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database. In some examples, the storage1040may be an example of one or more components described with reference toFIG.1, such as one or more network disks180.

For example, the report data access component1020may be configured as or otherwise support a means for receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The report data access component1020may be configured as or otherwise support a means for identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The report data access component1020may be configured as or otherwise support a means for applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The report data access component1020may be configured as or otherwise support a means for outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

By including or configuring the report data access component1020in accordance with examples as described herein, the system1005may support techniques for access authorization for report data in a multi-tenancy DMS, which may provide one or more benefits such as, for example, improved data management, compliance, efficiency, and security, among other possibilities.

FIG.11illustrates a flowchart showing a method1100that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The operations of the method1100may be implemented by a DMS or its components as described herein. For example, the operations of the method1100may be performed by a DMS as described with reference toFIGS.1through10. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1105, the method may include receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The operations of1105may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1105may be performed by a report data request component925as described with reference toFIG.9.

At1110, the method may include identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The operations of1110may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1110may be performed by a context information component930as described with reference toFIG.9.

At1115, the method may include applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The operations of1115may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1115may be performed by an access authorization component935as described with reference toFIG.9.

At1120, the method may include outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects. The operations of1120may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1120may be performed by a report data component940as described with reference toFIG.9.

FIG.12illustrates a flowchart showing a method1200that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The operations of the method1200may be implemented by a DMS or its components as described herein. For example, the operations of the method1200may be performed by a DMS as described with reference toFIGS.1through10. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1205, the method may include receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The operations of1205may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1205may be performed by a report data request component925as described with reference toFIG.9.

At1210, the method may include identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The operations of1210may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1210may be performed by a context information component930as described with reference toFIG.9.

At1215, the method may include identifying, in response to the request, one or more first object IDs for the first set of one or more computing objects, the one or more first object IDs included in the requested report data. The operations of1215may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1215may be performed by an object ID component945as described with reference toFIG.9.

At1220, the method may include accessing, based on the tenant ID of the tenant associated with the request, a database including hierarchical information associated with the hierarchy of computing objects. The operations of1220may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1220may be performed by a hierarchy component950as described with reference toFIG.9.

At1225, the method may include identifying, based on the hierarchical information, one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The operations of1225may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1225may be performed by an object ID component945as described with reference toFIG.9.

At1230, the method may include applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. In some examples, at1235, applying the filter may include determining whether the one or more first object IDs included in the requested report data match the one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The operations of1230and1235may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1230and1335may be performed by an access authorization component935as described with reference toFIG.9.

At1240, the method may include outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects. The operations of1240may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1240may be performed by a report data component940as described with reference toFIG.9.

FIG.13illustrates a flowchart showing a method1300that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The operations of the method1300may be implemented by a DMS or its components as described herein. For example, the operations of the method1300may be performed by a DMS as described with reference toFIGS.1through10. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1305, the method may include generating report data for a first set of one or more computing objects of the DMS. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by a report data component940as described with reference toFIG.9.

At1310, the method may include storing, at the DMS based on the generating, the report data for the first set of one or more computing objects and one or more object IDs for the first set of one or more computing objects. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by a report data storage component955as described with reference toFIG.9.

At1315, the method may include receiving, by the DMS, a request for the report data associated with the first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a report data request component925as described with reference toFIG.9.

At1320, the method may include identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The operations of1320may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1320may be performed by a context information component930as described with reference toFIG.9.

At1325, the method may include applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects, and where applying the filter is based on the one or more stored object IDs for the first set of one or more computing objects. The operations of1325may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1325may be performed by an access authorization component935as described with reference toFIG.9.

At1330, the method may include outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects. The operations of1330may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1330may be performed by a report data component940as described with reference toFIG.9.

FIG.14illustrates a flowchart showing a method1400that supports access authorization for report data in a multi-tenancy DMS in accordance with aspects of the present disclosure. The operations of the method1400may be implemented by a DMS or its components as described herein. For example, the operations of the method1400may be performed by a DMS as described with reference toFIGS.1through10. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1405, the method may include receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by a report data request component925as described with reference toFIG.9.

At1410, the method may include identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a context information component930as described with reference toFIG.9.

At1415, the method may include applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by an access authorization component935as described with reference toFIG.9.

At1420, the method may include outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects. The operations of1420may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1420may be performed by a report data component940as described with reference toFIG.9.

At1425, the method may include receiving a second request to view second report data associated with one or more other tenants of the set of multiple tenants of the DMS, where the second request is associated with the log-in session and the tenant, and where the one or more other tenants are one or more subtenants of the tenant within a tenant hierarchy associated with the set of multiple tenants. The operations of1425may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1425may be performed by a report data request component925as described with reference toFIG.9.

At1430, the method may include filtering, per tenant and in response to the second request, a database of report data stored by the DMS. The operations of1430may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1430may be performed by a report data filtering component960as described with reference toFIG.9.

At1435, the method may include outputting, to a user of the tenant via a user interface and in response to the second request, the second report data associated with the one or more other tenants based on the filtering and the one or more other tenants being one or more subtenant of the tenant within the tenant hierarchy. The operations of1435may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1435may be performed by a report data filtering component960as described with reference toFIG.9.

A method is described. The method may include receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects, identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants, applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects, and outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects, identify context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants, apply a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects, and output, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

Another apparatus is described. The apparatus may include means for receiving, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects, means for identifying context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants, means for applying a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects, and means for outputting, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to receive, by a DMS, a request for report data associated with a first set of one or more computing objects of the DMS, where the DMS is operable to provide protection for data sources associated with a set of multiple tenants of the DMS, and where computing objects of the DMS are organized as a hierarchy of computing objects, identify context information for a log-in session associated with the request to access the report data, where the context information for the log-in session includes a tenant ID for a tenant associated with the request, the tenant included in the set of multiple tenants, apply a filter to the first set of one or more computing objects associated with the requested report data, where the filter is based on a second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects, and output, in response to applying the filter, the report data for at least one computing object of the first set of one or more computing objects based on the at least one computing object being included in the second set of one or more computing objects.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, in response to the request, one or more first object IDs for the first set of one or more computing objects, the one or more first object IDs included in the requested report data, accessing, based on the tenant ID of the tenant associated with the request, a database including hierarchical information associated with the hierarchy of computing objects, and identifying, based on the hierarchical information, one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request may have access within the hierarchy of computing objects. In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, applying the filter includes determining whether the one or more first object IDs included in the requested report data match the one or more second object IDs for the second set of one or more computing objects to which the tenant associated with the request has access within the hierarchy of computing objects.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the hierarchical information includes a set of multiple rows of information and a row of the set of multiple rows includes the tenant ID of the tenant associated with the request and further includes the one or more second object IDs for the second set of one or more computing objects to which the tenant may have access within the hierarchy of computing objects.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for generating the report data for the first set of one or more computing objects and storing, at the DMS based on the generating, the report data for the first set of one or more computing objects and one or more object IDs for the first set of one or more computing objects, where applying the filter may be based on the one or more stored object IDs for the first set of one or more computing objects.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, storing the one or more object IDs for the first set of one or more computing objects may include operations, features, means, or instructions for storing a first object ID for a first computing object of the first set of one or more computing objects in a first field of the report data, where the first field may be included in a first row that includes report data associated with the first computing object and storing a second object ID for a second computing object of the first set of one or more computing objects in a second field of the report data, where the second field may be included in a second row that includes report data associated with the second computing object.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second request to view second report data associated with one or more other tenants of the set of multiple tenants of the DMS, where the second request may be associated with the log-in session and the tenant, and where the one or more other tenants may be one or more subtenants of the tenant within a tenant hierarchy associated with the set of multiple tenants, filtering, per tenant and in response to the second request, a database of report data stored by the DMS, and outputting, to a user of the tenant via a user interface and in response to the second request, the second report data associated with the one or more other tenants based on the filtering and the one or more other tenants being one or more subtenants of the tenant within the tenant hierarchy.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, accessing, based on the second request, a mapping table that includes mapping information for a set of multiple computing objects of the DMS, where the mapping information for a computing object of the set of multiple computing objects indicates at least one tenant that may have access to the computing object within the hierarchy of computing objects, selecting, from among the set of multiple computing objects of the DMS based on accessing the mapping table, one or more object IDs for a third set of one or more computing objects to which the one or more other tenants may have access within the hierarchy of computing objects, where selecting the one or more object IDs for the third set of one or more computing objects may be based on mapping information for the third set of one of more computing objects in the mapping table including one or more tenant IDs for the one or more other tenants, and identifying, after selecting the one or more object IDs of the third set of one or more computing objects, the second report data from among the database of report data based on the second report data including the one or more object IDs for the third set of one or more computing objects, where filtering the database of report data for the one or more other tenants may be based on the identifying.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying the third set of one or more computing objects to which the one or more other tenants may have access within the hierarchy of computing objects and storing the one or more tenant IDs of the one or more other tenants in a set of one or more rows of the mapping table, the set of one or more rows indexed by the one or more object IDs for the third set of one or more computing objects.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for refraining from outputting second report data for a second computing object of the first set of one or more computing objects based on the second computing object being absent from the second set of one or more computing objects.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the report data for the first set of one or more computing objects includes a compliance status, a size, a status of one or more tasks, or any combination thereof associated with at the least one computing object of the first set of one or more computing objects.