Symptoms:

You are getting the following messages on your AIX server backup:

gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /home gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /var gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /tmp gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /opt gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /usr gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /proc gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /u30 gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /u99 gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /users gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /orascratch gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /u10 gsoudv1_p1-FileIO: Filesystem change prohibited. Will not descend into /u20

But says they are not symbolic links, they are file systems. Is this strictly a permissions issue? Is that handled differently with AIX?

Resolution:

They are separate filesystems, and while they may not be symbolic links, they are "mount points". They most likely only specified the "/" filesystem. The other filesystems are "mounted" onto the directories they listed, so the "home" filesystem is mounted on "/home".

This is typical for all variations of Unix and Linux. Each separate filesystem that they want to backup should be specified separately in the Starting Files and Directories list. You may not want to backup /tmp for example, and certainly not /proc. The list below serves as a good starting point for the the Starting Files and Directories, and here is our initial recommendation:

/ /home /var /opt /usr /u30 /u99 /users /u10 /u20

Note that since "/" is specified, the Filesystem change prohibited. Will not descend into message will still be shown. If you do not want to see this, then:

  • The "/" Starting Directories and Files entry should be specified separately (not in a new FileSet or Client, just an additional Starting Directories and Files entry)
  • Each filesystem can then be specified in an Exclude matcher for Wild Directory, on the "/" Starting Directory and File
  • Below is an example fileset where the parent directory (like "/" in the customer example) is "/tmp/hithere". It has child directories "fs1", "fs2", and "fs3" that we want to backup, and we do not want complaints about: