From: "Konold, Martin" <martin.konold@konsec.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] VM storage and replication
Date: Wed, 08 Sep 2021 12:09:24 +0200 [thread overview]
Message-ID: <467c4ba60fe8307ae8c32023e2a22a5f@konsec.com> (raw)
In-Reply-To: <99b82feffbce274c20bfefb18e41efd8@verdnatura.es>
Hi,
while I highly recommend PBS I made good experience with using CIFS
instead of NFS for performing backups to a central NAS.
---
Regards
ppa. Martin Konold
--
Martin Konold - Prokurist, CTO
KONSEC GmbH - make things real
Amtsgericht Stuttgart, HRB 23690
Geschäftsführer: Andreas Mack
Im Köller 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
>
> 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
> 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
>
> dir: backup
> path /mnt/backup
> content vztmpl,backup,iso
>
> after this you will have backups accessible at both nodes
> hope it will help you
> Nada
>
>
> On 2021-09-08 10:05, Alex K wrote:
>> Hi all,
>>
>> I have setup a dual server setup, with latest proxmox v7.x. Each host
>> with
>> its own local storage. No shared storage (CEPH, GlusterFS).
>>
>> I understand I can have VMs hosted on top LVM with qcow2 disk images
>> or on
>> top thin LVM as raw thin LVM volumes. On both cases I still keep the
>> option
>> to be able to perform VM backups. Which one is the preferred way
>> according
>> to your experience? I will try to do some quick tests on the IO
>> performance
>> between the two.
>>
>> Also, I was thinking to replicate the VMs from one host to the other.
>> I
>> understand that for the Proxmox integrated replication feature I need
>> ZFS
>> backed storage. As I am not much into ZFS, although I really enjoy
>> 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
>> 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
>> 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
>> disk
>> images at the other host, readily available in case I face issues with
>> the
>> external media or one of the hosts. What do you think about this
>> approach?
>> Am I missing some other feature or better approach?
>>
>> Regrading the sync/replication of the VMs between the hosts (without
>> ZFS),
>> I was thinking also to have a dedicated local LVM volume for these
>> periodic
>> backup jobs configured within Proxmox and then the custom script to
>> just
>> rsync these backup images between the two hosts. This seems a simple
>> one
>> though it increases the storage requirements, while with the previous
>> approach with the custom script, the script would snapshot, sync to
>> the
>> other side and remove the snapshot without keeping a redundant local
>> copy
>> of the disk image in the same host.
>>
>> Sorry for the long read.
>> Appreciate any feedback.
>>
>> Alex
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2021-09-08 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:05 Alex K
2021-09-08 9:25 ` nada
2021-09-08 9:38 ` Alex K
2021-09-08 10:09 ` Konold, Martin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467c4ba60fe8307ae8c32023e2a22a5f@konsec.com \
--to=martin.konold@konsec.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox