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-linux-database-consistent-enhanced-pre-post.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
-
title: Database consistent snapshots using enhanced pre-post script framework
3
-
description: Learn how Azure Backup allows you to take database consistent snapshots, leveraging Azure VM backup and using packaged pre-post scripts
4
-
ms.topic: conceptual
2
+
title: Database consistent snapshots using enhanced prepost script framework
3
+
description: Learn how Azure Backup allows you to take database consistent snapshots, leveraging Azure Virtual Machine (VM) backup and using packaged prepost scripts
4
+
ms.topic: how-to
5
5
ms.custom: linux-related-content
6
-
ms.date: 09/16/2021
6
+
ms.date: 09/11/2024
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
9
9
---
10
10
11
-
# Enhanced pre-post scripts for database consistent snapshot
11
+
# Enhanced prepost scripts for database consistent snapshot
12
12
13
-
Azure Backup service already provides a [_pre-post_ script framework](./backup-azure-linux-app-consistent.md) to achieve application consistency in Linux VMs using Azure Backup. This involves invoking a pre-script (to quiesce the applications) before taking
13
+
Azure Backup service already provides a [_prepost_ script framework](./backup-azure-linux-app-consistent.md) to achieve application consistency in Linux VMs using Azure Backup. This process involves invoking a pre-script (to quiesce the applications) before taking
14
14
snapshot of disks and calling post-script (commands to un-freeze the applications) after the snapshot is completed to return the applications to the normal mode.
15
15
16
16
Authoring, debugging and maintenance of e pre/post scripts could be challenging. To remove this complexity, Azure Backup provides simplified pre/post-script experience for marquee databases to get application consistent snapshot with least overhead.
@@ -19,7 +19,7 @@ Authoring, debugging and maintenance of e pre/post scripts could be challenging.
19
19
20
20
The new _enhanced_ pre-post script framework has the following key benefits:
21
21
22
-
- These pre-post scripts are directly installed in Azure VMs along with the backup extension. This helps to eliminate authoring and download them from an external location.
22
+
- These pre-post scripts are directly installed in Azure VMs along with the backup extension, which helps to eliminate authoring and download them from an external location.
23
23
- You can view the definition and content of pre-post scripts in [GitHub](https://github.com/Azure/azure-linux-extensions/tree/master/VMBackup/main/workloadPatch/DefaultScripts), even submit suggestions and changes. You can even submit suggestions and changes via GitHub, which will be triaged and added to benefit the broader community.
24
24
- You can even add new pre-post scripts for other databases via [GitHub](https://github.com/Azure/azure-linux-extensions/tree/master/VMBackup/main/workloadPatch/DefaultScripts), _which will be triaged and addressed to benefit the broader community_.
25
25
- The robust framework is efficient to handle scenarios, such as pre-script execution failure or crashes. In any event, the post-script automatically runs to roll back all changes done in the pre-script.
@@ -56,7 +56,7 @@ The following table describes the parameters:
56
56
|Parameter |Mandatory |Explanation |
57
57
|---------|---------|---------|
58
58
|workload_name | Yes | This will contain the name of the database for which you need application consistent backup. The current supported values are `oracle` or `mysql`. |
59
-
|command_path/configuration_path || This will contain path to the workload binary. This is not a mandatory field if the workload binary is set as path variable. |
59
+
|command_path/configuration_path || This will contain path to the workload binary. This isn't a mandatory field if the workload binary is set as path variable. |
60
60
|linux_user | Yes | This will contain the username of the Linux user with access to the database user login. If this value isn't set, then root is considered as the default user. |
61
61
|credString || This stands for credential string to connect to the database. This will contain the entire login string. |
62
62
|ipc_folder || The workload can only write to certain file system paths. You need to provide here this folder path so that the pre-script can write the states to this folder path. |
@@ -87,9 +87,9 @@ Therefore, a daily snapshot + logs with occasional full backup for long-term ret
87
87
88
88
### Log backup strategy
89
89
90
-
The enhanced pre-post script framework is built on Azure VM backup that schedules backup once per day. So, the data loss window with RPO as 24 hours isn’t suitable for production databases. This solution is complemented with a log backup strategy where log backups are streamed out explicitly.
90
+
The enhanced pre-post script framework is built on Azure VM backup that schedules backup once per day. So, the data loss window with Recovery Point Objective (RPO) as 24 hours isn’t suitable for production databases. This solution is complemented with a log backup strategy where log backups are streamed out explicitly.
91
91
92
-
[NFS on blob](../storage/blobs/network-file-system-protocol-support.md) and [NFS on AFS (Preview)](../storage/files/files-nfs-protocol.md) help in easy mounting of volumes directly on database VMs and use database clients to transfer log backups. The data loss window, that is RPO, falls to the frequency of log backups. Also, NFS targets don't need to be highly performant as you might not need to trigger regular streaming (full and incremental) for operational backups after you have a database consistent snapshots.
92
+
[NFS on blob](../storage/blobs/network-file-system-protocol-support.md) and [NFS on AFS (Preview)](../storage/files/files-nfs-protocol.md) help in easy mounting of volumes directly on database VMs and use database clients to transfer log backups. The data loss window that is RPO, falls to the frequency of log backups. Also, NFS targets don't need to be highly performant as you might not need to trigger regular streaming (full and incremental) for operational backups after you have a database consistent snapshots.
93
93
94
94
>[!NOTE]
95
95
>The enhanced pre- script usually takes care to flush all the log transactions in transit to the log backup destination, before quiescing the database to take a snapshot. Therefore, the snapshots are database consistent and reliable during recovery.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-policy-supported-skus.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Supported VM SKUs for Azure Policy
3
3
description: 'An article describing the supported VM SKUs (by Publisher, Image Offer and Image SKU) which are supported for the built-in Azure Policies provided by Backup'
0 commit comments