Friday, April 19, 2024
 Popular · Latest · Hot · Upcoming
4
rated 0 times [  4] [ 0]  / answers: 1 / hits: 1171  / 2 Years ago, wed, february 16, 2022, 5:55:17

I often develop and test code on several remote machines, which aren't all on the same NFS filesystem. For interactive work, I usually use SSHFS to mount remote filesystems on my local machine. For example:



mkdir ~/machine1
sshfs [email protected]: ~/machine1 #mount machine1's home directory locally


I've been using CrashPlan for the last couple of years to back up my local hard disks. I'd like to start using CrashPlan to backup remote disks that are mounted locally.



In the CrashPlan UI, it gives me the option to back up ~/machine1. However, CrashPlan thinks that the ~/machine1 directory is empty, even when machine1.domain.org is mounted there.



How can I get CrashPlan to "see" drives that I've mounted using SSHFS?






A few closing thoughts:




  • I expect that backing up an SSHFS-mounted drive will be pretty slow. I'm not too worried about the speed; I just have small bits and pieces of data on each of these remote drives.

  • I could probably install CrashPlan on all the remote machines. But, this would be my last resort: CrashPlan doesn't have a command-line interface that I know of, so managing CrashPlan on a headless machine isn't very fun.


More From » 12.04

 Answers
7

The reason why it isn't working is that no other user than your user can see sshfs mounted directories. Unless Crashplan is running as your user it won't be able to back it up. You can try it for yourself:



sudo -i
ls -al ~me/ | grep machine1
ls: cannot access /home/me/machine1: Permission denied
?????????? ? ? ? ? ? machine1


There is a way to do mount sshfs to make files available for root too or everyone on the machine. If Crashplan is running as root you should only make it available for root.



sshfs -o allow_root [email protected]: ~/machine1 


Or you can allow anyone (including root) on the machine to see your files with:



sshfs -o allow_other [email protected]: ~/machine1 


You may need to allow for these flags in /etc/fuse.conf:



gksudo gedit /etc/fuse.conf


Change the line:



#user_allow_other


to



user_allow_other


You also need to be in the fuse group. run groups and if you are not fuse is listed you need to run:



sudo addgroup <your user> fuse


Then logout and in again and it should work.


[#29777] Friday, February 18, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
uxuriousrnal

Total Points: 279
Total Questions: 106
Total Answers: 96

Location: Fiji
Member since Wed, Mar 29, 2023
1 Year ago
uxuriousrnal questions
Wed, Mar 9, 22, 09:04, 2 Years ago
Mon, Jul 18, 22, 01:48, 2 Years ago
Wed, Apr 13, 22, 01:15, 2 Years ago
Thu, Aug 26, 21, 22:01, 3 Years ago
;