/ifs/data is kind of a toy example that materializes into real production -- and then there is Isilon_Support inside it. "Single namespace, single filesystem" thought too simple...  Great practise, in particular with SyncIQ, is to use /ifs/ /.../  You might not be able to change that while in production, so why not move Isilon_Support out of the path, and create a symlink, e.g.:  /ifs/data/Isilon_Support -> /ifs/localstuff/Isilon_Support  Isilon_Support will be accessed only from within the cluster, never through SMB or NFS, so that symlink can always be followed.  makes sense?  -- Peter
Hi,  Our customer has placed their production data folders under the /ifs/data directory on their cluster.  Everything is working fine, but when setting up SyncIQ then, they excluded /ifs/data/Isilon_Support from the sync.  Which again, is working OK, but we note that with excluded directories, we can't perform a SyncIQ failback (which makes sense).  Question:  Has anyone experience a similar configuration, or can you tell us of any negative ramifications of allowing /ifs/data/Isilon_Support to sync over to a remote cluster?  We see notes which allude to the best practice of avoiding /ifs/data for production folders, but the Admin Guide actually has several examples of its use, for instance, in the appended discussion of NDMP backups.    Thanks, Don ======================= from p. 152 of the Admin Guide: . . For example, assume that you are backing up the /ifs/data directory, and you include the following directories: /ifs/data/media/music /ifs/data/media/movies . . .
use of /ifs/data for production - SyncIQ ramifications?