This discussion is archived
4 Replies Latest reply: May 21, 2013 7:54 AM by user12063110 RSS

More information on "Error: multi-linked directory"

user12063110 Newbie
Currently Being Moderated
What does "Error: multi-linked directory" indicate, and how does one correct for this error? This error is from OSB 10.4.0.2.0.

I have found this in some of the logs for my servers' backups. Some of the directories are for NFS shares, however it is not only NFS shared directories. My concern is that when I attempt a test restore in one of the affected directories, there is no restore option. This seems to indicate that none of the data there is being backed up, which is a problem. This also begs the question - if whole directories are not being backed up due to errors, why don't those servers show up as having failed to back up successfully? It is VERY FRUSTRATING to have to look through the logs for "successful" backups in order to find these errors. It will be worse when customers go to restore from their "successful" backups to find that critical directories may have been skipped.

I found two unanswered posts from Dec 6th 2010 and Nov 9th 2010 on this forum with the same question, so I am not the only user encountering this error.

Please provide more information about this "multi-linked directory" error and why partially failed backups appear as successful backups with warnings.
  • 1. Re: More information on "Error: multi-linked directory"
    rdoogan Journeyer
    Currently Being Moderated
    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.

    Thanks

    Rich
  • 2. Re: More information on "Error: multi-linked directory"
    user12063110 Newbie
    Currently Being Moderated
    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):

    df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-root
    2.0G 251M 1.7G 14% /
    /dev/sda1 190M 13M 168M 8% /boot
    none 4.0G 0 4.0G 0% /dev/shm
    /dev/mapper/VolGroup00-home
    20G 3.4G 16G 19% /home
    /dev/mapper/VolGroup00-opt
    25G 568M 23G 3% /opt
    /dev/mapper/VolGroup00-tmp
    50G 647M 47G 2% /tmp
    /dev/mapper/Data_vg-u01
    79G 67G 8.7G 89% /u01
    /dev/mapper/Data_vg-u02
    24G 524M 22G 3% /u02
    /dev/mapper/Data_vg-u03
    24G 5.3G 18G 24% /u03
    /dev/mapper/Data_vg-u04
    20G 129M 19G 1% /u04
    /dev/mapper/Data_vg-u05
    20G 14G 5.1G 73% /u05
    /dev/mapper/Data_vg-u06
    20G 13G 6.4G 66% /u06
    /dev/mapper/VolGroup00-usr
    5.0G 2.3G 2.4G 49% /usr
    /dev/mapper/VolGroup00-usrlocal
    124M 82M 36M 70% /usr/local
    /dev/mapper/VolGroup00-var
    9.9G 1.3G 8.2G 14% /var
    /dev/mapper/Data_vg-subappname
    992M 11M 930M 2% /u01/subappname
    /u01/subappname 992M 11M 930M 2% /exports/subappname
    /u01/appname/shared 79G 67G 8.7G 89% /exports/shared
  • 3. Re: More information on "Error: multi-linked directory"
    rdoogan Journeyer
    Currently Being Moderated
    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.

    Thanks

    Rich
  • 4. Re: More information on "Error: multi-linked directory"
    user12063110 Newbie
    Currently Being Moderated
    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.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points