Agentless Ubuntu 20 backups - reports integration services is not running

Just setup a new 2019 HyperV server and installed the 6.5 Agent on it. The HyperV server is running 2x Ubuntu 20.04 LTS servers and we've run the commands on both servers for the integration services https://www.serverwatch.com/guides/installing-and-activating-hyper-v-linux-integration-services/ and restarted both machines, all of the Integration services and guest services are enabled on HyperV for both machines as well.

When we're looking at the virtual Ubuntu machines on the Rapid Recovery 6.5 Console, they're coming up with the warning "snapshots may only be crash-consistent because Integration Services is not running on the virtual machine or it is out of date".  We've also done a base image of both Ubuntu servers and the recovery points have a yellow circle next to the recovery point saying "Not consistent, machine may have boot problems".  

This is the first time we're backing up Ubuntu agentless, am i missing anything obvious or is this correct?

Parents
  • Hello Simon,

    In order to enable the integration services for a Linux box, additional components are required. You can install the following and perform a reboot right after.

    sudo apt-get install linux-tools-<Kernel version>
    sudo apt-get install linux-cloud-tools-<Kernel version>

    You can check the kernel version with the cmdlet: uname -r

    After rebooting the Linux machine and refreshing the metadata from the Rapid Recovery Core server, the crash-consistent backup banner should disappear.

  • Apologies for the delay, that's now worked Luciano, thankyou

    Just as a quick side note.  The Ubuntu server that this error relates to runs a webserver and a MySQL database with a big data load happening early in the morning and also drips through during the day.  We have noticed that if the big data load happens when a backup is happening, the incremental backup can explode in size and it also blocks any new data loads until the backup has finished....as an example, a normal 6am backup is 20GB, if the dataload is still happening when this backup starts, it can block all data loads until the backup finishes and it can cause the backup size to go from 20GB to 50-100GB.

Reply
  • Apologies for the delay, that's now worked Luciano, thankyou

    Just as a quick side note.  The Ubuntu server that this error relates to runs a webserver and a MySQL database with a big data load happening early in the morning and also drips through during the day.  We have noticed that if the big data load happens when a backup is happening, the incremental backup can explode in size and it also blocks any new data loads until the backup has finished....as an example, a normal 6am backup is 20GB, if the dataload is still happening when this backup starts, it can block all data loads until the backup finishes and it can cause the backup size to go from 20GB to 50-100GB.

Children