This content has been marked as final. Show 4 replies
It means the folder exists as another mount point on the machine and the backup was captured via that. Can you confirm the OS this is for, and also post the output from "df -h" so we can check.
Presumably you mean the OS and df output of the client, correct?
The client is RHEL 4.7. The OSB server is OEL 6.4.
The df -h output (redacted using "appname" and "subappname", per employer security policy):
Filesystem Size Used Avail Use% Mounted on
2.0G 251M 1.7G 14% /
/dev/sda1 190M 13M 168M 8% /boot
none 4.0G 0 4.0G 0% /dev/shm
20G 3.4G 16G 19% /home
25G 568M 23G 3% /opt
50G 647M 47G 2% /tmp
79G 67G 8.7G 89% /u01
24G 524M 22G 3% /u02
24G 5.3G 18G 24% /u03
20G 129M 19G 1% /u04
20G 14G 5.1G 73% /u05
20G 13G 6.4G 66% /u06
5.0G 2.3G 2.4G 49% /usr
124M 82M 36M 70% /usr/local
9.9G 1.3G 8.2G 14% /var
992M 11M 930M 2% /u01/subappname
/u01/subappname 992M 11M 930M 2% /exports/subappname
/u01/appname/shared 79G 67G 8.7G 89% /exports/shared
Which folder is getting the multi-linked error?
From this listing I would say that /exports/subappname is the same filesystem as /u01/subappname and both of these are potentially backed up via the /u01 in the dataset, which would explain the warning you are seeing.
That makes sense, although it seems to only be an issue with NFS exports. I have excluded /exports, which cleared up the issue.
Thank you for your response.