Ashley Paul James wrote:
Ronnie
Wow, that worked like a charm. One of three client servers are
currently backing up now, with no 'permission denied' errors. I am
pretty excited and i can now move on to building a trixbox server.
In retrospect the solution you suggested makes sense, my cmd line had
incorrect syntax. A fellow worker suggested i place the command in the
rc.local file. So the drive will mount upon reboot.
Thanks
---------------------------------------------------------
Ashley Paul James
Systems Administrator
Uniserve Communications Corp.
On 20-Mar-08, at 9:12 AM, Ronnie Gilkey wrote:
Ashley Paul James wrote:
Hi all,
I just signed on the mailing list, so hello to all.
I've been battling with an issue for over a week now, so I am pretty
exhausted from doing the same thing everyday. Its for a client so
they need a backup done.
It could be a simple fix, something I have missed after looking at
the same problem day in/day out. Im hoping some person out there can
help me.
First of the backupPC server is a vmdk running on ESX, though the
fact that its ESX should not matter.
The backupserver is on a private 192 network along with 3 clients
using a 2nd interface.
The NAS drive is a LaCie Big Ethernet Disk (1TB) with a 192.168.10.x
IP with a username and share name call backuppc.
SMB is being used to connect to the share as the LaCie will only use
SMB for linux. (CIFS to)
The NAS drive is formatted as xfs and cannot be changed.
To connect to the GUI I run a ssh tunnel.
I have mounted the NAS drive using the below cmd in fstab on the
backupserver.
//192.168.10.x/backuppc /mnt/net-storage smbfs
rw,uid=105,umask=666,username=backuppc,password=backuppc,auto
0 0
The drive mounts perfectly.
I have tried it with out the uid and umask and it works fine. (I
added these in as a last effort).
The basic trouble is BackupPC cannot write to the NAS drive as user
backuppc. You cannot run 'chown' any files on the NAS drive.
I have su'd to backuppc and ran the ./BackupPC_dump -v -f
192.168.10.x but receive a 'permission denied' error on creating
the file structure on the NAS drive.
Obviously you receive a similar error when you run a backup from the GUI
I have also added backuppc to the sudo file and ran the above cmd as
sudo. An error is produced informing that you must 'su backupppc' to
run it.
When you cd to the NAS drive you cannot create a file as user
backuppc, unless you sudo backuppc first.
As root you can create files on the NAS
All the files on the NAS drive are owned by root.user and cannot be
changed.
My research into this matter has not present many options.
Thanks all
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Ashley,
You can use smbmount (or mount.cifs on newer systems). And do this:
smbmount //192.168.10.x/backuppc /mnt/storage -o
username=DOMAIN\\USER,password=PASSWD,uid=backuppc,gid=backuppc
You won't be able to use fstab (that I know of), but the permissions
will work.
Thanks,
Ronnie Gilkey
[EMAIL PROTECTED]
--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com
Visit http://www.puryear-it.com/publications.htm to download your free
copies of:
"Best Practices for Managing Linux and UNIX Servers"
"Spam Fighting and Email Security in the 21st Century"
Ashley,
I'm not sure what distro you're running,but it is using SYS V based
controls. In my backuppc init script I have the line:
-------------------------------------------------------------------------------------
# chkconfig: - 91 35
-------------------------------------------------------------------------------------
I would recommend writing a small init script to handle this that
started at:
-------------------------------------------------------------------------------------
# chkconfig: - 90 40
-------------------------------------------------------------------------------------
This will ensure that it mounts the file system before BackupPC starts
and it will unmount it after BackupPC is halted. If you use rc.local,
the file system will not be mounted until after all other services,
including BackupPC, have started. This may or may not cause you
issues. If you use a script to do this you can prevent that.
Thanks,
Ronnie Gilkey
[EMAIL PROTECTED]
--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com
Visit http://www.puryear-it.com/publications.htm to download your free
copies of:
"Best Practices for Managing Linux and UNIX Servers"
"Spam Fighting and Email Security in the 21st Century"
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
