Pre and Post Commands Continue to Fail

[Claude_Morris]

We have Pre and Post commands associated with the backup of two servers that fail.

Our latest try was to set up batch files that copied a text file from one directory to another. These were set up on the backup server using the backup server admin account.

We have changed settings in many ways to try to get the commands to work.

Suggestions.

This have been going on for three weeks now. A previous thread on this subject petered out.

[Greg_Walker]

Hi Claude,

I have been using Pre commands (not post) with out trouble.

They way i have it set is to have the pre commands siting on the server that is being backed up. Then in the backup job, put the relatve path to the pre command. ie if the media server is Server1 and the server being backed up is Server2, have the script on Server2's d:\scripts directory. Then when creating the backup job in Server1, speficy d:\scripts\precommand.bat in the job and set it to run on the server being backed up.

Hope this helps.

G.

[priya_khire]

Hello,

What are the commands you use before and after the job? When the commands do not run, do you receive any error message? Refer to the following technotes in order to resolve the problem:

Title: How to execute batch files and executables (pre- and post- job commands) before and after a backup via the Backup Exec GUI
http://support.veritas.com/docs/240664

Title: A backup configured to use a batch file in a Pre/Post command does not execute the batch file.
http://support.veritas.com/docs/258695

Hope this helps. If the problem persists, revert with details.

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Regards.

[Claude_Morris]

Thanks for the reply.

We have been fighting this issue for three weeks.

We have been through all the path lines and job settings.
The batch jobs run when started manually.
The full paths are defined in the backup job as well as in the batch job.

We have changed job settings.

We have tried using different log on accounts.

We have tested similar jobs on different servers.

The jobs do not start. I believe there is a problem in the Veritas software. Is there a patch or other global setting that would fix this issue.

[Claude_Morris]

Thanks for the reply.

We have been fighting this issue for three weeks.

We have been through all the path lines and job settings.
The batch jobs run when started manually.
The full paths are defined in the backup job as well as in the batch job.

We have changed job settings.

We have tried using different log on accounts.

We have tested similar jobs on different servers.

The jobs do not start. I believe there is a problem in the Veritas software. Is there a patch or other global setting that would fix this issue.

[Shyam_Sundar]

Hello,

Please try copying the batch file under C:\Program Files\Veritas\Backup Exec\NT directory and try running the job. And manual execution of the file works?


Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm



Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Thanks.