Merge pull request #227006 from hasani-h/release-arc-data-feb2023-postgres

Release arc data feb2023 postgres

Author: JamesJBarnett

articles/azure-arc/data/backup-restore-postgresql.md

@@ -13,6 +13,35 @@ ms.topic: how-to
 
 # Back up and restore Azure Arc-enabled PostgreSQL servers
 
-Automated backups can be enabled by including the `--storage-class-backups` argument when creating an Azure Arc-enabled PostgreSQL server. Restore is not supported in the current preview release.
+Automated backups can be enabled by including the `--storage-class-backups` argument when creating an Azure Arc-enabled PostgreSQL server. Specify the retention period for backups with the `--retention-days` parameter, when creating or updating an Arc-enabled PostgreSQL server. The retention period can be between 0 and 35 days. If backups are enabled but no retention period is specified, the default is seven days.
+
+Restoring an Azure Arc-enable PostgreSQL server creates a new server by copying the configuration of the existing server (for example resource requests/limits, extensions etc.). Configurations that could cause conflicts (for example primary endpoint port) aren't copied. The storage configuration for the new resource can be defined by passing `--storage-class*` and `--volume-size-*` parameters to the `restore` command.
+
+Restore an Azure Arc-enabled PostgreSQL server to a new server with the `restore` command:
+```azurecli
+az postgres server-arc restore -n <destination-server-name> --source-server <source-server-name> --k8s-namespace <namespace> --use-k8s
+```
+
+## Examples:
+
+Create a new Arc-enabled PostgreSQL server `pg02` by restoring `pg01` using the latest backups:
+```azurecli
+az postgres server-arc restore -n pg02 --source-server pg01 --k8s-namespace arc --use-k8s
+```
+
+Create a new Arc-enabled PostgreSQL server `pg02` by restoring `pg01` using the latest backups, defining new storage requirements for pg02:
+```azurecli
+az postgres server-arc restore -n pg02 --source-server pg01 --k8s-namespace arc --storage-class-data azurefile-csi-premium --volume-size-data 10Gi --storage-class-logs azurefile-csi-premium --volume-size-logs 2Gi--use-k8s --storage-class-backups azurefile-csi-premium --volume-size-backups 15Gi
+```
+
+Create a new Arc-enabled PostgreSQL server `pg02` by restoring `pg01` to its state at `2023-02-01T00:00:00Z`:
+```azurecli
+az postgres server-arc restore -n pg02 --source-server pg01 --k8s-namespace arc -t 2023-02-01T00:00:00Z --use-k8s
+```
+
+For details about all the parameters available for restore review the output of the command:
+```azurecli
+az postgres server-arc restore --help
+```
 
 - Read about [scaling up or down (increasing/decreasing memory/vcores)](scale-up-down-postgresql-server-using-cli.md) your server.

articles/azure-arc/data/deploy-active-directory-postgresql-server-cli.md

