SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Bacula and Zarafa
Author Message
Post Bacula and Zarafa 
Short question: anyone using Bacula to backup Zarafa? What to consider?
Any pitfalls?

Ok... these were 3 questions... Smile)

Thanks a lot,
christian

Post Bacula and Zarafa 
Hi,

Am Donnerstag, 23. Februar 2012, 09:55:00 schrieb Masopust, Christian:
Short question: anyone using Bacula to backup Zarafa? What to consider?
Any pitfalls?

Ok... these were 3 questions... Smile)

Collax provides a number of Zarafa based products; our basic backup technology
is Bacula. So ... We do. Smile

1) Consider combining Zarafa's internal backup technology (Brick Level Backup)
with Bacula. We encourage users to create frequent incremental backups, which
then can/should be stored for longer-term usage via Bacula.

2) You can simply dump the Zarafa database with mysqldump (or anything the
like), possibly in conjunction with Bacula's bpipe plugin. This will result in
no longer being able to create incremental backups, but depending on the size
of your installation, that may well be OK.

3) File based backup of MySQL is possible, if appropriate steps are taken.
Cannot tell you too much about that, though. If you do something like this,
you might consider using Postgres for Bacula. This will help reduce load on
each of the databases, and will reduce write access (Catalog) to the database
your are backing up.

In our own infrastructure, we do frequent Brick-level backups with Zarafa's
tools, and backup up the database, the attachment store, and the brick-level
store in daily incrementals via Bacula (and bpipe/mysqldump in case of the
database).

Best regards
Bastian

--
Collax GmbH . Basler Str. 115a . 79115 Freiburg . Germany
p: +49 (0) 89-990 157-28 www.collax.com

Geschäftsführer: Bernd Bönte, Boris Nalbach
AG München HRB 173695. Ust.-IdNr: DE270819312


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Post Bacula and Zarafa 
Hi Bastian,

thanks a lot for your answers.

After reading the Zarafa documentation we also (at least we plan)
to use your described procedure with having brick level backups and
then backup that results with Bacula. And maybe once or twice a month
a "mysqldump-backup" of the database.

Just a short question: what would be "frequent incremental backups"
as you mentioned at 1) ?

thanks a lot,
christian

-----Ursprüngliche Nachricht-----
Von: Bastian Friedrich [mailto:bastian.friedrich < at > collax.com]
Gesendet: Donnerstag, 23. Februar 2012 11:25
An: bacula-users < at > lists.sourceforge.net
Cc: Masopust, Christian
Betreff: Re: [Bacula-users] Bacula and Zarafa

Hi,

Am Donnerstag, 23. Februar 2012, 09:55:00 schrieb Masopust, Christian:
Short question: anyone using Bacula to backup Zarafa?
What to consider?
Any pitfalls?

Ok... these were 3 questions... Smile)

Collax provides a number of Zarafa based products; our basic
backup technology
is Bacula. So ... We do. Smile

1) Consider combining Zarafa's internal backup technology
(Brick Level Backup)
with Bacula. We encourage users to create frequent
incremental backups, which
then can/should be stored for longer-term usage via Bacula.

2) You can simply dump the Zarafa database with mysqldump (or
anything the
like), possibly in conjunction with Bacula's bpipe plugin.
This will result in
no longer being able to create incremental backups, but
depending on the size
of your installation, that may well be OK.

3) File based backup of MySQL is possible, if appropriate
steps are taken.
Cannot tell you too much about that, though. If you do
something like this,
you might consider using Postgres for Bacula. This will help
reduce load on
each of the databases, and will reduce write access (Catalog)
to the database
your are backing up.

In our own infrastructure, we do frequent Brick-level backups
with Zarafa's
tools, and backup up the database, the attachment store, and
the brick-level
store in daily incrementals via Bacula (and bpipe/mysqldump
in case of the
database).

Best regards
Bastian

--
Collax GmbH . Basler Str. 115a . 79115 Freiburg . Germany
p: +49 (0) 89-990 157-28 www.collax.com

Geschäftsführer: Bernd Bönte, Boris Nalbach
AG München HRB 173695. Ust.-IdNr: DE270819312


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Post Bacula and Zarafa 
Hi,

Am Samstag, 25. Februar 2012, 17:16:19 schrieb Masopust, Christian:
1) Consider combining Zarafa's internal backup technology
(Brick Level Backup)
with Bacula. We encourage users to create frequent
incremental backups, which
then can/should be stored for longer-term usage via Bacula.

Just a short question: what would be "frequent incremental backups"
as you mentioned at 1) ?

I'd regard any interval between 1 hour and 24 hours as sensible for their
respective setups; this largely depends on the ammount of mails and users your
Zarafa installation handles, and the system load that you can spare for backup
purposes.

If your system can handle an incremental backup every hour, that might well be
the best choice. The size of the backups will be comparably small, as will be
the risk of losing data. Due to its nature, Zarafa's brick-level backup will
not have too much overhead for multiple small incrementals versus a single
large one.

Regards
Bastian

--
Collax GmbH . Basler Str. 115a . 79115 Freiburg . Germany
p: +49 (0) 89-990 157-28 www.collax.com

Geschäftsführer: Bernd Bönte, Boris Nalbach
AG München HRB 173695. Ust.-IdNr: DE270819312


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Post Bacula and Zarafa 
-----Ursprüngliche Nachricht-----
Von: Bastian Friedrich [mailto:bastian.friedrich < at > collax.com]
Gesendet: Montag, 27. Februar 2012 09:56
An: Masopust, Christian
Cc: bacula-users < at > lists.sourceforge.net
Betreff: Re: [Bacula-users] Bacula and Zarafa

Hi,

Am Samstag, 25. Februar 2012, 17:16:19 schrieb Masopust, Christian:
1) Consider combining Zarafa's internal backup technology (Brick
Level Backup) with Bacula. We encourage users to create frequent
incremental backups, which then can/should be stored for longer-term
usage via Bacula.

Just a short question: what would be "frequent incremental backups"
as you mentioned at 1) ?

I'd regard any interval between 1 hour and 24 hours as sensible for their
respective setups; this largely depends on the ammount of mails and users
your Zarafa installation handles, and the system load that you can spare
for backup purposes.

If your system can handle an incremental backup every hour, that might
well be the best choice. The size of the backups will be comparably small,
as will be the risk of losing data. Due to its nature, Zarafa's brick-
level backup will not have too much overhead for multiple small
incrementals versus a single large one.

Just FYI: A few weeks ago we had a problem with a Server running Zarafa. The only usable backup was a full and lots of incremental. The Zarafa support told me, that it is not recommended to have more than X incremental after a full. I can't remember the exact number, but i am sure it was less than 10. So having running an incremental every hour might not be the best thing to do. Though our restore with more than 100 incremental backups worked just fine.


Regards
Bastian

--
Collax GmbH . Basler Str. 115a . 79115 Freiburg . Germany
p: +49 (0) 89-990 157-28 www.collax.com

Geschäftsführer: Bernd Bönte, Boris Nalbach AG München HRB 173695. Ust.-
IdNr: DE270819312


--------------------------------------------------------------------------
----
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers is
just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB