Skip to content

Commit 034d5f3

Browse files
author
David Curwin
committed
Three changes
1 parent 3528692 commit 034d5f3

File tree

3 files changed

+12
-4
lines changed

3 files changed

+12
-4
lines changed

articles/backup/backup-azure-security-feature-cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -254,7 +254,7 @@ By default, all your data is encrypted using platform-managed keys. You don't ne
254254
When backing up your Azure Virtual Machines, you can now encrypt your data using keys owned and managed by you. Azure Backup lets you use your RSA keys stored in the Azure Key Vault for encrypting your backups. The encryption key used for encrypting backups may be different from the one used for the source. The data is protected using an AES 256 based data encryption key (DEK), which is, in turn, protected using your keys. This gives you full control over the data and the keys. To allow encryption, it's required that the Recovery Services vault be granted access to the encryption key in the Azure Key Vault. You can disable the key or revoke access whenever needed. However, you must enable encryption using your keys before you attempt to protect any items to the vault.
255255

256256
>[!NOTE]
257-
>This feature is currently in limited availability. Please fill out [this survey](https://forms.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR0H3_nezt2RNkpBCUTbWEapURE9TTDRIUEUyNFhNT1lZS1BNVDdZVllHWi4u) and email us at azbackupencryption@microsoft.com if you wish to encrypt your backup data using customer managed keys. Note that the ability to use this feature is subject to approval from the Azure Backup service.
257+
>This feature is currently in limited availability. Please fill out [this survey](https://forms.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR0H3_nezt2RNkpBCUTbWEapURE9TTDRIUEUyNFhNT1lZS1BNVDdZVllHWi4u) and email us at AskAzureBackupTeam@microsoft.com if you wish to encrypt your backup data using customer managed keys. Note that the ability to use this feature is subject to approval from the Azure Backup service.
258258
259259
### Backup of managed disk VMs encrypted using customer-managed keys
260260

articles/backup/sap-hana-faq-backup-azure-vm.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,17 +48,25 @@ Running the pre-registration script sets the required permissions to allow Azure
4848

4949
Refer to [this section](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot#upgrading-from-sap-hana-10-to-20) of the troubleshooting guide.
5050

51+
### Can Azure HANA Backup be set up against a virtual IP (load balancer) and not a virtual machine?
52+
53+
Currently we do not have the capability to set up the solution against a virtual IP alone. We need a virtual machine to execute the solution.
54+
55+
### I have a SAP HANA System Replication (HSR), how should I configure backup for this setup?
56+
57+
The primary and secondary nodes of the HSR will be treated as two individual, un-related VMs. You need to configure backup on the primary node and when the fail-over happens, you need to configure backup on the secondary node (which now becomes the primary node). There is no automatic 'fail-over' of backup to the other node.
58+
5159
## Restore
5260

53-
### Why cant I see the HANA system I want my database to be restored to?
61+
### Why can't I see the HANA system I want my database to be restored to?
5462

5563
Check if all the prerequisites for the restore to target SAP HANA instance are met. For more information, see [Prerequisites - Restore SAP HANA databases in Azure VM](https://docs.microsoft.com/azure/backup/sap-hana-db-restore#prerequisites).
5664

5765
### Why is the Overwrite DB restore failing for my database?
5866

5967
Ensure that the **Force Overwrite** option is selected while restoring.
6068

61-
### Why do I see the Source and target systems for restore are incompatible error?
69+
### Why do I see the "Source and target systems for restore are incompatible" error?
6270

6371
Refer to the SAP HANA Note [1642148](https://launchpad.support.sap.com/#/notes/1642148) to see what restore types are currently supported.
6472

articles/virtual-machines/windows/sql/virtual-machines-windows-sql-server-2008-eos-extend-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The [Database Migration Service](/azure/dms/dms-overview) is an option for custo
6161

6262
Disaster recovery solutions for EOS SQL Server on an Azure VM are as follows:
6363

64-
- **SQL Server backups**: Use Azure Backup to help protect your EOS SQL Server against ransomware, accidental deletion, and corruption. The solution is currently in preview for EOS SQL Server and supports SQL Server 2008 and 2008 R2 running on Windows 2008 R2 SP1. For more details, see [this article](https://docs.microsoft.com/azure/backup/backup-azure-sql-database#scenario-support).
64+
- **SQL Server backups**: Use Azure Backup to help protect your EOS SQL Server 2008 and 2008 R2 against ransomware, accidental deletion, and corruption with 15-min RPO and point-in-time recovery. For more details, see [this article](https://docs.microsoft.com/azure/backup/backup-azure-sql-database#scenario-support).
6565
- **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.
6666
- **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.
6767

0 commit comments

Comments
 (0)