bobs-devel — Developer mailing list

Re: [Bobs-devel] Wording in admin.php

[Joe Z. <jz...@co...>]

Jochen Metzger wrote:

>Hi Joe,
>
>Am Son, den 28.12.2003 schrieb Joe Zacky um 23:12:
> 
>  
>
>>I'm in California. It's 9 hours earlier here than Denmark. I'm guessing 
>>you're in Europe somewhere.
>>    
>>
>Yes, I am from Berlin, Germany.
>  
>
>Cheers 
>
>Jochen
>
>.. and have a nice day.
>Is it far from the beach? I love the seaside.
>  
>
Yes it is, about 3 hours away. California's a big place and I'm in the 
Central Valley in Fresno. My wife wishes we lived by the beach. At least 
we have a pool. It tends to get over 110 degrees in the summer.

Rene,
Thanks for checking those changes into cvs. I hope to try it out next 
weekend.

Joe

Re: [Bobs-devel] rsync over ssh -> ready

[Rene R. <re...@gr...>]

On Sun, 2003-12-28 at 23:48, Jochen Metzger wrote:
> > 
> > I guess it depends on whether we want to be able to browse the files without
> > being able to restore.
> Yes, that is a good question.
> Practically speaking, I would open my konqueror, open a sftp to the 
> backup server on left side and another sftp to the webserver on right
> side and then transfer.
> 
> I think browsing the files just makes sense, when you can restore them..
> What is your opinion Rene and Joe.
> 

You could be right. I'm fine with that solution.

> > 
> > 1. No access to the UI at all.
> > Simple to implement.
> > 
> THAT was the I did it now:
> 
Yes. I'm fine fine with this solution as implemented.


> > 3. Access to the UI, and ability to restore to the originating server.
> > Could be complex. How hard I'm really not able to say at the moment.
> > I'm a bit rusty on the internal workings of bobs.
> I would appreciate 3. of course:
> 

I'll take a closer look at implementing this. Sftp looks good to me and
this would give bobs a great new feature which would be useful to a lot
of people. Including myself.

> The scenario I am thinking about at present, is:
> 
> A user having an account on our webserver can 
> open the bobs-browser on the backup-machine
> and login with his account data (which is equal to his account
> on the webserver)

I would suggest getting rid of the dropdowns completely in that case.
Make the users type in the servername and sharename they wish to access.
They would get some fairly large dropdowns if you have a lot of users.

> Then he restores the data he needs, the data is restored using
> rsync and that is it.
> 
> But, I think this is more than a footstring away at present.
> Not sure about it. 
> 

Actually this seems to be rather easy to implemnt if we are using
private/public keys and sftp to do the copying.

> 
> mhm, can you have a look at current solution (1.) and tell me if 
> if it fits or something like (2.) would be better?

Well. 1. works and doesn't present a problem. 

> BTW... could you give me a commit access to sf.net like suggested?

Yes. I just need your sourceforge user number and/or sourceforge
username. 


Joe, do you have any comments on the changes proposed?

Otherwise I'll merge this and then have a go at make rsync_ssh 
restoring work.
I'll also bump the version number to 0.6.1 and include a doc 
describing how to make a key pair for the auth part.


Cheers
Rene

Re: [Bobs-devel] Wording in admin.php

[Jochen M. <ml...@om...>]

Hi Joe,

Am Son, den 28.12.2003 schrieb Joe Zacky um 23:12:

> >
> >Maybe it'll take some time to hear from you, cause you 
> >are sleeping, when I'm up.
> > 
Cool, well I am going to bed at approximately an hour or so...;o)

>  
> >
> I'm in California. It's 9 hours earlier here than Denmark. I'm guessing 
> you're in Europe somewhere.
> 
Yes, I am from Berlin, Germany.

> I'm printing out some of your emails. I like your ideas, 

THX
> and the 
> research and work you've done, especially the ssh/rsync stuff. It's 
> going to take me some time to review and try them out. I hope you'll 
> take Rene up on his offer to give you cvs commit access.
> 
yes maybe, but a present I do not know how much I can contribute, cause
I have to keep my business running.

> As far as who did what on bobs; Rene wrote bobs. I joined later and 
> rewrote the admin interface and did the make/install/rpm packaging.
> 
Yes, I got that from rene too.

> Joe
Cheers 

Jochen

.. and have a nice day.
Is it far from the beach? I love the seaside.

Re: [Bobs-devel] rsync over ssh -> ready

[Jochen M. <ml...@om...>]

Hi Rene,
hi Joe,

now I was a bit too quick.


> 
> I guess it depends on whether we want to be able to browse the files without
> being able to restore.
Yes, that is a good question.
Practically speaking, I would open my konqueror, open a sftp to the 
backup server on left side and another sftp to the webserver on right
side and then transfer.

I think browsing the files just makes sense, when you can restore them..
What is your opinion Rene and Joe.

> 
> A few possible solutions:
> 
> 1. No access to the UI at all.
> Simple to implement.
> 
THAT was the I did it now:

I have already implemented that no.
So I have double security here. 

1st) You cannot login to the server:
 cause: It does not show up in http://bobsdomain/bobs/
        when it is of restore_method = "none"

2nd) If you would do it with the correct REQUEST var via URL,
     you still cannot, because it is prohibited
     in class_server.php (method login)

Should we leave it that way or do something else about it?
At present it is in the patch attached as unified diff.

> 2. Access to the UI but no restore functionality.
> Also fairly simple to implement.
> 
> 3. Access to the UI, and ability to restore to the originating server.
> Could be complex. How hard I'm really not able to say at the moment.
> I'm a bit rusty on the internal workings of bobs.
> 
> 4. Access to the UI, and ability to restore somewhere else than the
> originating server.
> Possibly as (hard or soft) linked files. That those files could be
> accessed using sftp, smb rsync, nfs or what else you set up.
> Or plainly just using another server as receiver of the restored files.
> This would most likely require extensive testing since this goes to the
> heart of bobs.
> Almost everything is on someway connected to 
> "$this->backupdir . '/' . $this->server . '/' . $this->share"
> Changing the usage of those three vars requires touching most of the 
> code is one way or another.
> 
I would appreciate 3. of course:

The scenario I am thinking about at present, is:

A user having an account on our webserver can 
open the bobs-browser on the backup-machine
and login with his account data (which is equal to his account
on the webserver)

Then he restores the data he needs, the data is restored using
rsync and that is it.

But, I think this is more than a footstring away at present.
Not sure about it. 

Of course this is an ideal ISP - Solution in my opinion.

> If you are too busy with other projects 
Yes, that is really my problem at present. But it does not really
change. I always squeeze some time in between to work on also im-
portant projects (like backuping now).

I suggest the second solution and
> printing a notice when users log in. 

mhm, can you have a look at current solution (1.) and tell me if 
if it fits or something like (2.) would be better?

BTW... could you give me a commit access to sf.net like suggested?

Cheers 

Jochen 

Re: [Bobs-devel] rsync over ssh -> ready

[Rene R. <re...@gr...>]

> > I would prefer a check against the "none" method to determine if a login
> > succeeds. Just implementing this without a proper check is bad. 
> > 
> O.K. not a prob. You are right, that is the most proper method. I can do
> it with just some small changings in the class_restore.php class , I
> assume.
> 

I really need to get better at replying properly to emails.

I guess it depends on whether we want to be able to browse the files without
being able to restore.

A few possible solutions:

1. No access to the UI at all.
Simple to implement.

2. Access to the UI but no restore functionality.
Also fairly simple to implement.

3. Access to the UI, and ability to restore to the originating server.
Could be complex. How hard I'm really not able to say at the moment.
I'm a bit rusty on the internal workings of bobs.

4. Access to the UI, and ability to restore somewhere else than the
originating server.
Possibly as (hard or soft) linked files. That those files could be
accessed using sftp, smb rsync, nfs or what else you set up.
Or plainly just using another server as receiver of the restored files.
This would most likely require extensive testing since this goes to the
heart of bobs.
Almost everything is on someway connected to 
"$this->backupdir . '/' . $this->server . '/' . $this->share"
Changing the usage of those three vars requires touching most of the 
code is one way or another.

If you are too busy with other projects I suggest the second solution and
printing a notice when users log in. The give you a working UI with
little work required.

Cheers
Rene

Re: [Bobs-devel] Wording in admin.php

[Joe Z. <jz...@co...>]

Jochen Metzger wrote:

>Am Son, den 28.12.2003 schrieb Joe Zacky um 01:09:
>
>Hi,
>
>so where you from? I think we are having a time difference.
>You answered me in the middle of the night. Not really ->
>At 1.09 AM, based on my local time. What was the time
>at your place.
>
>Maybe it'll take some time to hear from you, cause you 
>are sleeping, when I'm up.
>  
>
I'm in California. It's 9 hours earlier here than Denmark. I'm guessing 
you're in Europe somewhere.

I'm printing out some of your emails. I like your ideas, and the 
research and work you've done, especially the ssh/rsync stuff. It's 
going to take me some time to review and try them out. I hope you'll 
take Rene up on his offer to give you cvs commit access.

As far as who did what on bobs; Rene wrote bobs. I joined later and 
rewrote the admin interface and did the make/install/rpm packaging.

Joe

Re: [Bobs-devel] rsync over ssh -> ready

[Rene R. <re...@gr...>]

Hi Jochen

> > 
> > Does this include the ssh key you described earlier? 
> > 
> 
> I am not sure, what you exactly mean.
> I have implemented it with the public/private key feature, not using
> a password at all, cause this is more safe.

That is what I meant with the question. Just wanted to be sure I wasn't
going down a wrong track.


> > 
> O.K. not a prob. You are right, that is the most proper method. I can do
> it with just some small changings in the class_restore.php class , I
> assume.
> 

Great! Just to clear things up a bit:
Joe is the mastermind behind the configuration (admin) pages and the
configuration/install parts.

There is a pretty clean split from those files to the user interface and
its functions to the backup code itself which I wrote.


> 
> > Its a time off for most people. I'll be happy to help you get your
> > changes included in bobs. Probably with a few changes to your work and
> > some to the restore code I made.
> 
> Well that would be great. I am glad to get some hints. The problem was, 
> I had to finish it, because I must switch back to some other project on
> Monday, so I had to get it finished.
> 

No problem. Please if you have any other features you need, let us know
so we can take that into consideration if we need to make changes.


> Can you give me a hint? What do you mean? I made the diffs on the
> commandline with 
> 
> cvs diff
> 
> That was all.
> 
> 

just do:

cvs diff -u > rsync_ssh.patch


> > But still, great work!
> Thanks a lot. I love the way you did that projekt. There is a lot
> brainwork within this architecture. 

A little too much at times ;). It was a simple idea born from a simple
thought: "Why should I spend so much time restoring files for users when
they know what they want better than me.". So i searched the net but
didn't find anything that would let me keep a live backup on a large
disk and let users do their thing. So BOBS was born.


Cheers
Rene

Re: [Bobs-devel] rsync over ssh -> ready

[Rene R. <re...@gr...>]

Jochen

Please change the way your patches are attached. 
It is pretty annoying to extract them from line wrapped emails.
If you just copied the file into the mail, please attach it and send it again.
Just one less error prone exchange method to worry about.

Cheers
Rene

Re: [Bobs-devel] rsync over ssh -> ready

[Jochen M. <j.m...@om...>]

Hi Rene,

nice to hear from you. I lived in Denmark as well for a 
couple of years, when I was a boy of five.


> > The differences are:
> > 1. rsync over ssh does not use sharenames (which were defined in
> > rsyncd.conf), you can just use the absolute paths (e.g. /path/to/dir)
> > 2. You need a username which you use for connection
> >    (Of course one could use the login name, but I didn't want to 
> >     use that, because it could be different in the "Internet Servers"
> >     case. If a user later on should have the ability to restore things
> >     he should have restricted rights, but a rsync user should probably
> >     have more rights to set ownerships etc.
> > 
> 
> Does this include the ssh key you described earlier? 
> 

I am not sure, what you exactly mean.
I have implemented it with the public/private key feature, not using
a password at all, cause this is more safe.

But, at present, the private key is not done automagically or something.
You have to do it by hand, as described in the earlier mail.
But it works o.k.

The rsync method you used before was assuming a non authorized access,
so you did not need a username / password at all.

> 
> > It is not really secure, because the server just does not turn up in the
> > select (under http://bobsdomain/bobs/) that all. Of course you could log
> > in by setting the correct vars in the request.
> > 
> I would prefer a check against the "none" method to determine if a login
> succeeds. Just implementing this without a proper check is bad. 
> 
O.K. not a prob. You are right, that is the most proper method. I can do
it with just some small changings in the class_restore.php class , I
assume.


> Its a time off for most people. I'll be happy to help you get your
> changes included in bobs. Probably with a few changes to your work and
> some to the restore code I made.

Well that would be great. I am glad to get some hints. The problem was, 
I had to finish it, because I must switch back to some other project on
Monday, so I had to get it finished.

> 
> > So here is my version. As Joe adviced, I checked out an cvs version and
> > made the changings (and testet them several times - they work / I put
> > them in the sources and made an installation (configure and make
> > install))
> > 
> > The I made the diffs. I tried to change as little as possible. 
> > 
> 
> Please make unified diffs in the future. 

Can you give me a hint? What do you mean? I made the diffs on the
commandline with 

cvs diff

That was all.


> I find those much easier to
> read and understand.  
is there a different way?


> But still, great work!
Thanks a lot. I love the way you did that projekt. There is a lot
brainwork within this architecture. 

> 
> > I hope that you like it. I am reading that list. So if some question are
> > coming up, I am ready to answer them
> 
> 
> I'll have a closer look now. I just wanted to say Hi! and welcome to the
> bobs team :)

Fine. ;o)
> 
> If you want cvs commit rights please let me know.
> 
Sure. But it is up to you. I cannot promise, that I can do many
changings and other stuff, because I have to keep my business running.
Of course commit rights would be great.

I am used to work with CVS and of course I will ask before commiting
something.


> Cheers
> Rene
> 
Cheers

Jochen Metzger

Hope you can get through it.

Re: [Bobs-devel] rsync over ssh -> ready

[Rene R. <re...@gr...>]

On Sun, 2003-12-28 at 19:39, Jochen Metzger wrote:

> The differences are:
> 1. rsync over ssh does not use sharenames (which were defined in
> rsyncd.conf), you can just use the absolute paths (e.g. /path/to/dir)
> 2. You need a username which you use for connection
>    (Of course one could use the login name, but I didn't want to 
>     use that, because it could be different in the "Internet Servers"
>     case. If a user later on should have the ability to restore things
>     he should have restricted rights, but a rsync user should probably
>     have more rights to set ownerships etc.
> 

Does this include the ssh key you described earlier? 


> It is not really secure, because the server just does not turn up in the
> select (under http://bobsdomain/bobs/) that all. Of course you could log
> in by setting the correct vars in the request.
> 
I would prefer a check against the "none" method to determine if a login
succeeds. Just implementing this without a proper check is bad. 

> So know I have been writing a lot. Unfortunately I could not get one of
> you, so I could have talked about some stuff to get it clear.
> 
Its a time off for most people. I'll be happy to help you get your
changes included in bobs. Probably with a few changes to your work and
some to the restore code I made.

> So here is my version. As Joe adviced, I checked out an cvs version and
> made the changings (and testet them several times - they work / I put
> them in the sources and made an installation (configure and make
> install))
> 
> The I made the diffs. I tried to change as little as possible. 
> 

Please make unified diffs in the future. I find those much easier to
read and understand.  But still, great work!

> I hope that you like it. I am reading that list. So if some question are
> coming up, I am ready to answer them


I'll have a closer look now. I just wanted to say Hi! and welcome to the
bobs team :)

If you want cvs commit rights please let me know.

Cheers
Rene

[Bobs-devel] rsync over ssh -> ready

[Jochen M. <ml...@om...>]

Hi,

as I needed rsync over ssh for my environment I have implemented it.
I have decided myself to implement it as extra "backup_method".

This way everything else stays untouched.

In my thread "..bobs for internet services.." you can find a description
of how ssh and rsync work together. 

rsync as implemented in the current cvs-bobs version did not go over
ssh, because the daemon - option, started by using "::" in the
commandline was stronger. So the "-e ssh"-option was "though present"
not used.

You can either use rsync over a daemon or ssh. 

Because there were some differences in the current implemented
"daemon"-rsync version in bobs, I decided to make up another
"backup method" to make it less complicated.

The differences are:
1. rsync over ssh does not use sharenames (which were defined in
rsyncd.conf), you can just use the absolute paths (e.g. /path/to/dir)
2. You need a username which you use for connection
   (Of course one could use the login name, but I didn't want to 
    use that, because it could be different in the "Internet Servers"
    case. If a user later on should have the ability to restore things
    he should have restricted rights, but a rsync user should probably
    have more rights to set ownerships etc.

Additional restore_method:
==========================

restore_method : "none"

Backing up from internet servers, I found NFS and smb to insecure, so I
decided myself to set the restore_method to none. 

I found this the easiest way. When setting this, you cannot log in to 
the restore area, cause you cannot choose those server who have restore
method none.

I know, this is just an interims solution. As mentioned in a mail before
it would be a nice way to use rsync as well to restore the files.
(making the access from the backup server to the remote server)

But I wanted to have a quick workaround.

It is not really secure, because the server just does not turn up in the
select (under http://bobsdomain/bobs/) that all. Of course you could log
in by setting the correct vars in the request.

So know I have been writing a lot. Unfortunately I could not get one of
you, so I could have talked about some stuff to get it clear.

So here is my version. As Joe adviced, I checked out an cvs version and
made the changings (and testet them several times - they work / I put
them in the sources and made an installation (configure and make
install))

The I made the diffs. I tried to change as little as possible. 

So here the diffs are:

I hope that you like it. I am reading that list. So if some question are
coming up, I am ready to answer them

Cheers

Jochen Metzger

Index: admin.php
===================================================================
RCS file: /cvsroot/bobs/bobs/admin.php,v
retrieving revision 1.24
diff -r1.24 admin.php
280a281,283
>         // avoid that "/" is used in Share name
>       if (substr_count($share,"/") > 0)
>           return "'/' is not allowed in the Share name (suggestion:
use '_' instead)";
358a362,368
> 
>     if (($settings['backup_method'] =='rsync_ssh')
>         && (trim($settings['rsync_ssh_path']) == "")){
>       return "Please specify the directory to backup on the rsync
Remote Server.";
> 
>     }
> 
Index: index.php
===================================================================
RCS file: /cvsroot/bobs/bobs/index.php,v
retrieving revision 1.5
diff -r1.5 index.php
69,81c69,99
<       echo '<form name="loginform" method="POST">';
<       echo "<p><big>Select the server and share you wish to
use</big><br><br>";
<       echo '<select name="server">';
<       foreach ( $srvcfg->servers as $server ) {
<               echo  '<option value="' . $server["server"] . '.' .
$server["share"] . '">'  . $server["server"] . ' / ' . $server["share"];
<       } 
<       echo '</select></p>';
<       echo '<p><big>Type the login name for the selected
server</big><br><br> <input type="text" value="login name"
name="loginname"></p>';
<       echo '<p><big>Type the password for the selected
server</big><br><br> <input type="password" name="password"></p>';
<       echo '<p><big>Press the Login button to
continue</big><br><br><input type="submit" name="login"
value="Login"></p>';
<       echo '<input type="hidden" name="trylogin">';
<       echo '</form>';
<       ?>
---
>         if (is_array($srvcfg->servers)){
> 
>         echo '<form name="loginform" method="POST">';
>         echo "<p><big>Select the server and share you wish to
use</big><br><br>";
> 
>         echo '<select name="server">';
>         foreach ( $srvcfg->servers as $server ) {       
>           if ($server["restore_method"] != "none")
>               $options.='<option value="' . $server["server"] . '.' .
$server["share"] . '">'  . $server["server"] . ' / ' .
$server["share"]."</option>";
>         }
>        
>         if ($options == ""){
>           $options.='<option value="">No Servers with Restore Ability
present</option>';
>         }
> 
>         echo $options;
> 
>         echo '</select></p>';
>         echo '<p><big>Type the login name for the selected
server</big><br><br> <input type="text" value="login name"
name="loginname"></p>';
>         echo '<p><big>Type the password for the selected
server</big><br><br> <input type="password" name="password"></p>';
>         echo '<p><big>Press the Login button to
continue</big><br><br><input type="submit" name="login"
value="Login"></p>';
>         echo '<input type="hidden" name="trylogin">';
>         echo '</form>';
> 
>       }
>       // show up when no servers are configured yet
>         else {
>         echo '<big>No servers configured yet.<br><a
href="admin.php">Configure Servers</a></big>';
>       }
> 
>         ?>
Index: inc/class_backup.php
===================================================================
RCS file: /cvsroot/bobs/bobs/inc/class_backup.php,v
retrieving revision 1.8
diff -r1.8 class_backup.php
28a29,37
> 
>         /* new stuff for rsync_ssh */
>         var $rsync_ssh_path     = '';   // name of the rsync path on
the remote server
>                                         // ssh only works with pathes
and not share on the remote server
>         var $rsync_ssh_user     = 'root';  // 'root' is default
>                                            // user used for connection
by ssh
>                                            // additional a public (on
remote server)/ private key (on backup server)  
>                                            // pair must be given 
> 
62d70
<               $this->restore_method   = $vol_conf["restore_method"];
64c72,79
<               
---
>               /* new stuff for rsync_ssh */
>               $this->rsync_ssh_path   = $vol_conf["rsync_ssh_path"];
> 
>                 /* only use when set, else stay default */
>               if (trim($vol_conf["rsync_ssh_user"]) != "")
>                 $this->rsync_ssh_user   = $vol_conf["rsync_ssh_user"];
> 
>               $this->restore_method   = $vol_conf["restore_method"];
147a163,167
> 
>                       case "rsync_ssh":
>                               $this->rsync_ssh_backup($exclude_from);
>                               break;
> 
155c175,177
< 
---
>       /* classic way -> rsync using an daemon 
>          * which has to run !!! on the remote side (backuped side)
>          */
173c195
<               $backupcommand  = 'rsync -e ssh --archive --verbose
--delete --backup ' ;
---
>               $backupcommand  = 'rsync --archive --verbose --delete
--backup ' ;
196a219,265
>       }
> 
> 
>       /* rsync_ssh used to backup with rsync over ssh */
>       function rsync_ssh_backup($exclude_from){
>         
>                // make backup using rsync over ssh
> 
>                // command to run, put ' > /dev/null &' at the end to
free the process and block output
> 
>               /*
>                options used for rsync
>                       --archive               = archive mode
>                       --verbose               = verbose execution
>                       --delete                = delete files from
backup when deleted on the original site
>                       --backup                = make backups
>                       --backup-dir=DIR        = move backups into this
dir
>                       --exclude-from=FILE     = exclude files listed
in this file
>               */
> 
>               // put together the script we need to execute
>               $backupcommand  = 'rsync -e ssh --archive --verbose
--delete --backup ' ;
>               $backupcommand .= $exclude_from;
>               $backupcommand .= '--backup-dir="' . $this->incomingdir
. '/' . $this->server . '/' . $this->share . '/"' ;
> 
>               // need to check if we are using IP or DNS!!!!
>               if ( $this->server_ip != '' ) {
>                       $backupcommand .= ' ' .
$this->rsync_ssh_user.'@'.$this->server_ip;
>               } else {
>                       $backupcommand .= ' ' .
$this->rsync_ssh_user.'@'.$this->server;
>               }
> 
>               // only one ":" when we use ssh 
>               $backupcommand .=  ':' . $this->rsync_ssh_path . ' "' .
$this->backupdir . '/' . $this->server . '/' . $this->share . '/"';
> 
>               $shell = "#!/bin/sh\n";
>               $shell .= "# Description: Backup files from server\n";
>               $shell .=  $backupcommand . "\n";
> 
> 
>               $this->command = $shell ;
> 
>               // add the script to command queue
>               $this->add_queue_command($shell, "bash");
> 
>               return $result;
> 
Index: inc/config.php.in
===================================================================
RCS file: /cvsroot/bobs/bobs/inc/config.php.in,v
retrieving revision 1.8
diff -r1.8 config.php.in
52,53c52,57
< $server_defs["backup_method"]["list"]["1"]      = "nfs";
< $server_defs["backup_method"]["list"]["2"]      = "smb";
---
> $server_defs["backup_method"]["list"]["1"]      = "rsync_ssh";
> $server_defs["backup_method"]["list"]["2"]      = "nfs";
> $server_defs["backup_method"]["list"]["3"]      = "smb";
> 
> 
> 
58a63
> $server_defs["restore_method"]["list"]["2"]     = "none";
89a95,109
> 
> 
> /* START OF ADDINGS for rsync_ssh */
> $server_defs["rsync_ssh_path"]["type"]                     = "path";
> $server_defs["rsync_ssh_path"]["desc"]                     =
"Directory on rsync Remote Host to backup (absolute / starting with
'/')";
> $server_defs["rsync_ssh_path"]["depends"]["name"]["0"]     =
"backup_method";
> $server_defs["rsync_ssh_path"]["depends"]["value"]["0"]    =
"rsync_ssh";
> $server_defs["rsync_ssh_path"]["depends"]["rule"]["0"]     = TRUE;
> 
> $server_defs["rsync_ssh_user"]["type"]                     = "text";
> $server_defs["rsync_ssh_user"]["desc"]                     =
"SSH-Connect with User (use 'root' by default)";
> $server_defs["rsync_ssh_user"]["depends"]["name"]["0"]     =
"backup_method";
> $server_defs["rsync_ssh_user"]["depends"]["value"]["0"]    =
"rsync_ssh";
> $server_defs["rsync_ssh_user"]["depends"]["rule"]["0"]     = TRUE;
> /* END OF ADDINGS for rsync_ssh */

