12 thoughts on - C8 And Backup Solution

• Le 02/04/2020

• Il 02/04/20 17:49, Nicolas Kovacs ha scritto:
  Hi Niki, thank you for your answer.

  I remember you when I used Slackware and I think your KISS is inherited by there but sometimes more complex things are needed. Rsnapshot is a great tool but I need catalog, jobs info, pre/post job script on remote target, mailing, compression and possibly store data off-site (no on a public cloud).

• Just a point of clarification — you need an rsync binary on both sides of the SSH session, so ‘rsync’ would be the agent needed on the target.

• Yes you are right. I meant that I don’t need an real agent like with bacula that need to be configured completely

  Il Gio 2 Apr 2020, 19:52 Jonathan Billings ha scritto:

• Il 02/04/20 21:14, Karl Vogel ha scritto:

  Hi Karl,

  thank you for your answer. I’m trying SSH scripted rsync using a faster cypher like you suggested and seems that transfer on 10GB is better of default selected cypher (129 sec vs 116 using aes128-gcm, I tested this multiple times). Now I will try to check on the entire dataset and see how much benefit I gain.

  Waiting that, what do you think about bacula as backup solution?

  Thank you in advance.

• I have been using rsnapshot for years, with great success.

  https://rsnapshot.org/

• Do note, backup systems that use rsync or similar file by file copies of a running system do not make coherent atomic snapshots, so things like relational databases should be excluded from those, and backed by database tools

• Long ago I learned to back up databases by dumping them (with a flag
  “lock” or similar to make sure no changed are made during dump), and backing up dump file.

  Just my 2 cents.

  Valeri

• Once upon a time, Valeri Galtsev said:

  It isn’t just databases – there are other things that backing up individual files one at a time is not so good. The best way to handle that is to freeze/snapshot the whole filesystem, and then back up the snapshot. This can be scripted pretty easily if the filesystem is on LVM.

  Even better is to freeze _all_ filesystems simultaneously – this is usually easiest if the system is a virtual machine and/or the storage is on a SAN with snapshot capabilities.

• Then again, to get a _really_ consistent backup, you can only terminate all applications who read/write files, or instruct the applications to go into a state which allows consistent file backups. Of course after the backup you have to instruct the applications to go on with the work. You can not achieve this consistency even with freezing _all_ filesystems simultaneously. That’s why usually RDBMS’s and other more complex applications provide their own backup mechanism embedded into the application.

  That’s why rsnapshot backups are not so much worse than filesystem snapshots.

  Regards, Simon

• Since no one else has mentioned it as a solution, I’ve been using amanda for years.  About the only change has been replacing my physical tape drive with mhVTL (Anybody need some unused DSS-3 tapes? Free to good home.).

  Cheers, Dave

  —
  “They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.”

  — Benjamin Franklin

• I tried this with a fairly busy and rather large database server (ok, it was a database server running a simulation of a production workload) and LVM (with either ext4 or xfs) and found LVM snapshots to be completely unworkable under busy 8K block random write workloads

  now, ZFS does snapshots very nicely