Jump to content

Eshell Returncodes And Examples


Recommended Posts

Using FSW 4.5.12011.0, we're suffering from slow backups, the biggest problem during VSS snapshotting of the drives.

 

File system activity shows large spikes during the backup process as expected but the data throughput during the backup of the VSS is about 50% of the throughput during the backup of the HDD

 

Since we can't exclude kernel paths e.g. ("\Device\HarddiskVolumeShadowCopy") from realtime scanning, I am intending to try disabling FSW as a pre-backup command and then enabling as a post-backup command.

 

Am I right in thinking that the command:

c:\Program Files\ESET\ESET File Security\eshell.exe start batch "&" set status disabled

will disable FSW (pre-backup)

and then

c:\Program Files\ESET\ESET File Security\eshell.exe start batch "&" restore status

will re-enable post backup ?

 

(or, alternatively are there any examples of eshell batch files available as .bat)

 

Backup exec also has the option to check the return codes from the pre and post commands and further control the backup job accordingly. Would the above commands give a return code of zero on successful completion?

 

Thanks

 

 

Link to comment
Share on other sites

  • 2 weeks later...
  • Former ESET Employees

Hello,

     The commands listed should work, however, you will need to run as "status set disabled" and "status restore" for them to function properly

 

     Also, if the Endpoint protection does not have a settings password, you may incur an error that will not let ESET become disabled (security feature)

 

     Lastly, I was able to find a user guide for eShell located at hxxp://download.eset.com/manuals/eset_eshell_11_userguide_enu.pdf

Link to comment
Share on other sites

Thanks for the reply.

 

After some experimenting, I don't think that its possible to do.

 

Whilst I can create a .bat file with the commands I want to run and the passwords required for eshell, the user that the backup software runs as cannot disable FSW.

 

eshell returns with: "Operation requires elevation. The following command was not executed: set status disabled"

 

As far as I can see, disabling FSW requires an elevated command prompt to run eshell.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...