Enabling Guest Scripting

To specify pre-snapshot and post-snapshot scripts that must be executed for Azure VMs:

  • For Azure VMs running Linux OS, set the Scripting for Linux instances toggle to On.

The Specify scripting settings for Linux instances window will open.

  • For Azure VMs running Microsoft Windows OS, set the Scripting for Windows instances toggle to On.

The Specify scripting settings for Microsoft Windows instances window will open.

Important

Supported script formats:

  • For Windows-based Azure VMs Veeam Backup for Microsoft Azure supports EXE, BAT, CMD, WSF, JS, VBS and PS1 file format.
  • For Linux-based Azure VMs Veeam Backup for Microsoft Azure supports SH file format.

In the opened window, specify pre-snapshot and post-snapshot scripts that must be executed before and after the backup operation:

  1. In the Pre-snapshot script section, do the following:
  1. In the Path in guest field, specify a path to the directory on an Azure VM where the pre-snapshot script file resides.
  2. In the Arguments field, specify additional arguments that must be passed to the script when the script is executed.

You can use runtime variables as arguments for the script. To see the list of available variables, click Parameters.

 

Important

Veeam Backup for Microsoft Azure will try to run a script residing in the specified directory for all Azure VMs added to the backup policy. If you want to execute different scripts for different Azure VMs, ensure that script files uploaded to these VMs have the same path and name.

  1. Repeat step 1 for post-snapshot scripts in the Post-snapshot script section.
  1. In the Additional Options section, choose whether you want to run scripts only while creating repository snapshots, to proceed with snapshot creation even though scripts are missing on some of the processed instances, and to ignore exit codes returned while executing the scripts.
  2. Click Apply.

 

Enabling Guest Scripting 

 

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.