On 2013-01-04 12:40, Travis Schwenke wrote:
>   * Ok.. I can't even change backuppc password!  I figured I would su over
>     to backuppc but that doesn't even work.  *How do I change the password
>     on Ubuntu?*

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.

However, your example commands also run as "travis@TAS-Server", not root.
Consider using sudo, as travis can't edit most of these files.

>   * Ubuntu seems to install (without a prompt) the data directory at
>     /var/lib/backuppc (owner: backuppc / group: backuppc).  *I really want
>     to change this* as that is NOT where I reserved space.

Change $Conf{TopDir} in /etc/backuppc/config.pl and restart BackupPC.
Consider also adding a symlink to your new destination:

sudo mv /var/lib/backuppc/* /data01/
sudo ln -s /data01 /var/lib/backuppc

However, it is easy to remount or bind /data01 to /var/lib/backuppc:

mount -o bind /data01 /var/lib/backuppc

In /etc/fstab:

/data01 /var/lib/backuppc               none    bind    0       0

>       o I did read some of the things I found and it looked like in my
>         version I could just change TopDir (which is NOT in the GUI) but
>         when I tired, I broke the web GUI.  My guess is that I changed the
>         file using root and I then had a permission issue.
>       o This really gets me back to, *how should I be changing these
>         files?*

Editing the file with sudo or root is fine. The permissions won't change.
*Copying* the files will result in the new files being owned by the wrong
user, unless you do "cp -a".

If you change TopDir, you'll have to restart BackupPC.

Some *really* important tips:

1. Give BackupPC its own filesystem. Do not use the filesystem at
/var/lib/backuppc (/data01 for you) for any other purpose. Some months down
the line you'll need to fsck this filesystem while the server is online and
you'll regret it if you didn't separate them. I used a shared /var/
partition until recently and it bit me in the butt repeatedly.

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.

3. Your BackupPC filesystem must support hardlinks. It sounds like you've
done this before, but /data01 in your case must be ext2/3/4, xfs, or some
other filesystem that supports hard links. There's plenty of discussion on
this but I'm quite happy with ext4 and its default options.

Regards,
Tyler

-- 
"Those who make peaceful revolution impossible will make violent
revolution inevitable."
   -- John F. Kennedy

------------------------------------------------------------------------------
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/