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 54A0071154 for ; Wed, 8 Sep 2021 12:09:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 425C624729 for ; Wed, 8 Sep 2021 12:09:26 +0200 (CEST) Received: from mx0.konsec.net (hbase53.h.konsec.com [88.99.94.78]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 529CA2471E for ; Wed, 8 Sep 2021 12:09:25 +0200 (CEST) Received: from kolab.konsec.com (unknown [10.21.1.190]) by mx0.konsec.net (Postfix) with ESMTPS id 982FD80C9EE for ; Wed, 8 Sep 2021 12:09:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsec.com; s=201809; t=1631095764; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=svrjJFNGi2zPqLxK6OG6DFatmcCDW7ZACO8k/awsYLo=; b=Huk4OKvVRnSHHP0HJ8KrQolbx5za7+GFGLxMI+FspHzsLr14NsSlLLKdrW2BZcwnpjN2nQ 8nVKcwJa1uwoHBItUFDVMue64cknyf3qex4wrXHpyisvz34SsgRFTGk3YOnuyZrDKnVKG3 RNr6sJUw/jLBfKhnJIYSQcMrRSxnJbzJ/bvQc/5FNhUIWj3D6F6D7psamqByAYBHirFqOc FUh/cyJmGxFkc+f7nGTAh6tCVURQNpZrkggiCnNag5ZEEqrZcH1VZInbPPQ4L8DRoC0gjN vk+MajGWO2JDfy1cazh1aPDxXFTi4f7nP+29ydRppiLVZ9R/g/oM8Zm0EI6iRQ== Sender: martin.konold@konsec.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Date: Wed, 08 Sep 2021 12:09:24 +0200 From: "Konold, Martin" To: Proxmox VE user list Reply-To: martin.konold@konsec.com In-Reply-To: <99b82feffbce274c20bfefb18e41efd8@verdnatura.es> References: <99b82feffbce274c20bfefb18e41efd8@verdnatura.es> Message-ID: <467c4ba60fe8307ae8c32023e2a22a5f@konsec.com> X-Sender: martin.konold@konsec.com Organization: KONSEC GmbH Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.120 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks 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] VM storage and replication 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: Wed, 08 Sep 2021 10:09:56 -0000 Hi, while I highly recommend PBS I made good experience with using CIFS=20 instead of NFS for performing backups to a central NAS. --- Regards ppa. Martin Konold -- Martin Konold - Prokurist, CTO KONSEC GmbH -=E2=81=A0 make things real Amtsgericht Stuttgart, HRB 23690 Gesch=C3=A4ftsf=C3=BChrer: Andreas Mack Im K=C3=B6ller 3, 70794 Filderstadt, Germany Am 2021-09-08 11:25, schrieb nada: > hi Alex > in case you have a limited budget now > you may do backups local backups but it is not recommended by some > cheap NAS ASAP >=20 > temporal solution: > 1. create some filesystem LVM/ext4 @node1 and mount at /mnt/backup > 2. install NFS server @node1 and export /mnt/backup to node2 > 3. install NFS client @node2 and create mountpoint /mnt/backup > 4. edit fstab @node2 example > node1:/mnt/backup /mnt/backup nfs =20 > defaults,noatime,bg 0 2 > 5. mount /mnt/backup > 6. add directory to your proxmox storage via webGUI > or add to /etc/pve/storage.cfg example >=20 > dir: backup > path /mnt/backup > content vztmpl,backup,iso >=20 > after this you will have backups accessible at both nodes > hope it will help you > Nada >=20 >=20 > On 2021-09-08 10:05, Alex K wrote: >> Hi all, >>=20 >> I have setup a dual server setup, with latest proxmox v7.x. Each host=20 >> with >> its own local storage. No shared storage (CEPH, GlusterFS). >>=20 >> I understand I can have VMs hosted on top LVM with qcow2 disk images=20 >> or on >> top thin LVM as raw thin LVM volumes. On both cases I still keep the=20 >> option >> to be able to perform VM backups. Which one is the preferred way=20 >> according >> to your experience? I will try to do some quick tests on the IO=20 >> performance >> between the two. >>=20 >> Also, I was thinking to replicate the VMs from one host to the other.=20 >> I >> understand that for the Proxmox integrated replication feature I need=20 >> ZFS >> backed storage. As I am not much into ZFS, although I really enjoy=20 >> FreeNAS >> and its great features and will definitely look into it later, I was >> thinking to prepare a custom script that would snapshot the LVM=20 >> volumes >> where the VM images reside and sync the VM disks from one host to the >> other, using rsync, just for a local copy of them. Of course I will=20 >> take >> care to have an external media also to periodically export the VMs for >> backup purposes, though I would like to have a local copy of the VM=20 >> disk >> images at the other host, readily available in case I face issues with= =20 >> the >> external media or one of the hosts. What do you think about this=20 >> approach? >> Am I missing some other feature or better approach? >>=20 >> Regrading the sync/replication of the VMs between the hosts (without=20 >> ZFS), >> I was thinking also to have a dedicated local LVM volume for these=20 >> periodic >> backup jobs configured within Proxmox and then the custom script to=20 >> just >> rsync these backup images between the two hosts. This seems a simple=20 >> one >> though it increases the storage requirements, while with the previous >> approach with the custom script, the script would snapshot, sync to=20 >> the >> other side and remove the snapshot without keeping a redundant local=20 >> copy >> of the disk image in the same host. >>=20 >> Sorry for the long read. >> Appreciate any feedback. >>=20 >> Alex >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >=20 > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user