Skip to main content

I’ve been using the free Veeam Windows agent for quite sometime, to backup my 3 Windows desktops to my TrueNAS server.  Wonderful product, I might add!

One of my Windows machines is a Windows 10 box that cannot be upgraded to Windows 11 due to hardware limitations.  So I have installed Linux Mint Cinnamon on this machine.  I have then installed the free Linux agent to allow me to backup this system to my backup server.  This is where the problems begin.

The machine now running Linux Mint will not wake up at the specified time to do a Veeam backup.  I have installed the Linux agent (blksnap) and have created a backup configuration, performed a full backup, created and patched the recovery imaged and tested the recovery all without any problems.  Now, I have put my Linux system into “suspend” mode and then waited till 02:30 to see if it would wake and do an incremental backup.

Well, nothing happens; the system does not wake up at 02:30.

I have done a manual incremental and it works fine, but the system will not wake automatically!

What am I doing wrong?  It this a Linux thing or a Veeam thing?

Veeam on Windows automatically wakes, does the backup and then sleeps again.  While the Windows version doesn’t always stop correctly, it usually doesn’t fail to do the nightly backup.

Thanks in advance for any help of suggestions.

Greg

First off I know Linux Mint is not on the supported list - System Requirements for Linux Computers - Veeam Agent Management Guide

For the wake piece it looks like you need to program that part as the Agent for Veeam does not have a setting that I can see.  There are utilities that will wake a Linux machine at a specified period you may want to check out.


Hi ​@GChuck -

Linux doesn’t have the same setting there like Agent for Windows to ‘wake’ it up to back it up. Not sure if there’s a BASH script out there that can do this. This isn’t a Veeam thing really...but a Linux thing. You can ping the Forums and see if Veeam Product Managers can add this feature in Agent for Linux.


I have to agree with ​@Chris.Childerhose  here. I think Linux doesn’t have the same built-in wake-from-sleep scheduling integration tied into cron/systemd timers like Windows does. You might want to take a look at "rtcwake" to see if this helps. You can find more information here: https://man7.org/linux/man-pages/man8/rtcwake.8.html. Alternatively, you can enable WoL in the BIOS or network settings and have another device send a WoL signal. Here is a video demonstrating this step. Lastly, I think the following method, “scheduled boot via an RTC event” from the BIOS/UEFI will be the easiest. 


Thank you to both Chris and coolsport00 for responding.

First, I know that Linux Mint is not an officially “supported” version, but I have had the exact same issues getting this to work using Ubuntu (supported) and Debian (supported).  

As for a “wake piece”, I’m testing this now using the BIOS wake function in my old HP to wake the computer at a specified time and then hope that once the machine is awake, the Veeam backup will start.  I told the BIOS to wake the computer 5 minutes before the scheduled Veeam backup time.  Just trying to reconcile the UTC vs local time issue (HP hardware is on UTC but is the Veeam schedule on Local Time ??).

Will let you know how this works out.

Thanks again

Greg


Thank you to both Chris and coolsport00 for responding.

First, I know that Linux Mint is not an officially “supported” version, but I have had the exact same issues getting this to work using Ubuntu (supported) and Debian (supported).  

As for a “wake piece”, I’m testing this now using the BIOS wake function in my old HP to wake the computer at a specified time and then hope that once the machine is awake, the Veeam backup will start.  I told the BIOS to wake the computer 5 minutes before the scheduled Veeam backup time.  Just trying to reconcile the UTC vs local time issue (HP hardware is on UTC but is the Veeam schedule on Local Time ??).

Will let you know how this works out.

Thanks again

Greg

Sounds good let us know how it goes.  Also check out the utility mentioned too if BIOS wake does not work.

 
 
 

Thank you to both Chris and coolsport00 for responding.

First, I know that Linux Mint is not an officially “supported” version, but I have had the exact same issues getting this to work using Ubuntu (supported) and Debian (supported).  

As for a “wake piece”, I’m testing this now using the BIOS wake function in my old HP to wake the computer at a specified time and then hope that once the machine is awake, the Veeam backup will start.  I told the BIOS to wake the computer 5 minutes before the scheduled Veeam backup time.  Just trying to reconcile the UTC vs local time issue (HP hardware is on UTC but is the Veeam schedule on Local Time ??).

Will let you know how this works out.

Thanks again

Greg

Hi Greg, as shared above. This should work fine. We will be very happy if you could share the steps you employed when you are done with the community.


@GChuck - ok, sounds good...let us know how it goes!


Hi ​@GChuck 

 

Veeam Agent for Linux does not support wake from suspend. Use rtcwake or BIOS RTC to schedule wake up before backup time. This is a Linux limitation, not a Veeam issue.

 

 


waqasali, it just seems odd to me that using the Veeam configuration screens, it asks at what time to do the backup, but then does not support waking the computer at that time to execute the job!  I must assume that Veeam Linux backup is designed for “always on” Linux servers.

Thanks for replying

Greg


waqasali, it just seems odd to me that using the Veeam configuration screens, it asks at what time to do the backup, but then does not support waking the computer at that time to execute the job!  I must assume that Veeam Linux backup is designed for “always on” Linux servers.

Thanks for replying

Greg

 

 

You are absolutely right, Greg. Veeam Agent for Linux is indeed optimized for always-on systems. Hopefully, future versions will include wake functionality to support more flexible setups. Appreciate your thoughts!

 

 


Before migrating my digital life from Windows to Linux, I started with must-haves.  Automatic backup is on that list.  I spent a lot of time trying to get my Linux Mint 22.1 test system to do backup using Synology ABB. I know Mint is not on the supported list but hoped it would work because Ubuntu is supported. The actual reason it failed is beyond my ken, but I moved on to Veeam.  I got Veeam for Linux working fine. It’s been backing up nightly since late May.  I more or less gave up on the migration (for the time being) after running into serious obstacles to porting over my music production. Accordingly, how I did any of it is somewhat faded in my memory.  What I recall is that I created a “script” to set an rtcwake call using a daily crontab.  The rtcwake call has to be renewed every day because rtcwake executes only once.  oYes Windows is much smoother at this task]  The wake up call is set for a couple of minutes before Veeam goes to work.  I’m saving the backups to an NFS location on my Synology NAS.  I just let it run as I’ve lost hope (for the time being) of getting MSFT out of my life.  In case this helps someone, here are a few notes I made back in May.

How to Automatically Suspend and Wake a Linux Machine:
https://www.baeldung.com/linux/auto-suspend-wake

Wake your Linux up from sleep for a cron job

https://www.dedoimedo.com/computers/wake-cron.html

https://forums.linuxmint.com/viewtopic.php?t=289481

https://commandmasters.com/commands/rtcwake-linux/ explains how to see whether an alarm is set:

sudo rtcwake -m show -v

My goal was to wake the machine at 12:28 a.m. the next day for a 12:30 a.m. backup:

sudo /usr/sbin/rtcwake -m no -u -t $(date +%s -d "tomorrow 00:28")

This worked.

From my sketchy notes, I think I wound up using anacron.  Here are a few links I wrote down:

Use anacron for a better crontab

https://linuxconfig.org/how-to-run-commands-periodically-with-anacron-on-linux

rtcwake not executed as root cron job

https://www.petefreitag.com/blog/cron-daily-not-running/

I hope these breadcrumbs are of some use. As it stands, I am no longer working on the Linux Mint system. 

In another year …

 


Comment