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/sap/workloads/dbms-guide-ibm.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ For information about supported SAP products and Azure VM types, refer to SAP No
48
48
## IBM Db2 for Linux, UNIX, and Windows Configuration Guidelines for SAP Installations in Azure VMs
49
49
### Storage Configuration
50
50
For an overview of Azure storage types for SAP workload, consult the article [Azure Storage types for SAP workload](./planning-guide-storage.md)
51
-
All database files must be stored on mounted disks of Azure block storage (Windows: NTFS, Linux: xfs, if [supported](https://www.ibm.com/support/pages/file-systems-recommended-db2-linux-unix-and-windows) for the DB2 version, or ext3).
51
+
All database files must be stored on mounted disks of Azure block storage (Windows: NTFS, Linux: xfs, [supported](https://www.ibm.com/support/pages/file-systems-recommended-db2-linux-unix-and-windows) for the DB2 versions higher than 11.1, or ext3).
52
52
53
53
Remote shared volumes like the Azure services in the listed scenarios are **NOT** supported for Db2 database files:
54
54
@@ -60,7 +60,7 @@ Remote shared volumes like the Azure services in the listed scenarios are suppor
60
60
61
61
* Hosting Linux guest OS based Db2 data and log files on NFS shares hosted on Azure NetApp Files is supported!
62
62
63
-
Using disks based on Azure Page BLOB Storage or Managed Disks, the statements made in [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) apply to deployments with the Db2 DBMS as well.
63
+
If you are using disks based on Azure Page BLOB Storage or Managed Disks, the statements made in [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) apply to deployments with the Db2 DBMS as well.
64
64
65
65
As explained earlier in the general part of the document, quotas on IOPS throughput for Azure disks exist. The exact quotas are depending on the VM type used. A list of VM types with their quotas can be found [here (Linux)](../../virtual-machines/sizes.md) and [here (Windows)](../../virtual-machines/sizes.md).
66
66
@@ -81,7 +81,7 @@ IBM Db2 LUW 11.5 released support for 4-KB sector size. Though you need to enabl
81
81
82
82
For older Db2 versions, a 512 Byte sector size must be used. Premium SSD disks are 4-KB native and have 512 Byte emulation. Ultra disk uses 4-KB sector size by default. You can enable 512 Byte sector size during creation of Ultra disk. Details are available [Using Azure ultra disks](../../virtual-machines/disks-enable-ultra-ssd.md#deploy-an-ultra-disk---512-byte-sector-size). This 512 Byte sector size is a prerequisite for IBM Db2 LUW versions lower than 11.5.
83
83
84
-
On Windows using Storage pools for Db2 storage paths for `log_dir`, `sapdata` and `saptmp` directories, you must specify a physical disk sector size of 512 Byte. When using Windows Storage Pools, you must create the storage pools manually via command line interface using the parameter `-LogicalSectorSizeDefault`. For more information, see [New-StoragePool](/powershell/module/storage/new-storagepool).
84
+
On Windows using Storage pools for Db2 storage paths for `log_dir`, `sapdata` and `saptmp` directories, you must specify a physical disk sector size of 512 Bytes. When using Windows Storage Pools, you must create the storage pools manually via command line interface using the parameter `-LogicalSectorSizeDefault`. For more information, see [New-StoragePool](/powershell/module/storage/new-storagepool).
85
85
86
86
## Recommendation on VM and disk structure for IBM Db2 deployment
87
87
@@ -145,7 +145,7 @@ The usage of NFS v4.1 volumes based on Azure NetApp Files (ANF) is supported wit
145
145
146
146
A fifth potential volume could be an ANF volume that you use for more long-term backups that you use to snapshot and store the snapshots in Azure Blob store.
147
147
148
-
The configuration could look like shown here
148
+
The configuration could look like shown here:
149
149
150
150

151
151
@@ -246,7 +246,7 @@ For the disks containing the Db2 storage paths for your sapdata and saptmp direc
246
246
All other general areas like Azure Availability Sets or SAP monitoring apply as described in the document [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) for deployments of VMs with the IBM Database as well.
247
247
248
248
## Next steps
249
-
Read the article
249
+
Read the article:
250
250
251
251
-[Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md)
0 commit comments