public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	mj <lists@merit.unu.edu>
Subject: Re: [PVE-User] Proxmox Backup Server (beta)
Date: Sat, 11 Jul 2020 15:47:47 +0200	[thread overview]
Message-ID: <5e9d8265-a255-f726-b8a1-8bd3934b58ca@proxmox.com> (raw)
In-Reply-To: <c522fc9b-6b3f-7770-d32a-c1bb47961884@merit.unu.edu>

Hi MJ,

On 11.07.20 15:34, mj wrote:
> On 7/11/20 1:38 PM, Thomas Lamprecht wrote:
>> Nope, can do everything[0][1][2]! You can do file-based backups also. The client
>> is a statically linked binary and runs on every relatively current Linux with
>> an amd64 based CPU, so it doesn't even has to be a Debian server.
> 
> That is great.
> 
> And then some follow=up questions if I may...:
> 
> - I don't see any 'DR' options, right? As in: bare metal disaster recovery restores, using a recovery boot iso, and restore a system from scratch to bootable state. It's not a tool for that, right?

Currently there's no such integrated tool, but honestly I do not think that
would be *that* hard to make. We have a similar process in plan for VMs, i.e.,
boot a VM with a live system and the backup disks as read only disks
plugged in.

Note also that the client has already support to mount an archive of a backup
locally over a FUSE filesystem implementation - maybe that would help already.

> 
> - I guess with VMs etc, the backup will use the available VM options (ceph, zfs, lvm) to snapshot a VM, in order to get consistent backups, like the current pve backup does.

Yes.

> But how does that work with non-VM client? (some non-VM client systems run LVM, so lvm could be used to create a snapshot and backup that, for example. Does it do that? Will my non-VM mysql backups be consistent?)

So here I do not have all details in mind but AFAIK: mot yet, it detects
some file changes where inconsistencies could have happened but doesn't
yet tries to detect if the underlying storage supports snapshots and uses
that to get a more consistent state. For containers we do that explicit
through the vzdump tooling.

> 
> - Any timeframe for adding LTO tape support..?

No, currently I do not have any, I'm afraid.

> We're really excited, and time-permitted I will try to play around with this monday/tuesday. :-)
> 

Great, hope it fits your use case(s).

cheers,
Thomas




  reply	other threads:[~2020-07-11 13:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 10:56 Martin Maurer
2020-07-10 11:42 ` Roland
2020-07-10 12:09   ` Dietmar Maurer
2020-07-10 12:24     ` Roland
2020-07-10 13:43       ` Thomas Lamprecht
2020-07-10 14:06         ` Roland
2020-07-10 14:15           ` Thomas Lamprecht
2020-07-10 14:46             ` Roland
2020-07-10 17:31               ` Roland
2020-07-10 13:44       ` Dietmar Maurer
     [not found] ` <mailman.77.1594381090.12071.pve-user@lists.proxmox.com>
2020-07-10 11:45   ` Dietmar Maurer
     [not found]     ` <a92c7f1d-f492-2d43-00b9-15bdb0e805ec@binovo.es>
2020-07-10 13:50       ` Thomas Lamprecht
2020-07-10 12:03 ` Lindsay Mathieson
2020-07-10 12:13   ` Dietmar Maurer
2020-07-10 15:41     ` Dietmar Maurer
2020-07-11 11:03       ` mj
2020-07-11 11:38         ` Thomas Lamprecht
2020-07-11 13:34           ` mj
2020-07-11 13:47             ` Thomas Lamprecht [this message]
2020-07-11 14:40             ` Dietmar Maurer
2020-07-14 14:30               ` Alexandre DERUMIER
2020-07-14 15:52                 ` Thomas Lamprecht
2020-07-14 21:17                   ` Alexandre DERUMIER
2020-07-15  4:52                     ` Thomas Lamprecht
     [not found]                       ` <176392164.4390.1594849016963.JavaMail.zimbra@numberall.com>
2020-07-16  7:33                         ` Thomas Lamprecht
     [not found]                       ` <mailman.204.1594849027.12071.pve-user@lists.proxmox.com>
2020-07-16 10:17                         ` Wolfgang Bumiller
2020-07-16 14:36                           ` Mark Schouten
2020-07-16 17:04                             ` Thomas Lamprecht
2020-07-16 13:03                   ` Tom Weber
2020-07-17  7:31                     ` Fabian Grünbichler
2020-07-17 13:23                       ` Tom Weber
2020-07-17 17:43                         ` Thomas Lamprecht
2020-07-18 14:59                           ` Tom Weber
2020-07-18 18:07                             ` Thomas Lamprecht
2020-07-10 12:45 ` Iztok Gregori
2020-07-10 13:41   ` Dietmar Maurer
2020-07-10 15:20     ` Iztok Gregori
2020-07-10 15:31       ` Dietmar Maurer
2020-07-10 16:29         ` Iztok Gregori
2020-07-10 16:46           ` Dietmar Maurer
     [not found] ` <a1e5f8dd-efd5-f8e2-50c1-683d42b0f61b@truelite.it>
2020-07-10 14:23   ` Thomas Lamprecht
2020-07-10 15:59 ` Lindsay Mathieson
     [not found] ` <mailman.86.1594396120.12071.pve-user@lists.proxmox.com>
2020-07-10 16:32   ` Dietmar Maurer
2020-10-06 13:12 ` Lee Lists
2020-10-08  8:21   ` Thomas Lamprecht
2020-10-09  9:27     ` Lee Lists
2020-10-09 12:10 Lee Lists

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e9d8265-a255-f726-b8a1-8bd3934b58ca@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=lists@merit.unu.edu \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal