public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	Petric Frank <pfrank@gmx.de>
Subject: Re: [PVE-User] LXC mount point not in backup
Date: Fri, 29 Jan 2021 15:59:50 +0100 (CET)	[thread overview]
Message-ID: <1182254484.1418.1611932390376@webmail.proxmox.com> (raw)
In-Reply-To: <3515667.kIdP2CnQM6@main>


> Petric Frank <pfrank@gmx.de> hat am 29.01.2021 13:36 geschrieben:
> 
>  
> Hello,
> 
> in my config i have a mountp point defined as:
> 
>   mp0: /storage/nextcloud-gz,mp=/nextcloud,ro=0,backup=1
> 
> Despite the option "backup=1" it is not included in an backup. The backup screen log:
> --------------------------- cut --------------------------
> INFO: starting new backup job: vzdump 200 --compress gzip --node proxmox-gz --remove
> 0 --mode stop --storage zfs-raid
> INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp31209_200 for
> temporary files
> INFO: Starting Backup of VM 200 (lxc)
> INFO: Backup started at 2021-01-29 13:23:05
> INFO: status = stopped
> INFO: backup mode: stop
> INFO: ionice priority: 7
> INFO: CT Name: nextcloud
> INFO: including mount point rootfs ('/') in backup
> INFO: excluding bind mount point mp0 ('/nextcloud') from backup (not a volume)
> INFO: creating vzdump archive '/storage/vz/dump/vzdump-
> lxc-200-2021_01_29-13_23_05.tar.gz'
> INFO: Total bytes written: 3123005440 (3.0GiB, 21MiB/s)
> INFO: archive file size: 1.39GB
> INFO: Finished Backup of VM 200 (00:02:27)
> INFO: Backup finished at 2021-01-29 13:25:32
> INFO: Backup job finished successfully
> TASK OK
> --------------------------- cut --------------------------
> 
> As you can see the line below states that as "not a volume":
> INFO: excluding bind mount point mp0 ('/nextcloud') from backup (not a volume)
> 
> Is there a way to include the mount point in a backup ?

no. the assumption here is that you are using a bind mount to pass in something that is not managed by PVE (e.g., a dir used in more than one container, some network share mounted on the host, ..) and thus also not included in backups.

> Additional question: What is the behaviour of PBS in this case ?

if you of mean of vzdump when backing up to PBS - identical. of course if you run proxmox-backup-client from within the container you can choose yourself which mountpoints are included or not..




      reply	other threads:[~2021-01-29 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 12:36 Petric Frank
2021-01-29 14:59 ` Fabian Grünbichler [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=1182254484.1418.1611932390376@webmail.proxmox.com \
    --to=f.gruenbichler@proxmox.com \
    --cc=pfrank@gmx.de \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal