best practices for backing up ZFS?
Adam Thompson
This captures both the global zone and all the hosted zones simultaneously, and it - so far - works adequately.
But... performance isn't great (~7MB/sec from the older server, ~20MB/sec from the newer, all-gigabit network) and of course this doesn't even get me known-good crash-consistent backups of the (running) Oracle databases.
Is there a "good" way to backup an entire ZFS-based system using, e.g. snapshots? The number of ZFS datasets will fluctuate as zones are added and removed, and I don't want to have to constantly adjust the backup job to handle that.
I particularly would like crash-consistent backups of the (cloned) Oracle databases - snapshots are good enough, but what's an appropriate way to handle this with Bareos? I dislike the notion of having cron jobs running on each host with no coordination w/Bareos; surely there's a better way?
Advice/suggestions welcome both on performance and best-practices.
Thanks,
-Adam
Marco van Wieringen
Think about some scripting with pre- and post scripts that perform the
snapshot operations based on reading the mounted filesystems and skip
the uninteresting ones and snapshot the others (works for ufs, vxfs and zfs)
and clone them to an so called alternative root. Then you create a auto generated
fileset that captures all these snapshots and saves things with the "strip" option
which essentially means things end up in your backup as if they are in their original
place but are located under the alternative_root.
I have this running since I programmed it for Bacula in 2008 never had a single problem
with it. Its called bareos_backup_manager and even includes things like quiesce and unquiesce
scripts which can be run before the snapshots are taken and after things are done.
The script also auto-excludes zone roots and if you setup things right on Solaris e.g.
delegated the ZFS fileset to the zone the script also runs fine in a zone. It does count
a bit on a proper setup Solaris environment but should be able to handle most of the quirks.
This is all part of our commercial Solaris packages which saves you the hassle of having
to program it all yourself. But if you think you can do it yourself fine I mostly told you
the things to think about. B.T.W. pre- and post backup jobs are the only thing you want to
use anything with cron make absolutely no sense.
--
Marco van Wieringen marco.van...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
P. Storz, M. v. Wieringen
Adam Thompson
> I have this running since I programmed it for Bacula in 2008 never had a single problem
>
> This is all part of our commercial Solaris packages which saves you the hassle of having
Marco,
I've been looking, but I can't find any listing of what the difference is between the commercial binary subscription and the open-source edition.
This is one difference, I assume there are others?
Thanks,
-Adam
Maik Aussendorf
I've sent information regarding the subscription earlier.
The main difference is: there are patches and updates to the major
version in the subscription repositories, all tested by our continuous
integration tests. And there is support available for the subscription.
Regarding Solaris, AIX and HP-UX: binary packages are only available by
subscription - or self built.
Here is the text from a previous mail:
---
About our subscription and it's value for customers:
The Bareos project publishes binary packages for Windows, MacOS and most
Linux distributions for every major version, this means approximately
once a year.
Furthermore the project publishes binary packages of the latest
development branch, whenever new code has been excepted and commited.
We at Bareos maintain the major version over time by fixing bugs and
adding features. The source code is always published on GitHub, while
the updated packages for the stable version are made accessible for
subscription customers, only.
This is very similar to the way like RedHat or Suse maintain their
Enterprise Linux Subscriptions.
For use in production we highly recommend to deploy our well tested and
maintained subscription packages. For environments with subscription
packages, we offer additional support.
More about subscription, support and pricing can be found on our webpage:
http://www.bareos.com/en/Subscription.html
With kind regards
----
With kind regards // Mit freundlichen Grüßen
--
Maik Außendorf maik.au...@bareos.com
Bareos GmbH & Co. KG Phone: +49221630693-93
http://www.bareos.com Fax: +49221630693-10
Marco van Wieringen
> Hello Adam,
>
> I've sent information regarding the subscription earlier.
>
> The main difference is: there are patches and updates to the major
> version in the subscription repositories, all tested by our continuous
> integration tests. And there is support available for the subscription.
> Regarding Solaris, AIX and HP-UX: binary packages are only available by
> subscription - or self built.
>
> Am 10.11.2015 um 18:37 schrieb Adam Thompson:
>> On Monday, November 9, 2015 at 11:41:19 AM UTC-6, Marco van Wieringen wrote:
>>> I have this running since I programmed it for Bacula in 2008 never had a single problem
>>> with it. Its called bareos_backup_manager and even includes things like [...]
>>>
>>> This is all part of our commercial Solaris packages which saves you the hassle of having
>>> to program it all yourself. [...]
>> Marco,
>> I've been looking, but I can't find any listing of what the difference is between the commercial binary subscription and the open-source edition.
>> This is one difference, I assume there are others?
which you install with pkgadd/pkgrm/pkginfo etc. Further more they are
build as 32 bits and 64 bits and use the isaexec method for selecting the
right architecture (although that gets less and less important now that sparcv9
is kind of default.)
Last but not least it includes proper SMF methods and manifests to let the SD and
DIR run as bareos user (with proper SMF permissions for the SD to access low level
SCSI stuff etc.) The FD has two SMF manifests one running as root with all rights
and one in readonly mode running as bareos with the rights to read and search for
all files but not do anything else.
Its also includes SMF authorization roles e.g. solaris.smf.manage.application.bareos
which allows you to give people right to administrate the instances them self without
needing root access.
This all comes from my 20 years of Solaris consultancy. And is what I have run myself
for the last 8 years or so.
Maik already explained the differences regarding the Linux packages which mean either
run the experimental in production, build yourself or keep on running the last stable.
In essence experimental is always having the latest and greatest stuff ages before we
ship it as a stable product. So if you want to live on the bleeding edge that is a good
way to do so.
Next to that the subscription make sure things will continue in the future.
If everyone thinks things will go on for ever they have clearly misunderstood the
meaning of Open Source. In the end we are not a charity so also have to pay people
and invoices.
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com
Adam Thompson
 |
Adam Thompson Senior Systems Administrator voice: 204.789.9596 x24 | email: atho...@avant.ca | web: avant.ca |
--
You received this message because you are subscribed to a topic in the Google Groups "bareos-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bareos-users/gS8VftvK3lc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bareos-users...@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Bruno Friedmann
> Marco, I've already got the PO in our system; I understand that I have to
> support a project for it to continue!
>
> My problem is that there's a quite important piece of functionality that
> you say is included with the Solaris packages, but *that isn't documented
> anywhere*.
>
> I was able to use that fact to help justify the expense, which was
> otherwise a hard sell ("why don't we just compile it ourselves, then?").
>
> If there are any other features bundled with the commercial / official /
> supported / whatever-you-call-them binaries, *I want to know*, because that
> helps me get purchase orders approved, and that makes my life easier.
>
> I can't find anything on the website telling me why my company should pay
> the €290 (and more) other than the highly intangible (and thus
> not-commercially-viable) idea of supporting the developers.
>
> Please, help me (and, I suspect, most other north-americans) help you.
>
> -Adam
>
There's one point which is not taken into accounts by your "boss".
If you take holidays, or got sick, and the other guy that perhaps know
how to build got fired last week, who will be able to install the software ?
With pre-done Bareos made its question of seconds or minute, in the other case
hours, days ?
When you will be on rescue after disaster mode, do you really think
that you will have time to got the time to recompile the sources,
And also run all the tests before putting in production.
The Build, the Test, and quick delivery make the paid product easy.
Also if you're doing your own compilation, there's less chance to upgrade
for direct support in case of need.
I wouldn't have two different version. This drive free software to "evil core" things.
and remove the warranty of FOSS. Now with the honest price of a subscription
you got a build, certified, ready to use binary, and help the project
to develop.
ps : I'd like to check with you if the argument are enough or not.
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member & Board, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
Adam Thompson
> There's one point which is not taken into accounts by your "boss".
> If you take holidays, or got sick, and the other guy that perhaps know
> how to build got fired last week, who will be able to install the software ?
When I took over this position, I had no idea how to restore from the existing tapes, and no DR recovery procedures were documented, so it seems this is not a major concern for the owner.
> With pre-done Bareos made its question of seconds or minute, in the other case
> hours, days ?
We would have to wait days to get another LTO6 tape drive...
> When you will be on rescue after disaster mode, do you really think
> that you will have time to got the time to recompile the sources,
See previous point... yes, we would have the time. LTO6 drives don't grow on trees. (Unfortunately.)
> And also run all the tests before putting in production.
> The Build, the Test, and quick delivery make the paid product easy.
That is a concern, yes.
> Also if you're doing your own compilation, there's less chance to upgrade
> for direct support in case of need.
Why? At the point of needing support, we would simply purchase the certified binaries first.
> I wouldn't have two different version. This drive free software to "evil core" things.
> and remove the warranty of FOSS. Now with the honest price of a subscription
> you got a build, certified, ready to use binary, and help the project
> to develop.
I agree with that; but I have difficulty justifying the business requirement to spend over C$1000 to get... the same thing I can get for free? FOSS (in this model) still doesn't mesh well with (some) business needs.
It would be much easier to justify spending double the amount on support that merely includes binaries - then I can point to the support and say "*that's* what we're paying for".
> ps : I'd like to check with you if the argument are enough or not.
If it was my own money: maybe. Very much maybe. It would depend on how easily I could afford it at the moment.
When it's not my money and I have to justify a business case: nope, not at all.
-Adam