Backup algorithm needs to be changed to work OK for a chrooted environment

Customer expect that all files will to be backed up. This works under RHEL 6 buts makes trouble in a chrooted environment under RHEL 7.

It seems that RedHat in RHEL 7 has changed the way they deal with a directory that is on one side part of the “/” filesystem (as many other directories) and on the other side is part of a chroot environment.

In RHEL 6 only the “named” process (running “chrooted”) sees /var/named/chroot and subdirectories in a special way, but the TSM BA client does not. On RHEL 6 TSM BA client does not handle /var/named/chroot and subdirectories diffenrently than any other subdirectory of”/”.

In RHEL 7 this is no longer true.
In RHEL 7 both, the named process and the TSM BA client see /var/named/chroot and subdirectories in a special way.


(Now a statement, that I got from TSM L3 support)

The Backup algorithm (TSM b/a client) needs to be changed to work OK for the following chrooted environment:

This design doesn't expect to encounter an ordinary (per the system mount table) directory ("/var/named" in our case) which seems to be located in one file system ("/" the root file system), but in fact it is hard linked with the mount point of a different file system
("/var/named/chroot/var/named" file system).

The local fix is to backup the "hard-linked" directory ('/var/named') contents via it is "native" mount point path ('/var/named/chroot/var/named') i.e. run: 'dsmc incr /var/named/chroot/var/named' or 'dsmc sele /var/named/chroot/var/named/ -su=yes' or whatever the customer needs to back up underneath the '/var/named/chroot/var/named' mount point.