On 16/04/2019 12:24, Marcio Demetrio Bacci wrote:
I have some doubts about Bacula, however I did not find answers on the
Internet or in the books for the following doubts:
1. Is there any problem in using Bacula virtualized? (I didn't find
anything saying otherwise)
If you mean "running on a VM", then no, there are no problems. I
wouldn't do it, but there are reasons I prefer critical infrastructure
to be stand-alone.
2. Is there any restriction on mounting the Bacula VM on a DRBD volume
in the hypervisor. In this VM I will implement ZFS deduplication for my
backups?
I /think/ you are asking if Bacula can handle fail-over during backup?
Short answer is "no". (I am willing to accept corrections on this, but
AFAICS Bacula doesn't checkpoint its output.)
3. Is there any limitation on the size of Backups with Bacula Community
version? (I did not find information about any limitations)
No. But then I use tape, so limitations are for lusers.
4. Having a few jobs with 300 GB or more, though I set up my volumes on
Bacula with 100 GB, so would you recommend increasing the size of the
volumes to 200 GB or more?
I will let someone who uses disk storage answer that.
5. Currently the OS and Backup disks are on the same DRBD volume, so
would it be better to put the OS disk out of the DRBD volume? (the VM
has frequently crashing what makes me think that excessive writing on
the disk may be impacting the OS)
If your VM is crashing, you have really, really bad problems.
Solve them before you put any (more) critical infrastructure on it/them.
Also, see the second half of my answer to your first question.
Cheers,
Gary B-)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
