How To Create ASM Diskgroups using NFS/NAS Files?
(Doc ID 731775.1)
Last updated on MARCH 22, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
The current document shows an example to create ASM diskgroups using NAS/NFS files.
Note: Caution should be exercised when considering using NFS storage, in an Oracle database environment, with ASM. In general, such configurations should be avoided or at least carefully considered. The issue is that to prevent data corruption, NFS file systems must be hard-mounted. Hard mounting means that the database or an ASM instance must wait indefinitely when an NFS server, or the communications link it operates over, becomes unavailable. This means that ASM cannot effectively provide data mirroring.
Situations where NFS on ASM may be a reasonable option include:
Situations where NFS on ASM may be a reasonable option include:
- Using NFS for an ASM Quorum Failure Group, as is often done with Extended Clusters. NFS on Quorum Failure Groups with 11.2.0.4 or later, does not need, or should not use hard NFS mounts.
- Situations where reliable access to NFS service can be assured.
- When using NFS storage only for an External Redundancy Diskgroup.
- Situations where the lost of ASM file access for an extended period is not critical.
ASM is completely supported on NAS (e.g. NFS filesystem on NetApps).
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| ASM is completely supported on NAS (e.g. NFS filesystem on NetApps). |
| Solution |
| Community Discussions |