NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Data Protection

Plugin request for new feature

ondemandinf
4,772 Views

Hello,

We are using version 3.6. The SC executes bash commands on the target machine, so it cannot set environment variables successfully because our user uses csh as default shell.

We have to set variables in the user environment first, so that the backup would end successfully although SC fails to set variables.

We want to request the new feature of supporting more shells, like executing different commands according to the shells.

example: oracle plugin

****************SC Server Log****************

[Fri Dec 21 02:51:32 2012] DEBUG: Command [/bin/su - oracle -c "ORACLE_HOME=/sctest_oracle/SCTEST/112_64;export ORACLE_HOME;

ORACLE_SID=SCTEST;export ORACLE_SID;

/sctest_oracle/SCTEST/112_64/bin/sqlplus /nolog @/tmp/s7vNWiYikh.sc"]

finished with exit code: [0]

...

...

...

stderr: [ORACLE_HOME=/sctest_oracle/SCTEST/112_64: Command not found.

         export: Command not found.

         ORACLE_SID=SCTEST: Command not found.

       export: Command not found.]

****************scAgent****************


testserver /sctest_oracle/> echo $shell   $ORACLE_HOME   $ORACLE_SID

/bin/csh   /sctest_oracle/SCTEST/112_64   SCTEST

Regards,

Carmen

2 REPLIES 2

sivar
4,772 Views

Hello Carmen,

Thank you for the suggestion.

I have requested the developer team to add support for multiple shells.

I will keep you posted on the progress.

Thanks,
Siva Ramanathan

Snapcreator Community Moderator

cferbrache
4,772 Views

Wrong person on this also.

Thanks,

Cary Ferbrache, Sr. Systems Engineer

(904) 296-4562| AVN 810-4562

6600 Corporate Center Parkway, Jacksonville, FL 32216

[email protected]<mailto:[email protected]>

Please consider the environment before printing this email.

Public