From: tts <the...@o2...> - 2007-11-10 01:49:13
|
Guys I really been struggling with shh and getting backuppc to log to the client with no password. Done it before but just cant remember how (done it by luck). I just cant get my head around how the key stuff works and where you are suppose to generate the key? server side? were backuppc runs ? both machines? place the key where? I found some guides at google but its hard to follow when you don't know how its suppose to work.I just cant get my head around it. If one could make a animated video of where exactly the keys exchange. I will donate a reasonable amount to you or what ever oginisation you like. Please get back to me even if the answer is no, a yes would be great ;) I'm very greatfull to the backuppc creators Backuppc is simply the best *hands on heart*. ----- Original Message ----- From: <bac...@li...> To: <bac...@li...> Sent: Sunday, November 04, 2007 3:42 AM Subject: BackupPC-users Digest, Vol 19, Issue 4 > Send BackupPC-users mailing list submissions to > bac...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/backuppc-users > or, via email, send a message with subject or body 'help' to > bac...@li... > > You can reach the person managing the list at > bac...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of BackupPC-users digest..." > > > Today's Topics: > > 1. Re: backuppc Windows client failed ! (tu...@fr...) > 2. Re: backuppc backing up backup directory (Paul Archer) > 3. Backing up VMs (Bradley Alexander) > 4. Re: Backing up VMs (Paul Archer) > 5. Re: Backing up VMs (Stephen Joyce) > 6. Re: Backing up VMs (dan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 03 Nov 2007 21:32:18 +0100 > From: "tu...@fr..." <tu...@fr...> > Subject: Re: [BackupPC-users] backuppc Windows client failed ! > To: Toni Van Remortel <ton...@p-...>, > bac...@li... > Message-ID: <472...@fr...> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Toni Van Remortel a ?crit : >> tu...@fr... wrote: >>> smb method : failed too : timeout 20000 millisecond ... >>> tar : hang !!! >>> i try all rsync parameter... but , the system hang all the time >> What anti-virus tool are you using on your Windows client? >> >> It seems to timeout on files, due to an issue on your Windows client. >> To test this: >> - Create a dummy share with 2 files: 1 file of about 20kB and one of >> about 2GB. >> - Create a dummy host in BackupPC to backup this share >> - Run the backup command by hand (su - backuppc, >> /usr/share/backuppc/bin/BackupPC_dump -v -f "dummy server") >> Then you can see what is happening. Also, open a network monitor which >> can show you the traffic between your backup server and Windows client >> (iftop is handy, as you can specify the IP range to show). >> >> Please report this test, it might help us to find the source of the >> problem. >> > Hello all > > just for saying "MEACULPA" .... > :( :( :( > > all my request and question are obsolete because my problem come from my > wifi connexion ... yes and NOT FROM BACKUPPC > > i explain : i have my server (with dwl-g510) connect by WIFI to my FAI > ADSL GATEWAY (FREEBOX) and connect by WIFI to my laptop ... > > the problem coming beetwen the ADSL GATEWAY and my server. the wifi > doesn't work fine and got few disconnection ... i'm very disappointing > with that ... > > when i connect with hardlink , all work fine , no disconnect.... > > so , i'm sorry with this problem that backuppc software doesn't the cause > > Best Regards, Olivier > > > > > > > > > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.15.19/1105 - Release Date: > 02/11/2007 11:04 > > > > > ------------------------------ > > Message: 2 > Date: Sat, 3 Nov 2007 17:41:35 -0500 (CDT) > From: Paul Archer <ti...@io...> > Subject: Re: [BackupPC-users] backuppc backing up backup directory > To: "BackupPC users' mailing list" > <Bac...@li...> > Message-ID: <200...@er...> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > 8:01am, Paul Archer wrote: > >> First, I'm new to backuppc, so this may be something I've missed in the >> docs. >> >> Setup: (K)ubuntu 7.10 on an old PIII >> backup directory is on /backup filesystem (as /backup/backuppc) >> changed backup directory by modifying /etc/init.d/backuppc >> machine name is shebop >> >> I'm using rsync to backup the machine itself. Here's the relevent section >> of >> /backup/backuppc/pc/shebop/config.pl: >> >> $Conf{RsyncShareName} = [ >> '/', >> '/export/bedroom', >> '/export/lildell', >> '/data/extra', >> '/data/home_videos', >> '/data/images', >> '/data/mp3s', >> ]; >> > > I did a couple of more tests. First I removed > /backup/backuppc/pc/shebop/config.pl, and it backed up normally (backed up > the root filesystem, that is). > > Then I changed the order of $Conf{RsyncShareName}: > > $Conf{RsyncShareName} = [ > '/export/bedroom', > '/', > '/export/lildell', > '/data/extra', > '/data/home_videos', > '/data/images', > '/data/mp3s', > ]; > > The odd thing here is it seems to have completely skipped root. So far > it's > backed up /export/bedroom, /export/lildell, and /data/extra. > > Anyone have any idea(s) about this? > > Paul > > >> In my main config.pl I have: >> $Conf{XferMethod} = 'rsync'; >> $Conf{RsyncShareName} = '/'; >> #and >> $Conf{RsyncArgs} = [ >> '--numeric-ids', >> '--perms', >> '--owner', >> '--group', >> '--devices', >> '--links', >> '--times', >> '--block-size=2048', >> '--recursive', >> '-D', >> '--one-file-system', >> ]; >> >> >> My problem is that the system is backing up the /backup filesystem for >> some >> reason: >> >> oot@shebop:/backup/backuppc/pc/shebop# cd new >> root@shebop:/backup/backuppc/pc/shebop/new# l >> total 0 >> drwxr-x--- 3 backuppc backuppc 72 2007-11-03 05:27 f%2f >> root@shebop:/backup/backuppc/pc/shebop/new# cd f%2f/ >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f# l >> total 0 >> drwxr-x--- 3 backuppc backuppc 80 2007-11-03 05:27 fbackup >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f# cd fbackup/ >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f/fbackup# l >> total 0 >> drwxr-x--- 6 backuppc backuppc 208 2007-11-03 05:27 fbackuppc >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f/fbackup# cd fbackuppc/ >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f/fbackup/fbackuppc# l >> total 8 >> -rw-r----- 2 backuppc backuppc 955 2007-11-02 17:29 f.bash_history >> drwxr-x--- 2 backuppc backuppc 48 2007-11-03 05:27 fcpool >> drwxr-x--- 2 backuppc backuppc 320 2007-11-03 05:27 flog >> drwxr-x--- 3 backuppc backuppc 72 2007-11-03 05:27 fpc >> drwxr-x--- 2 backuppc backuppc 200 2007-11-03 05:27 f.ssh >> -rw-r----- 2 backuppc backuppc 3747 2007-11-02 17:29 f.viminfo >> root@shebop:/backup/backuppc/pc/shebop/new/f%2f/fbackup/fbackuppc# du -sh >> 3.4G . >> >> >> root@shebop:/etc/backuppc# ps auxww |grep rsync >> backuppc 26824 0.2 1.2 6040 3240 ? S 19:21 0:00 >> /usr/bin/ssh >> -q -x -l root shebop >> /usr/bin/rsync --server --sender --numeric-ids --perms >> --owner --group --devices --links --times --block-size=2048 --recursive -D >> --one-file-system --exclude=/proc --exclude=/sys --ignore-times . / >> root 26828 3.8 3.5 10648 9020 ? Ss 19:21 0:14 >> /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group >> --devices --links --times --block-size=2048 --recursive -D --one-file-system >> --exclude=/proc --exclude=/sys --ignore-times . / >> >> You can see here that the rsync is being passed two directories: '.' and >> '/'. >> Is that normal? I think this may be the root of my problem, but I can't >> quite >> figure out how the . is getting there. Any suggestions? >> >> Paul >> > > > > ----------------------------------------------------------- > If you live in a small town /You might meet a dozen or two/ > Young alien types /Who step out /And dare to declare/ > "We're through being cool." -- Devo, "Through Being Cool" > ----------------------------------------------------------- > > -----10945 days until retirement!----- > > > > ------------------------------ > > Message: 3 > Date: Sat, 3 Nov 2007 20:55:58 -0400 (EDT) > From: Bradley Alexander <st...@tu...> > Subject: [BackupPC-users] Backing up VMs > To: bac...@li... > Message-ID: <18838235.611194137758950.JavaMail.root@merrimac> > Content-Type: text/plain; charset="utf-8" > > I have a VMware server with a number of virtual servers (as well as a > VirtualBox installation on another box). > > Is it better to back up the virtual hosts individually or to just back up > the VMware/VirtualBox installation? From a space perspective, if anything > changes in the virtual machine, does the entire VM get backed up, as > opposed to the individual file getting backed up again, thereby making the > backups in general smaller? > > Thanks, > --b > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 4 > Date: Sat, 3 Nov 2007 20:48:47 -0500 (CDT) > From: Paul Archer <ti...@io...> > Subject: Re: [BackupPC-users] Backing up VMs > To: "BackupPC users' mailing list" > <bac...@li...> > Message-ID: <200...@er...> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > 8:55pm, Bradley Alexander wrote: > >> I have a VMware server with a number of virtual servers (as well as a >> VirtualBox installation on another box). >> >> Is it better to back up the virtual hosts individually or to just back up >> the VMware/VirtualBox installation? From a space perspective, if anything >> changes in the virtual machine, does the entire VM get backed up, as >> opposed to the individual file getting backed up again, thereby making >> the backups in general smaller? >> > In general, you're better off backing up the virtual machines as if they > were real machines. That way you'll be able to do incrementals. If you > backup the files that represent the virtual disks, you'll have to get the > entire file all over again for even minor changes. > You may want to look around for a specialized backup solution that > understands VMs, something that can do a binary diff on the disk image > files. Keep in mind that if you do that, you won't really be able to > restore > by individual files. (That's another advantage of backing up the machines > individually (from within the OS.)) > > Paul > > > > ------------------------------ > > Message: 5 > Date: Sat, 3 Nov 2007 22:16:17 -0400 (EDT) > From: Stephen Joyce <st...@ph...> > Subject: Re: [BackupPC-users] Backing up VMs > To: Paul Archer <ti...@io...> > Cc: BackupPC users' mailing list > <bac...@li...> > Message-ID: > <Pin...@he...> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Sat, 3 Nov 2007, Paul Archer wrote: > >> In general, you're better off backing up the virtual machines as if they >> were real machines. That way you'll be able to do incrementals. If you >> backup the files that represent the virtual disks, you'll have to get the >> entire file all over again for even minor changes. > > I agree; treat the VMs as regular PCs. If the guest OS is Windows and you > have no other bare-metal recovery plan, a monthly ASR backup, in addition > to your normal fulls and incrementals, is good insurance against disaster. > (Because ASR operates on all of C: it's a good idea to keep C: small and > store data on another partition). It's a good idea for VMs and real Ms. > > Keep in mind that if you do back up the VM disk files from the host OS > you'll probably need to suspend or poweroff the VM for the duration of the > backup, which may take a very long time (vmware recommends this anyway) or > make sure the VM disk files are on a filesystem on the host OS that > supports snapshots or some other occult mechanism of insuring the disk > files are quiescent. > > Hope this helps! > > Cheers, Stephen > -- > Stephen Joyce > Systems Administrator P A N I C > Physics & Astronomy Department Physics & Astronomy > University of North Carolina at Chapel Hill Network Infrastructure > voice: (919) 962-7214 and Computing > fax: (919) 962-0480 http://www.panic.unc.edu > > > > ------------------------------ > > Message: 6 > Date: Sat, 3 Nov 2007 20:42:54 -0700 > From: dan <dan...@gm...> > Subject: Re: [BackupPC-users] Backing up VMs > To: "Stephen Joyce" <st...@ph...> > Cc: BackupPC users' mailing list > <bac...@li...> > Message-ID: > <470...@ma...> > Content-Type: text/plain; charset="iso-8859-1" > > i only run some test servers and redundant servers on vmware but i treat > them like a real machine. monthly, i power down the VM and do a snapshot > on > the host. best of both worlds. then the VM host gets backed up and i > have > a long term backup of the VM image. > > On 11/3/07, Stephen Joyce <st...@ph...> wrote: >> >> On Sat, 3 Nov 2007, Paul Archer wrote: >> >> > In general, you're better off backing up the virtual machines as if >> > they >> > were real machines. That way you'll be able to do incrementals. If you >> > backup the files that represent the virtual disks, you'll have to get >> the >> > entire file all over again for even minor changes. >> >> I agree; treat the VMs as regular PCs. If the guest OS is Windows and you >> have no other bare-metal recovery plan, a monthly ASR backup, in addition >> to your normal fulls and incrementals, is good insurance against >> disaster. >> (Because ASR operates on all of C: it's a good idea to keep C: small and >> store data on another partition). It's a good idea for VMs and real Ms. >> >> Keep in mind that if you do back up the VM disk files from the host OS >> you'll probably need to suspend or poweroff the VM for the duration of >> the >> backup, which may take a very long time (vmware recommends this anyway) >> or >> make sure the VM disk files are on a filesystem on the host OS that >> supports snapshots or some other occult mechanism of insuring the disk >> files are quiescent. >> >> Hope this helps! >> >> Cheers, Stephen >> -- >> Stephen Joyce >> Systems Administrator P A N I >> C >> Physics & Astronomy Department Physics & >> Astronomy >> University of North Carolina at Chapel Hill Network >> Infrastructure >> voice: (919) 962-7214 and >> Computing >> fax: (919) 962-0480 >> http://www.panic.unc.edu >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> BackupPC-users mailing list >> Bac...@li... >> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki: http://backuppc.wiki.sourceforge.net >> Project: http://backuppc.sourceforge.net/ >> > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ------------------------------ > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > > > End of BackupPC-users Digest, Vol 19, Issue 4 > ********************************************* > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.15.13/1099 - Release Date: > 10/30/2007 10:06 AM > |