Skip to content

Commit d10a66e

Browse files
ttorblettorble
authored
Merge pull request #298930 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 4/28
2 parents 5fb2bb0 + 9cf3be5 commit d10a66e

12 files changed

+127
-77
lines changed

‎articles/application-gateway/monitor-application-gateway-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ For Application Gateway v2 SKU, the following metrics are available. What follow
4646
- **Client TLS protocol**. Count of TLS and non-TLS requests.
4747
- **Current capacity units**. There are three determinants to capacity unit: compute unit, persistent connections, and throughput. Each capacity unit is composed of at most one compute unit, or 2500 persistent connections, or 2.22-Mbps throughput.
4848
- **Current compute units**. Factors affecting compute unit are TLS connections/sec, URL Rewrite computations, and WAF rule processing.
49-
- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway.
49+
- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway, including probes for the health of the application gateway's instances.
5050
- **Estimated Billed Capacity units**. With the v2 SKU, consumption drives the pricing model. Capacity units measure consumption-based cost that is charged in addition to the fixed cost. *Estimated Billed Capacity units indicate the number of capacity units using which the billing is estimated. This amount is calculated as the greater value between *Current capacity units* (capacity units required to load balance the traffic) and *Fixed billable capacity units* (minimum capacity units kept provisioned).
5151
- **Failed Requests**. This value includes the 5xx codes that are generated from the Application Gateway and the 5xx codes that are generated from the backend. The request count can be further filtered to show count per each/specific backend pool-http setting combination.
5252
- **Fixed Billable Capacity Units**. The minimum number of capacity units kept provisioned as per the *Minimum scale units* setting in the Application Gateway configuration. One instance translates to 10 capacity units.

‎articles/backup/azure-file-share-backup-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: About Azure Files backup
33
description: Learn how to back up Azure Files in the Recovery Services vault
44
ms.topic: overview
5-
ms.date: 04/30/2025
5+
ms.date: 04/15/2025
66
ms.service: azure-backup
77
ms.custom:
88
- engagement-fy23

