A Namespace is a logical group of resources that consists of datastores, networks (application network), and external storage (local and cloud storage) created by a Provider Administrator in VMware Data Services Manager. It is a logical grouping or subset of the resources in an environment that can be used for provisioning a database.
As a Provider Administrator, you can see the following columns:
Column Name | Description |
---|---|
Namespace Name | The name of the Namespace. |
Environment | The environment with which the Namespace is associated. |
Status | The status or current state of the Namespace. Status can be Init, Online, or Warning. |
Associated Organizations | The number of organizations associated with the Namespace. |
Number of Databases | The number of databases created by using the Namespace. |
Last Modified | The time and date of last modification of the Namespace. |
If you click a Namespace in the Namespaces view, you can get more information about the Namespace through the following tabs:
Apart from provisioning Replica databases, all other database operations, such as backup, restore, recover, PITR, and so on, use the same Namespace as the database VM on which these operations are performed.
While creating Replica databases in an organization, you can select from the list of Namespaces associated with the organization and vCenter that have the Primary database node. Therefore, Replica databases and the Primary database of a database cluster can be associated with different Namespaces that are associated with different environments. Thus, you can create Zone Redundant Database High Availability Clusters.
If you navigate to Databases in the left navigation pane, you can see the Namespace associated with a particular database in the Namespace column of the Databases view.
If you navigate to Namespaces in the left navigation pane, you can see the number of databases created using a particular Namespace in the Number of Databases column of the Namespaces view.
If the Namespace with which a database is created is not shared with the Provider organization, only the following operations can be performed on the database by the Provider Administrator: