From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 981FD6221D for ; Sat, 11 Jul 2020 15:47:50 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 88609B9DD for ; Sat, 11 Jul 2020 15:47:50 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id CBF16B9D0 for ; Sat, 11 Jul 2020 15:47:48 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 980A4430D2; Sat, 11 Jul 2020 15:47:48 +0200 (CEST) To: Proxmox VE user list , mj References: <7d1bd7a4-f47b-4a1a-9278-ff1889508c33@gmail.com> <1768587204.461.1594383204281@webmail.proxmox.com> <450971473.487.1594395714078@webmail.proxmox.com> From: Thomas Lamprecht Message-ID: <5e9d8265-a255-f726-b8a1-8bd3934b58ca@proxmox.com> Date: Sat, 11 Jul 2020 15:47:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.000 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Proxmox Backup Server (beta) X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2020 13:47:50 -0000 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