Skip to main content

How to change Pre and Post Scripts

This article describes how to bulk edit pre- and post-scripts from the Configured VMs page. For more information on pre- and post-scripts, see Protect applications with Pre and Post Scripts.

Procedure

  1. Log in to the Management Console.

  2. Select your organization if organizations are enabled.

  3. Click Protect > VMware.

  4. The All vCenters/ESXi Hosts page appears that lists all the registered vCenters/Hypervisors.

  5. Select the vCenter/ESXi Host. Click Configured VMs.

  6. Select the already configured virtual machines for which you want to enable/disable the pre/post scripts settings.

  7. Click Restore > Change Pre-Post Script.

  8. In the Change Pre-Post Backup Script Settings dialog, toggle the Enable Pre-Post Scripts for selected VMs option to enable all the scripts.

    1. For Windows VM Script Directory: Path to the folder on the Windows backup proxy containing scripts for Windows guest VMs.

    2. For Linux VM Script Directory: Path to the folder on the Linux backup proxy containing scripts for Linux guest VMs.

    3. Script Settings

      1. Skip backup if script is not present at the specified location: When enabled, the backup will be skipped if the scripts directory does not exist or is empty on the proxy.

      2. Skip backup if script execution fails: When enabled, the backup will be skipped if a script returns a non-zero exit code.

    You can apply a uniform script configuration to multiple VMs simultaneously. Click Save.


    📝 Note

    If you select either the For Windows VMs or the For Linux VMs option, then only the corresponding Windows or Linux script inputs are displayed on the screen.


    Alternatively, you can toggle the Enable Pre-Post Scripts for selected VMs option to disable all the scripts, and click Save. This prompts a confirmation warning and removes script settings entirely from selected VMs.


    📝 Note

    If a selection includes older proxies that lack script support, the configuration is only applied to VMs on supported proxies; unsupported proxies are skipped.


Did this answer your question?