Greetings, > Sent: Sunday, August 05, 2018 at 4:09 PM > From: "G.W. Haywood via BackupPC-users" <backuppc-users@lists.sourceforge.net> > To: backuppc-users@lists.sourceforge.net > Cc: "G.W. Haywood" <bac...@jubileegroup.co.uk> > Subject: Re: [BackupPC-users] backup in a special scenario > > Hi there, > > On Sun, 5 Aug 2018, daggs wrote: > > > I have a windows installation running inside a kvm vm, for past > > experience, backup using the samba protocol is unreliable ... > > For more than a decade, using the SMB protocol, I've backed up some > hundreds of Windows machines, and a fair number of SMB shares on Linux > boxes, with perfectly acceptable reliability - even over considerably > less than perfect network connections. Perhaps you're doing something > especially tricky that you haven't mentioned, but otherwise I suspect > that with a little effort you could make it work reliably too. > as said, it worked great until a time in which I started to get permission errors.
> > ... I want to run a script on the vm's host ... run the backup and > > run another script on the vm's host ... the main idea is to mount > > the image remotely, use rsync to backup and unmount the image. > > Are you planning to back up the entire Windows VM image each time? > > The design of BackupPC makes it most useful in the situation where > there are many files, potentially distributed across many machines, > potentially replicated many times, most of which, most of the time, > will not change from one backup to the next. Think of a corporate > site, containing a number of buildings full of offices, and in each > office there are numerous workstations. Here and there on the site > there are a few servers. It is in this kind of situation that I've > applied BackupPC successfully, occasionally saving somebody's bacon. > > BackupPC wins most when a small proportion of a large number of small > files changes between each backup, and this success is extended when > at least some of the files permit substantial compression. If even a > single byte in a large file changes, on the next backup BackupPC will > store a complete new copy of the file. It will make no attempt to do > anything like a binary diff to store just the changes. Patches would > I'm sure be welcome. :) > > If you plan to back up an image of a single VM, then > > (1) there's only one file, > (2) it's very large, > (3) it's difficult to compress and > (4) it probably changes every few seconds. > > If I were planning to back up an entire VM image then BackupPC would > not be my first choice for the backup the tool. I would think that it > would add considerable complexity for no practical benefit. no, I plan to backup personal files only. > > -- > > 73, > Ged. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