@@ -0,0 +1,96 @@
+---
+title: Deploy Active Directory integrated Azure Arc-enabled PostgreSQL server using Azure CLI
+description: Explains how to deploy Active Directory integrated Azure Arc-enabled PostgreSQL server using Azure CLI
+services: azure-arc
+ms.service: azure-arc
+ms.subservice: azure-arc-data-postgresql
+author: hasani-h
+ms.author: hasaniholder
+ms.reviewer: mikeray
+ms.date: 02/10/2023
+ms.topic: how-to
+---
+
+# Deploy Active Directory integrated Azure Arc-enabled PostgreSQL using Azure CLI
+
+This article explains how to deploy Azure Arc-enabled PostgreSQL server with Active Directory (AD) authentication using Azure CLI.
+
+See these articles for specific instructions:
+
+- [Tutorial – Deploy AD connector in customer-managed keytab mode](deploy-customer-managed-keytab-active-directory-connector.md)
+
+### Prerequisites
+
+Before you proceed, install the following tools:
+
+- The [Azure CLI (az)](/cli/azure/install-azure-cli)
+- The [`arcdata` extension for Azure CLI](install-arcdata-extension.md)
+
+To know more further details about how to set up OU and AD account, go to [Deploy Azure Arc-enabled data services in Active Directory authentication - prerequisites](active-directory-prerequisites.md)
+
+
+## Deploy and update Active Directory integrated Azure Arc-enabled PostgreSQL server
+
+### Customer-managed keytab mode
+
+#### Create an Azure Arc-enabled PostgreSQL server
+
+To view available options for the create command for Azure Arc-enabled PostgreSQL server, use the following command:
+
+```azurecli
+az postgres server-arc create --help
+```
+
+To create a SQL Managed Instance, use `az postgres server-arc create`. See the following example:
+
+```azurecli
+az postgres server-arc create 
+--name < PostgreSQL server name >  
+--k8s-namespace < namespace > 
+--ad-connector-name < your AD connector name > 
+--keytab-secret < PostgreSQL server keytab secret name >  
+--ad-account-name < PostgreSQL server AD user account >  
+--dns-name < PostgreSQL server primary endpoint DNS name > 
+--port < PostgreSQL server primary endpoint port number >
+--use-k8s
+```
+
+Example:
+
+```azurecli
+az postgres server-arc create 
+--name contosopg 
+--k8s-namespace arc 
+--ad-connector-name adarc 
+--keytab-secret arcuser-keytab-secret
+--ad-account-name arcuser 
+--dns-name arcpg.contoso.local
+--port 31432
+--use-k8s
+```
+
+#### Update an Azure Arc-enabled PostgreSQL server
+
+To update an Arc-enabled PostgreSQL server, use `az postgres server-arc update`. See the following example:
+
+```azurecli
+az postgres server-arc update 
+--name < PostgreSQL server name >  
+--k8s-namespace < namespace > 
+--keytab-secret < PostgreSQL server keytab secret name >  
+--use-k8s
+```
+
+Example:
+
+```azurecli
+az postgres server-arc update 
+--name contosopg 
+--k8s-namespace arc 
+--keytab-secret arcuser-keytab-secret
+--use-k8s
+```
+
+## Next steps
+- **Try it out.** Get started quickly with [Azure Arc Jumpstart](https://github.com/microsoft/azure_arc#azure-arc-enabled-data-services) on Azure Kubernetes Service (AKS), AWS Elastic Kubernetes Service (EKS), Google Cloud Kubernetes Engine (GKE) or in an Azure VM. 
+

articles/azure-arc/data/limitations-postgresql.md

@@ -17,10 +17,6 @@ This article describes limitations of Azure Arc-enabled PostgreSQL.
 
 [!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
 
-## Backup and restore 
-
-Enable automated backups. Include the `--storage-class-backups` argument when you create an Azure Arc-enabled PostgreSQL server. Restore has been temporarily removed as we finalize designs and experiences.
-
 ## High availability
 
 Configuring high availability to recover from infrastructure failures isn't yet available.

articles/azure-arc/data/supported-versions-postgresql.md

@@ -12,26 +12,25 @@ ms.topic: how-to
 ---
 
 # Supported versions of PostgreSQL with Azure Arc-enabled PostgreSQL server
-The list of supported versions evolves over time as we progress on ensuring parity with Postgres managed services in Azure PaaS. Today, the major versions that is supported is PostgreSQL 14.
+The list of supported versions evolves over time as we progress on ensuring parity with PostgreSQL managed services in Azure PaaS. Today, the major version that is supported is PostgreSQL 14.
 
 [!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
 
 ## How to choose between versions?
-It is recommend you look at what versions your applications have been designed for and what are the capabilities of each of the versions. 
+It's recommended you look at what versions your applications have been designed for and what are the capabilities of each of the versions. 
 To learn more, read about each version on the official PostgreSQL site:
 - [PostgreSQL 14 (default)](https://www.postgresql.org/docs/14/index.html)
 
 ## How to create a particular version in Azure Arc-enabled PostgreSQL server?
-At creation time, you have the possibility to indicate what version to create by passing the _--engine-version_ parameter. 
-If you do not indicate a version information, by default, a server group of PostgreSQL version 14 will be created.
+Currently only PostgreSQL version 14 is supported.
 
-Note that there is only one PostgreSQL Custom Resource Definition (CRD) in your Kubernetes cluster no matter what versions we support.
+There's only one PostgreSQL Custom Resource Definition (CRD) in your Kubernetes cluster no matter what versions we support.
 For example, run the following command:
 ```console
 kubectl get crds
 ```
 
-It will return an output like:
+It returns an output like:
 ```console
 NAME                                                             CREATED AT
 dags.sql.arcdata.microsoft.com                                   2021-10-12T23:53:40Z
@@ -44,10 +43,10 @@ sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com   2021-10-12T23:5
 sqlmanagedinstances.sql.arcdata.microsoft.com                    2021-10-12T23:53:37Z
 ```
 
-In this example, this output indicates there are one CRD related to PostgreSQL: postgresqls.arcdata.microsoft.com, shortname postgresqls. The CRD is not a PostgreSQL server. The presence of a CRD is not an indication that you have - or not - created a server. The CRD is an indication of what kind of resources can be created in the Kubernetes cluster.
+In this example, this output indicates there is one CRD related to PostgreSQL: `postgresqls.arcdata.microsoft.com`, shortname `postgresqls`. The CRD isn't a PostgreSQL server. The presence of a CRD isn't an indication that you have - or not - created a server. The CRD is an indication of what kind of resources can be created in the Kubernetes cluster.
 
 ## How can I be notified when other versions are available?
-Come back and read this article. It will be updated as appropriate.
+Come back and read this article. It's updated as appropriate.
 
 
 ## Next steps:

articles/azure-arc/data/toc.yml

@@ -252,6 +252,10 @@ items:
       items:
         - name: Manage
           items:
+            - name: Active Directory
+              items:
+                - name: Deploy PostgresSQL server - CLI
+                  href: deploy-active-directory-postgresql-server-cli.md
             - name: Back up and restore
               href: backup-restore-postgresql.md
             - name: Change PostgreSQL port

articles/azure-arc/data/using-extensions-in-postgresql-server.md

@@ -20,72 +20,95 @@ PostgreSQL is at its best when you use it with extensions.
 
 ## Supported extensions
 For this preview, the following standard [`contrib`](https://www.postgresql.org/docs/14/contrib.html) extensions are already deployed in the containers of your Azure Arc-enabled PostgreSQL server:
-- adminpack
-- amcheck
-- autoinc
-- bloombtree_gin
-- btree_gist
-- citext
-- cube
-- dblink
-- dict_int
-- dict_xsyn
-- earthdistance
-- file_fdw
-- fuzzystrmatch
-- hstore
-- insert_username
-- intagg
-- intarray
-- isn
-- lo
-- ltree
-- moddatetime
-- old_snapshot
-- pageinspect
-- pg_buffercache
-- pg_freespacemap
-- pg_prewarm
-- pg_stat_statements
-- pg_surgery
-- pg_trgm
-- pg_visibility
-- pgcrypto
-- pgrowlocks
-- pgstattuple
-- postgres_fdw
-- refint
-- seg
-- sslinfo
-- tablefunc
-- tcn
-- tsm_system_rows
-- tsm_system_time
-- unaccent
-- xml2
+- `address_standardizer_data_us` 3.3.1
+- `adminpack` 2.1
+- `amcheck` 1.3
+- `autoinc` 1
+- `bloom` 1
+- `btree_gin` 1.3
+- `btree_gist` 1.6
+- `citext` 1.6
+- `cube` 1.5
+- `dblink` 1.2
+- `dict_int` 1
+- `dict_xsyn` 1
+- `earthdistance` 1.1
+- `file_fdw` 1
+- `fuzzystrmatch` 1.1
+- `hstore` 1.8
+- `hypopg` 1.3.1
+- `insert_username` 1
+- `intagg` 1.1
+- `intarray` 1.5
+- `isn` 1.2
+- `lo` 1.1
+- `ltree` 1.2
+- `moddatetime` 1
+- `old_snapshot` 1
+- `orafce` 4
+- `pageinspect` 1.9
+- `pg_buffercache` 1.3
+- `pg_cron` 1.4-1
+- `pg_freespacemap` 1.2
+- `pg_partman` 4.7.1
+- `pg_prewarm` 1.2
+- `pg_repack` 1.4.8
+- `pg_stat_statements` 1.9
+- `pg_surgery` 1
+- `pg_trgm` 1.6
+- `pg_visibility` 1.2
+- `pgaudit` 1.7
+- `pgcrypto` 1.3
+- `pglogical` 2.4.2
+- `pglogical_origin` 1.0.0
+- `pgrouting` 3.4.1
+- `pgrowlocks` 1.2
+- `pgstattuple` 1.5
+- `plpgsql` 1
+- `postgis` 3.3.1
+- `postgis_raster` 3.3.1
+- `postgis_tiger_geocoder` 3.3.1
+- `postgis_topology` 3.3.1
+- `postgres_fdw` 1.1
+- `refint` 1
+- `seg` 1.4
+- `sslinfo` 1.2
+- `tablefunc` 1
+- `tcn` 1
+- `timescaledb` 2.8.1
+- `tsm_system_rows` 1
+- `tsm_system_time` 1
+- `unaccent` 1.1
 
 Updates to this list will be posted as it evolves over time.
 
-> [!IMPORTANT]
-> While you may bring to your server an extension other than those listed above, in this Preview, it will not be persisted to your system. It means that it will not be available after a restart of the system and you would need to bring it again.
+## Create an Arc-enabled PostgreSQL server with extensions enabled
+You can create an Arc-enabled PostgreSQL server with any of the supported extensions enabled by passing a comma separated list of extensions to the `--extensions` parameter of the `create` command. *NOTE:* Extensions are enabled on the database for the admin user that was supplied when the server was created:
+```azurecli
+az postgres server-arc create -n <name> --k8s-namespace <namespace> --extensions "pgaudit,pg_partman" --use-k8s
+```
 
+## Add or remove extensions
+You can add or remove extensions from an existing Arc-enabled PostgreSQL server.
 
-## Create extensions
-Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
+First describe the server to get the current list of extensions:
 ```console
-CREATE EXTENSION <extension name>;
+kubectl describe postgresqls <server-name> -n <namespace>
 ```
-
-## Show the list of extensions created
-Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
-```console
-select * from pg_extension;
+If there are extensions enabled the output contains a section like this:
+```yml
+  config:
+    postgreSqlExtensions: pgaudit,pg_partman
+```
+Add new extensions by appending them to the existing list, or remove extensions by removing them from the existing list. Pass the desired list to the update command. For example, to add `pgcrypto` and remove `pg_partman` from the server in the example above:
+```azurecli
+az postgres server-arc update -n <name> --k8s-namespace <namespace> --extensions "pgaudit,pgrypto" --use-k8s
 ```
 
-## Drop an extension
+## Show the list of enabled extensions
 Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
 ```console
-drop extension <extension name>;
+select * from pg_extension;
 ```
 
 ## Next steps

articles/azure-arc/data/what-is-azure-arc-enabled-postgresql.md

@@ -19,17 +19,17 @@ ms.topic: how-to
 
 **Azure Arc-enabled PostgreSQL server** is one of the database engines available as part of Azure Arc-enabled data services. 
 
-## Compare Postgres solutions provided by Microsoft in Azure
+## Compare PostgreSQL solutions provided by Microsoft in Azure
 
-Microsoft offers Postgres database services in Azure in two ways:
+Microsoft offers PostgreSQL database services in Azure in two ways:
 - As a managed service in **[Azure PaaS](https://portal.azure.com/#create/Microsoft.PostgreSQLServer)** (Platform As A Service)
 - As a semi-managed service with Azure Arc as it is operated by customers or their partners/vendors
 
 ### Features
 
-- Manage Postgres simply
+- Manage PostgreSQL simply
 - Simplify monitoring, back up, patching/upgrade, access control & more
-- Deploy Postgres on any [Kubernetes](https://kubernetes.io/) infrastructure
+- Deploy PostgreSQL on any [Kubernetes](https://kubernetes.io/) infrastructure
     - On-premises
     - Cloud providers like AWS, GCP, and Azure
     - Edge deployments (including lightweight Kubernetes [K3S](https://k3s.io/))