UNIX/Linux Scenario Considerations

Consider the following when creating UNIX/Linux scenarios:

• A directory can be present in only one scenario.
• For Network File Sharing (NFS) server, install the Engine on the NFS server and make sure the exported directory resides in the root directory.

Notes:

• For NFS v4, make sure to set the fsid option in /etc/exports. Also, help ensure that each exported directory has a different fsid value (1-255) if you have multiple exported directories. Example:

cat /etc/exports

/usr/nfsroot *

(rw,sync,no_root_squash,nohide,crossmnt,fsid=5)

• If Arcserve Continuity Suite root directory is inside NFS exported directory, refer to the KB article.
• NFS support is not provided with SUSE 11.
• NFS Client replication
• Arcserve Continuity Suite does not replicate changes made on NFS Server, including changes made from other NFS Clients while the scenario is running.
• NFSv4 is only supported on SUSE 12, RHEL 7, or Oracle Linux 7 or later.
• NFSv4 ACLs only replicate to other NFSv4 clients that support NFSv4 ACLs. In such cases, the version and configuration of the NFS Client and Server should be identical between the Master and the Replica.
• For UNIX-to-UNIX replication, UID, GID, and ACLs, the associated name mapping is not replicated. The name resolution is stored independently in LDAP, /etc/passwd, /etc/group or another site-managed authentication scheme.
• For Linux-to-Linux replication of ACLs and extended attributes, ACLs need to be supported and enabled on the underlying file system. When ACL support on the replica file system is not enabled, ACLs are lost.
• For Windows-to-UNIX replication, Windows ACLs are lost.
• For UNIX-to-Windows replication, UID, GUID, symbolic links, and hard links are lost.
• File names on Windows are not case-sensitive, so conflicts are possible.
• Root directories cannot be intersected in different scenarios; that is, you cannot create a second Replication scenario using the same master directory and root directory used for your first Replication scenario.
• For the user credentials property of master and replica, you need to input the username and password of master and replica that has full control permission to the parent directory available in the root directory.
• HA parameters on a UNIX/Linux host:
  • System Information: The AD Domain Controller and MS Cluster properties are not supported so the values are always set to No. For the DNS Server property, only the BIND server process named is checked; if named is running, then the DNS Server property is set to Yes, otherwise it is set to No.
  • Network Configuration: NetBIOS name is not supported.
• Hard links are now supported. Hard links cannot be created between different file systems or between root directories on the same file system.
• Running scenarios concurrently from different non-global zones on Solaris is not supported. The work-around is to create multiple scenarios from the Solaris global zone and managing all scenario from there.
• Note: Make sure that all directories in local zones are accessible from the Solaris global zone.