Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using BackupExec 12.5, and need to run some pre- and post-command scripts on my jobs.

I have several servers, some need the commands, some don't, but I don't want to create several policies, as they can be a bit complex.

I assume one solution is to create a common script on every server, perhaps in C:\BackupScripts\pre.bat for example, and do server-specific stuff in each one.

How do I handle servers without a C: drive (such as our Citrix servers)? Can I use the %SYSTEMDRIVE% or %WINDIR% variables in the job setup?


share|improve this question

I haven't seen anything in the BE documentation that would suggest that this is possible. My recommendation would be to set up a test job and see.

share|improve this answer
Yeah, I did that and it doesn't work. Looks like separate jobs. – Cylindric Jul 30 '10 at 8:07
up vote 0 down vote accepted

The only thing I can think of is that the path is relative to the installation of the BE agent, so in the worst case I could just put the script in that location and just put "pre.bat" in the option box.

Of course that script can be something simple that calls the 'real' script somewhere else - I don't like storing important custom scripts buried in the Program Files path of a third-party application.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.