From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <t.lamprecht@proxmox.com> 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 779E961CF0 for <pve-user@lists.proxmox.com>; Fri, 10 Jul 2020 16:24:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6363222E91 for <pve-user@lists.proxmox.com>; Fri, 10 Jul 2020 16:23:53 +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)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 8BA9022E84 for <pve-user@lists.proxmox.com>; Fri, 10 Jul 2020 16:23:52 +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 5B5FF43147; Fri, 10 Jul 2020 16:23:52 +0200 (CEST) To: Simone Piccardi <piccardi@truelite.it>, pve-user@lists.proxmox.com References: <c84ac772-d577-27fd-710c-293d8a4baffe@proxmox.com> <a1e5f8dd-efd5-f8e2-50c1-683d42b0f61b@truelite.it> From: Thomas Lamprecht <t.lamprecht@proxmox.com> Message-ID: <f4429d20-df2f-95d2-c06e-04d4814cb907@proxmox.com> Date: Fri, 10 Jul 2020 16:23:51 +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: <a1e5f8dd-efd5-f8e2-50c1-683d42b0f61b@truelite.it> 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] 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 <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 10 Jul 2020 14:24:23 -0000 On 10.07.20 16:01, Simone Piccardi wrote: > Il 10/07/20 12:56, Martin Maurer ha scritto: >> We are proud to announce the first beta release of our new Proxmox Backup Server. >> > > > Thanks for the effort, that's very interesting. > Two question: > > 1. Having two indipendend Proxmox server can install it on both, to do a cross backup? You can add remotes to Proxmox Backup servers which can be synced efficiently and also automatically with a set schedule. And, you can also use it as target for multiple seprate Proxmox VE clusters, albeit some optimizations are still planned here: https://pbs.proxmox.com/wiki/index.php/Roadmap > 2. There is a stress on ZFS support on the kernel and in the documentation there is a chapter on managing it, it's not clear to me if this is needed just for better performance or I can use it also just using an installation having just LVM > Effectively you can use whatever is supported on the system where Proxmox Backup Server is installed, it needs to be a filesystem. The web-interface of PBS supports creating an ext4 or XFS backed datastore besides ZFS also. We recommend ZFS mainly because it has built-in support to get some redundancy easily and can work with really huge datasets (hundreds of TB), so this makes it ideal for a future proof Backup Server where hundreds to thousand of hosts backup too. If you're rather happy with another filesystem as backing datastore you can naturally use it :) cheers, Thomas