Re: [qubes-users] qvm-backup --exclude no longer exluding specified VMs from backup

2018-03-13 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Xaver: > After updating system from 4.0-rc4 to rc5 qvm-backup --exclude no > longer excludes the specified VM from the backup. I recently broke that. Sorry, and thanks for the bug report! https://github.com/QubesOS/qubes-core-admin/pull/202 Rusty

[qubes-users] qvm-backup --exclude no longer exluding specified VMs from backup

2018-03-13 Thread 'Xaver' via qubes-users
After updating system from 4.0-rc4 to rc5 qvm-backup --exclude no longer excludes the specified VM from the backup. When the command is run the specified VMs are in fact included in the backup. This was not an issue with 4.0-rc4 and a system backup was created prior to updating to rc5 without

[qubes-users] qvm-backup-restore bug qubes 4.0-rc4

2018-02-10 Thread cyberian
i have successfully backed up and restored several vm's after upgrading from rc-1 to rc-4 there is a bug which happens repeatedly when restoring the fedora-25-dvm domain. I have already restored fedora-25 template successfully. when restore begins the vm is added to the qubes vm menu but soon

Re: [qubes-users] qvm-backup-restore --verify-only broken ?

2017-11-30 Thread Jean-Luc Duriez
Le jeudi 30 novembre 2017 15:03:57 UTC+1, Francesco a écrit : > On Wed, Nov 29, 2017 at 10:02 PM, Chris Laprise wrote: > On 11/29/2017 05:43 PM, Jean-Luc Duriez wrote: > > > Hello Qubists > > > > I currently use Qubes R4 RC2, and would like to upgrade to RC3 after a >

Re: [qubes-users] qvm-backup-restore --verify-only broken ?

2017-11-30 Thread Franz
On Wed, Nov 29, 2017 at 10:02 PM, Chris Laprise wrote: > On 11/29/2017 05:43 PM, Jean-Luc Duriez wrote: > >> Hello Qubists >> >> I currently use Qubes R4 RC2, and would like to upgrade to RC3 after a >> backup. But I experience problems with the qvm-restore-backup

Re: [qubes-users] qvm-backup-restore --verify-only broken ?

2017-11-30 Thread Jean-Luc Duriez
Thanks for your feedback. Same issue when I try to verify the backup on a freshly installed 4RC3 system. More annoyingly, the standard restore does not work neither with the same error, so at this time we cannot restore any backup in a Qubes 4 based system. So I am going to be careful and

Re: [qubes-users] qvm-backup-restore --verify-only broken ?

2017-11-29 Thread Chris Laprise
On 11/29/2017 05:43 PM, Jean-Luc Duriez wrote: Hello Qubists I currently use Qubes R4 RC2, and would like to upgrade to RC3 after a backup. But I experience problems with the qvm-restore-backup --verify-only command. Should I worry about the quality of my backup ? Hi, I created issue #3303

[qubes-users] qvm-backup-restore --verify-only broken ?

2017-11-29 Thread Jean-Luc Duriez
Hello Qubists I currently use Qubes R4 RC2, and would like to upgrade to RC3 after a backup. But I experience problems with the qvm-restore-backup --verify-only command. Should I worry about the quality of my backup ? Here is my workflow: 1) backup on a USB external drive: [jl@dom0 bin]$

Re: [qubes-users] QVM Backup

2016-08-30 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-08-29 19:59, Drew White wrote: > On Monday, 29 August 2016 14:58:57 UTC+10, Andrew David Wong > wrote: >> Yes, that's just the way it does the backup, even for a single >> guest. However, there are plans to implement a qvm-export-vm tool

Re: [qubes-users] QVM Backup

2016-08-28 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-08-28 18:04, Drew White wrote: > Hi folks, > > Just wondering.. > > I've looked at the backup data for the XML file and it contains > ALL of the guests on the machine, not just the one I'm backing up. > > Is there any particular reason

[qubes-users] QVM Backup

2016-08-28 Thread Drew White
Hi folks, Just wondering.. I've looked at the backup data for the XML file and it contains ALL of the guests on the machine, not just the one I'm backing up. Is there any particular reason for this? Is it just the way that it does the backup for 1 guest? -- You received this message because