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: articles/backup/backup-azure-sql-database.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Azure Backup has recently announced support for [EOS SQL Severs](https://docs.mi
55
55
2. .NET Framework 4.5.2 and above needs to be installed on the VM
56
56
3. Backup for FCI and mirrored databases isn’t supported
57
57
58
-
All of the other [feature considerations and limitations](#feature-consideration-and-limitations) apply to these versions as well. The customer won’t be charged for this feature till the time it is generally available.
58
+
Users will not be charged for this feature till the time it is generally available. All of the other [feature considerations and limitations](#feature-consideration-and-limitations) apply to these versions as well. Kindly refer to the [prerequisites](backup-sql-server-database-azure-vms.md#prerequisites) before you configure protection on SQL Servers 2008 and 2008 R2 which include setting the [registry key](backup-sql-server-database-azure-vms.md#add-registry-key-to-enable-registration) (this step would not be required when the feature is generally available).
59
59
60
60
61
61
## Feature consideration and limitations
@@ -189,13 +189,13 @@ Add **NT AUTHORITY\SYSTEM** and **NT Service\AzureWLBackupPluginSvc** logins to
189
189
8. Repeat the same sequence of steps (1-7 above) to add NT Service\AzureWLBackupPluginSvc login to the SQL Server instance. If the login already exists, make sure it has the sysadmin server role and under Status it has Grant the Permission to connect to database engine and Login as Enabled.
190
190
9. After granting permission, **Re-discover DBs** in the portal: Vault **->** Backup Infrastructure **->** Workload in Azure VM:
191
191
192
-

192
+

193
193
194
194
Alternatively, you can automate giving the permissions by running the following PowerShell commands in admin mode. The instance name is set to MSSQLSERVER by default. Change the instance name argument in script if need be:
195
195
196
196
```powershell
197
197
param(
198
-
[Parameter(Mandatory=$false)]
198
+
[Parameter(Mandatory=$false)]
199
199
[string] $InstanceName = "MSSQLSERVER"
200
200
)
201
201
if ($InstanceName -eq "MSSQLSERVER")
@@ -207,7 +207,7 @@ else
207
207
$fullInstance = $env:COMPUTERNAME + "\" + $InstanceName # In case of named instance
208
208
}
209
209
try
210
-
{
210
+
{
211
211
sqlcmd.exe -S $fullInstance -Q "sp_addsrvrolemember 'NT Service\AzureWLBackupPluginSvc', 'sysadmin'" # Adds login with sysadmin permission if already not available
212
212
}
213
213
catch
@@ -216,7 +216,7 @@ catch
216
216
Write-Host $_.Exception|format-list -force
217
217
}
218
218
try
219
-
{
219
+
{
220
220
sqlcmd.exe -S $fullInstance -Q "sp_addsrvrolemember 'NT AUTHORITY\SYSTEM', 'sysadmin'" # Adds login with sysadmin permission if already not available
0 commit comments