Re: [Bobs-devel] .. responsible for gui ? / changing of structure ["list"]

[Jochen M. <ml...@om...>]

uups,


> 
> At present:
> <option value="rsync">rsync</option>
> <option value="rsync_ssh">rsync_ssh</option>
> 
> Could be:
> <option value="rsync">rsync (using daemon)</option>
> <option value="rsync_ssh">rsync (using ssh)</option>
> 
> Only two changings would be necessary for this:

ought to be changed.


Well I'll first make a suggestion for the rsync_ssh version 
and then you can have a look at it.

Think it would be nicer with the options the suggested way.

Cheers 

Jochen

[Bobs-devel] .. responsible for gui ? / changing of structure ["list"]

[Jochen M. <ml...@om...>]

Hi,

who did the concept for the gui?
Joe or Rene?

What I think about, is if it is possible to change the "list" item
in config.

The advantage would be, that one could seperate option and value,
which would be better if a option should be longer.

I am running into problems, creating another backup method in the 
options.

At present:
<option value="rsync">rsync</option>
<option value="rsync_ssh">rsync_ssh</option>

Could be:
<option value="rsync">rsync (using daemon)</option>
<option value="rsync_ssh">rsync (using ssh)</option>

Only two changings would be necessary for this:

1. definition in config.php.in
now:
$server_defs["backup_method"]["list"]["0"]      = "rsync";
then:
$server_defs["backup_method"]["list"]["rsync"]  = "rsync (using
daemon)";

2. little changing in "html_list":
gui.pinc

now:

  
        foreach ($options as $option){
            $html .= "<option value=\"$option\"";
            if ($value == $option) {
                $html .= " selected";
            }
            $html .= ">$option\n";
        }

then:
foreach ($options as $index => $option){
            $html .= "<option value=\"$index\"";
            if ($value == $index) {
                $html .= " selected";
            }
            $html .= ">$option\n";
        }

Advantages:

o Option could be more descriptive and independent from value
o Better support for probably multilanguage - support

Disadvantage:
o config.php.in not downwards compatible to 0.6.0

Looking forward to your feedback

[Bobs-devel] Wording: Server Details

[Jochen M. <ml...@om...>]

Hi,

I think there should be a prefix after

Servers IP Address 

Something like:

Servers IP Address ( optional / if Network name cannot be resolved )

What do you think about that.

Makes things clearer.
(Cause it also only used, when there is no entry for Network name,
although this is not possible in GUI)

Cheers

Jochen Metzger

Re: [Bobs-devel] Error when using "/" in share name

[Jochen M. <j.m...@om...>]

Hi,
> 
> >Another smal obstactle is the following:
> >4. When creating a new share and using "/" in the descriptive name
> >   the system will take it, but display an error, cause
> >   the corresponding ini-file (e.g. inc/servers/domain.share.inc)
> >   can not be created correctly.
> >
> >   -> What would be the best way to change this ? 
> >   Display an error? Or maybe change "/" in "_" while creating?
> >  
> >
> I think an error message would be appropriate. As discussed in your 
> other email, it's really a name and not a description.

so here comes the diff:

Index: admin.php
===================================================================
RCS file: /cvsroot/bobs/bobs/admin.php,v
retrieving revision 1.24
diff -r1.24 admin.php
280a281,283
>         // avoid that "/" is used in Share name
>       if (substr_count($share,"/") > 0)
>           return "'/' is not allowed in the Share name (suggestion: use '_' instead)";

THX

Jochen

Re: [Bobs-devel] .. using bobs for internet servers ....

[Jochen M. <ml...@om...>]

Am Son, den 28.12.2003 schrieb Joe Zacky um 01:31:

> >First of all I think that BOBS is a masterpiece of software.
> >I have installed it at a clients place, using it for his 
> >Fileserver (this is only Intranet though).
> >
> I think Rene did a great job and filled a vacant niche. It's hard to 
> come up with new software ideas. That's primarily why I joined this project.

Yes, that is pretty true... 

> 
> >
> >My current approach is to use it for backupping a mixture
> >of Intranet (2x) and Internet-Server (2x). 
> >
> >Approaching this my preferred backupping method is rsync 
> >through ssh. 
> >
> >Well, I have come through some obstacles concerning this:
> >
> >1. I do not want to have an rsync - daemon running on
> >   the Internet Server, but I have seen that class_backup.php
> >   (method: rsync_backup) uses one.
> >
> >2. I want to use user and pw for ssh. 
> >
> >3. I do not want to write a rsyncd.conf file on every server.
> >   At present with to Internet-Servers it is not problem,
> >   but of course you can do without, and it would be less 
> >   overhead like this.
> >  
> >
> Are you saying ssh can be used in place of rsync to copy the files from 
> one machine to the other? I've not used ssh that way before. Can you 
> give some more details on this?

Well, I have been spending about one day to get into the SSH / rsync
stuff.

There are to ways of using rsync:

o Use a daemon running on an own port ( started by e.g. rsync --daemon )
  (AFAIK this will make it impossible to use ssh
   - so the option 
  "-e ssh" in class_backup.php ( method rsync_backup) is IMHO 
superfluent (which also causes the error mentioned in the mailinglist)

o Use rsync in conjunction with ssh. So rsync makes an ssh tunnel and   
calls rsync on the remote server.

There is one easy way to figure out which one you are using:
(= difference between ":" and "::")

Example:
1. rsync -vre ssh /local/path ro...@re...::/save/here

Here the daemon (remote sync server) is used, cause you use "::".
(Refer to the manpages (man rsync) Section GENERAL
 There are six ways different ways of using rsync:
)
   So it would be the same to write:
   rsync -vr /local/path ro...@re...::/save/here

2. rsync -vre ssh /local/path ro...@re...:/save/here

Here we only use one ":" so the connection is done over a 
"remote shell program as the transport (such as rsh or ssh)"
(quoted from manpages)

=========

I would appreciate the second way, cause there are some advantages:
o secure connection
o not necessary to create rsyncd.conf on each backupped machine (less
overhead)
You do not need to create Shares.

o makes it possible (and secure) to backup internet hosts.
o no additional ports open on internet host.


There is of course an obstacle concerning the password:
>>>>>>>>
After studying a while, I found out, that the best way,
is to use authorized keys (private/public key),
cause there is no "plain" password for the backuped
server remaining on the backup server.

The thing is that you first have to create the authorized
keys and transfer them to the backuped server to get every
thing working.

Well, I have done this this way:
( I know using root is not the best way, but it is a
  present the way with the less overhead concerning right etc.)

Steps:
======
1. Login as root on the backup server.
2. ssh-keygen -t dsa
(it takes a while - about 5 minutes till the first output comes up)
Press Return (without entering a password) when prompted for passphrase
Press Return a 2nd time (without entering a password) when prompted for
passphrase a second time
(If additional questions are given always press return without further
input)
3. The DSA-pair is created in ~/.ssh/
   The following files can be found there now:
   id_dsa (private key - has to remain - and only there - on the
backupserver)
   id_dsa.pub (public - has to be transfered to all the backupped
machines)
4. cd .ssh
5. Now make up a sftp connection to backuped server as root
   ( you have to use the same user both on the backup (local machine)
     and the backupped server (remote machine))
   sftp ro...@re...
   
   #Now you are prompted for the password:    
   mypassword [ENTER]   

   # Transfer the public key now 
   cd .ssh
   put id_dsa.pub

   # Jump to Shell by just entering "!"
   !

   # Create a file authorized_keys2 or just add a line with the public
   # key of the backup server to it
   cat id_dsa.pub >> authorized_keys2
 
   # remove the public key - just for nicer clean up
   rm -f id_dsa.pub

   # exit the connection
   exit

6. Make up a test connection 

   ssh ro...@re...
 
   # you should now not be prompted for the password anymore

7. Everything should work beautifully now

REMARK:
Doing it this way, only the backup server can connect to the
backupped machine (Remote Server) BUT NOT vice versa, which
is great.

Sorry, I am sure, you know all these steps, but to make the process
clear and maybe think about how it can be automated, I wrote it 
down. And maybe it can used for the docs.

( and additional remark:
  Difference between RSA and DSA. You come accross these in conjunction 
  with autorized keys:

  DSA is newer.
  DSA is OpenSource.
  DSA seems to be slightly safer.
 
  But they do not have that great difference. RSA seems to have been 
  cracked a couple of times more. That's it
)


Security Issues:
================

I think it is time to think about some security issues here concerning
an internet host.

1. I think it is okay, that the BackupServer can connect to the 
   Backuped Machine (RemoteServer) with authorized keys, but it
shouldn't work the other way round. 
 
   So the backupServer running with bobs can also be behind a firewall
   Thinking of Internet Host in my opinion it would be to dangerous to 
   allow a connection from the Internet Host to the BackupServer.

2. I have added a "none" - restore method, to be able to work with that
   at present for our Internet Hosts, because
   
   smb and nfs 

   are to insecure for that purpose.

   I have implemented it that way, that the Server also does not come
   up when calling:

   http://bobsdomain/bobs/
   
   This shall be a quick interims solution till it is clear, which
restore method for internet hosts could be appropriate.

3. Restore method for Internet Hosts.

   This is really a problem, cause 

   NFS and smb seems to dangerous to me.
   But:
   The 2nd most important thing is, that you to have a daemon running
   on the other side (The Remote (backuped) Server)

   A suggestion would be, to make up connection with rsync over ssh
   and use that.

   So, the backupServer makes up the connection and puts them to 
   the backuped machine.

   What do you think about that?


====

So hopefully, I have come to end for the first mail.
I'll work on the issue of rsync / ssh  - backup, to
get that working.


Looking forward to your feedback

Cheers

Jochen Metzger
Berlin, Germany



 










The good structure of the sources makes it easy to get into it.










> 
> >Another smal obstactle is the following:
> >4. When creating a new share and using "/" in the descriptive name
> >   the system will take it, but display an error, cause
> >   the corresponding ini-file (e.g. inc/servers/domain.share.inc)
> >   can not be created correctly.
> >
> >   -> What would be the best way to change this ? 
> >   Display an error? Or maybe change "/" in "_" while creating?
> >  
> >
> I think an error message would be appropriate. As discussed in your 
> other email, it's really a name and not a description.
> 
Well I've done that already. I assumed the way, you suggested here.
I'll send the diffs to the mailing list, as soon as I have checked out
the version from cvs.




> >So my questions are:
> >
> >1. Is there an approach towards this ?
> >2. Is this interesting for bobs and further development.
> >   When making changes, the best is, in my opinion, doing 
> >   it in a way, that it can be reused for the next version
> >
> I'd be wary of running an rsync or smb daemon on an internet server too. 
> So if it can be done with ssh it would be more secure. I thinks that's 
> worthwhile and interesting.
> 
> >3. I have to make changes, so I would like to discuss, what would
> >   be the best way 
> >4. How can I communicate the changes? Should I put them in the  
> >bugs-list (bugzilla or whatever sourceforge uses)?
> >  
> >
> Download the CVS version to a development directory on your pc. 
> Instructions on how to do that are under "Anonymous CVS Access" at 
> http://sourceforge.net/cvs/?group_id=54656

Yeah, I'll do that.

> If you want to share the changes, run 'diff' on the files you change and 
> post them to this list.

OK, I'll do it this way. I have already documented some small changes.

> 
> If you really want to get into it, perhaps Rene would add you to the 
> developer list and you could upload the changes. Someone should work on 
> this project and Rene and I haven't done anything in months.

Well, of course I can do some changes, that will make the project
better. Based on my situation of being forced to earn money with my
own business to feed my family, I think it wouldn't have to time
to join the project as a developer.

Of course I can commit minor changes though to keep the overhead mini-
malistic. I'll do it the best way for you ( either diffs or commit
directly)


> 
> Thanks for your interest,
> Joe Zacky
> 
Thanks for your feedback.

Re: [Bobs-devel] Wording in admin.php

[Jochen M. <j.m...@om...>]

Am Son, den 28.12.2003 schrieb Joe Zacky um 01:09:

Hi,

so where you from? I think we are having a time difference.
You answered me in the middle of the night. Not really ->
At 1.09 AM, based on my local time. What was the time
at your place.

Maybe it'll take some time to hear from you, cause you 
are sleeping, when I'm up.


> Jochen Metzger wrote:
> 
> >Hi Folks,
> >
> >IMHO it would be better to change the wording of:
> >Share description:
> >
> >I have been struggling across this, because you think
> >of "Share description" as something like this:
> >
> >e.g.
> >"complete share of all webpages"
> >
> >When an error occurs (when e.g. not entering a Share Description)
> >at all, there also comes up:
> >
> >Share name ......
> >(not Share description)
> >
> >In my opinion, this would be understanding a bit easier.....
> >
> I agree. I changed it to "share name" on June 28th, but it's only in the 
> CVS; it didn't make the June 22nd release 0.6.0.
> 
> Joe
> 
> 
Cool that is great... Next time I'll checkout the CVS-Version
immediately.

I am also working with cvs at my office


-- 
omatix internet services
omatix solutions & trainings
omatix onlineverlag

Jochen Metzger
j.m...@om...

Telefon +49(30) 78709298
Fax     +49(30) 78709296

Re: [Bobs-devel] .. using bobs for internet servers ....

[Joe Z. <jz...@co...>]

Jochen Metzger wrote:

>Hi Rene,
>hi joe,
>hi folks,
>
>hoping all of you had a pretty good christmas.
>
Very good, thanks.

>
>First of all I think that BOBS is a masterpiece of software.
>I have installed it at a clients place, using it for his 
>Fileserver (this is only Intranet though).
>
I think Rene did a great job and filled a vacant niche. It's hard to 
come up with new software ideas. That's primarily why I joined this project.

>
>My current approach is to use it for backupping a mixture
>of Intranet (2x) and Internet-Server (2x). 
>
>Approaching this my preferred backupping method is rsync 
>through ssh. 
>
>Well, I have come through some obstacles concerning this:
>
>1. I do not want to have an rsync - daemon running on
>   the Internet Server, but I have seen that class_backup.php
>   (method: rsync_backup) uses one.
>
>2. I want to use user and pw for ssh. 
>
>3. I do not want to write a rsyncd.conf file on every server.
>   At present with to Internet-Servers it is not problem,
>   but of course you can do without, and it would be less 
>   overhead like this.
>  
>
Are you saying ssh can be used in place of rsync to copy the files from 
one machine to the other? I've not used ssh that way before. Can you 
give some more details on this?

>Another smal obstactle is the following:
>4. When creating a new share and using "/" in the descriptive name
>   the system will take it, but display an error, cause
>   the corresponding ini-file (e.g. inc/servers/domain.share.inc)
>   can not be created correctly.
>
>   -> What would be the best way to change this ? 
>   Display an error? Or maybe change "/" in "_" while creating?
>  
>
I think an error message would be appropriate. As discussed in your 
other email, it's really a name and not a description.

>So my questions are:
>
>1. Is there an approach towards this ?
>2. Is this interesting for bobs and further development.
>   When making changes, the best is, in my opinion, doing 
>   it in a way, that it can be reused for the next version
>
I'd be wary of running an rsync or smb daemon on an internet server too. 
So if it can be done with ssh it would be more secure. I thinks that's 
worthwhile and interesting.

>3. I have to make changes, so I would like to discuss, what would
>   be the best way 
>4. How can I communicate the changes? Should I put them in the  
>bugs-list (bugzilla or whatever sourceforge uses)?
>  
>
Download the CVS version to a development directory on your pc. 
Instructions on how to do that are under "Anonymous CVS Access" at 
http://sourceforge.net/cvs/?group_id=54656