‎articles/backup/azure-kubernetes-service-backup-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-backup
66
ms.custom:
77
- ignite-2023
88
- ignite-2024
9-
ms.date: 04/30/2025
9+
ms.date: 04/15/2025
1010
author: jyothisuri
1111
ms.author: jsuri
1212
---
@@ -445,4 +445,4 @@ You incur charges for:
445445
>- [Prerequisites for Azure Kubernetes Service backup](azure-kubernetes-service-cluster-backup-concept.md).
446446
>- [Back up AKS using Azure PowerShell](azure-kubernetes-service-cluster-backup-using-powershell.md).
447447
>- Restore AKS using [Azure CLI](azure-kubernetes-service-cluster-restore-using-cli.md).
448-
>- [Well-architected design for AKS cluster protection](/azure/cloud-adoption-framework/scenarios/app-platform/aks/management#design-considerations-1).
448+
>- [Well-architected design for AKS cluster protection](/azure/cloud-adoption-framework/scenarios/app-platform/aks/management#design-considerations-1).

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: About the SAP HANA database backup on Azure VMs
33
description: In this article, you'll learn about backing up SAP HANA databases that are running on Azure virtual machines.
44
ms.topic: overview
5-
ms.date: 04/30/2025
5+
ms.date: 04/15/2025
66
ms.service: azure-backup
77
author: jyothisuri
88
ms.author: jsuri
@@ -107,4 +107,4 @@ Learn how to:
107107
- [Back up SAP HANA database snapshot instances on Azure VMs](sap-hana-database-instances-backup.md).
108108
- [Restore SAP HANA databases on Azure VMs](./sap-hana-db-restore.md).
109109
- [Manage SAP HANA databases that are backed up by using Azure Backup](./sap-hana-db-manage.md).
110-
- [Well-architected data reliability enhancement for SAP HANA](/azure/well-architected/sap/design-areas/data-platform#use-data-backups).
110+
- [Well-architected data reliability enhancement for SAP HANA](/azure/well-architected/sap/design-areas/data-platform#use-data-backups).

‎articles/batch/batch-compute-node-environment-variables.md

Lines changed: 44 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ The command lines executed by tasks on compute nodes don't run under a shell. Th
3434
> [!NOTE]
3535
> `AZ_BATCH_AUTHENTICATION_TOKEN` is deprecated and will be retired on September 30, 2024. See the [announcement](https://azure.microsoft.com/updates/azure-batch-task-authentication-token-will-be-retired-on-30-september-2024/) for details and alternative implementation.
3636
37-
3837
| Variable name | Description | Availability | Example |
3938
|-----------------------------------|--------------------------------------------------------------------------|--------------|---------|
4039
| AZ_BATCH_ACCOUNT_NAME | The name of the Batch account that the task belongs to. | All tasks. | mybatchaccount |
@@ -45,24 +44,59 @@ The command lines executed by tasks on compute nodes don't run under a shell. Th
4544
| AZ_BATCH_HOST_LIST | The list of nodes that are allocated to a [multi-instance task](batch-mpi.md) in the format `nodeIP,nodeIP`. | Multi-instance primary and subtasks. | `10.0.0.4,10.0.0.5` |
4645
| AZ_BATCH_IS_CURRENT_NODE_MASTER | Specifies whether the current node is the master node for a [multi-instance task](batch-mpi.md). Possible values are `true` and `false`.| Multi-instance primary and subtasks. | `true` |
4746
| AZ_BATCH_JOB_ID | The ID of the job that the task belongs to. | All tasks except start task. | batchjob001 |
48-
| AZ_BATCH_JOB_PREP_DIR | The full path of the job preparation [task directory](files-and-directories.md) on the node. | All tasks except start task and job preparation task. Only available if the job is configured with a job preparation task. | C:\user\tasks\workitems\jobprepreleasesamplejob\job-1\jobpreparation |
49-
| AZ_BATCH_JOB_PREP_WORKING_DIR | The full path of the job preparation [task working directory](files-and-directories.md) on the node. | All tasks except start task and job preparation task. Only available if the job is configured with a job preparation task. | C:\user\tasks\workitems\jobprepreleasesamplejob\job-1\jobpreparation\wd |
47+
| AZ_BATCH_JOB_PREP_DIR | The full path of the job preparation [task directory](files-and-directories.md) on the node. | All tasks except start task and job preparation task. Only available if the job is configured with a job preparation task. | [AZ_BATCH_JOB_PREP_DIR](#task-environment-variables-related-to-directory-location) |
48+
| AZ_BATCH_JOB_PREP_WORKING_DIR | The full path of the job preparation [task working directory](files-and-directories.md) on the node. | All tasks except start task and job preparation task. Only available if the job is configured with a job preparation task. | [AZ_BATCH_JOB_PREP_WORKING_DIR](#task-environment-variables-related-to-directory-location) |
5049
| AZ_BATCH_MASTER_NODE | The IP address and port of the compute node on which the primary task of a [multi-instance task](batch-mpi.md) runs. Do not use the port specified here for MPI or NCCL communication - it is reserved for the Azure Batch service. Use the variable MASTER_PORT instead, either by setting it with a value passed in through command line argument (port 6105 is a good default choice), or using the value AML sets if it does so. | Multi-instance primary and subtasks. | `10.0.0.4:6000` |
5150
| AZ_BATCH_NODE_ID | The ID of the node that the task is assigned to. | All tasks. | tvm-1219235766_3-20160919t172711z |
5251
| AZ_BATCH_NODE_IS_DEDICATED | If `true`, the current node is a dedicated node. If `false`, it is an [Azure Spot node](batch-spot-vms.md). | All tasks. | `true` |
5352
| AZ_BATCH_NODE_LIST | The list of nodes that are allocated to a [multi-instance task](batch-mpi.md) in the format `nodeIP;nodeIP`. | Multi-instance primary and subtasks. | `10.0.0.4;10.0.0.5` |
54-
| AZ_BATCH_NODE_MOUNTS_DIR | The full path of the node level [file system mount](virtual-file-mount.md) location where all mount directories reside. Windows file shares use a drive letter, so for Windows, the mount drive is part of devices and drives. | All tasks including start task have access to the user, given the user is aware of the mount permissions for the mounted directory. | In Ubuntu, for example, the location is: `/mnt/batch/tasks/fsmounts` |
55-
| AZ_BATCH_NODE_ROOT_DIR | The full path of the root of all [Batch directories](files-and-directories.md) on the node. | All tasks. | C:\user\tasks |
56-
| AZ_BATCH_NODE_SHARED_DIR | The full path of the [shared directory](files-and-directories.md) on the node. All tasks that execute on a node have read/write access to this directory. Tasks that execute on other nodes do not have remote access to this directory (it is not a "shared" network directory). | All tasks. | C:\user\tasks\shared |
57-
| AZ_BATCH_NODE_STARTUP_DIR | The full path of the [start task directory](files-and-directories.md) on the node. | All tasks. | C:\user\tasks\startup |
53+
| AZ_BATCH_NODE_MOUNTS_DIR | The full path of the node level [file system mount](virtual-file-mount.md) location where all mount directories reside. Windows file shares use a drive letter, so for Windows, the mount drive is part of devices and drives. | All tasks including start task have access to the user, given the user is aware of the mount permissions for the mounted directory. | [AZ_BATCH_NODE_MOUNTS_DIR](#environment-variables-related-to-directory-location) |
54+
| AZ_BATCH_NODE_ROOT_DIR | The full path of the root of all [Batch directories](files-and-directories.md) on the node. | All tasks. | [AZ_BATCH_NODE_ROOT_DIR](files-and-directories.md#batch-root-directory-location) |
55+
| AZ_BATCH_NODE_SHARED_DIR | The full path of the [shared directory](files-and-directories.md) on the node. All tasks that execute on a node have read/write access to this directory. Tasks that execute on other nodes do not have remote access to this directory (it is not a "shared" network directory). | All tasks. | [AZ_BATCH_NODE_SHARED_DIR](#environment-variables-related-to-directory-location) |
56+
| AZ_BATCH_NODE_STARTUP_DIR | The full path of the [start task directory](files-and-directories.md) on the node. | All tasks. | [AZ_BATCH_NODE_STARTUP_DIR](#environment-variables-related-to-directory-location) |
5857
| AZ_BATCH_POOL_ID | The ID of the pool that the task is running on. | All tasks. | batchpool001 |
59-
| AZ_BATCH_TASK_DIR | The full path of the [task directory](files-and-directories.md) on the node. This directory contains the `stdout.txt` and `stderr.txt` for the task, and the AZ_BATCH_TASK_WORKING_DIR. | All tasks. | C:\user\tasks\workitems\batchjob001\job-1\task001 |
58+
| AZ_BATCH_TASK_DIR | The full path of the [task directory](files-and-directories.md) on the node. This directory contains the `stdout.txt` and `stderr.txt` for the task, and the AZ_BATCH_TASK_WORKING_DIR. | All tasks. | [AZ_BATCH_TASK_DIR](#task-environment-variables-related-to-directory-location) |
6059
| AZ_BATCH_TASK_ID | The ID of the current task. | All tasks except start task. | task001 |
61-
| AZ_BATCH_TASK_SHARED_DIR | A directory path that is identical for the primary task and every subtask of a [multi-instance task](batch-mpi.md). The path exists on every node on which the multi-instance task runs, and is read/write accessible to the task commands running on that node (both the [coordination command](batch-mpi.md#coordination-command) and the [application command](batch-mpi.md#application-command). Subtasks or a primary task that execute on other nodes do not have remote access to this directory (it is not a "shared" network directory). | Multi-instance primary and subtasks. | C:\user\tasks\workitems\multiinstancesamplejob\job-1\multiinstancesampletask |
62-
| AZ_BATCH_TASK_WORKING_DIR | The full path of the [task working directory](files-and-directories.md) on the node. The currently running task has read/write access to this directory. | All tasks. | C:\user\tasks\workitems\batchjob001\job-1\task001\wd |
60+
| AZ_BATCH_TASK_SHARED_DIR | A directory path that is identical for the primary task and every subtask of a [multi-instance task](batch-mpi.md). The path exists on every node on which the multi-instance task runs, and is read/write accessible to the task commands running on that node (both the [coordination command](batch-mpi.md#coordination-command) and the [application command](batch-mpi.md#application-command). Subtasks or a primary task that execute on other nodes do not have remote access to this directory (it is not a "shared" network directory). | Multi-instance primary and subtasks. | [AZ_BATCH_TASK_SHARED_DIR](#task-environment-variables-related-to-directory-location) |
61+
| AZ_BATCH_TASK_WORKING_DIR | The full path of the [task working directory](files-and-directories.md) on the node. The currently running task has read/write access to this directory. | All tasks. | [AZ_BATCH_TASK_WORKING_DIR](#task-environment-variables-related-to-directory-location) |
6362
| AZ_BATCH_TASK_RESERVED_EPHEMERAL_DISK_SPACE_BYTES | The current threshold for disk space upon which the VM will be marked as `DiskFull`. | All tasks. | 1000000 |
6463
| CCP_NODES | The list of nodes and number of cores per node that are allocated to a [multi-instance task](batch-mpi.md). Nodes and cores are listed in the format `numNodes<space>node1IP<space>node1Cores<space>`<br/>`node2IP<space>node2Cores<space> ...`, where the number of nodes is followed by one or more node IP addresses and the number of cores for each. | Multi-instance primary and subtasks. |`2 10.0.0.4 1 10.0.0.5 1` |
6564

65+
66+
> [!Important]
67+
> Exact values for paths for Environment Variables are considered implementation details and are subject to change.
68+
> Use the Batch provided Environment Variables instead of attempting to construct raw path representations.
69+
70+
## Environment variables related to directory location
71+
72+
The following table specifies the values of each environment variable value postfix after the AZ_BATCH_NODE_ROOT_DIR value, see [AZ_BATCH_NODE_ROOT_DIR](files-and-directories.md#batch-root-directory-location) for more information.
73+
74+
|Environment Variable Name|Environment Variable Value Directory Postfix|
75+
|:---|:---|
76+
|AZ_BATCH_NODE_STARTUP_DIR|`startup`|
77+
|AZ_BATCH_NODE_SHARED_DIR|`shared`|
78+
|AZ_BATCH_NODE_MOUNTS_DIR|`fsmounts`|
79+
80+
## Task environment variables related to directory location
81+
82+
The job directories are different between [single-run job](jobs-and-tasks.md#jobs) and [job schedule](jobs-and-tasks.md#scheduled-jobs). The following table specifies the values of job directory in single-run job and job schedule.
83+
84+
|Job Type|Job Directory Value Postfix after AZ_BATCH_NODE_ROOT_DIR|
85+
|:---|:---|
86+
|Job|`workitems\{job name}\job-1`|
87+
|Job Schedule|`workitems\{job schedule name}\{job name}`|
88+
89+
The following table specifies the values of each environment variable value postfix after the job directory.
90+
91+
|Environment Variable Name|Environment Variable Value Directory Postfix After Job Directory|
92+
|:---|:---|
93+
|AZ_BATCH_TASK_WORKING_DIR|`{task name}\wd`|
94+
|AZ_BATCH_TASK_DIR|`{task name}`|
95+
|AZ_BATCH_TASK_SHARED_DIR|`{task name}`|
96+
|AZ_BATCH_JOB_PREP_DIR|`{job prepration task name}`|
97+
|AZ_BATCH_JOB_PREP_WORKING_DIR|`{job prepration task name}\wd`|
98+
99+
66100
## Next steps
67101

68102
- Learn how to [use environment variables with Batch](jobs-and-tasks.md#environment-settings-for-tasks).

‎articles/batch/batch-pool-vm-sizes.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,9 @@ node state. Support for `unverified` images isn't guaranteed.
8282
> [PowerShell](/powershell/module/az.batch/get-azbatchsupportedimage), or [Azure CLI](/cli/azure/batch/pool/supported-images).
8383
> For more information, see the [Batch best practices guide](best-practices.md) regarding Batch pool VM image selection.
8484
85+
> [!TIP]
86+
> The value of the `AZ_BATCH_NODE_ROOT_DIR` compute node environment variable is dependent upon if the VM has a local temporary disk or not. See [Batch root directory location](files-and-directories.md#batch-root-directory-location) for more information.
87+
8588
## Next steps
8689

8790
- Learn about the [Batch service workflow and primary resources](batch-service-workflow-features.md) such as pools, nodes, jobs, and tasks.

‎articles/batch/files-and-directories.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,19 @@ The root directory contains the following directory structure:
3939
> [!IMPORTANT]
4040
> When a node is removed from the pool, all of the files that are stored on the node are removed.
4141
42+
## Batch root directory location
43+
44+
The value of the `AZ_BATCH_NODE_ROOT_DIR` compute node environment variable will be determined by the VM size and the presence of a local temporary disk.
45+
46+
|Local Temporary Disk Present|Operating System Type|`AZ_BATCH_NODE_ROOT_DIR` Value|
47+
|:---|:---|:---|
48+
|No|Linux|`/opt/batch/data`|
49+
|Yes|Linux|`/mnt/batch` or `/mnt/resource/batch`|
50+
|No|Windows|`C:\batch\data`|
51+
|Yes|Windows|`D:\batch`|
52+
53+
These environment variable values are implementation details and should not be considered immutable. As these values may change at any time, the use of environment variables instead of hardcoding the value is recommended.
54+
4255
## Next steps
4356

4457
- Learn about [error handling and detection](error-handling.md) in Azure Batch.

0 commit comments

Comments
 (0)