OK, that makes a little sense now. The ssh/tar line is the remote extract command and the BackupPC_tarCreate line is the local command to send it the tar archive. Backuppc arranges a pipeline between these commands. I normally use (and recommend) rsync instead of tar so mine look a little different.
I still don't understand why the remote command is going to host fichiers00 but it is being extracted from what must be configured in backuppc as localhost. Do you have a ClientAliasName set for it? Yes I added a sudo based on certain recommandations in wikis and forums so that the backuppc user could execute the tar command successfully. The backup part (it's a tar backup) works so I'm guessing that sudo concept is working for me. Note that there are separate command settings for backups and restores. And since restores aren't working, I'm guessing your change isn't working... Yes, a download of a tar image works (as does the zip). It's only the in-place restore that gives me a problem. Sometimes it helps to debug a problem if you compare the things that work to the one that doesn't. The download version of a restore should show the working BackupPC_tar_Create command line. If it is the same as it is in the non-working remote restore, the problem must be in the remote tar command part. Double-check the change you made to the restore command and figure out why the hostname is different in the 2 lines. But, my 'big-picture' recommendation would be to switch to rsync if possible, mostly because the incrementals will correct instead of just looking at timestamps. -- Les Mikesell lesmikesell < at > gmail.com ------------------------------ Les, Thanks again for the replies. Yes, there is a ClientAlias. I'm not entirely sure WHY I put that in there (i.e. did it solve a problem or something). Do you think it's problematic or did you simply need to understand why it was there? Looking at the logs for the successful tar download sounds interesting...if I could find them! ;c) I'm not seeing any logs (in the web interface) for download processes. Do you know if those are, in fact, stored somewhere? I looked at the BackupPC_tarCreate code to find the "bad share or directory" message. It's only in one place and it is produced as the result of a failed Perl FIND function. So that makes me think that the "sudo tar" question is not the source of the issue, but unfortunately, I've never messed with Perl so to recreate a test with all the variables filled in to figure out exactly WHAT it's complaining about is a bit beyond me. I use rsync for backing up some windows machines and when I do a backup that is from one machine to another simply to save bandwidth. Since this was local, I went with the default tar. I could see if an rsync restore gives me better results, though it would be nice to see something work that's supposed to. Thanks! +---------------------------------------------------------------------- |This was sent by da...@leighweb.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ 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/
