Comprehensive data protection for all workloads
Post Reply
piuttostoorbo
Novice
Posts: 3
Liked: 2 times
Joined: Jul 29, 2019 7:51 am
Full Name: PiuttostoOrbo
Contact:

Automatic Power On/Off repository

Post by piuttostoorbo »

Hi everyone
I have a question about script before/after backup on Veeam Backup & Replication 9.5U4.
I have a Windows Server 2016 VM with Veeam and a Linux server repository on a physical machine. I want that the vm automatically power on repository, do the backup and after power off.
In Edit Backup Job /advanced / Script i flag "run the following script before the job" i put my cmd script

WolCmd.exe "MAc Address" "IP" 255.255.255.0 7

and it works (power on machine)

but the poweroff script doesn't work

plink.exe -batch -pw password user@ip shutdown -h now

If i click on poweroff cmd or use a scheduled task, physical machine correctly poweroff, but if i put on "run after backup" dosen't work.

I have only one user on vm server, i also tried to convert cmd to exe but it's the same
HannesK
Product Manager
Posts: 14287
Liked: 2877 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: Automatic Power On/Off repository

Post by HannesK »

Hello,
and welcome to the forums.

The official way is to open a support case... but I'm pretty sure that you will find the answer in one of the job logfiles (c:\programdata\veeam\backup\job name\) and search for the script / plink command

I guess that plink is not in the %path% of the local system account. Did you try the absolute path to plink.exe already?

Best regards,
Hannes
nitramd
Veteran
Posts: 297
Liked: 85 times
Joined: Feb 16, 2017 8:05 pm
Contact:

Re: Automatic Power On/Off repository

Post by nitramd »

An alternative to shutdown is halt. Since you want to power off the repo you can use : halt -p
piuttostoorbo
Novice
Posts: 3
Liked: 2 times
Joined: Jul 29, 2019 7:51 am
Full Name: PiuttostoOrbo
Contact:

Re: Automatic Power On/Off repository

Post by piuttostoorbo » 2 people like this post

thank you so much
I solved by raising the user running the veeam service to administrator
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 144 guests