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: azure-sql/virtual-machines/windows/backup-restore.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,9 +72,6 @@ If you want to manually manage backup and restore operations on your SQL VMs, th
72
72
73
73
-[Backup and restore for SQL Server 2016 and later](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases)
74
74
-[Backup and restore for SQL Server 2014](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases?viewFallbackFrom=sql-server-2014)
75
-
-[Backup and restore for SQL Server 2012](/previous-versions/sql/sql-server-2012/ms187048(v=sql.110))
|**Azure Elastic SAN preview**| October | You can now place your SQL Server workloads on an Azure Elastic SAN for improved performance, throughput, and cost. The Azure Elastic SAN is currently in preview. Review [Azure Elastic SAN](performance-guidelines-best-practices-storage.md#azure-elastic-san) to learn more. |
SQL Server 2012 has reached the [end of its support (EOS) life cycle](/lifecycle/products/microsoft-sql-server-2012). Because many customers are still using this version, we're providing several options to continue getting support. You can migrate your on-premises SQL Server instances to Azure virtual machines (VMs), migrate to Azure SQL Database, or stay on-premises and purchase extended security updates.
18
18
19
-
Unlike with a managed instance, migrating to an Azure VM does not require recertifying your applications. And unlike with staying on-premises, you'll receive free extended security patches by migrating to an Azure VM.
19
+
Unlike with Azure SQL Managed Instance, migrating to an Azure VM doesn't require your applications to be recertified. And unlike with staying on-premises, you receive free extended security patches by migrating to an Azure VM.
20
20
21
21
The rest of this article provides considerations for migrating your SQL Server instance to an Azure VM.
22
22
23
23
For more information about end of support options, see [End of support](/sql/sql-server/end-of-support/sql-server-end-of-support-overview).
24
24
25
25
## Provisioning
26
26
27
-
There is a pay-as-you-go **SQL Server 2012on Windows Server 2012 R2** image available on Azure Marketplace.
27
+
Customers who are on an earlier version of SQL Server need to either self-install or upgrade to SQL Server 2012. Likewise, customers on an earlier version of Windows Server need to either deploy their VM from a custom VHD or upgrade to Windows Server 2012 R2.
Customers who are on an earlier version of SQL Server will need to either self-install or upgrade to SQL Server 2012. Likewise, customers on an earlier version of Windows Server will need to either deploy their VM from a custom VHD or upgrade to Windows Server 2012 R2.
32
-
33
-
Images deployed through Azure Marketplace come with the SQL IaaS Agent extension pre-installed. The SQL IaaS Agent extension is a requirement for flexible licensing and automated patching. Customers who deploy self-installed VMs will need to manually install the SQL IaaS Agent extension.
29
+
Images deployed through Azure Marketplace come with the SQL IaaS Agent extension preinstalled. The SQL IaaS Agent extension is a requirement for flexible licensing and automated patching. Customers who deploy self-installed VMs need to manually install the SQL IaaS Agent extension.
34
30
35
31
> [!NOTE]
36
32
>
37
-
> Although the SQL Server **Create** and **Manage** options will work with the SQL Server 2012 image in the Azure portal, the following features are _not supported_: Automatic backups, Azure Key Vault integration, and R Services.
33
+
> Although the SQL Server **Manage** options work with SQL Server 2012, the following features aren't supported_: Automatic backups, and Azure Key Vault integration.
38
34
39
35
## Licensing
40
36
@@ -46,7 +42,7 @@ Self-installed SQL Server 2012 instances on an Azure VM can register with the SQ
46
42
47
43
## Migration
48
44
49
-
You can migrate EOS SQL Server instances to an Azure VM with manual backup/restore methods. This is the most common migration method from on-premises to an Azure VM.
45
+
You can migrate end of support SQL Server instances to an Azure VM with manual backup/restore methods. This is the most common migration method from on-premises to an Azure VM.
50
46
51
47
### Azure Site Recovery
52
48
@@ -60,13 +56,13 @@ The [Azure Database Migration Service](/azure/dms/dms-overview) is an option for
60
56
61
57
## Disaster recovery
62
58
63
-
Disaster recovery solutions for EOS SQL Server on an Azure VM are as follows:
59
+
Disaster recovery solutions for end of support SQL Server on an Azure VM are as follows:
64
60
65
-
-**SQL Server backups**: Use Azure Backup to help protect your EOS SQL Server 2012 against ransomware, accidental deletion, and corruption with a 15-minute RPO and point-in-time recovery. For more details, see [this article](/azure/backup/sql-support-matrix#scenario-support).
61
+
-**SQL Server backups**: Use Azure Backup to help protect your end of support SQL Server 2012 against ransomware, accidental deletion, and corruption with a 15-minute RPO and point-in-time recovery. For more information, see [this article](/azure/backup/sql-support-matrix#scenario-support).
66
62
67
63
-**Log shipping**: You can create a log shipping replica in another zone or Azure region with continuous restores to reduce the RTO. You need to manually configure log shipping.
68
64
69
-
-**Azure Site Recovery**: You can replicate your VM between zones and regions through Azure Site Recovery replication. SQL Server requires app-consistent snapshots to guarantee recovery in case of a disaster. Azure Site Recovery offers a minimum 1-hour RPO and a 2-hour (plus SQL Server recovery time) RTO for EOS SQL Server disaster recovery.
65
+
-**Azure Site Recovery**: You can replicate your VM between zones and regions through Azure Site Recovery replication. SQL Server requires app-consistent snapshots to guarantee recovery if there's a disaster. Azure Site Recovery offers a minimum 1-hour RPO and a 2-hour (plus SQL Server recovery time) RTO for end of support SQL Server disaster recovery.
70
66
71
67
## Security patching
72
68
@@ -77,11 +73,11 @@ Extended security updates for SQL Server VMs are delivered through the Microsoft
77
73
For improved patching management, which also includes Cumulative Updates, try the integrated [Azure Update Manager](../azure-update-manager-sql-vm.md) experience.
78
74
79
75
> [!NOTE]
80
-
> Registration with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md)is not required for _manual_ installation of extended security updates on Azure virtual machines. Microsoft Update automatically detects the VM is running in Azure and presents relevant updates for download even if the extension is not installed.
76
+
> Registration with the [SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md)isn't required for _manual_ installation of extended security updates on Azure virtual machines. Microsoft Update automatically detects the VM is running in Azure and presents relevant updates for download even if the extension isn't installed.
81
77
82
78
83
79
84
-
[Azure Update management](/azure/automation/update-management/overview) as of today does not detect patches for SQL Server Marketplace images. You should look under Windows Updates to apply SQL Server updates in this case.
80
+
[Azure Update management](/azure/automation/update-management/overview) as of today doesn't detect patches for SQL Server Marketplace images. You should look under Windows Updates to apply SQL Server updates in this case.
Copy file name to clipboardExpand all lines: azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,12 +90,10 @@ The following table provides a matrix of pay-as-you-go SQL Server images.
90
90
|**SQL Server 2019**|[Windows Server 2022](https://portal.azure.com/#create/microsoftsqlserver.sql2019-ws2022enterprise-gen2), [Windows Server 2019](https://portal.azure.com/#create/microsoftsqlserver.sql2019-ws2019enterprise-ARM)|
91
91
|**SQL Server 2017**|[Windows Server 2019](https://portal.azure.com/#create/microsoftsqlserver.sql2017-ws2019enterprise-ARM), [Windows Server 2016](https://portal.azure.com/#create/Microsoft.SQLServer2017EnterpriseWindowsServer2016-ARM)|
92
92
|**SQL Server 2016**|[Windows Server 2019](https://portal.azure.com/#create/microsoftsqlserver.sql2016sp3-ws2019enterprise), [Windows Server 2016](https://portal.azure.com/#create/Microsoft.SQLServer2016SP2EnterpriseWindowsServer2016-ARM)|
93
-
|**SQL Server 2014**|[Windows Server 2012 R2](https://portal.azure.com/#create/microsoftsqlserver.sql2014sp3-ws2012r2enterprise-ARM)|
94
-
|**SQL Server 2012**|[Windows Server 2012 R2](https://portal.azure.com/#create/Microsoft.SQLServer2012SP4EnterpriseWindowsServer2012R2-ARM)|
95
93
96
94
<sup>1</sup> The SQL Server 2025 image is currently only available to deploy through [Azure marketplace directly](https://portal.azure.com/#create/microsoftsqlserver.sql2025-ws2025entdev-gen2), and not yet available to choose from the Azure SQL deployment page or as a VM image on the **Create Azure VM** page in the Azure portal.
To see the available SQL Server on Linux virtual machine images, see [Overview of SQL Server on Azure Virtual Machines (Linux)](../linux/sql-server-on-linux-vm-what-is-iaas-overview.md).
The instructions for basic details vary between deploying a conventional SQL Server on Azure VM, and [SQL Server on an Azure confidential VM](sql-vm-create-confidential-vm-how-to.md).
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/active-secondaries-backup-on-secondary-replicas-always-on-availability-groups.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ In a [distributed availability group](distributed-availability-groups.md), backu
51
51
52
52
## New for SQL Server 2025
53
53
54
-
Starting with [!INCLUDE [sssql25-md](../../../includes/sssql25-md.md)], in addition to copy-only backups, you can also perform full, and differential backups on any secondary replica.
54
+
Starting with [!INCLUDE [sssql25-md](../../../includes/sssql25-md.md)], in addition to existing copy-only and transaction log backups, you can also perform full, and differential backups on any secondary replica.
55
55
56
56
Use the following trace flags to enable backups on secondary replicas:
57
57
-[Trace flag 3261](../../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md#tf3261): Enables differential backups on secondary replicas.
0 commit comments