You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: product_docs/docs/bart/2.6/bart_inst/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,8 @@ This guide provides information about how to install and configure the EDB Backu
22
22
- To view a complete list of supported platforms, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility).
23
23
24
24
25
-
!!! Note
26
-
BART 2.6 is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform.
25
+
!!! Note
26
+
BART is not supported by EDB Postgres Advanced Server or PostgreSQL version 14 and later. EDB strongly recommends you move to Barman or pgBackRest as your backup recovery tool. See [Moving to a New Backup Tool](../bart_migration) for more information.
Copy file name to clipboardExpand all lines: product_docs/docs/biganimal/release/administering_cluster/01_portal_access.mdx
+33-33Lines changed: 33 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -4,35 +4,36 @@ redirects:
4
4
- 01_user_access
5
5
---
6
6
7
-
BigAnimal uses Azure Active Directory (AD) to authenticate users and rolebased access controls to grant users access to different parts of the application.
7
+
BigAnimal uses Azure Active Directory (AD) to authenticate users and role-based access controls to grant users access to different parts of the application.
8
8
9
9
## Organizations
10
10
11
-
Each subscribed customer has a unique *organization*. Each organization’s database clusters are deployed and managed in the customer's cloud account. This ensures complete segregation of customer data between organizations.
11
+
Each subscribed customer has a unique *organization*. Each organization’s database clusters are deployed and managed in the customer's cloud account. This approach ensures complete segregation of customer data between organizations.
12
12
13
-
Each BigAnimal organization is associated with an Azure AD tenant. Azure AD establishes the identity of users that belong to an organization. After Azure AD is linked during subscription, users that belong to that AD can login with minimum access privileges.
13
+
Each BigAnimal organization is associated with an Azure AD tenant. Azure AD establishes the identity of users that belong to an organization. After Azure AD is linked during subscription, users that belong to that AD can log in with minimum access privileges.
14
14
15
-
BigAnimal supports rolebased access control policies. A user with the owner role may assign roles to other users in the same organization.
15
+
BigAnimal supports role-based access control policies. A user with the owner role can assign roles to other users in the same organization.
16
16
17
17
## Roles
18
18
Access to BigAnimal is controlled by roles. Roles are sets of permissions. You use roles to manage permissions assigned to users.
19
19
20
-
*Each organization will have three default roles available:
20
+
Each organization has three default roles available:
21
21
* owner
22
22
* reader
23
23
* contributor
24
-
* These roles can be edited by changing their name or description.
24
+
25
+
You can edit these roles by changing their name or description.
25
26
26
27
### Permissions
27
28
28
-
Permissions are generally represented in the format *action*:*object* where *action* represents an operation that can be performed and *object* represents a category of portal functionality.
29
+
Permissions are generally represented in the format *action*:*object* where *action* represents an operation to perform and *object* represents a category of portal functionality.
29
30
30
-
The available *actions* are: create, read, update, delete
31
+
*The available actions are: create, read, update, and delete.
31
32
32
-
The available *objects* are: backups, billing, clusters, events, permissions, roles, users, versions
33
+
*The available objects are: backups, billing, clusters, events, permissions, roles, users, and versions.
33
34
34
35
!!! Note
35
-
Not every object supports all the actions. A typical example is *versions* object is always *read*only.
36
+
Not every object supports all the actions. For example, versions objects are always read-only.
36
37
37
38
### Permissions by role
38
39
@@ -54,63 +55,62 @@ The following are the default permission by role:
54
55
|| delete |||||||||
55
56
56
57
57
-
### Editing roles
58
+
### Edit roles
58
59
59
-
To edit roles:
60
60
1. Navigate to **Admin > Roles**.
61
61
62
62
3. Select the edit icon for the role in the list.
63
63
64
-
#### Changing role name
64
+
#### Change role name
65
65
66
-
To change the name or description of the role:
67
66
1. Select the **Settings** tab.
68
67
69
68
2. Edit **Name** or **Description**.
70
-
3. Press **Save**.
69
+
3. Select **Save**.
70
+
71
+
#### Change role permissions
71
72
72
-
#### Changing role permissions
73
+
You can change permissions associated with the role.
73
74
74
-
To change permissions associated with the role:
75
75
1. Select the **Permissions** tab.
76
76
77
-
2. Select the **Change Permissions**button on the top right.
78
-
3. Select the list of permissions you want to be associated with the role.
79
-
4.Press**Submit**
77
+
2. Select **Change Permissions**in the top right.
78
+
3. Select the list of permissions you want to associate with the role.
79
+
4.Select**Submit**.
80
80
81
81
!!! Note
82
-
Changing role permissions will affect every user who is assigned the same role.
82
+
Changing role permissions affects every user who is assigned that role.
83
83
84
84
## Users
85
85
86
-
When you configured your Azure subscription, you also enabled BigAnimal to authenticate users from your organization using Azure AD. Before users become visible in the BigAnimal **Users** screen they need to sign in using Azure AD after receiving special emails sent by your organization. New users signed in to BigAnimal have a minimum set of permissions until you assign them a role.
86
+
When you configured your Azure subscription, you also enabled BigAnimal to authenticate users from your organization using Azure AD. Before users become visible in the BigAnimal **Users** screen, they need to sign in using Azure AD after receiving special emails from your organization. New users signed in to BigAnimal have a minimum set of permissions until you assign them a role.
87
+
88
+
### Assign roles to users
87
89
88
-
### Assigning roles to users
89
-
To assign appropriate roles to users:
90
90
1. Navigate to **Admin > Users**.
91
91
92
92
2. Select the edit icon for the user.
93
93
3. Select **Assign Roles**.
94
-
4. Select or deselect roles for the user.
94
+
4. Select or clear roles for the user.
95
95
5. Select **Submit**.
96
96
97
97
!!! Note
98
-
For a user's role assignment to take effect, the user needs to log out from BigAnimal and log in again.
98
+
For a user's role assignment to take effect, the user must log out from BigAnimal and log in again.
99
99
100
-
### Viewing users
100
+
### View users
101
101
102
-
To view all users from your organization that have logged in at least once:
102
+
You can view all users from your organization who have logged in at least once.
103
103
104
104
1. Navigate to **Admin > Users**.
105
105
106
-
2. View the list of users sorted by most recent log in.
106
+
2. View the list of users sorted by most recent login.
107
107
108
108
## Example scenario
109
109
110
110
1. The BigAnimal organization is created, and Tom logs in and is granted the owner role.
111
111
112
-
2. Tom asks Jerry to log in, using his Azure AD account; Jerry's account in BigAnimal is created.
113
-
3. Tom grants Sally the contributor role. Sally logs out and back in, and she can now create BigAnimal clusters.
114
-
4. Sally asks Jerry to log in, and grants him the reader role.
115
-
5. Jerry logs out and back in, and he can now see the clusters that Sally has created.
112
+
2. Tom asks Jerry to log in, using his Azure AD account. Jerry's account in BigAnimal is created.
113
+
3. Tom grants Sally the contributor role. Sally logs out and back in. She can now create BigAnimal clusters.
114
+
4. Sally asks Jerry to log in and grants him the reader role.
115
+
5. Jerry logs out and back in. He can now see the clusters that Sally created.
Copy file name to clipboardExpand all lines: product_docs/docs/biganimal/release/administering_cluster/03_account_activity.mdx
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Reviewing account activity"
3
3
---
4
-
The activity log collects BigAnimal events based on user activity within the portal. It can be used to audit activities performed by users from your organizations or research activities that may have affected your account.
4
+
The activity log collects BigAnimal events based on user activity in the portal. You can use the log to audit activities performed by users from your organizations or research activities that might have affected your account.
5
5
6
6
## Events
7
7
@@ -20,17 +20,17 @@ Events are related to the following resource types:
20
20
* organization
21
21
22
22
!!! Note
23
-
Database events are **not** logging activity on the Postgres server. They are logging the use of the portal to create or modify database clusters.
23
+
Database events are not logging activity on the Postgres server. They are logging the use of the portal to create or modify database clusters.
24
24
25
-
## Viewing and searching the activity log
25
+
## View and search the activity log
26
26
27
-
To view events, navigate to the [**Activity Log**](https://portal.biganimal.com/activityLog) page on the [BigAnimal](https://portal.biganimal.com) portal. To search events, use the filters at the top of the page.
27
+
To view events, navigate to the [Activity Log](https://portal.biganimal.com/activityLog) page on the [BigAnimal](https://portal.biganimal.com) portal. To search events, use the filters at the top of the page.
Copy file name to clipboardExpand all lines: product_docs/docs/biganimal/release/administering_cluster/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
title: "Administering your account"
3
3
---
4
4
5
-
In this section, account owners can find information on administrative activities for the BigAnimal account including portal and database user access management as well as account activity reviews.
5
+
Administrative activities for the BigAnimal account include portal and database user access management as well as account activity reviews.
By default, Azure sets a very low limit on the number of virtual machines and cores per region and on the number of Public IP Addresses per region that are available in a given subscription.
6
6
7
-
The default number of total cores per subscription per region is 20. See [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager) for more information. You need to increase the total cores to account for the total number of cores you expect to use in each region and reserve these cores to be used by EDB. See the next section [Virtual Machine Quota Requirements](#virtual-machine-quota-requirements)for more information.
7
+
The default number of total cores per subscription per region is 20. See [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager) for more information. You need to increase the total cores to account for the total number of cores you expect to use in each region and reserve these cores to be used by EDB. See [Virtual Machine Quota Requirements](#virtual-machine-quota-requirements)for more information.
8
8
9
-
The default Public IP address limits for Public IP Addresses Basic and Public IP Addresses Standards is set to 10. See [Public IP address limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#publicip-address) for more information. You need to increase the limit of `Public IP Addresses - Basic` and `Public IP Addresses - Standard`for the regions where you plan to deploy your EDB clusters with the total number of EDB clusters you plan to use.
9
+
The default Public IP address limits for Public IP Addresses Basic and Public IP Addresses Standards is set to 10. See [Public IP address limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#publicip-address) for more information. You need to increase the limit of `Public IP Addresses - Basic` and `Public IP Addresses - Standard` to the total number of clusters you plan to deploy in a particular region.
10
10
11
11
12
12
## Virtual machine quota requirements
13
-
In each region, BigAnimal uses eight Dv4 virtual machine cores to manage your BigAnimal infrastructure. Your Postgres clusters deployed in the region use separate ESv3 virtual machine cores. The number of cores depends on the Instance Type and High Availability options of the clusters you provision. You can calculate the number of ESv3 cores required for your cluster based on the following:
13
+
In each region, BigAnimal uses eight Dv4 virtual machine cores to manage your BigAnimal infrastructure. Your Postgres clusters deployed in the region use separate ESv3 virtual machine cores. The number of cores depends on the **Instance Type** and **High Availability** options of the clusters you provision. You can calculate the number of ESv3 cores required for your cluster based on the following:
14
14
15
15
* Virtual machine instance of type E{N}Sv3 uses {N} cores. For example, an instance of type E64Sv3 uses 64 ESv3 cores.
16
16
* Cluster running on an E{N}Sv3 instance with high availability not enabled uses exactly {N} ESv3 cores.
17
17
* Cluster running on an E{N}Sv3 instance with high availability enabled uses 3 * {N} ESv3 cores.
18
18
19
19
As an example, if you provision the largest virtual machine E64Sv3 with high availability enabled, it requires (3 * 64)=192 ESv3 cores per region. BigAnimal infrastructure requires an additional eight Dv4 virtual machine cores per region.
20
20
21
-
## Checking current utilization
21
+
## Check current utilization
22
22
23
-
To check if you have adequate Azure resources to provision new clusters:
23
+
You can check whether you have adequate Azure resources to provision new clusters.
24
24
25
25
1. In the [Azure portal](https://portal.azure.com/), select **Subscription**.
4. Search for "Total Regional vCPUs" and select the **Location** to check the regional vCPUs limits.
29
-
5. Search for "DSv2" and "ESv3" to view virtual machines limits.
27
+
3.In the **Settings**section, select**Usage + quotas**.
28
+
4. Search for _Total Regional vCPUs_ and select the location to check the regional vCPUs limits.
29
+
5. Search for _DSv2_ and _ESv3_ to view virtual machines limits.
30
30
6. Search for Public IP to view networks limits.
31
31
32
32
33
33
## Increasing network quota
34
34
35
-
You can increase the number of public IP addresses for your account either by using Azure's portal if you have appropriate privileges or by submitting a support request. See:
35
+
You can increase the number of public IP addresses for your account either by using Azure's portal, if you have appropriate privileges, or by submitting a support request. See:
36
36
37
37
-[Request Networking quota increase at subscription level using Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-help--support)
38
38
@@ -41,11 +41,11 @@ You can increase the number of public IP addresses for your account either by us
41
41
42
42
## Increasing virtual machine quota
43
43
44
-
You can increase the number of ESv3 Series virtual machines per region for your account either by using Azure's portal if you have appropriate privileges or by submitting a support request. See:
44
+
You can increase the number of ESv3 Series virtual machines per region for your account either by using Azure's portal, if you have appropriate privileges, or by submitting a support request. See:
45
45
46
-
-[Request a quota increase by region from Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#request-a-quota-increase-by-region-from-help--support)
46
+
-[Request a quota increase by region from Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#increase-a-regional-quota-from-help--support)
47
47
48
-
-[Request a quota increase by region from subscriptions](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#request-a-quota-increase-by-region-from-subscriptions)
48
+
-[Request a quota increase by region from subscriptions](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#increase-a-regional-vcpu-quota)
0 commit comments