You might want to try starting it on Rpi with some ARM to x86 emulator, however you should keep in mind that such configuration is not officially supported so we cannot guarantee that VAL will be fast and stable. If you choose to conduct such an experiment please share you results with us.

I wanted to ask if there is new information about this topic.
ARM based systems are more powerful today (RasPi3, Odroid XU4 etc) and get more and more popular. So maybe it would make sense to develope an Veeam Agent for Linux for ARM based systems?

considering that ARM based SBCs (Single Board Computer) like Odroid-XU4, Rock64, RockPro64, Tinker Board S, Raspberry Pi 3 B+, Raspberry Pi Zero are getting more and more popular... it would be a great start to add support for the "Veeam Agent for Linux" to backup those systems...

Hi,
here exists some interest as well.
We are using RPis for all kinds of stuff.
Home automation, network monitoring, vpn.

I think a full image backup would be interesting for most of the users out there.
I mean what makes veeam good is how easy to use it is for unexperienced users.
And those are the people that are getting more and more involved with ARM based computers.

For me as professional a Veeam ARM Agent would be interesting for infrastructure reasons beeing able to do full image backups of all our RPis.
For me as a tinkerer at home it would be the convenience to "just take a backup" before going on trying something.

Correct me if I am wrong, but I guess that none of those tiny devices usually host any frequently changing data? That is, there will be probably no need to take a snapshot of those?
Speaking of the image level backup, I think it is an interesting topic how to perform a BMR restore on those. I see it as a roomy SD card that will contain a bootloader and a minimalistic recovery environment (the one that you see in Recovery Media).
Alternatively, it should be possible to create an additional recovery environment boot entry on live systems. Sounds like a plan? : )

I think there is an underestimation on what these little devices can do.
There are lots of use-cases for these embedded devices. like as a micro server, servers that run only certain not so heavy services, may it be, for information gathering from sensors and acting as simple storage nodes, or become servers for automation in an Infrastructure.

So their main job is usually either gathering data for later analyze or managing some devices based on sensor data and microcontrollers. which on both cases contain important data.

Another reason these devices actually in need of a serious backup solution is that most of them don't have a dedicated flash chip for storing data and they usually boot from SD cards, Which is terrible since there is no wear leveling and due to that they get screwed. Having an Image backup to restore them in case of failure would be a dream.

I personally even have a Raspberry Pi 3 in my home acting as a full headless Debian server, helping me download data and serving me as a NAS/Media manager/Router/VPN/Docker Server. It does a ton of tasks for its little price.

So their main job is usually either gathering data for later analyze or managing some devices based on sensor data and microcontrollers. which on both cases contain important data.

Would you tell me more, please?

So, they don't transfer that data somewhere else, but keep it locally until some tech guy needs it? If so, then I am curios about what kind of storage is used for that data and in what format is that data kept - is it just a bunch of plain text files that rotate on local SD, or some sort of light-weight database that keeps all those records? If not, then I guess some external storage is used (hdd, thumb) for data.

So yeah i'm posting because this could be very useful at my job as well as at home.

We don't use any backup solutions for our Pi's but if Veeam could develop some sort of agent to use with their backup system for Pi's and ARM in general we'd definitely want to try the system out.
We use the Pi's as a simple ticket submission device for our printers if something is down they just press the button associated with the issue and it sends us a ticket and alert. We also have some that are used as basic kiosk's. I also use a Pi 3+ as a basic SNMP monitoring node as well as config backup, syslog and traps reciever.

As for what to backup on the device i'd imagine a full image backup as an initial step adding the devices would be awesome then incremental backups that backup whatever files change and keep them indexed if anything needs to be restored individually or the full restore. Again just some ideas on how backup process could be done but i think a full and partial backup schedule for the file system would be excellent for restoring options as well as keeping control of the backup sizes on the backup storage.

As for what to backup on the device i'd imagine a full image backup as an initial step adding the devices would be awesome then incremental backups that backup whatever files change and keep them indexed if anything needs to be restored individually or the full restore.<...>

Ok, while I clearly understand the requirement to be able to back up certain files and directories ("config backup, syslog and traps"), I don't quite get it why do you need a full image backup. How do you see the restore procedure if the sd card dies? Also, what do you mean by "indexed"?