Skip to content

Commit 459a782

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #299006 from AbhishekMallick01/Apr-29-2025-ASE
SAP ASE (Sybase) database backup GA - PLR review incorporation
2 parents c2d1dd4 + 5b327c6 commit 459a782

11 files changed

+142
-138
lines changed

‎articles/backup/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.topic: landing-page
1111
author: jyothisuri
1212
ms.author: jsuri
13-
ms.date: 04/17/2025
13+
ms.date: 05/14/2025
1414
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1515

1616
landingContent:

‎articles/backup/sap-ase-backup-support-matrix.md

Lines changed: 22 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: SAP ASE Backup support matrix
33
description: In this article, learn about the supported scenarios and limitations when you use Azure Backup to back up SAP ASE databases on Azure VMs.
44
ms.topic: reference
55
ms.custom: references_regions, ignite-2024
6-
ms.date: 04/18/2025
6+
ms.date: 05/13/2025
77
ms.service: azure-backup
88
author: jyothisuri
99
ms.author: jsuri
@@ -21,19 +21,19 @@ This article summarizes the scenarios supported and limitations present when you
2121
| **Scenario** | **Supported configurations** | **Unsupported configurations** |
2222
| ------- | -------- | -------- |
2323
| **Topology** | SAP ASE Database running in Azure Linux VMs only. | Windows |
24-
| **Regions** | **Americas** – Canada Central, Canada East, Brazil South.<br> <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India. <br><br> **Europe** – West Europe, North Europe, France Central, France South, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South. <br><br> **Africa/ME** - South Africa North, South Africa West, UAE North, UAE Central. | Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, Germany Central, Germany Northeast, US Gov IOWA, Azure Gov, China East, China East 2, China East 3, China North, China North 2, China North 3. |
24+
| **Regions** | **Americas** – Canada Central, Canada East, Brazil South.<br> <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India. <br><br> **Europe** – West Europe, North Europe, France Central, France South, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South. <br><br> **Africa/ME** - South Africa North, South Africa West, UAE North, UAE Central, Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, China East, China East 2, China East 3, China North, China North 2, China North 3, US GOV Arizona, US GOV Texas, US GOV Virginia. | Germany Central, Germany Northeast, US Gov IOWA, Azure Gov. |
2525
| **OS versions** | SLES 12 with SP0, SP1, SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, and SP5, 15.6 <br><br> RHEL 7.1, 7.2, 7.3, 7.4, 7.6, 7.7, 7.9, 8.1, 8.2, 8.3, 8.4,8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.2 | |
2626
| **ASE versions** | SAP Adaptive Server Enterprise 16.0 SP02, SP03, SP04 | |
27-
| **ASE Instances** | A single SAP ASE instance on a single Azure Virtual Machine (VM). | HA and multi SID on single VM isn't currently supported. |
27+
| **ASE Instances** | A single SAP ASE instance on a single Azure Virtual Machine (VM). <br><br> Multi SID on single VM. | HA on single VM isn't currently supported. |
2828
| **Backup types** | Full, Differential, and Log backups. | Incremental, archival support is currently not available. |
2929
| **Restore types** | ALR-Alternate Location Restore, OLR-Original Location Restore (In-Place), Restore as Files. | |
3030
| **Cross Subscription Restore** | Supported via the Azure portal.<br>Cross Subscription Restore to Paired Region. | Region of Choice isn't supported. |
3131
| **Number of full backups per day** | One scheduled backup. <br><br> Three on-demand backups. <br> <br> We recommend not to trigger more than three backups per day. However, to allow user retries for failed attempts, hard limit for on-demand backups is set to nine attempts. |
32-
| **ASE deployments** | Standalone | HA, Multi SID on Single VM. |
32+
| **ASE deployments** | Standalone, Multi SID on Single VM. | HA on Single VM. |
3333
| **Compression** | You can enable ASE Native compression via the Backup policy and when you take an on-demand Backup/Backup Now. In Preregistration Script, Compression Level is set to **Level 101** for Optimal results. | |
3434
| **Striping Support** | You can increase your backup throughput by enabling Striping configuration, which needs to be set in **Preregistration script** – refer parameters **enable-striping** - Set to **true** and **stripesCount** set to 4 by Default and can be adjusted. | |
3535
| **Azure CLI/PowerShell** | | Azure CLI/PowerShell support is currently not available. |
36-
| **Security Capabilities** | Immutability, Soft Delete, MUA, Private Endpoint, Encryption at rest are supported. | |
36+
| **Security Capabilities** | Immutability, Soft Delete, MUA, Private Endpoint, and Encryption at rest are supported. | |
3737

