On Fri, Jan 4, 2013 at 9:08 AM, Travis Schwenke
<travis.schwenke AT gmail DOT com> wrote:
>
>> Are you talking about the "backuppc" system user, which owns the data
>> files
>> and SSH keys, and runs some programs like rsync? Or are you talking about
>> the HTTPauth user? Your example commands seem to indicate that you
>> understand there are two.
>
> Well, I figured there were two but wasn't 100% sure. So the frustrating
> part would be that I seem to NOT know then the password to the backuppc USER
> that was created on the system.
It may not have a valid password and probably doesn't have a valid
shell. They aren't necessary and omitting them is good for security.
You just need to know how to work around it.
> After the install it gave me a password and
> that works for the web page but obviously NOT for the user, since su fails.
> I also tried su -s /bin/bash backuppc, but the password seemed wrong.
If you start as root, you don't need the password.
> Guess
> I might need to open a shell as root (or sudo) so that I can force change
> the password. Just frustrating that on a clean install I can't even RUN the
> command all the instructions say to run. I am not totally used to the sudo
> thing since I had Mandriva running for years and would su over to the root
> to fix/update system things.
On ubuntu, the problem is that root doesn't get a password. So, use
sudo su - (or maybe the special-case 'sudo -i') with your password to
become root. From there you can
su -s /bin/bash backkuppc
>> Consider also adding a symlink to your new destination:
> Not sure what benefit this has if I just point to a new spot?? The /data01
> is a 800Gb partition on a separate drive, the other 200Gb is mounted as /www
> or /ftp (don't remember how I did that 2 weeks ago!). In any case I have
> /data01, /data02 and /data03 all mounted at the root right now which are all
> individual drives. (/data02 is the main one I need to backup on this
> system, has all our music etc!)
The simple-minded approach here is to mount your volume at
/var/lib/backuppc (where the distribution packager decided it should
be) _before_ installing the package. Moving it works, of course,
with varying degrees of hassle.
>> 2. Test your SSH key authentication carefully. Consider giving the
>> backuppc
>> user a shell (see "sudo chsh backuppc"), temporarily, so you can login and
>> test. I give it one permanently, although that could be regarded as a
>> security risk.
If you understand the options with sudo and su, you don't need that.
> Ok, I have to do all this (maybe, might stick with tar). My first thing was
> to get the BackupPC running and backing up the windows boxes in the house
> using smb (to the RIGHT SPOT).
You mentioned something about your 'only' list being ignored. When
you specify this, the 'key' part is the sharename or '*' for all
shares, and the value is the path to back up. And with smb you can't
specify both backupfilesonly and backupexclude because there is no way
to pass both to the client.
--
Les Mikesell
lesmikesell AT gmail DOT com
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
