|
From: James W. B. <jbe...@mi...> - 2003-06-23 13:56:08
|
Hi all:
I've installed BOBS on a Fresh RH 9.0 setup. It's running but I'm not
getting backups. on the Current tab in the upper right corner I have
"185718904.Preparation failed (mount)
130810167.Preparing backup
130810167.Preparation failed (mount)
When I run the configuration check on the admin screen I get Pass for
everything except this:
Attempting to write, read and delete a file on
/backup/bobsdata/current/process/mounts/main/Admin Directory FAIL
Write file test failed with these messages:
file already exists.
(server name is 'main' and the directory mounted via NFS is 'Admin')
The messges in the server logs show the successfull authentication and
mount
and unmount of the directory as BOBS does it so there isn't an error there.
Do I have some kind of permission/user/owenership issue?
Any help is appreciated. I'm sure it's a stupid mistake on my part since
this appears to work for most people out of the box.
James
James W. Beauchamp, P.E.
2121 Newmarket Pkwy.
Suite 140
Marietta, GA 30067
phone - 770-690-9552 ext. 227
fax - 770-690-9529
www.gesinc.com
|
|
From: Joe Z. <jz...@at...> - 2003-06-24 02:55:29
|
James W. Beauchamp wrote:
> Hi all:
> I've installed BOBS on a Fresh RH 9.0 setup. It's running but I'm not
> getting backups. on the Current tab in the upper right corner I have
> "185718904.Preparation failed (mount)
> 130810167.Preparing backup
> 130810167.Preparation failed (mount)
>
> When I run the configuration check on the admin screen I get Pass for
> everything except this:
>
> Attempting to write, read and delete a file on
> /backup/bobsdata/current/process/mounts/main/Admin Directory FAIL
> Write file test failed with these messages:
>
> file already exists.
>
>
>
> (server name is 'main' and the directory mounted via NFS is 'Admin')
>
> The messges in the server logs show the successfull authentication and
>mount
> and unmount of the directory as BOBS does it so there isn't an error there.
> Do I have some kind of permission/user/owenership issue?
>
> Any help is appreciated. I'm sure it's a stupid mistake on my part since
> this appears to work for most people out of the box.
>
> James
>
>
> James W. Beauchamp, P.E.
>
>
That's a tough one. "Check Configuration" says it can mount and unmount
okay, but the mount command during the backup fails - that's where the
"Preparation failed (mount)" message comes from.
Let's start with the "file already exists." error in Check
Configuration. The test is to write a file named "bobswritetest.out" and
then delete it. See if that file exists on the 'main' computer, delete
it if it does. Then on the bobs computer, with the Admin nfs share
un-mounted, see if that file exists in
/backup/bobsdata/current/process/mounts/main/Admin and delete it if it
does. Then, copy the mount command from the Check Configuration page and
manually run it as root. Then 'touch
/backup/bobsdata/current/process/mounts/main/Admin/bobstest.out' and see
if you get an error. If the write is successful, delete the file and
unmount the share.
I notice your data directory is /backup/bobsdata instead of
/var/bobsdata. I assume you used './configure --with-bobsdata=/backup'.
That should be okay.
If you want to debug the actual backup, here's what you do (I hope I
don't leave out something).
As root:
* Comment out the check_loop line in /etc/crontab with a #.
* Kill the cmdloop process: 'kill $(pidof -x cmdloop)'
* Run the backup: /etc/cron.daily/backup.php
* cd /backup/bobsdata/current/process/cmd. You should have several
scripts sitting there waiting to run. They were created by backup.php.
* Run each script in numerical order with ./script_name. For the
bash scripts, if you want to see the commands being run you can
run them as 'sh -xv script_name'. With patience and careful
looking you should be able to spot the point of failure and see
what the error message is.
Please let me know how it goes.
Joe
|
|
From: Arnaud C. <arn...@ar...> - 2003-06-24 18:22:07
|
Hi, I've been using BOBS for some time now and there is something strange i've been noticing... I run bobs on a linux RH9 srv with large disks which backups several servers such as NT4 SRV servers, and Linux servers running samba. I use the smb way for all the backups... (why not NFS would you say?... i didn't have time to set this up, and moreover the smb way works just fine...). But speaking of the NT4 servers, i've noticed lots of backups done everyday, lots of things in the incremental folder... After a little research, i saw that the backup server saved lots of files on the NT4 server whereas neither the file's content change, nor the modification time. BUT, it seems that my backup server saves files which have been lately accessed, and on which the "last accessed time" changed. For a reminder, on a NTFS time you have 3 times: -creation time -modification time -last access time you can never see the "last access time" because windows updates this one each time you access the file... and in my backups, the files in current and in incremental are strictly the same (same name, same creation/modif time)... Am I the only one with this issue? Is there a way to prevent this to happen (except kicking NT4 away for linux based servers ;) ) Bye Arnaud. |
|
From: James W. B. <jbe...@mi...> - 2003-06-24 18:55:11
|
Arnaud: I've seen this quite a number of times in the past when using smbmount to mount shares on a Windoze box. If you look at the archives for samba you'll see many references to this in relation to backups and backup software in general. I believe there is a bug in smbmount that causes this IIRC and I don't believe there is much you can do about it. If I've misspoken I'm sure somone will correct me. HTH James ----- Original Message ----- From: "Arnaud CONCHON" <arn...@ar...> To: <bob...@li...> Sent: Tuesday, June 24, 2003 2:21 PM Subject: RE: [Bobs-devel] Backup files from a NT4 server... > Hi, > I've been using BOBS for some time now and there is something strange i've > been noticing... > I run bobs on a linux RH9 srv with large disks which backups several servers > such as NT4 SRV servers, and Linux servers running samba. I use the smb way > for all the backups... (why not NFS would you say?... i didn't have time to > set this up, and moreover the smb way works just fine...). But speaking of > the NT4 servers, i've noticed lots of backups done everyday, lots of things > in the incremental folder... After a little research, i saw that the backup > server saved lots of files on the NT4 server whereas neither the file's > content change, nor the modification time. BUT, it seems that my backup > server saves files which have been lately accessed, and on which the "last > accessed time" changed. For a reminder, on a NTFS time you have 3 times: > -creation time > -modification time > -last access time > > you can never see the "last access time" because windows updates this one > each time you access the file... and in my backups, the files in current and > in incremental are strictly the same (same name, same creation/modif > time)... Am I the only one with this issue? Is there a way to prevent this > to happen (except kicking NT4 away for linux based servers ;) ) > > Bye > Arnaud. > > ---------------------------------------------------------------------------- ---- ---------------------------------------------------------------------------- --------------- Ce message et toutes les pièces jointes sont confidentiels et établis à l'attention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur. Le Groupe C3D, ses filiales et ses partenaires déclinent toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. This message and all attachments are confidential and intended solely for the addressees. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you receive this message in error, please delete it and immediately notify the sender. Neither C3D Group nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ---------------------------------------------------------------------------- --------------- |