[Feature Request] Ability to run pre/post job scripts without triggering application-aware processing

[cko]

Hello,

Currently, if you want to run pre/post job scripts you must check «Enable application-aware processing» to enable script execution.

Doing this on a file-level backup, you do not have access to the "General", "Oracle", "MySQL", and "PostgreSQL" tabs under "Processing Settings".

This means that application-aware processing is triggered and you cannot disable it in the «General» tab.

If a machine running one of the previously mentionned databases is added to such a job, the backup will fail because Veeam cannot interact with it (no credentials defined).

It would make more sense if application processing were not triggered at all in this case, or if you could access the "General" tab to disable it.

Best Regards,

[PetrM]

Hi Charles and Welcome to Veeam R&D Forums!

What about running pre/post-job job scripts instead?

Thanks!

[cko]

Hi Petr,

Thank you for your reply.

From what I understand, these pre/post job scripts run on the backup server.

I need them to run on the agent.

Regards,

[PetrM]

Hi Charles,

Got it. My only suggestion is to run these scripts on the backup server and execute the necessary commands remotely.

Thanks!

[cko]

Hi Petr,

Of course, I could work around this problem by launching the script remotely from the backup server.

But I still find it a shame not to be able to use a feature offered natively.

Moreover, it doesn't make sense to trigger application-aware processing without giving access to its settings.

I used the term "feature request" here, but depending on your point of view, this could be considered a bug since the backup fails in such a scenario.

I also opened a support case (#03636594) for this issue.

Regards,

[PetrM]

Hi Charles,

Actually, a "bug" means that the behavior differs from the intended design, so I would treat this as a feature request. Anyway, let's set aside the terminology and focus on the improvement you're proposing. From my perspective, your feedback is absolutely relevant. I simply wanted to assess the impact and offer a potential workaround (since I wasn’t sure whether you were aware of it) by sharing my thoughts above.

Your request is noted, but I cannot provide an ETA. As with any improvement, this change requires engineering resources, and estimates can only be made after several rounds of discussion with the engineering team.

Thanks!