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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 19F7D72909 for ; Tue, 13 Apr 2021 11:22:20 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0D14028B76 for ; Tue, 13 Apr 2021 11:22:20 +0200 (CEST) Received: from 14.mo1.mail-out.ovh.net (14.mo1.mail-out.ovh.net [178.32.97.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id ECC3228B6A for ; Tue, 13 Apr 2021 11:22:17 +0200 (CEST) Received: from player687.ha.ovh.net (unknown [10.108.1.219]) by mo1.mail-out.ovh.net (Postfix) with ESMTP id 779C11F675C for ; Tue, 13 Apr 2021 10:44:38 +0200 (CEST) Received: from riminilug.it (host-79-7-69-158.business.telecomitalia.it [79.7.69.158]) (Authenticated sender: piviul@riminilug.it) by player687.ha.ovh.net (Postfix) with ESMTPSA id DA0771D033A37 for ; Tue, 13 Apr 2021 08:44:37 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-101G00468f49967-389b-49f4-9419-9169ff76814a, CDEB2A25AF39A537C598A742E51F32E21BE5CBF1) smtp.auth=piviul@riminilug.it X-OVh-ClientIp: 79.7.69.158 To: pve-user@lists.proxmox.com References: From: Piviul Message-ID: <432743f5-b0ab-414f-297b-e55d8163166f@riminilug.it> Date: Tue, 13 Apr 2021 10:44:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: it-IT X-Ovh-Tracer-Id: 6482368717229577246 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledrudekledgtdekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefrihhvihhulhcuoehpihhvihhulhesrhhimhhinhhilhhughdrihhtqeenucggtffrrghtthgvrhhnpeevgeeftdfgleegueekffelleeuheehuefgjeeuheevffeiheejgfduieffjeelvdenucffohhmrghinhepphhrohigmhhogidrtghomhenucfkpheptddrtddrtddrtddpjeelrdejrdeiledrudehkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphdqohhuthdphhgvlhhopehplhgrhigvrheikeejrdhhrgdrohhvhhdrnhgvthdpihhnvghtpedtrddtrddtrddtpdhmrghilhhfrhhomhepphhivhhiuhhlsehrihhmihhnihhluhhgrdhithdprhgtphhtthhopehpvhgvqdhushgvrheslhhishhtshdrphhrohigmhhogidrtghomh X-SPAM-LEVEL: Spam detection results: 0 AWL -0.649 Adjusted score from AWL reputation of From: address KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years 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 RCVD_IN_MSPIKE_H3 0.001 Good reputation (+3) RCVD_IN_MSPIKE_WL 0.001 Mailspike good senders 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. [protonmail.ch, proxmox.com] Subject: Re: [PVE-User] pve-user Digest, Vol 157, Issue 12 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: Tue, 13 Apr 2021 09:22:20 -0000 Hi Oleksii, if you want to unsuscribe this list please go to https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user; you can found the instructions at the end of the page. Best regards Piviul Il 12/04/21 00:43, Oleksii Tokovenko ha scritto: > unsibscribe > > нд, 11 квіт. 2021 о 13:00 пише: > >> Send pve-user mailing list submissions to >> pve-user@lists.proxmox.com >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> or, via email, send a message with subject or body 'help' to >> pve-user-request@lists.proxmox.com >> >> You can reach the person managing the list at >> pve-user-owner@lists.proxmox.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of pve-user digest..." >> >> >> Today's Topics: >> >> 1. Re: Revisited: External disk backup using PBS - Requesting >> Criticism/Advice? (Lindsay Mathieson) >> 2. PBS Incremental and stopped VM's (Lindsay Mathieson) >> 3. Re: PBS Incremental and stopped VM's (Arjen) >> 4. Re: PBS Incremental and stopped VM's (Lindsay Mathieson) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sat, 10 Apr 2021 23:28:50 +1000 >> From: Lindsay Mathieson >> To: pve-user@lists.proxmox.com >> Subject: Re: [PVE-User] Revisited: External disk backup using PBS - >> Requesting Criticism/Advice? >> Message-ID: >> Content-Type: text/plain; charset=windows-1252; format=flowed >> >> 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 >> >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sat, 10 Apr 2021 23:36:23 +1000 >> From: Lindsay Mathieson >> To: pve-user@lists.proxmox.com >> Subject: [PVE-User] PBS Incremental and stopped VM's >> Message-ID: >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> I'm guessing only running VM's (with dirty bitmap support) can be >> incrementally backed up? >> >> >> Might be nice if we could schedule backups for only running VM's >> >> -- >> Lindsay >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Sat, 10 Apr 2021 13:43:43 +0000 >> From: Arjen >> To: Proxmox VE user list >> Subject: Re: [PVE-User] PBS Incremental and stopped VM's >> Message-ID: >> >> > protonmail.ch> >> >> Content-Type: text/plain; charset=utf-8 >> >> On Saturday, April 10th, 2021 at 15:36, Lindsay Mathieson < >> lindsay.mathieson@gmail.com> wrote: >> >>> I'm guessing only running VM's (with dirty bitmap support) can be >>> >>> incrementally backed up? >>> >>> Might be nice if we could schedule backups for only running VM's >> Just to be clear: PBS always makes a full backup. The resulting data is >> deduplicated (before sending it to the server), which almost always reduces >> the writes to the server. An administration of changed virtual disk blocks >> is kept for running VMs, which only reduces the reads from VMs that have >> not been restarted between backups. It data transfer over the network is >> the bottleneck, you will have most benefit from the former (less changes, >> less transfers). The latter only speeds up the backup due to less reads (of >> unchanged data) from disk. >> >> best regards, Arjen >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Sun, 11 Apr 2021 00:06:19 +1000 >> From: Lindsay Mathieson >> To: pve-user@lists.proxmox.com >> Subject: Re: [PVE-User] PBS Incremental and stopped VM's >> Message-ID: <90b0f7df-ca15-f9cd-b76a-0f8f26e24917@gmail.com> >> Content-Type: text/plain; charset=windows-1252; format=flowed >> >> On 10/04/2021 11:43 pm, Arjen via pve-user wrote: >>> Just to be clear: PBS always makes a full backup. The resulting data is >> deduplicated (before sending it to the server), which almost always reduces >> the writes to the server. >> >> Ah, I see now, thanks, I didn't understand that part of things. Looking >> at the logs of my 2nd backup, I see that stopped VM's had zero bytes >> written to the backup server. >> >> -- >> Lindsay >> >> >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> >> >> ------------------------------ >> >> End of pve-user Digest, Vol 157, Issue 12 >> ***************************************** >> >>