From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <lindsay.mathieson@gmail.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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C04A771FC9 for <pve-user@lists.proxmox.com>; Sat, 10 Apr 2021 15:29:09 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id ADCEDEB5F for <pve-user@lists.proxmox.com>; Sat, 10 Apr 2021 15:29:09 +0200 (CEST) Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 2AACCEB50 for <pve-user@lists.proxmox.com>; Sat, 10 Apr 2021 15:29:09 +0200 (CEST) Received: by mail-pl1-x636.google.com with SMTP id p10so4096616pld.0 for <pve-user@lists.proxmox.com>; Sat, 10 Apr 2021 06:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=1+lSW/YByYq10dSlIYilGFZOD2uUoFLLbo9oJzHlUrU=; b=jhdhu7mWtQkuLZtdHt5CP2Eki7Rk6UjSFNXCADXa7CRED6ym0qb4KQjMFMwCBeEkNY dyE72kGv5+91/brJAsaYXdXgxAh8Nua/wp9CZ8VLbSTD4NNbqb3DM59DaXU61wzGKGhm c9RyomswT+x1qrPa/gkMzW5xrpZb1ZBnECDwvNEtPaZQbezdsZMxIQJl1tHmNrCTU4YL sZZmMHFq02jMb68hRPt0gnC32gXessQ5/zinG8XVI1bJbOYFihwPdaTRMaFpGbocP6j9 ia/fZoJN8RmtsKqhbFJaMMwhqA1zMtvz8Kzo4K5AvMtEuoXvz7qgxeWLa05r6nRmgnDC kL9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=1+lSW/YByYq10dSlIYilGFZOD2uUoFLLbo9oJzHlUrU=; b=Q7CDrVHxEp8rT1oqb6OanuCdeLHltXcHMcjs8mfYiL6nTkVmcLn9gNNEUKHerjUVoN uhUDqbGIYqpHhsITqm4DxpX2vpUcr0JnVq1rd0Nvk5DkatLq67YN8ERaJsatOEricevK 5hjev9KN1h0uOmX7lyZDLWBnUp/goen/lTPMCjtfWAie/YxZlJKTNbYl1rBntzQKpSR7 xH7lpS/hHsY9ClyhLBWFDN5uHGCzYmyISVZUDAUjZZ3Oc5WF68e0UoBZ/cmEEmeBgAwZ KusfBG503o7c+AD7hWDY2prE7BPIhs/j4eQodGkMLxssH0gFl5kPtxcGCYJMg6ZcNlo/ 4/ng== X-Gm-Message-State: AOAM531ugARrHWSdFqJrMa63BDpB+SSJHUsYRg/TBQ1ID6/NVKRcLFhx DEB4lpKnrbm0LNSlQtG106+qkrwTwzNFTQ== X-Google-Smtp-Source: ABdhPJx8lHcdtA8e3qJGXg0VsU51K6zzN5T8ACfiA1dGMG6tP+fUqX7wJXG71iQ+gcptjLCGN0V6Bg== X-Received: by 2002:a17:90a:29a5:: with SMTP id h34mr14948432pjd.158.1618061340748; Sat, 10 Apr 2021 06:29:00 -0700 (PDT) Received: from [192.168.1.11] (167-179-176-9.a7b3b0.bne.nbn.aussiebb.net. [167.179.176.9]) by smtp.gmail.com with ESMTPSA id r1sm5292631pjo.26.2021.04.10.06.28.58 for <pve-user@lists.proxmox.com> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Apr 2021 06:28:59 -0700 (PDT) To: pve-user@lists.proxmox.com References: <15e5bfd5-7458-fdbe-5079-ce78a19e0099@gmail.com> <mailman.235.1618038675.359.pve-user@lists.proxmox.com> From: Lindsay Mathieson <lindsay.mathieson@gmail.com> Message-ID: <e92b8b56-e89f-928d-a3c8-7b423e334cf5@gmail.com> Date: Sat, 10 Apr 2021 23:28:50 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: <mailman.235.1618038675.359.pve-user@lists.proxmox.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-SPAM-LEVEL: Spam detection results: 0 AWL 0.044 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no 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] Revisited: External disk backup using PBS - Requesting Criticism/Advice? 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: Sat, 10 Apr 2021 13:29:09 -0000 On 10/04/2021 5:10 pm, Arjen via pve-user wrote: > Don't expect to be able to backup the PBS container with 4TB to a 2TB external drive. I only passed 2TB through and the actual backup data comes to 1.3TB > The Datastore of a PSB does not compress much further and Proxmox VE Backup will only backup virtual disks and not mountpoints or storages passed from host, if I understand correctly. I wondered that. Will be testing. > I suggest adding a virtual disk of 2TB to the PBS container (and format it with ext4) which can be backed up by the Proxmox VE Backup. Certainly a possibility. I also wondered if it was practical to attach an external disk to PBS as a Datastore, then detach it. A bit more manual, but doable. > I would also run the PBS container (with virtual disk) on the cluster instead on separate hardware which is a single point of failure. The local PBS would be then just as reliable as your cluster. I want to keep the storage separate from the cluster, in that regard the local storage is a single point of failure, hence the need for offsite storage as well :) > > Regarding safeness: I suggest doing a automated disaster recovery every week to make sure it works as expected. Or at least partially, like restoring the PBS from an external drive. I'll definitely be testing restore options to check that it works. > Regarding practicality: I would have a remote PBS sync with your local PBS instead of moving physical disks (but you mentioned before that that was not really possible). Alas :( Perhaps I could do a backup on site, then physically move it offsite and attach it to a offsite PBS server and then sync it remotely - incremental backups over the net would be doable. nb. Our NAS died, hence my increased investigation of this :) Definitely want to go with a more open and targeted solution this time, the NAS was a good appliance, but inflexible. Thanks! -- Lindsay