If you want to share the changes, run 'diff' on the files you change and 
post them to this list.

If you really want to get into it, perhaps Rene would add you to the 
developer list and you could upload the changes. Someone should work on 
this project and Rene and I haven't done anything in months.

Thanks for your interest,
Joe Zacky

Re: [Bobs-devel] Wording in admin.php

[Joe Z. <jz...@co...>]

Jochen Metzger wrote:

>Hi Folks,
>
>IMHO it would be better to change the wording of:
>Share description:
>
>I have been struggling across this, because you think
>of "Share description" as something like this:
>
>e.g.
>"complete share of all webpages"
>
>When an error occurs (when e.g. not entering a Share Description)
>at all, there also comes up:
>
>Share name ......
>(not Share description)
>
>In my opinion, this would be understanding a bit easier.....
>
I agree. I changed it to "share name" on June 28th, but it's only in the 
CVS; it didn't make the June 22nd release 0.6.0.

Joe

[Bobs-devel] Wording in admin.php

[Jochen M. <ml...@om...>]

Hi Folks,

IMHO it would be better to change the wording of:
Share description:

I have been struggling across this, because you think
of "Share description" as something like this:

e.g.
"complete share of all webpages"

When an error occurs (when e.g. not entering a Share Description)
at all, there also comes up:

Share name ......
(not Share description)

In my opinion, this would be understanding a bit easier.....


Cheers

[Bobs-devel] .. using bobs for internet servers ....

[Jochen M. <ml...@om...>]

Hi Rene,
hi joe,
hi folks,

hoping all of you had a pretty good christmas.

First of all I think that BOBS is a masterpiece of software.
I have installed it at a clients place, using it for his 
Fileserver (this is only Intranet though).

My current approach is to use it for backupping a mixture
of Intranet (2x) and Internet-Server (2x). 

Approaching this my preferred backupping method is rsync 
through ssh. 

Well, I have come through some obstacles concerning this:

1. I do not want to have an rsync - daemon running on
   the Internet Server, but I have seen that class_backup.php
   (method: rsync_backup) uses one.

2. I want to use user and pw for ssh. 

3. I do not want to write a rsyncd.conf file on every server.
   At present with to Internet-Servers it is not problem,
   but of course you can do without, and it would be less 
   overhead like this.

Another smal obstactle is the following:
4. When creating a new share and using "/" in the descriptive name
   the system will take it, but display an error, cause
   the corresponding ini-file (e.g. inc/servers/domain.share.inc)
   can not be created correctly.

   -> What would be the best way to change this ? 
   Display an error? Or maybe change "/" in "_" while creating?

So my questions are:

1. Is there an approach towards this ?
2. Is this interesting for bobs and further development.
   When making changes, the best is, in my opinion, doing 
   it in a way, that it can be reused for the next version
3. I have to make changes, so I would like to discuss, what would
   be the best way 
4. How can I communicate the changes? Should I put them in the  
bugs-list (bugzilla or whatever sourceforge uses)?

Thanks for your feedback.


cheers 


Jochen Metzger

[Bobs-devel] Re: db3

[Joe Z. <jz...@co...>]

michymak wrote:

>hi
>
>i have the little problem with config php.ini for db3
>
>i have rh8.0 with apache 2 and php4 
>
>thanks advance
>
>  
>
Check this link 
http://sourceforge.net/mailarchive/forum.php?thread_id=3008442&forum_id=9561

If that doesn't help please post more information to 
bob...@li... including any error output you have.

Joe Zacky

Re: [Bobs-devel] Restore remote server error

[Rene R. <re...@gr...>]

> Installed BOBS on RH9 and backed up largest SMB share fine.  When
> attempting a test restore of a 25kb file, response was:
> Error: not enough free diskspace on remote server.  Error: 100MB plus
> the size of the file you wish to restore is needed.
>
> I've got 900MB free on the server and share in question.
>
> Thanks for your help,
> Michael...


In inc/class_restore.php find the line:
if ( ($serv_free_size/1024) > (($filesize/1024/1024)+100) ) {

and try replacing it with this:
if ( ($serv_free_size/1024) > ($filesize/1024/1024) ) {

or this if the above still fails:
if ( true ) {


Sorry, I'm too pressed for time to get further into it. Please file a bug
report on the project page. If you do, please also state that "4GB
problems will mess the filesize calculation. Check if where the 32 bit
limitation is, php or dba." (just a reminder to me)

Cheers
Rene

Mail again if this doesn't help.

[Bobs-devel] Restore remote server error

[Michael O. <mo...@co...>]

Installed BOBS on RH9 and backed up largest SMB share fine.  When attempting
a test restore of a 25kb file, response was:
Error: not enough free diskspace on remote server.  Error: 100MB plus the
size of the file you wish to restore is needed.

I've got 900MB free on the server and share in question.

Thanks for your help,
Michael...

Re: [Bobs-devel] Dba and db3 Error

[Rene R. <re...@gr...>]

> Hello everybody,
>
> When i run bobs, after entering the password, i click for example on
> "Browse  Current" and it displays :
>
> On the left side :
>
> Warning: dba_open(/var/bobsdata/current/testserver/share.dirindex.db,c):
> No  such handler: db3 in /var/www/html/bobs/inc/class_db.php on line 66
>
> Warning: dba_firstkey(): supplied argument is not a valid DBA identifier
>  resource in /var/www/html/bobs/inc/class_db.php on line 130
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> Warning: dba_nextkey(): supplied argument is not a valid DBA identifier
> resource in /var/www/html/bobs/inc/class_db.php on line 233
>
> You are browsing the current directories of testserver/share
>
> And on the right side:
>
> Warning: dba_open(/var/bobsdata/current/testserver/share.dirindex.db,c):
> No  such handler: db3 in /var/www/html/bobs/inc/class_db.php on line 66
> No files were found in
>
>
> Can u help me ?
>
>

It should work fine when you have a backup. Wait a day or do it manually
from the admin page. The errors occur becuase bobs is trying to open a
database that doesn't exist yet.

Cheers
Rene