pre-command with python script [TTY - ERROR]
Hello, I'm trying to run pre-command/post-command with execution of python script on remote linux server. But I can see many error on agent RALUS log (/var/VRTSralus/beremote.service.log): sudo: sorry, you must have a tty to run sudo sudo: sorry, you must have a tty to run sudo sudo: sorry, you must have a tty to run sudo When I'm trying to run my python script localy on my linux server its works well. I think the problem come from in the fact of the execution of the script is made by a real user when i do it in local (manually) and not from backup exec pre-command/post-command. By curiosity i've try to execute the python script from an other linux server through SSH Like this : ssh XXXX@XXXXX 'symantec-script/test.py -c' sudo: sorry, you must have a tty to run sudo So can you tell me if we can force the pseudo tty allocation from symantec backup exec ? or the only workaround is to comment on my sudoers files the options : #Defaults requiretty Do you know an other workaround on symantec side ? like an argument to put in the pre-command with my script path ? Thanks for your feedback :)
Backup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers