Data Service Restrictions

This section describes restrictions for specific data services. There are no restrictions that apply to all data services.

Future Sun Cluster Release Notes will not include data service restrictions that apply to specific data services. However, Sun Cluster Release Notes will document any data service restrictions that apply to all data services.

For additional data service restrictions that apply to specific data services, see the Sun Cluster 3.0 12/01 Data Services Installation and Configuration Guide.

Sun Cluster HA for Oracle

• Adhere to the Oracle Parallel Fail Safe/Real Application Clusters Guard option of Oracle Parallel Server/Real Application Clusters because you cannot change hostnames after you install Sun Cluster software.

  For more information on this hostnames/node names restriction, see the Oracle Parallel Fail Safe/Real Application Clusters Guard documentation.

Sun Cluster and NetBackup Restrictions

• If the VERITAS NetBackup client is a cluster, only one logical host can be configured as the client because there is only one bp.conf file.

• If the NetBackup client is a cluster and if one of the logical hosts on the cluster is configured as the NetBackup client, NetBackup cannot back up the physical hosts.

Sun Cluster HA for NetBackup Restrictions

• On the cluster running the master server, the master server is the only logical host that can be backed up.

• Backup media cannot be attached to the master server, so one or more media servers are required.

Sun Cluster 3.0 HA for NFS Restrictions

• No Sun Cluster node may be an NFS client of a Sun Cluster HA for NFS‐exported file system being mastered on a node in the same cluster. Such cross-mounting of Sun Cluster HA for NFS is prohibited. Use the cluster file system to share files among cluster nodes.

• Applications running locally on the cluster must not lock files on a file system exported via NFS. Otherwise, local blocking (for example, flock(3UCB) or fcntl(2)) might interfere with the ability to restart the lock manager (lockd). During restart, a blocked local process may be granted a lock which may be intended to be reclaimed by a remote client. This would cause unpredictable behavior.

• Sun Cluster HA for NFS requires that all NFS client mounts be “hard” mounts.

• For Sun Cluster HA for NFS, do not use hostname aliases for network resources. NFS clients mounting cluster file systems using hostname aliases might experience statd lock recovery problems.

• Sun Cluster 3.0 software does not support Secure NFS or the use of Kerberos with NFS, in particular, the secure and kerberos options to the share_nfs(1M) subsystem. However, Sun Cluster 3.0 software does support the use of secure ports for NFS by adding the entry set nfssrv:nfs_portmon=1 to the /etc/system file on cluster nodes.