From: Stefan Reiter <s.reiter@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>, pve-user@lists.proxmox.com
Subject: Re: [PVE-User] PBS backup/restore issue
Date: Wed, 24 Feb 2021 11:34:33 +0100 [thread overview]
Message-ID: <748aba12-573f-0bc8-17d7-b94b9b9b8cef@proxmox.com> (raw)
In-Reply-To: <c390959d-e5b5-9a95-770c-ff6853357cbe@binovo.es>
On 2/23/21 8:46 AM, Eneko Lacunza wrote:
> Hi all,
>
> Yesterday I hit a problem with PBS. My sequence of actions was:
>
> 1.a Install debian 10 VM (updated to latest, only system utilities and
> SSH server)
> 1.b Add SSH access key to root
> 1.c Shutdown VM
> 1.d Backup to PBS and to NFS vía regular backup.
> 1.e Start VM and install various packages - all OK.
> 1.f Stop VM
>
> 2.a Restore VM from PBS backup
> 2.b Start VM and install various packages - apt complains about no
> newline in linux-image-amd64 file manifest, can't install new packages.
> 2.c Stop VM
>
> 3.a Restore VM from NFS regular backup
> 3.b Start VM and install various packages - all OK.
>
Hi,
I tried to replicate your problem by following pretty much the exact
steps you mention above, but to no avail.
Fresh Debian 10 VM, PBS backup + VMA to local disk, restored both and
both work. I compared the disk images of the restored VMs with md5sum
and the hashes matched, as expected. Tested with the latest package
versions, though using QEMU 5.2.0, but the backup and restore
functionality shouldn't have changed there.
Could you try to see what the difference is between the restored disks
from the VMA and the PBS backups (if there is any)? I.e. restore them
both to seperate VMIDs and then compare hashes and/or run (v)bindiff on
the disk images (best restore to a directory storage in 'raw' mode) to
see where they differ - of course, this only makes sense if the backups
are created when the VM was shut down.
Potentially something about your NFS/PBS setup is corrupting data? You
mentioned in another mail that they "are the same disks", how is that
configured?
Also please post the exact error messages APT is giving you, and your VM
config.
> I hit the issue 3 times, and tried creating a new VM and a new Debian
> installation each time.
>
> Any ideas? I have the "broken" PBS backups saved.
>
> VM node:
> # pveversion -v [...]
>
> PBS node:
> # pveversion -v [...]
FYI, the more useful command for PBS would be:
proxmox-backup-manager versions --verbose
next parent reply other threads:[~2021-02-24 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c390959d-e5b5-9a95-770c-ff6853357cbe@binovo.es>
2021-02-24 10:34 ` Stefan Reiter [this message]
[not found] ` <6120d3f8-67c8-873f-164c-1913c2016a54@binovo.es>
2021-02-24 19:03 ` Thomas Lamprecht
[not found] <mailman.28.1614066435.365.pve-user@lists.proxmox.com>
2021-02-23 8:06 ` Dietmar Maurer
2021-02-24 9:44 ` mj
[not found] ` <mailman.44.1614161184.365.pve-user@lists.proxmox.com>
2021-06-13 18:36 ` proxmox
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=748aba12-573f-0bc8-17d7-b94b9b9b8cef@proxmox.com \
--to=s.reiter@proxmox.com \
--cc=elacunza@binovo.es \
--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