Re: Can I interrupt an rdiff-backup backup?

Hi, 

it's still not quite enough information to be sure what you're trying to do, but you are aware that you can install rdiff-backup on Ubuntu as well as Windows, enable SSH on Windows, as to remotely backup Windows without going through a Samba drive?

It might not be the best approach for your use case, but what you should definitely avoid is to use Samba _and_ the remote feature of rdiff-backup, as you would incur twice the network induced latency.

A short explanation of which command you're calling where would help us help you.

KR, Eric 

On January 22, 2023 11:03:20 AM UTC, Mike Hart <[email protected]> wrote:
>Hi Robert
>
>Thanks again for your quick response and thanks to Eric also.  I took your advice and deleted the whole directory.  That worked!  It wouldn't have occurred to me that the *rm -rf* command would not work on the rdiff-backup-data directory directly but issued one level up, would work?!  Anyway you don't look a gift horse in the mouth :).
>
>FYI both the server and the client are running Ubuntu 22.04.  It is a Samba network.  This is because I can't wean my wife off of Windows, so I need to be able to connect a Windows 10 machine to the network.
>
>I'll start the 3 day backup again.  Even if the rdiff-backup backup gets corrupted at some point, the actual data is still accessible, so it seems worth the small risk.  I'm not sure why my machine closed halfway through, but whatever the reason, it's unlikely to happen again, so worth a second try IMO.
>
>
>On 22/01/2023 04:52, Robert Nichols wrote:
>> On 1/21/23 12:14 PM, Mike Hart wrote:
>>> Hi Robert
>>> 
>>> Many thanks for the reply.  Your answer explains why there's no activity on the local drive but steady activity on the remote drive (as well as what rdiff-backup is doing, of course).
>>> 
>>> I'm going to delete the lot and start again, but I have a problem deleting the rdiff-backup-data directory
>>> 
>>> below is what happens.  I'd be grateful for any solutions.  This is Ubuntu 22.04 in case it's not obvious.
>>> 
>>> mike@TV-PC:/media/primary/backups/Mike-PC/Projects$ rm -rfv rdiff-backup-data
>>> removed 'rdiff-backup-data/.fuse_hidden0014522e000000c4'
>>> removed 'rdiff-backup-data/.fuse_hidden0014522f000000c1'
>>> removed 'rdiff-backup-data/.fuse_hidden00145a71000000c2'
>>> removed 'rdiff-backup-data/.fuse_hidden00145fa2000000c3'
>>> rm: cannot remove 'rdiff-backup-data': Directory not empty
>>> mike@TV-PC:/media/primary/backups/Mike-PC/Projects$ ls rdiff-backup-data
>>> mike@TV-PC:/media/primary/backups/Mike-PC/Projects$ ls -la rdiff-backup-data
>>> total 804
>>> drwxrwxrwx 1 root root   4096 Jan 21 12:47 .
>>> drwxrwxrwx 1 root root    464 Jan 21 04:40 ..
>>> -rwxrwxrwx 1 root root      0 Jan 21 04:00 .fuse_hidden0014522e000000c5
>>> -rwxrwxrwx 1 root root 220862 Jan 21 07:11 .fuse_hidden0014522f000000c6
>>> -rwxrwxrwx 1 root root 572052 Jan 21 08:31 .fuse_hidden00145a71000000c7
>>> -rwxrwxrwx 1 root root  23842 Jan 21 04:13 .fuse_hidden00145fa2000000c8
>> 
>> How are you accessing this server? What OSs are involved. FUSE mounts can present some tricky problems. Personally, I'd be deleting the entire Projects directory, but I suspect that with everything else gone from the rdiff-backup-data directory, rdiff-backup won't find anything to revert and will run normally.
>>