On Fri, 19 Jun 2015 10:27:33 +0200 notoneofmy <notoneofmyseeds@gmx.de> wrote: > > > On 15-06-19 10:01 AM, Petter Adsen wrote: > >> > Just two quick question I hope to get help one. > >> > > >> > I've spent now weeks putting installing Jessie and solving > >> > problems. It makes sense to find a good backup and restore > >> > program. Ideally, something that I can use to back up the entire > >> > system to a NAS and restore a broken system from the NAS. And > >> > following restoration; all will be good as new. Any ideas? > > I use backintime - it uses rsync to actually make the backups, so > > it's easy to traverse the backup tree and restore a specific > > version of a file that you want. It has frontends for Qt and GTK, > > and sets up cron jobs for automated backups. YMMV, I like it. > Thanks a lot. I will give this a try. But to be clear, would this > backup the entire system and restore it, in the event of a crash of > something going horribly wrong? I'm hoping it to be like the Time > Machine for linux; is that what it does? backintime will back up exactly what you tell it to, using hardlinks instead of copies of files that haven't changed, so you don't store full copies of every single file when it isn't necessary. The first time you run it it will make copies of everything, on later runs it will make copies of files that have changed, and use hardlinks for the ones that haven't to save space. By default it will exclude stuff like /proc, /sys, /run, cache directories and so on, but you can of course edit that if you want to add or remove something. Time Machine is something I haven't used, so I can't compare them. backintime will give you a directory tree where you have one directory for each run of the backup, named by the date and time the backup was run, and under that you get a full tree of the things you have backed up. Makes it easy to get a certain version of a file like it was on a specific date. The best way to judge would be to take a look at it, and get comfortable with the way it works. Make a few backups, and test the restore functionality to make sure it works if you suddenly need it. If you decide you like it, set up a schedule. Test it regularly to make sure everything works OK. > >> > Also, any ideas on a functioning dlna client. I've spent weeks > >> > on this...lots of servers out there but no client being > >> > developed. Most of the ones mentioned in wikipedia don't even > >> > exist anymore. > > I'm pretty sure Kodi (used to be called XBMC) can play from DLNA > > sources, although I simply export via NFS now. It's a great client > > with a ton of functionality, and it can also act as a DLNA server. > > You can also set up a shared MySQL database so that all metadata is > > shared between several clients. > Thanks also for this. I knew about XMBC and also about its rename. But > I'm only interested in a client. I know as far as servers go, this is > perhaps the best. And I like a lot of the new things they've done to > it. But this is a laptop from which I want to listen to music on NAS > while I work. XMBC is too much for this purpose. Kodi/XBMC is both a server and a client, so you can use it in either role. I run it on a Raspberry Pi as a media center, it isn't really that big a drain on resources. If you only want to play music, I would guess several of the "big" players would support that, I only use Kodi. > Could you please explain more what you do now, exporting via NFS? I have all my media on a big disk on my file server, and I export that via NFS to the Pi. Kodi on the Pi indexes all the media and builds a library. Simple, and at least in my experience it seems faster than DLNA/UPNP. Petter -- "I'm ionized" "Are you sure?" "I'm positive."
Attachment:
pgprSpPziESTZ.pgp
Description: OpenPGP digital signature