Post-command not run when job is cancelled due to time-out

[Frido]

Hello,

Post-command does not run when a job is cancelled due to a time-out.

Last week I installed Hotfix 03. I rebooted the server remotely. Hotfix 03 probably caused the tape to eject, which caused the weekly backup job to time out.

Pre-command was executed, Post-command was not.

Is this behaviour by design, or am I overlooking something?

Policy Option "Run post-command even if job failed" is enabled.

All the other pre/post-run checkboxes are empty.

I'm running rev.7170

TIA,

Frido.

Message Edited by Frido on 05-07-200702:30 AM

[Jared_S_]

Hi Frido -

From the sounds of it the Post-Command attempted to operate but did not initialize past the limited time frame set in the global settings for using pre and post commands.

If you goto Tools>Options>Pre/Post Commands

There are a few options you can select/deselect depending on your needs. By default the "Cancel command if not completed within" field is set to 30 minutes. I am assuming the policy was willing to run the post-command, however, the command did not initialize within the specified time frame and cancelled. The maximum limit is 300 minutes. If it did in fact happen this way then yes it was by design.

Here is a tech note to further explain:

http://support.veritas.com/docs/270489

Are your pre-post commands working now?

- Jared

[Frido]

Hi Jared,

BE did not attempt to run the post-command. Or at least it did not mention this in the job log.

When a job is not cancelled, the pre- and post commands run as expected.

Best regards,

Frido.