Skip to content

Commit ed74ddf

Browse files
committed
formatting
1 parent b7cb8d5 commit ed74ddf

File tree

2 files changed

+0
-6
lines changed

2 files changed

+0
-6
lines changed

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-automated-backup-v2.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -114,9 +114,6 @@ Then, on Tuesday at 10 for 6 hours, full backups of all databases start again.
114114
> [!IMPORTANT]
115115
> When scheduling daily backups, it is recommended that you schedule a wide time window to ensure all databases can be backed up within this time. This is especially important in the case where you have a large amount of data to back up.
116116
117-
## Configure in the portal
118-
119-
You can use the Azure portal to configure Automated Backup v2 during provisioning or for existing SQL Server 2016/2017 VMs.
120117

121118
## Configure for new VMs
122119

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-automated-backup.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,6 @@ The following table describes the options that can be configured for Automated B
6464
| **Encryption** | Enable/Disable (Disabled) | Enables or disables encryption. When encryption is enabled, the certificates used to restore the backup are located in the specified storage account in the same `automaticbackup` container using the same naming convention. If the password changes, a new certificate is generated with that password, but the old certificate remains to restore prior backups. |
6565
| **Password** | Password text | A password for encryption keys. This is only required if encryption is enabled. In order to restore an encrypted backup, you must have the correct password and related certificate that was used at the time the backup was taken. |
6666

67-
## Configure in the portal
68-
69-
You can use the Azure portal to configure Automated Backup during provisioning or for existing SQL Server 2014 VMs.
7067

7168
## Configure new VMs
7269

0 commit comments

Comments
 (0)