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
If you are using a LoadBalancer type, you'll want to copy the external IP address and port number. If you are using NodePort, you'll want to use the IP address of your Kubernetes API server and the port number listed under the PORT(S) column.
47
-
48
-
Now, you'll want to construct a URL to your endpoint by combining this information like so:
49
-
50
-
```console
51
-
https://<ip address>:<port>
52
-
53
-
Example:
54
-
https://52.154.152.24:30080
55
-
```
56
-
57
-
Take note of your IP address as you will use it in the next step.
58
27
59
28
### Connect
60
29
61
30
1. Open Azure Data Studio
31
+
2. Select the **Connections** tab on the left
32
+
3. Expand the panel called **Azure Arc Controllers**
33
+
4. Click the **Connect Controller** button. This will open a blade on the right side
34
+
5. By default, Azure Data Studio will try to read from the kube.config file in your default directory and list the available kubernetes cluster contexts and pre-select the current cluster context. If this is the right cluster to connect to, enter the namespace where the Azure Arc data controller is deployed in the input for **Namespace**. If you need to retrieve the namespace where the Azure Arc data controller is deployed, you can run ```kubectl get datacontrollers -A``` on your kubernetes cluster.
35
+
6. Optionally add a display name for the Azure Arc data controller in the input for **Name**
36
+
7. Select **Connect**
62
37
63
-
1. Select the **Connections** tab on the left
64
-
65
-
Towards the bottom, expand the panel called **Azure Arc Controllers**.
66
-
67
-
Click the + icon to add a new data controller connection.
68
-
69
-
At the top of the screen in the command palette, enter the URL you constructed in Step 1, click enter.
70
-
Enter the username for the data controller. This was the username value that you passed during the deployment of the data controller. Click enter.
71
-
Enter the password for the data controller. This was the password value that you passed during the deployment of the data controller. Click enter.
72
38
73
39
Now that you are connected to a data controller, you can view the dashboards for the data controller and any SQL managed instances or PostgreSQL Hyperscale server group resources that you have.
When you back up or restore your Azure Arc-enabled PostgreSQL Hyperscale server group, the entire set of databases on all the PostgreSQL nodes of your server group is backed-up and/or restored.
24
-
25
-
## Take a manual full backup
26
-
27
-
To take a full backup of the entire data and log folders of your server group, run the following command:
-__no-wait__ indicates that the command line will not wait for the backup to complete for you to be able to continue to use this command-line window
35
-
36
-
This command will coordinate a distributed full backup across all the nodes that constitute your Azure Arc-enabled PostgreSQL Hyperscale server group. In other words, it will backup all data in your Coordinator and Worker nodes.
The Timestamp column indicates the point in time UTC at which the backup was taken.
88
-
89
-
## Restore a backup
90
-
In this section we are showing you how to do a full restore or a point in time restore. When you restore a full backup, you restore the entire content of the backup. When you do a point in time restore, you restore up to the point in time you indicate. Any transaction that was done later than this point in time is not restored.
91
-
92
-
> [!CAUTION]
93
-
> You can only restore to a server group that has the same number of worker nodes that it had when the backup was taken. If you increased or reduced the number of worker nodes since the backup was taken, before you restore, you need to increase/reduce the number of worker nodes - or create a new server group - to match the content of the backup. The restore will fail when the number of worker nodes do not match.
94
-
95
-
### Restore a full backup
96
-
To restore the entire content of a backup run the command:
97
-
```console
98
-
azdata arc postgres backup restore --server-name <target server group name> [--source-server-name <source server group name> --backup-id <backup id>]
99
-
or
100
-
azdata arc postgres backup restore -sn <target server group name> [-ssn <source server group name> --backup-id <backup id>]
101
-
```
102
-
<!--To read the general format of restore command, run: azdata arc postgres backup restore --help -->
103
-
104
-
Where:
105
-
-__backup-id__ is the ID of the backup shown in the list backup command shown above.
106
-
This will coordinate a distributed full restore across all the nodes that constitute your Azure Arc-enabled PostgreSQL Hyperscale server group. In other words, it will restore all data in your Coordinator and Worker nodes.
107
-
108
-
#### Examples:
109
-
110
-
__Restore the server group postgres01 onto itself:__
This operation is supported for any version of PostgreSQL starting version 11. The target server group must be created before the restore operation, must be of the same configuration and must be using the same backup PVC as the source server group.
124
-
125
-
When the restore operation is complete, it will return an output like this to the command line:
126
-
127
-
```json
128
-
{
129
-
"ID": "d134f51aa87f4044b5fb07cf95cf797f",
130
-
"state": "Done"
131
-
}
132
-
```
133
-
134
-
> [!NOTE]
135
-
> It is not yet possible to:
136
-
> - Restore a backup by indicating its name
137
-
> - Show the progress of a restore operation
138
-
139
-
140
-
### Do a point in time restore
141
-
142
-
To restore a server group up to a specific point time, run the command:
143
-
```console
144
-
azdata arc postgres backup restore --server-name <target server group name> --source-server-name <source server group name> --time <point in time to restore to>
145
-
or
146
-
azdata arc postgres backup restore -sn <target server group name> -ssn <source server group name> -t <point in time to restore to>
147
-
```
148
-
149
-
To read the general format of restore command, run: `azdata arc postgres backup restore --help`.
150
-
151
-
Where `time` is the point in time to restore to. Provide either a timestamp or a number and suffix (`m` for minutes, `h` for hours, `d` for days, or `w` for weeks). For example `1.5h` goes back 90 minutes.
152
-
153
-
#### Examples:
154
-
__Do a point in time restore of the server group postgres01 onto itself:__
155
-
156
-
It is not yet possible to do point in time restore of a server group onto itself.
157
-
158
-
__Do a point in time restore of the server group postgres01 to a different server group postgres02 to a specific timestamp:__
This example restores into server group postgres02 the state at which server group postgres01 was on December 8th 2020 at 04:23:48.75 UTC. Note that "+00" indicates the timezone of the point in time you indicate. If you do not indicate a timezone, the timezone of the client from which you run the restore operation will be used.
164
-
165
-
For example:
166
-
-`2020-12-08 04:23:48.751326+00` is interpreted as `2020-12-08 04:23:48.751326` UTC
167
-
- if you are in the Pacific Standard Time zone (PST = UTC+08), `2020-12-08 04:23:48.751326` is interpreted as `2020-12-08 12:23:48.751326` UTC
168
-
This operation is supported for any version of PostgreSQL starting version 11. The target server group must be created before the restore operation and must be using the same backup PVC as the source server group.
169
-
170
-
171
-
__Do a point in time restore of the server group postgres01 to a different server group postgres02 to a specific amount of time in the past:__
This example restores into server group postgres02 the state at which server group postgres01 was 22 minutes ago.
177
-
This operation is supported for any version of PostgreSQL starting version 11. The target server group must be created before the restore operation and must be using the same backup PVC as the source server group.
178
-
179
-
> [!NOTE]
180
-
> It is not yet possible to:
181
-
> - Show the progress of a restore operation
182
-
183
-
## Delete backups
184
-
185
-
Backup retention cannot be set in Preview. However you can manually delete backups that you do not need.
You can retrieve the name and the ID of your backups by running the list backup command as explained in the previous paragraph.
212
-
213
-
For more details about the delete command, run:
214
-
215
-
```console
216
-
azdata arc postgres backup delete --help
217
-
```
218
-
219
-
## Next steps
220
18
- Read about [scaling out (adding worker nodes)](scale-out-in-postgresql-hyperscale-server-group.md) your server group
221
19
- Read about [scaling up or down (increasing/decreasing memory/vcores)](scale-up-down-postgresql-hyperscale-server-group-using-cli.md) your server group
Copy file name to clipboardExpand all lines: articles/azure-arc/data/change-postgresql-port.md
+26-23Lines changed: 26 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,57 +7,60 @@ ms.subservice: azure-arc-data
7
7
author: TheJY
8
8
ms.author: jeanyd
9
9
ms.reviewer: mikeray
10
-
ms.date: 07/30/2021
10
+
ms.date: 11/03/2021
11
11
ms.topic: how-to
12
12
---
13
13
14
14
15
15
# Change the port on which the server group is listening
16
16
17
-
Changing the port is a standard edit operation of the server group. In order to change the port, run the following command:
17
+
To change the port, edit the server group. For example, run the following command:
18
+
18
19
```azurecli
19
20
az postgres arc-server edit -n <server group name> --port <desired port number> --k8s-namespace <namespace> --use-k8s
20
21
```
21
22
22
-
For example, let's assume the name of your server group is _postgres01_ and you would like it to listen on port _866_. You would run the following command:
23
+
If the name of your server group is _postgres01_ and you would like it to listen on port _866_. Run the following command:
To verify that the port was changed, run the following command to show the configuration of your server group:
32
+
30
33
```azurecli
31
34
az postgres arc-server show -n <server group name> --k8s-namespace <namespace> --use-k8s
32
35
```
33
36
34
37
In the output of that command, look at the port number displayed for the item "port" in the "service" section of the specifications of your server group.
35
-
Alternatively, you can verify in the item externalEndpoint of the status section of the specifications of your server group that the IP address is followed by the port number you configured.
36
38
37
-
As an illustration, if we continue the example above, you would run the command:
39
+
Alternatively, you can verify in the item `externalEndpoint` of the status section of the specifications of your server group that the IP address is followed by the port number you configured.
40
+
41
+
As an illustration, to continue the example above, run the command:
42
+
38
43
```azurecli
39
-
az postgres arc-server show -n postgres01 --k8s-namespace <namespace> --use-k8s
44
+
az postgres arc-server show -n postgres01 --k8s-namespace arc --use-k8s
0 commit comments