Hi list, I'm building a backup server for 3 hosts (1 workstation, 2 server). I will use bacula to perform backups. The backup is performed on disks (2 x 3TB on mdraid mirror) and for each hosts I've created a logical volume with related size. This 3 hosts have different data size with different disk change rate. Each host must have a limited sized resource and a reserved space. If a server needs more space to perform backup, It must be enabled and provisioned. My first solution was put each host pools on different logical volumes, like: host1 -> lv1 host2 -> lv2 host3 -> lv3 and store pools/volumes on specified storage daemon that uses a specified device for each different hosts. host1 -> storage1 -> device_lv1 host2 -> storage2 -> device_lv2 host3 -> storage3 -> device_lv3 Unfortunately, I can't define on bacula-sd.conf multiple storage definition but only multiple devices. To use different storage I must run 3 bacula-sd on same host (I can?), run a bacula-sd on a vm/host. Ah, I must use only one physical server. With one single machine and the current state I can't use multiple storage daemons. There are other ways to store host volumes on different devices? My second solution was, use only one storage daemon (on the same host) with a single device LVM over mdraid, create pool for each hosts and limit the size for each volumes on related pool. Suggestions? Thanks in advance.
Hi list, I've solved my problem. I've understood some concepts. I've defined bacula-sd multiple devices with different Media Type and configured different storage directives in director. Thanks.> Hi list, > I'm building a backup server for 3 hosts (1 workstation, 2 server). I > will use bacula to perform backups. The backup is performed on disks (2 > x 3TB on mdraid mirror) and for each hosts I've created a logical volume > with related size. > > This 3 hosts have different data size with different disk change rate. > Each host must have a limited sized resource and a reserved space. If a > server needs more space to perform backup, It must be enabled and > provisioned. > > My first solution was put each host pools on different logical volumes, > like: > > host1 -> lv1 > host2 -> lv2 > host3 -> lv3 > > and store pools/volumes on specified storage daemon that uses a > specified device for each different hosts. > > host1 -> storage1 -> device_lv1 > host2 -> storage2 -> device_lv2 > host3 -> storage3 -> device_lv3 > > > Unfortunately, I can't define on bacula-sd.conf multiple storage > definition but only multiple devices. To use different storage I must > run 3 bacula-sd on same host (I can?), run a bacula-sd on a vm/host. > Ah, I must use only one physical server. > > With one single machine and the current state I can't use multiple > storage daemons. > > There are other ways to store host volumes on different devices? > > My second solution was, use only one storage daemon (on the same host) > with a single device LVM over mdraid, create pool for each hosts and > limit the size for each volumes on related pool. > > Suggestions? > > Thanks in advance. > > > > >
I'm sure some people will tell me I'm doing it wrong but I always just use rsync for backups, automated in cron. I may be doing it wrong but it always works. On 10/12/2016 07:14 AM, Alessandro Baggi wrote:> Hi list, > I've solved my problem. > > I've understood some concepts. > > I've defined bacula-sd multiple devices with different Media Type and > configured different storage directives in director. > > Thanks. > > >> Hi list, >> I'm building a backup server for 3 hosts (1 workstation, 2 server). I >> will use bacula to perform backups. The backup is performed on disks (2 >> x 3TB on mdraid mirror) and for each hosts I've created a logical volume >> with related size. >> >> This 3 hosts have different data size with different disk change rate. >> Each host must have a limited sized resource and a reserved space. If a >> server needs more space to perform backup, It must be enabled and >> provisioned. >> >> My first solution was put each host pools on different logical volumes, >> like: >> >> host1 -> lv1 >> host2 -> lv2 >> host3 -> lv3 >> >> and store pools/volumes on specified storage daemon that uses a >> specified device for each different hosts. >> >> host1 -> storage1 -> device_lv1 >> host2 -> storage2 -> device_lv2 >> host3 -> storage3 -> device_lv3 >> >> >> Unfortunately, I can't define on bacula-sd.conf multiple storage >> definition but only multiple devices. To use different storage I must >> run 3 bacula-sd on same host (I can?), run a bacula-sd on a vm/host. >> Ah, I must use only one physical server. >> >> With one single machine and the current state I can't use multiple >> storage daemons. >> >> There are other ways to store host volumes on different devices? >> >> My second solution was, use only one storage daemon (on the same host) >> with a single device LVM over mdraid, create pool for each hosts and >> limit the size for each volumes on related pool. >> >> Suggestions? >> >> Thanks in advance. >> >> >> >> >> > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos-- -=- Sent my from my laptop, may not be able to respond timely
I'm not a bacula expert, but have had 30+ years in the industry doing backups. I'm a little concerned about what you are planning. As I understand it you are going to be keeping just one copy of each machine on a disk attached to the server. This will help if you loose the running disks (though it is hardly backup in depth), but what happens if you loose the server due to fire, flood, electrical problems, theft or even plain old dropping it? In general you should aim for multiple backup copies; are you willing to bet the company's future on one untried copy? You should ensure that the backup copies are held preferably off site, failing that in a separate building, or else in a secure fireproof strongbox. Start by assuming you come into work one day to find the building burnt out and collapsed. Now work out how to rebuild your system on new kit on another site and you'll find that you define your backup needs. Regards, Martin On 12/10/16 12:54, Alessandro Baggi wrote:> Hi list, > I'm building a backup server for 3 hosts (1 workstation, 2 server). I > will use bacula to perform backups. The backup is performed on disks (2 > x 3TB on mdraid mirror) and for each hosts I've created a logical volume > with related size. > > This 3 hosts have different data size with different disk change rate. > Each host must have a limited sized resource and a reserved space. If a > server needs more space to perform backup, It must be enabled and > provisioned. > > My first solution was put each host pools on different logical volumes, > like: > > host1 -> lv1 > host2 -> lv2 > host3 -> lv3 > > and store pools/volumes on specified storage daemon that uses a > specified device for each different hosts. > > host1 -> storage1 -> device_lv1 > host2 -> storage2 -> device_lv2 > host3 -> storage3 -> device_lv3 > > > Unfortunately, I can't define on bacula-sd.conf multiple storage > definition but only multiple devices. To use different storage I must > run 3 bacula-sd on same host (I can?), run a bacula-sd on a vm/host. > Ah, I must use only one physical server. > > With one single machine and the current state I can't use multiple > storage daemons. > > There are other ways to store host volumes on different devices? > > My second solution was, use only one storage daemon (on the same host) > with a single device LVM over mdraid, create pool for each hosts and > limit the size for each volumes on related pool. > > Suggestions? > > Thanks in advance. > > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20161013/acad2e8a/attachment-0001.sig>
Mark has asked me to forward this to the list: ---------%<----------------------------------------- Subject: Re: [CentOS] Backup Suggestion on C7 Date: Thu, 13 Oct 2016 17:09:41 -0400 From: m.roth at 5-cent.us To: J Martin Rushton <martinrushton56 at btinternet.com> Please forward to the CentOS list - my hosting provider claims they been working with SORBS, but it's now been blocking me from posting for two weeks.... J Martin Rushton wrote:> I'm not a bacula expert, but have had 30+ years in the industry doing > backups. I'm a little concerned about what you are planning. As I > understand it you are going to be keeping just one copy of each machine > on a disk attached to the server. This will help if you loose the > running disks (though it is hardly backup in depth), but what happens if > you loose the server due to fire, flood, electrical problems, theft or > even plain old dropping it? In general you should aim for multiple > backup copies; are you willing to bet the company's future on one > untried copy? You should ensure that the backup copies are held > preferably off site, failing that in a separate building, or else in a > secure fireproof strongbox.To start, is the OP doing disaster recovery backups, or archive backups? The difference is the former you only keep for a limited amount of time, and the later forever. If the former: first, you should not be backing up one server to its own disks. The backup should reside on a different server. Secondly, consider an offline backup. Here at work, we use a home-grown rsync solution (with hard links), and typically save those for five weeks. We also back up the backups to either offline disks (mounted in hot swap bays, and they reside the rest of the time in a fire safe; for things that one fit on one disk, they're backed up to a server in another building with a large RAID. For the latter, which I have not been involved with, you should probably have x weeks, then save the weeklies for x months, then the montlies for x years. And *ALL* of that should be offsite. mark, hoping this gets through ------------------%<---------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20161013/893f23d0/attachment-0001.sig>
Hi Martin, this is the off-site backup. Each server is backupped also in farm. Il 13/10/2016 22:24, J Martin Rushton ha scritto:> I'm not a bacula expert, but have had 30+ years in the industry doing > backups. I'm a little concerned about what you are planning. As I > understand it you are going to be keeping just one copy of each machine > on a disk attached to the server. This will help if you loose the > running disks (though it is hardly backup in depth), but what happens if > you loose the server due to fire, flood, electrical problems, theft or > even plain old dropping it? In general you should aim for multiple > backup copies; are you willing to bet the company's future on one > untried copy? You should ensure that the backup copies are held > preferably off site, failing that in a separate building, or else in a > secure fireproof strongbox. > > Start by assuming you come into work one day to find the building burnt > out and collapsed. Now work out how to rebuild your system on new kit > on another site and you'll find that you define your backup needs. > > Regards, > Martin > > On 12/10/16 12:54, Alessandro Baggi wrote: >> Hi list, >> I'm building a backup server for 3 hosts (1 workstation, 2 server). I >> will use bacula to perform backups. The backup is performed on disks (2 >> x 3TB on mdraid mirror) and for each hosts I've created a logical volume >> with related size. >> >> This 3 hosts have different data size with different disk change rate. >> Each host must have a limited sized resource and a reserved space. If a >> server needs more space to perform backup, It must be enabled and >> provisioned. >> >> My first solution was put each host pools on different logical volumes, >> like: >> >> host1 -> lv1 >> host2 -> lv2 >> host3 -> lv3 >> >> and store pools/volumes on specified storage daemon that uses a >> specified device for each different hosts. >> >> host1 -> storage1 -> device_lv1 >> host2 -> storage2 -> device_lv2 >> host3 -> storage3 -> device_lv3 >> >> >> Unfortunately, I can't define on bacula-sd.conf multiple storage >> definition but only multiple devices. To use different storage I must >> run 3 bacula-sd on same host (I can?), run a bacula-sd on a vm/host. >> Ah, I must use only one physical server. >> >> With one single machine and the current state I can't use multiple >> storage daemons. >> >> There are other ways to store host volumes on different devices? >> >> My second solution was, use only one storage daemon (on the same host) >> with a single device LVM over mdraid, create pool for each hosts and >> limit the size for each volumes on related pool. >> >> Suggestions? >> >> Thanks in advance. >> >> >> >> >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >