-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jo wrote:
Gregory Brauer schreef:
Jo wrote:
Christoff Buch schreef:
Hi all,
what I need to know is:
Can they be backed up with bacula while opened?
[...]
Another, potentially faster, strategy is to use rsync to duplicate the
files to another location while Notes is stopped and then back up
from the duplicated area (meaning you are free to restart Notes).
rsync only copies changed data, so the time period that Notes is stopped
should be fairly short. Note, however, that this will double your disk
usage.
>>
Greg
That seems like a good way to go about it. We don't do it that way
because we tend to be asleep around 1 am.
You can schedule rsync like any other Linux/Unix job. You could write a
RunBeforeJob script for Bacula that shuts down your Domino server, waits
a bit (to give it time to actually come down), runs rsync, and brings
back up Domino afterwards.
The other option is a replica
of the Notes server that can be switched off (and used as a stand in),
but that would double the license cost, of course
The other disadvantages are:
- - you need to ensure every new database created on the server gets
replicated (otherwise its instance will be missing in the backups)
- - you need to monitor ACLs, replication settings and the logs to ensure
that nobody tinkers with them in a way that breaks or impacts
replication between the two (otherwise you back up old data or just an
empty shell)
Or you need to buy tools that can take over the above for you.
In short:
1. If you must be up all the time and need an absolute clean backup: Use
archive transaction logging and the Domino Backup API. (Unfortunately
Bacula doesn't support it, so you'll probably have to shell out money
for expensive proprietary backup software)
2. If you must be up all the time and have lots of time/diskspace:
create a 2nd server/workstation to where you replicate everything
3. If you must be up all the time and don't mind risking some
corruption: Just grab the files while open while trying to avoid busy times
4. If you can afford a very short downtime and have a SAN (or LVM and
powerful drives): Down the server, take a snapshot, bring back up the
server and backup your snapshot in the background (N.B. Using snapshots
can really degrade performance so be sure to test and measure it before)
5. If you can afford longer downtimes and have loads of diskspace: Down
the server and use rsync, zip or whatever you like to create a copy of
the data.
6. If you can afford even longer downtime but don't have diskspace: down
the server and back it up directly.
Only 1 cannot be done with Bacula. The others should all be possible
with various degrees of scripting (check out RunBeforeJob, RunAfterJob,
...).
Note that 3 doesn't ensure consistency but, as stated by several people
here, it has not been witnessed failing yet.
Greetings,
Michel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959
iD8DBQFEAraY2Vs+MkscAyURAp2SAJ9DekHlB4P0aMM81kR+icyff1QfCwCfRN4E
dktdx1NtXy/qilh6GEjbacg=
=Lq9P
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
