Running a PowerShell script from a BAT fails when using pre-freeze/post-thaw or pre-job/post job scripts

KB ID: 2183
Products: Veeam Backup & Replication
Version: 9.x
Published:
Last Modified: 2016-10-24

Challenge

To provide a bat file template for calling PowerShell scripts to prevent Script execution errors

Cause

PowerShell execution policy and UAC/Windows permissions issues may be causing script call to fail

Solution

The following template .bat file may be used to call PowerShell scripts.


@ECHO OFF
REM edit the example line bellow to set  PowerShellScriptPath  to the PowerShell script path on the guest VM being backed up
SET PowerShellScriptPath="C:\Windows\Scripts\script.ps1”   
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Start-Process PowerShell -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""%PowerShellScriptPath%""' -Verb RunAs}";

 

More Information

When you run a pre-freeze/post-thaw script from a BAT file, the BAT file is stored on the Veeam Backup Server, and will be copied to a temporary location on the guest when the job runs.  The Powershell script will need to be located on the guest that is being backed up and that you want the script to run on.  The path for PowerShellScriptPath variable needs to be the exact path and file name on the guest.    
 
When you are running pre or post job scripts, both the BAT file and the PowerShell script will be launched from the VeeamBackup server independent of the guest.
 
For error reporting you can add “>> C:\TEMP\Err_ps.txt” to the end of each action line on the PowerShell script, or “>> C:\TEMP\Err_cmd.txt” to the end of each  action line in the BAT file to get error reporting output. 
5 / 5 (1 votes cast)

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system