3838
>[!NOTE]
3939
>- Azure Backup doesn’t automatically adjust for daylight saving time changes when backing up an SAP ASE (Sybase) database running in an Azure VM. We recommend you to modify the policy manually as needed.
@@ -63,26 +63,37 @@ Learn more [about SAP ASE (Sybase) Azure Virtual Machine storage and SAP ASE (Sy
6363
## Support for multiple SAP ASE instances on a single host
6464

6565
Azure Backup now enables seamless backups for multiple ASE (Sybase) database instances on Azure VMs, utilizing Multi-SID support. This advancement is particularly useful for shared VM environments, such as non-production setups, where multiple users require efficient data protection and recovery. SAP ASE Multi-SID support includes the following configurations:
66+
6667
| Sap ASE instance | Support |
6768
| --- |--- |
68-
| Standalone (SID1)+ Standalone (SID2) | Supported |
69+
| Standalone (SID1) + Standalone (SID2) | Supported |
6970
| HA (SID1) + Standalone (SID2) | Supported |
7071
| HA (SID1) + HA (SID2)| Supported |
7172

72-
***SID1(HXE) and SID2 (HYE) represent two ASE instances running on the same host.**
73+
***SID1 (HXE) and SID2 (HYE) represent two ASE instances running on the same host.**
7374

7475
The following table lists the required parameters for adding/removing SAP ASE instances:
7576

7677
| Action | Parameter | Description | Example script |
7778
| --- | --- | --- | --- |
7879
| Add an instance | `--sid` | SAP ASE database instance that you want to protect. <br><br> By default, the first instance is selected. | `./PreReg.sh --add --sid HXE` <br><br> Or <br><br> `./PreReg.sh --sid HXE` <br><br> (Default mode is `add` for the script.) <br><br> After you add instances, registration needs to be done on recovery services vault. If a new instance is added later, re-registration is required. |
7980
| | `sudo` | Add a `SID` from the **Config** file. | `"<Path_to_the_Pre-Reg_Script" -aw SAPAse --sid "<SID>" --sid-user "<sidUser>" --db-port "<dbPort>" --db-user <dbUser> --db-host "<dbHost>" --enable-striping <true/false> --skip-network-checks` |
80-
| Remove an instance | `--sid` | SAP ASE database instance that you want to remove protection. <br><br> SID is a mandate parameter for remove. | `./PreReg.sh --remove --sid HXE` |
81+
| Remove an instance | `--sid` | SAP ASE database instance that you want to remove protection from. <br><br> SID is a mandate parameter for remove. | `./PreReg.sh --remove --sid HXE` |
8182
| | `sudo` | Remove a `SID` from the **Config** file. | `"<Path_to_the_Pre-Reg_Script" -aw SAPAse --sid "<SID>" --sid-user "<sidUser>" --db-port "<dbPort>" --db-user <dbUser> --db-host "<dbHost>" --enable-striping <true/false> --skip-network-checks --remove` |
8283
| | `--dbHost` | The private IP of the specific SID instance that you intend to register. <br><br> In multi-instance setups, each System ID (SID) might have a different private IP. Use the IP available in `/sybase/<SID>/interfaces` for the correct instance. | |
8384

85+
86+
>[!Note]
87+
>If you have the preregistration script already installed, update the script name by running the following bash command:
88+
>
89+
> `sudo ./<script name> -us`
90+
91+
8492
## Next steps
8593

86-
- [Back up SAP ASE (Sybase) databases on Azure VMs](sap-ase-database-backup.md).
87-
- [Restore SAP ASE (Sybase) databases on Azure VMs](sap-ase-database-restore.md).
88-
- [Manage SAP ASE (Sybase) databases backup](sap-ase-database-manage.md).
94+
- [Configure backup for SAP ASE (Sybase) databases on Azure VMs using Azure portal](sap-ase-database-backup.md).
95+
- [Restore SAP ASE database on Azure VMs using Azure portal](sap-ase-database-restore.md).
96+
- [Manage and monitor backed-up SAP ASE database using Azure portal](sap-ase-database-manage.md).
97+
- [Quickstart: Run the preregistration script for SAP ASE (Sybase) database backup in Azure Cloud Shell](sap-ase-database-backup-run-preregistration-quickstart.md).
98+
- [Tutorial: Back up SAP ASE (Sybase) database using Azure Business Continuity Center](sap-ase-database-backup-tutorial.md).
99+
- [Troubleshoot SAP ASE (Sybase) database backup](troubleshoot-sap-ase-sybase-database-backup.md).

‎articles/backup/sap-ase-database-about.md

Lines changed: 15 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: About the SAP ASE (Sybase) database backup on Azure VMs
33
description: In this article, learn about backing up SAP ASE (Sybase) databases that are running on Azure virtual machines.
44
ms.topic: overview
5-
ms.date: 11/19/2024
5+
ms.date: 05/13/2025
66
ms.service: azure-backup
77
ms.custom:
88
- ignite-2024
@@ -40,32 +40,25 @@ You can back up SAP ASE (Sybase) databases that are running inside an Azure VM a
4040
* The Azure VM that's running the SAP ASE server is registered with the vault, and the databases to be backed up are discovered. To enable the Azure Backup service to discover databases, a [preregistration script](https://go.microsoft.com/fwlink/?linkid=2173610) must be run on the ASE server as a root user.
4141
* This script creates the *AZUREWLBACKUPASEUSER* database user or uses the custom Backup user you already created. It then creates a corresponding key with the same name in *hdbuserstore*. To learn more about the functionality of the script, see [Back up SAP ASE (Sybase) databases in an Azure VM](sap-ase-database-backup.md).
4242
* The Azure Backup service now installs the Azure Backup plugin for ASE on the registered SAP ASE server.
43-
* The `AZUREWLBACKUPASEUSER` database user (created by the preregistration script or the custom Backup user you created, and added as input to the preregistration script) is used by the Azure Backup plugin for ASE to back up and restore. If you attempt to configure backup for SAP ASE (Sybase) databases without running this script, you might receive the UserErrorHanaScriptNotRun error.
43+
* The `AZUREWLBACKUPASEUSER` database user (created by the preregistration script or the custom Backup user you created, and added as input to the preregistration script) is used by the Azure Backup plugin for ASE to back up and restore. If you attempt to configure backup for SAP ASE (Sybase) databases without running this script, you might receive the UserErrorASEScriptNotRun error.
4444
* To configure a backup on the databases that you discovered, choose the required backup policy, and then enable backups.
4545

46-
* After you configure the backup, the Azure Backup service sets up the following Backint parameters at the database level on the protected SAP ASE server:
47-
* `[catalog_backup_using_backint:true]`
48-
* `[enable_accumulated_catalog_backup:false]`
49-
* `[parallel_data_backup_backint_channels:1]`
50-
* `[log_backup_timeout_s:900)]`
51-
* `[backint_response_timeout:7200]`
52-
5346
> [!NOTE]
5447
> Ensure that these parameters aren't present at the host level. Host-level parameters override these parameters and might cause unexpected behavior.
5548
5649

57-
* The Azure Backup plugin for ASE maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the ASE backup engine through the Backint APIs.
58-
* The ASE backup engine returns a Backint stream with the data to be backed up.
50+
* The Azure Backup plugin for ASE maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the ASE backup engine through the APIs.
51+
* The ASE backup engine returns a stream with the data to be backed up.
5952
* All the scheduled backups and on-demand backups (triggered from the Azure portal) that are either full or differential are initiated via the Azure Backup plugin for ASE. However, the ASE backup engine manages and triggers log backups.
60-
* Azure Backup for SAP ASE, because it's a Backint-certified solution, doesn't depend on underlying disk or VM types. ASE generates streams that actively perform the backup.
53+
* Azure Backup for SAP ASE, because it's a certified solution, doesn't depend on underlying disk or VM types. ASE generates streams that actively perform the backup.
6154

6255
:::image type="content" source="./media/sap-ase-database-about/database-backup-architecture.png" alt-text="Diagram shows the SAP ASE Sybase database backup." lightbox="./media/sap-ase-database-about/database-backup-architecture.png":::
6356

6457
## Use Azure VM backup with Azure SAP ASE backup
6558

6659
In addition to using SAP ASE backup in Azure, which provides database-level backup and recovery, you can use the Azure VM backup solution to back up the operating system and nondatabase disks.
6760

68-
You can use the [Backint certified Azure SAP ASE backup solution](#backup-architecture-for-sap-ase-sybase-databases) for database backup and recovery.
61+
You can use the [certified Azure SAP ASE backup solution](#backup-architecture-for-sap-ase-sybase-databases) for database backup and recovery.
6962

7063
You can use [an Azure VM backup](backup-azure-vms-introduction.md) to back up the operating system and other nondatabase disks. The VM backup is run once a day, and it backs up all disks, except the Write Accelerated operating system disks and ultra disks. Because you're backing up the database by using the Azure SAP ASE backup solution, you can take a file-consistent backup of only the operating system and nondatabase disks by using the [selective disk backup and restore for Azure VMs](selective-disk-backup-restore.md) feature.
7164

@@ -92,20 +85,22 @@ For example, if you protect a 1.2 TB ASE database in an East US2 instance, you
9285

9386
## Cross Subscription Restore for SAP ASE (Sybase) database
9487

95-
Azure Backup now supports restoring SAP ASE databases to any subscription, provided the [necessary Azure Role-Based Access Control (Azure RBAC) permissions](backup-rbac-rs-vault.md#minimum-role-requirements-for-sap-ase-sybase-database--cross-subscription-restore) are met. By default, restores are performed within the same subscription where the restore points are located.
96-
97-
With Cross-Subscription Restore (CSR), you can restore SAP ASE databases to any subscription and Recovery Services vault within the same tenant, as long as they have the required restore permissions. CSR is enabled by default on all Recovery Services vaults, including both existing and newly created vaults.
88+
Azure Backup now supports restoring SAP ASE databases to any subscription and Recovery Services vault, provided they are in the same tenant and the necessary [Azure role-based access control (Azure RBAC) permissions for restore](backup-rbac-rs-vault.md#minimum-role-requirements-for-sap-ase-sybase-database--cross-subscription-restore) are met. By default, restores are performed within the same subscription where the restore points are located.
9889

9990
>[!Note]
91+
>- CSR is enabled by default on all Recovery Services vaults, including both existing and newly created vaults.
10092
>- Cross-Subscription Restore can be initiated directly from the Recovery Services vault.
10193
>- Cross Regional Restore (CRR) with CSR isn't supported.
10294
103-
Learn how to [trigger Cross Subscription Restore to a Private Endpoint enabled vault](sap-ase-database-restore.md#restore-to-a-private-endpoint-enabled-vault-in-a-different-subscription).
95+
Learn how to [trigger Cross Subscription Restore to a private endpoint enabled vault](sap-ase-database-restore.md#restore-to-a-private-endpoint-enabled-vault-in-a-different-subscription).
10496

10597
## Next steps
10698

10799
Learn how to:
108100

109-
- [Back up SAP ASE (Sybase) databases on Azure VMs](sap-ase-database-backup.md).
110-
- [Restore SAP ASE (Sybase) databases on Azure VMs](sap-ase-database-restore.md).
111-
- [Manage SAP ASE (Sybase) databases backup](sap-ase-database-manage.md).
101+
- [Configure backup for SAP ASE (Sybase) databases on Azure VMs using Azure portal](sap-ase-database-backup.md).
102+
- [Restore SAP ASE database on Azure VMs using Azure portal](sap-ase-database-restore.md).
103+
- [Manage and monitor backed-up SAP ASE database using Azure portal](sap-ase-database-manage.md).
104+
- [Quickstart: Run the preregistration script for SAP ASE (Sybase) database backup in Azure Cloud Shell](sap-ase-database-backup-run-preregistration-quickstart.md).
105+
- [Tutorial: Back up SAP ASE (Sybase) database using Azure Business Continuity Center](sap-ase-database-backup-tutorial.md).
106+
- [Troubleshoot SAP ASE (Sybase) database backup](troubleshoot-sap-ase-sybase-database-backup.md).

0 commit comments

Comments
 (0)