Managing Scenarios › UNIX/Linux Scenario Considerations

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), V4 is not supported. You should install the Engine on the NFS server and make sure the exported directory resides in the root directory.
• NFS support is not provided with SUSE 11.
• 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.
• 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.