Good afternoon
I've never used the backup feature of xbian but I want to repair this mistake.
I would use "file" as type of destination.
What is best:
- Use a usb key connected to the raspi? (what format would you recommend for it ext2? ext3? ext4? another one?)
- Use a network share on my nas? (My raspi is connected to the network through wifi).
Thanks. :-)
(7th Nov, 2019 07:02 AM)Chiron Wrote: [ -> ]Good afternoon
I've never used the backup feature of xbian but I want to repair this mistake.
I would use "file" as type of destination.
What is best:
- Use a usb key connected to the raspi? (what format would you recommend for it ext2? ext3? ext4? another one?)
- Use a network share on my nas? (My raspi is connected to the network through wifi).
Thanks. :-)
I'm using network shares for years, using nfs, samba and sftp shares, IMO much better than backup to usb
Three of them are connected via wireless LAN w/o any problems
Thanks for the advice. :-)
Where do you create your mountpoint for your backups? In the root?
Is it ok to edit /etc/fstab ?
And is there a way to exclude the mountpoint from the backup?
(8th Nov, 2019 07:09 AM)Chiron Wrote: [ -> ]Thanks for the advice. :-)
Where do you create your mountpoint for your backups? In the root?
No.
First step: create share in Kodis Filemanager
Second step: Use this share when configure your backup strategy inside of Kodi's XBian-GUI
Quote:Is it ok to edit /etc/fstab ?
Of course, you can do that
Quote:And is there a way to exclude the mountpoint from the backup?
You don't have to worry about mountpounts. Only the volumes on sd-card are included in backup
(8th Nov, 2019 07:14 AM)Nachteule Wrote: [ -> ] (8th Nov, 2019 07:09 AM)Chiron Wrote: [ -> ]Thanks for the advice. :-)
Where do you create your mountpoint for your backups? In the root?
No.
First step: create share in Kodis Filemanager
Second step: Use this share when configure your backup strategy inside of Kodi's XBian-GUI
Quote:Is it ok to edit /etc/fstab ?
Of course, you can do that
Quote:And is there a way to exclude the mountpoint from the backup?
You don't have to worry about mountpounts. Only the volumes on sd-card are included in backup
Thanks
Everything is working flawlessly except fstab mounting at startup
I've added this line to my fstab:
Code:
192.168.30.50:/mnt/SDB1/Backups/xbian /bkp nfs defaults,nofail,_netdev 0 2
but it never mounts at startup, i have to perform a "sudo mount -a"
I never could have this working with any combination of server/client distributions.
That's frustrating. ;-(
(18th Nov, 2019 05:48 AM)Chiron Wrote: [ -> ]Thanks
Everything is working flawlessly except fstab mounting at startup
I've added this line to my fstab:
Code:
192.168.30.50:/mnt/SDB1/Backups/xbian /bkp nfs defaults,nofail,_netdev 0 2
but it never mounts at startup, i have to perform a "sudo mount -a"
I never could have this working with any combination of server/client distributions.
That's frustrating. ;-(
Usually you don't have to do this. Such mounts are included into autofs configuration and will be automatically mounted on access
Look into files
/etc/auto.master.d/auto.xbian and
/etc/auto.master.d/xbian.autofs
I'm always doing double backups, one on an USB stick, and one on a NAS; I used to do only the former, but I once lost a lot of work due to a corrupted USB stick, and I'm afraid of the NAS failing if I were to do only the latter.
(30th Apr, 2021 12:55 AM)HiroariTillWhen Wrote: [ -> ]I'm always doing double backups, one on an USB stick, and one on a NAS; I used to do only the former, but I once lost a lot of work due to a corrupted USB stick, and I'm afraid of the NAS failing if I were to do only the latter.
Having backups only on one place has never been a good idea. I always have my backups on 2 different systems, but I wouldn't even trust USB sticks with temporary files.
Yes, they're not the most reliable tool out there, but they're also cheap, which allows you to have a couple extra backups for a negligible price.
Yes, I agree with everything in this article, and I just want to say that it is a very nice and helpful piece. I will be sure to read more of your blog
io games