Skip to content

Commit ab11642

Browse files
author
Mike Ray (Microsoft)
committed
Update for marm
1 parent 0fc1c41 commit ab11642

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/azure-arc/data/backup-controller-database.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.topic: how-to
1515

1616
When you deploy Azure Arc data services, the Azure Arc Data Controller is one of the most critical components of the deployment. The data controller:
1717

18-
- Provisions and de-provisions resources
18+
- Provisions and deprovisions resources
1919
- Orchestrates most of the activities for Azure Arc-enabled SQL Managed Instance
2020
- Captures the billing and usage information of each Arc SQL managed instance.
2121

@@ -26,7 +26,7 @@ This article explains how to back up the controller database.
2626
Following steps are needed in order to back up the `controller` database:
2727

2828
1. Retrieve the credentials for the secret
29-
1. Decode the credentials as they are base64 encoded
29+
1. Decode the credentials from base64
3030
1. Use the decoded credentials to connect to the SQL instance hosting the controller database, and issue the `BACKUP` command
3131

3232
## Retrieve the credentials for the secret
@@ -50,13 +50,14 @@ The contents of the yaml file of the secret `controller-db-rw-secret` contain a
5050

5151
## Use the decoded credentials to connect to the SQL instance hosting the controller database, and issue the `BACKUP` command
5252

53-
With the decoded credentials run the following command to issue a T-SQL `BACKUP` command to backup the controller database.
53+
With the decoded credentials, run the following command to issue a T-SQL `BACKUP` command to back up the controller database.
5454

5555
```azurecli
5656
kubectl exec controldb-0 -n contosons -c mssql-server -- /opt/mssql-tools/bin/sqlcmd -S localhost -U controldb-rw-user -P "<password>" -Q "BACKUP DATABASE [controller] TO DISK = N'/var/opt/controller.bak' WITH NOFORMAT, NOINIT, NAME = N'Controldb-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10, CHECKSUM"
5757
```
5858

5959
Once the backup is created, you can move the `controller.bak` file to a remote storage for any recovery purposes.
6060

61-
Ideally, it is recommended to backup the controller database before and after any custom resource change such as creating or deleting an Arc-enabled SQL Managed Instance.
61+
> [!TIP]
62+
> Back up the controller database before and after any custom resource changes such as creating or deleting an Arc-enabled SQL Managed Instance.
6263

0 commit comments

Comments
 (0)