16:24:58(info): raspberrypi: Loading file list… 1 filesystem lookups 0 db lookups and 0 db updates 16:24:58(error): Creating snapshot of “home” failed. 16:24:58(error): /dev/root is not a device mapper device. 16:24:58(error): Snapshotting device /dev/root via dm… 16:24:58(error): Creating snapshot of “/home” failed Performing incremental (virtual full) indexing… 16:24:58(info): Last virtual full index unfinished. 16:24:58(info): Starting unscheduled full file backup… The full image backup failed on the Raspberry Pi-zero with this: I’ll keep playing around with the client, to see if I can figure out anything else. The server has been working perfectly for the one Windows system I have set up to use it, so I’m not sure why the Linux client can’t seem to connect (even though it display as “online”) right now. The max simultaneous backups is set to 10, well above what the 3 clients I’ve got should be doing. I’ve left all the communications port numbers, clean up and backup time windows, and most of the other parameters (aside from the max backups to keep) as their installed defaults. Which shows the value for the default directory to back up that I’d set via the server’s web interface for that client system. home/* rootfs follow_symlinks,symlinks_optional,share_hashes Yes usr/local/bin/urbackupclientctl list-backupdirs I also ran a client list-backupdirs command too: The status window is showing the “last seen” value for the client as nearly 12 hours ago, although they are connected and able to communicate (http and ssh) within the same local network. Never saw anything on the server status window change either as I did that. Timeout while waiting for server to start backup usr/local/bin/urbackupclientctl start -f I logged into one of my Linux systems (found where the client executable was hidden) and tried to manually start a backup like this: Neither of my two Linux systems have any sleeping or hibernations intervals set up, nor are any of them running on a laptop. Any thoughts or suggestions would be greatly appreciated! Thank you! Puzzled that they are not running any backups. I am presuming that the Linux clients are actually running correctly, because they are showing up “online” in the Urbackup server status window. I looked through the manual to see what the various command line options for the Linux client were, but since my browser won’t allow an automated search of the large document couldn’t find where this was actually discussed. I saw in another post that someone had explictly set the included and excluded files on their Linux client, so I tried that too (using “/” for the included and then a short list of excluded directories), but still no backups were started for these clients. The logs display does not show that any backup was ever started on the Linux systems. No backups are started or performed however and the next time I refresh the server status window there is no message about these processes still being queued. I had adjusted the file backup parameters for each Linux client on the server (changing the defaults which were set up for Windows to “/home/*” for a default directory) and then used the server status window’s “With Selected” option to queue full file and image backups. Both systems showed up as “online” in the server status window - but I can’t get them to run either a full file or image backup. I installed the Linux client on a small X86 Mint (Ubuntu) system and a RaspberryPi-Zero running Pi-OS (both using block mode snapshots), rebooting after the install was complete.
0 Comments
Leave a Reply. |