Has anyone found a way around this?
xxxx-mbpro:NetBackup_7.6.1_CLIENTS1 root# ./install Symantec Installation Script Copyright 1993 - 2014 Symantec Corporation, All Rights Reserved. Installing NetBackup Client Software Please review the SYMANTEC SOFTWARE LICENSE AGREEMENT located on the installation media before proceeding. The agreement includes details on the NetBackup Product Improvement Program. For NetBackup installation and upgrade information specific to your platform and to find out if your installed EEBs or hot fixes are contained in this release, check out the Symantec Operations Readiness Tools (SORT) Installation and Upgrade Checklist and Hot fix and EEB Release Auditor, respectively, at https://sort.symantec.com/netbackup. Do you wish to continue? [y,n] (y) y Checking for required system conditions... Checking for recommended system conditions... ok nb_761_hotfix_auditor: No potential for regression of hotfixes or EEBs was detected. Do you want to install the NetBackup client software for this client? [y,n] (y) y This package will install MACINTOSH/MacOSX10.6 client. This package will install NetBackup client 7.6.1. Enter the name of the NetBackup master server : yyyy Would you like to use "xxxx-mbpro.local" as the configured name of the NetBackup client? [y,n] (y) n Enter the name of this NetBackup client : xxxx-mbpro Client binaries are located in /Users/xxxx/Temp/a/NetBackup_7.6.1_CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/MACINTOSH/MacOSX10.6. Saving client binaries for MACINTOSH/MacOSX10.6. mkdir: /usr/openv: Operation not permitted chmod: /usr/openv: No such file or directory chgrp: /usr/openv: No such file or directory mkdir: /usr/openv: No such file or directory chmod: /usr/openv/pack: No such file or directory chgrp: /usr/openv/pack: No such file or directory mkdir: /usr/openv/pack: No such file or directory chmod: /usr/openv/pack/NB_CLT_7.6.1: No such file or directory chgrp: /usr/openv/pack/NB_CLT_7.6.1: No such file or directory mkdir: /usr/openv/pack/NB_CLT_7.6.1: No such file or directory chmod: /usr/openv/pack/NB_CLT_7.6.1/save: No such file or directory chgrp: /usr/openv/pack/NB_CLT_7.6.1/save: No such file or directory tar: Failed to open '/usr/openv/pack/NB_CLT_7.6.1/save/NB_CLT_22.214.171.124015_203229.tar' ERROR: tar failed. Aborting... ERROR: Saving client binaries for MACINTOSH/MacOSX10.6 failed. Aborting ... ERROR: A failure was detected running /Users/xxxx/Temp/a/NetBackup_7.6.1_CLIENTS1/NBClients/anb/Clients/usr/op env/netbackup/client/MACINTOSH/MacOSX10.6/cp_to_client yyyy xxxx-mbpro /tmp/in stall_trace.15795 File /tmp/install_trace.15795 contains a trace of this install. That file can be deleted after you are sure the install was successful.
Solved! Go to Solution.
The install above was done whilst running as root!
And this fails too!
xxxx-mbpro:tmp root# cd /usr xxxx-mbpro:usr root# id uid=0(root) gid=0(wheel) groups=0(wheel),1(daemon),2(kmem),3(sys),...etc.... xxxx-mbpro:usr root# mkdir openv mkdir: openv: Operation not permitted
...so it's definitely an OS issue.
Just wondering whether, and hoping that, someone has worked out what to do... and is willing to share their workaround?
I found the same page, but you replied before I completed my testing, so you win the points!
From that page, I did the following which worked, and I now have a backup running...
1) Restart OSX into recovery mode.
2) When booted into recovery mode start Terminal, and enter:
3) Reboot normally.
4) When back in normal OSX, start Terminal and enter commands:
sudo su - cd /usr mkdir openv chown root:sys openv chmod 775 openv
4) Reboot into recovery mode again.
5) When in recovery mode, start Terminal and enter:
6) Reboot back in to normal OSX.
7) Install NetBackup Client as you normally would via root.
8) Run your usual bptestbpcd and/or test backups.
And it would appear that the NetBackup installation script has changed the perms on the openv folder anyway:
hostname:usr root# ls -lash total 8 ... 0 drwxr-xr-x 16 root kmem 544B Oct 20 21:18 openv
...and so in the steps above, perhaps the chown and chmod instructions should be:
4) When back in normal OSX start Terminal and enter the commands:
sudo su - cd /usr mkdir openv chown root:kmem openv chmod 755 openv
I must say that this is really just a workaround!!! and not a FIX!
Veritas should make the installation go to a non SIP protected folder like /usr/local/openv .
Hope veritas will make a new installer soon..
Also this is a message from more than a year ago!! Come on!! Veritas!!! you need to keep up with the technology!!!