I'll start by explaining the environment:
Windows: Storage Server 2008 R2 (with UAC enabled)
Veeam: 188.8.131.52 (64bit)
Backup Exec: 2010 R3
I'm looking to have a Backup Exec job started at the completion of a Veeam job - mainly to ensure the backup happens as soon as possible to ensure it fits within the backup window.
My problem seems to be that bemcmd (the command line program for backup exec) won't start unless you execute it in an elevated fashion (e.g. from an elevated command prompt) - this is because UAC is requiring approval.
I was wondering if anybody is having any success starting a Backup Exec as part of a post command while UAC is enabled (and not in auto-approval mode)?
Thanks in advance,
- Veeam Software
- Posts: 5978
- Liked: 1795 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2020
Veeam VMCE #1
- Product Manager
- Posts: 24744
- Liked: 2055 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Here is a good reading about that: http://www.computerperformance.co.uk/Lo ... ontrol.htm
- Veeam Software
- Posts: 19881
- Liked: 1845 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Thanks for the replies so far. I'm familiar with UAC (part of my MSc is based on it) - was more after checking everyone else is in the same position as I'm not so familiar with Veeam.
@Foggy - I was thinking about the scheduled task approach but was struggling with chaining it onto my Veeam job. That link gave me the missing piece of the puzzle so I'll give that a go and feed back.
Edit: Corrected spelling mistake
- Posts: 293
- Liked: 18 times
- Joined: Apr 13, 2011 12:45 pm
- Full Name: Thomas McConnell
Code: Select all
$pass = Read-Host "Enter Password" -AsSecureString $myProg = New-Object System.Diagnostics.ProcessStartInfo $myProg.UserName = "administrator" $myProg.Password = $pass $myProg.WorkingDirectory = "C:\Windows\system32\WindowsPowerShell\v1.0\" $myProg.FileName = "powershell.exe" $myProg.UseShellExecute = $false [System.Diagnostics.Process]::Start($myProg)