|
|
Subject: How to get geographic store redundancy right now? - msg#00151
Hi all,
Maybe this is the wrong time, with all the development work going on,
but I wanted to get some pointers for how best to, right now, provide
geographic store redundancy, that is, keeping reasonably similar
versions of the client data in at least 2 locations physically
separated by many miles/kilometers.
I found some conceptual discussions with this google:
http://www.google.com/search?q=+redundancy+OR+%22multiple+stores%22+site%3Alists.warhead.org.uk
and in the wiki:
http://boxbackup.hostworks.ca/index.php/Future_design_changes#8._Server_Redundancy_.28grabbed_from_message_by_Ben_on_9.2F24.2F04.29
But, I'm wondering what I should do right now.
All of my outside clients are on Windows (my boxes are mixed Windows
and GNU/Linux, mostly Ubuntu).
I'm not sure at all, but I guess that the best option right now is just
rsyncing the store to a remote server, as frequently as practical,
would work reasonably well (secure, reliable, fairly network and
storage efficient, convenient, fairly easily restorable).
Is it silly to ask, to give the client user a little more control than
the rsync method above, if it is possible (with maybe 5 or 10 lines of
one-off code tweaking) to run 2 boxbackup services on the Windows
client, pointing each service to separate bbackupd.conf files wherein
the clients are pointed to geographically separated StoreHostname's?
(Separately, I thought it'd be neat to be able to, someday, have a
bbackupd.conf line like:
StoreHostname = eastcoast.domain.com westcoast.domain.com
and have the single bbackupd service make best efforts to backup to
both of them, but I presume that would take quite a bit of coding.)
Thank you!
Pete
Thread at a glance:
Previous Message by Date:
Re: Release Candidate 3, Debian 3.1 DeMuDi test results, non-root user
The test results were the same as root and a non-root user.
petjal@demudi:~/boxbackup-0.09_plus3$ id
uid=1000(petjal) gid=1000(petjal)
groups=20(dialout),24(cdrom),25(floppy),29(audio),44(video),46(plugdev),1000(petjal)
petjal@demudi:~/boxbackup-0.09_plus3$ grep FAIL box-release.log
petjal@demudi:~/boxbackup-0.09_plus3$ grep FAIL box-debug.log
FAILURE: Condition [time(0) < (beginTime + 40)] failed at
testbackupdiff.cpp(544)
FAILED: 1 tests failed
backupdiff: FAILED: 1 tests failed
petjal@demudi:~/boxbackup-0.09_plus3$
--- "E.W. Peter Jalajas" <pjalajas-oIlVEpD3c1LQT0dZR+AlfA@xxxxxxxxxxxxxxxx>
wrote:
> I'm running the tests as a normal user now. If I see anything
> different, I'll report it.
>
> Now, I'd like to run some serious tests on the WinXP client. A few
> of
> the tests under ~/boxbackup-0.09_plus3/test look like they might be
> appropriate. Any guidance on how to start going about such an
> adventure would be much appreciated! I presume I could use cygwin
> under WinXP for this?
>
> Thanks,
> Pete
>
> --- Martin Ebourne <lists-lOE7s1aLf+QJ3nxcUk3PyQ@xxxxxxxxxxxxxxxx> wrote:
> >
> > > Should I run the tests as non-root?
> >
> > Definitely. You should never compile anything as root. Likewise for
> > running compile tests in general.
> >
Next Message by Date:
RE: How to get geographic store redundancy right now?
Hi Pete,
we currently have that situation working now. I do however
use a program called rdiff-backup this enables us to maintain increments of
a servers state at the remote location. Our Linux boxes also run two
versions of bbackupd with different conf without an issue.
Do make sure that you use a SNAPSHOT system or similar on the server store
of course or shut it down during backup.
-----Original Message-----
From: boxbackup-admin-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx
[mailto:boxbackup-admin-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx] On
Behalf Of E.W. Peter Jalajas
Sent: Wednesday, 22 February 2006 4:28 PM
To: Box Backup Mailing List
Subject: [Box Backup] How to get geographic store redundancy right now?
Hi all,
Maybe this is the wrong time, with all the development work going on, but I
wanted to get some pointers for how best to, right now, provide geographic
store redundancy, that is, keeping reasonably similar versions of the client
data in at least 2 locations physically separated by many miles/kilometers.
I found some conceptual discussions with this google:
http://www.google.com/search?q=+redundancy+OR+%22multiple+stores%22+site%3Al
ists.warhead.org.uk
and in the wiki:
http://boxbackup.hostworks.ca/index.php/Future_design_changes#8._Server_Redu
ndancy_.28grabbed_from_message_by_Ben_on_9.2F24.2F04.29
But, I'm wondering what I should do right now.
All of my outside clients are on Windows (my boxes are mixed Windows and
GNU/Linux, mostly Ubuntu).
I'm not sure at all, but I guess that the best option right now is just
rsyncing the store to a remote server, as frequently as practical, would
work reasonably well (secure, reliable, fairly network and storage
efficient, convenient, fairly easily restorable).
Is it silly to ask, to give the client user a little more control than the
rsync method above, if it is possible (with maybe 5 or 10 lines of one-off
code tweaking) to run 2 boxbackup services on the Windows client, pointing
each service to separate bbackupd.conf files wherein the clients are pointed
to geographically separated StoreHostname's?
(Separately, I thought it'd be neat to be able to, someday, have a
bbackupd.conf line like:
StoreHostname = eastcoast.domain.com westcoast.domain.com and have the
single bbackupd service make best efforts to backup to both of them, but I
presume that would take quite a bit of coding.)
Thank you!
Pete
_______________________________________________
boxbackup mailing list
boxbackup-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx
http://lists.warhead.org.uk/mailman/listinfo/boxbackup
Previous Message by Thread:
Re: Release Candidate 3, Debian 3.1 DeMuDi test results, non-root user
The test results were the same as root and a non-root user.
petjal@demudi:~/boxbackup-0.09_plus3$ id
uid=1000(petjal) gid=1000(petjal)
groups=20(dialout),24(cdrom),25(floppy),29(audio),44(video),46(plugdev),1000(petjal)
petjal@demudi:~/boxbackup-0.09_plus3$ grep FAIL box-release.log
petjal@demudi:~/boxbackup-0.09_plus3$ grep FAIL box-debug.log
FAILURE: Condition [time(0) < (beginTime + 40)] failed at
testbackupdiff.cpp(544)
FAILED: 1 tests failed
backupdiff: FAILED: 1 tests failed
petjal@demudi:~/boxbackup-0.09_plus3$
--- "E.W. Peter Jalajas" <pjalajas-oIlVEpD3c1LQT0dZR+AlfA@xxxxxxxxxxxxxxxx>
wrote:
> I'm running the tests as a normal user now. If I see anything
> different, I'll report it.
>
> Now, I'd like to run some serious tests on the WinXP client. A few
> of
> the tests under ~/boxbackup-0.09_plus3/test look like they might be
> appropriate. Any guidance on how to start going about such an
> adventure would be much appreciated! I presume I could use cygwin
> under WinXP for this?
>
> Thanks,
> Pete
>
> --- Martin Ebourne <lists-lOE7s1aLf+QJ3nxcUk3PyQ@xxxxxxxxxxxxxxxx> wrote:
> >
> > > Should I run the tests as non-root?
> >
> > Definitely. You should never compile anything as root. Likewise for
> > running compile tests in general.
> >
Next Message by Thread:
RE: How to get geographic store redundancy right now?
Hi Pete,
we currently have that situation working now. I do however
use a program called rdiff-backup this enables us to maintain increments of
a servers state at the remote location. Our Linux boxes also run two
versions of bbackupd with different conf without an issue.
Do make sure that you use a SNAPSHOT system or similar on the server store
of course or shut it down during backup.
-----Original Message-----
From: boxbackup-admin-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx
[mailto:boxbackup-admin-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx] On
Behalf Of E.W. Peter Jalajas
Sent: Wednesday, 22 February 2006 4:28 PM
To: Box Backup Mailing List
Subject: [Box Backup] How to get geographic store redundancy right now?
Hi all,
Maybe this is the wrong time, with all the development work going on, but I
wanted to get some pointers for how best to, right now, provide geographic
store redundancy, that is, keeping reasonably similar versions of the client
data in at least 2 locations physically separated by many miles/kilometers.
I found some conceptual discussions with this google:
http://www.google.com/search?q=+redundancy+OR+%22multiple+stores%22+site%3Al
ists.warhead.org.uk
and in the wiki:
http://boxbackup.hostworks.ca/index.php/Future_design_changes#8._Server_Redu
ndancy_.28grabbed_from_message_by_Ben_on_9.2F24.2F04.29
But, I'm wondering what I should do right now.
All of my outside clients are on Windows (my boxes are mixed Windows and
GNU/Linux, mostly Ubuntu).
I'm not sure at all, but I guess that the best option right now is just
rsyncing the store to a remote server, as frequently as practical, would
work reasonably well (secure, reliable, fairly network and storage
efficient, convenient, fairly easily restorable).
Is it silly to ask, to give the client user a little more control than the
rsync method above, if it is possible (with maybe 5 or 10 lines of one-off
code tweaking) to run 2 boxbackup services on the Windows client, pointing
each service to separate bbackupd.conf files wherein the clients are pointed
to geographically separated StoreHostname's?
(Separately, I thought it'd be neat to be able to, someday, have a
bbackupd.conf line like:
StoreHostname = eastcoast.domain.com westcoast.domain.com and have the
single bbackupd service make best efforts to backup to both of them, but I
presume that would take quite a bit of coding.)
Thank you!
Pete
_______________________________________________
boxbackup mailing list
boxbackup-u3BOLVezVvXQXOPxS62xeg@xxxxxxxxxxxxxxxx
http://lists.warhead.org.uk/mailman/listinfo/boxbackup
|
|