To ensure that all data on a shared disk is highly available,
you configure how file systems are mounted in System
Automation for Multiplatforms.
Before you begin
To be informed about any potential limitations with your operating
system, see the information about known issues in
Microsoft Windows shared
disk environments on the IBM® Support
site.
About this task
You use this configuration only as part of standby configurations
where a single node is running. You cannot use this method for product
features that require a shared directory for multiple nodes. If the
file system is not one of the supported types, such as ext2, ext3,
or reiserfs, then it cannot be automatically harvested by
System
Automation for Multiplatforms,
and the
IBM.AgFilesystem resource must be added
manually.
Procedure
- To manually add the resource, run the following command: mkrsrc
IBM.AgFileSystem Name=shared resource nameDeviceName=name
of deviceVfs=file system typeMountPoint=mountpointNodeNameList={list
of nodes separated by commas} For
example, enter mkrsrc IBM.AgFileSystem Name=wasshared
DeviceName=/dev/sdb1 Vfs=NFS MountPoint=/wasshared NodeNameList={tpaeha01,tpaeha02}
- Ensure that the System
Automation for Multiplatforms Linux
policies are installed on all nodes that require the mount.
- From the /usr/sbin/rsct/sapolicies/ directory,
open the local_mount.def file and edit the mount
point and node name parameters.
- From the /etc/fstab directory, ensure
that the noauto parameter is set for the file
system that you want to automate.
- Ensure that a System
Automation for Multiplatforms domain
was created and is online with all the required nodes defined.
- To create the application resources, run the following
command: mkrsrc -f /usr/sbin/rsct/sapolicies/local_mount/local_mount.def
IBM.Application
- To add the application resource to the resource group,
run the following command: addrgmbr -g rgname IBM.Application:applicationname For example, enter addrgmbr -g was IBM.Application:wasshard-rs
- To create a managed relationship dependency and restrict
the mount to the active node that is based on Service IP, run the
following command: mkrel -p DependsOn -S IBM.Application:wasshard-rs
-G IBM.ServiceIP:wasipwasmount_dependson_ip The variable value wasip represents the assigned
name of a resource that was created for the Service IP.
- To ensure the applications that require the mounted drive
have a relationship defined to depend on the mount, run the following
command: mkrel -p DependsOn -S IBM.Application:SA-was-na
-G IBM.Application:wasshard-rs nodeagent_dependson_share