Highlighted

Veritas Backup changes directories ownership

Hi, 

After installing NetBackup agernt on Ubuntu 18.04.1, we found out that it changed folder structure.

# cat /usr/openv/netbackup/bin/version
NetBackup-Debian2.6.32 8.1.2

It modifietd  ownership of some directories  /etc, /opt, /usr  etc... from root user to  random number '437'  and root group to 'uuidd' group, on all Ubuntu systems.

# ls -la /
drwxr-xr-x  91  437 uuidd  4096 Aug 30 09:13 /etc
drwxr-xr-x   7  437 uuidd  4096 Jul 12 12:00 /opt
drwxr-xr-x  11  437 uuidd  4096 Jul 23  2018 /usr

437 uuidd   /usr 
437 uuidd   /usr/openv 
437 uuidd   /usr/openv/lib 
437 uuidd   /usr/openv/lib/ost-plugins 
437 uuidd   /usr/openv/lib/ost-plugins/libstspipdMT.so 
437 uuidd   /usr/openv/lib/ost-plugins/libstspipd.so 
437 uuidd   /usr/openv/lib/ost-plugins/mtstrm.conf 
437 uuidd   /usr/openv/pdde 
437 uuidd   /etc 
437 uuidd   /etc/pdregistry.cfg 
437 uuidd   /etc/init.d 
437 uuidd   /etc/init.d/pdde-spws.sh 
437 uuidd   /etc/init.d/pdde-storage 
437 uuidd   /etc/init.d/velocity-storage 
437 uuidd   /opt 
437 uuidd   /opt/pdshared 
437 uuidd   /opt/pdde 
437 uuidd   /opt/pdde/pddeuninstall.sh 
437 uuidd   /opt/pdag : unexpected operator
437 uuidd   /usr 
437 uuidd   /usr/openv 
437 uuidd   /usr/openv/lib 
437 uuidd   /usr/openv/lib/ost-plugins 
437 uuidd   /usr/openv/lib/ost-plugins/libstspipdMT.so 
437 uuidd   /usr/openv/lib/ost-plugins/libstspipd.so 
437 uuidd   /usr/openv/lib/ost-plugins/mtstrm.conf 
437 uuidd   /usr/openv/pdde 
437 uuidd   /etc 
437 uuidd   /etc/pdregistry.cfg 
437 uuidd   /etc/init.d 
437 uuidd   /etc/init.d/pdde-spws.sh 
437 uuidd   /etc/init.d/pdde-storage 
437 uuidd   /etc/init.d/velocity-storage 
437 uuidd   /opt 
437 uuidd   /opt/pdshared 
437 uuidd   /opt/pdde 
437 uuidd   /opt/pdde/pddeuninstall.sh 
437 uuidd   /opt/pdag 

Proper configuration should be:

# ls -la /
drwxr-xr-x  91  root root  4096 Aug 30 09:13 etc
drwxr-xr-x   7  root root  4096 Jul 12 12:00 opt
drwxr-xr-x  11  root root  4096 Jul 23  2018 usr

 

I will apreciate any help or hints as currently it breaks our whole infrastructure.

Thank you and Regards

700grm

Tags (2)
6 Replies

Re: Veritas Backup changes directories ownership

Can't offer any reason or hints, but I thought I'd test it too using NetBackup Client v8.1.2 (from CLIENTS2.tar.gz) on a guest VM of Ubuntu Server 18.04.3 LTS.  I got similar result of ownership of etc and opt and usr etc changing to owners 437:uuidd, but I don't understand what you mean when you list many more folder names as having no owner.

What I do see is that the elements of the client install related to "pdde" and client-side dedupe seem to be the culprit, i.e. in whichever folder a file related to pdde/dedupe has needed to be installed/copied-to then the installer appears to have set the file and reset the folder owner to 437:uuidd, whereas all other folders and files related to traditional elements of the NetBackup Client install are still owned by root:root.

I think you've found a bug in the installer.

Re: Veritas Backup changes directories ownership

I have created my custom script that checks ownership, when owner is not present it just print "has no owner", basically it mean 437:uuidd. I update command output in more readable way now.

If this is the bug, how it is passible that no one noticed it till now?

Thx

Re: Veritas Backup changes directories ownership

@700grm 

Best to log a Support call with Veritas.

Please let us know what they say. 

Re: Veritas Backup changes directories ownership

not that it's any comfort - but I just re-tested with a fresh install of NetBackup Client v7.7.3 - and no problems there, everything still owned by root:root as expected.

Re: Veritas Backup changes directories ownership

tested several client versions, and it's only the v8.1.2 installer that goofs :

7.7.3  ok
8.0     ok
8.1     ok
8.1.1  ok
8.1.2  bad
8.2     ok

Re: Veritas Backup changes directories ownership

@sdo You did a great job testing it, acording to your results looks like they have fixed this bug in latest releases. And there  is no reason for openning support request with Veritas.

Thx