Unable to back up some VMs

I reported this back I believe in the Consultation thread but saw it was supposed have been fixed already. I get this in my automated back up log:

Backing up mysql-3.hldns.net to /backup/mysql-3.hldns.net.gz on host system .. .. backup failed : All disks have been either excluded from the backup or are for swap   Backing up mysql-4.hldns.net to /backup/mysql-4.hldns.net.gz on host system .. .. backup failed : All disks have been either excluded from the backup or are for swap

The other VMs back up just fine. The only thing different is that this is an image I made. I set up a CentOS 7 image and installed Webmin and MySQL on it with all of my configurations. I then shut down the VM and created an image of it through CM. I then created these two VMs (above with errors) using that image. This seems to happen using images that I create through Cloudmin. If I use one of the CM images, for example the base CentOS 7 image, it works fine every time.

What am I missing?

Status: 
Active

Comments

Steffan's picture
Submitted by Steffan on Tue, 10/11/2016 - 23:07 Pro Licensee

I can't even manually back it up either.

Backing up mysql-4.hldns.net to /backup on system h4.hldns.com .. Finding systems to backup .. .. found 1 systems Working out backup destinations .. .. found 1 usable destinations   Backing up mysql-4.hldns.net to /backup/mysql-4.hldns.net.gz on system h4.hldns.com .. .. backup failed : All disks have been either excluded from the backup or are for swap
Steffan's picture
Submitted by Steffan on Tue, 10/11/2016 - 23:32 Pro Licensee

Progress. It seems the CM Official images have the parameter: xen_filesystem_lv in their /etc/webmin/servers/xxxx.serv file but when I create an image of a VM I made and then reuse it to create a new VM it does not. Manually adding that parameter xen_filesystem_lv to the .serv file seems to correct the issue.

How long before you patch this? Seems to be a long standing bug. I found other references to this issue in the archives.

Damn, I thought I'd fixed that a few releases back.

Did you originally create the VM on LVM, but after the imaging and re-creation it was using regular files for disks?

Steffan's picture
Submitted by Steffan on Tue, 10/11/2016 - 23:44 Pro Licensee

It can replicated it easily.

  1. Make a VM of CentOS 7 using the official CM image using LVM
  2. Make your own image of the CentOS 7 VM above
  3. Make a new VM using the custom image above with LVM (I have that set as default anyway)
  4. Try a backup - it fails

What if you just try backing up immediately after step 1 - does that work?

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 00:14 Pro Licensee

Yes, I said that earlier. Stock CM images work fine. It fails on images you create yourself.

That is very odd, since the CM images were created by me using CM!

Can I login to your system and try creating a test VM?

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 00:23 Pro Licensee

Yes, you have my credentials in a previous email.

Ok, taking a look now.

What was the name of the image you created?

Which host system can I create a VM on, and what IP should I use for it?

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 00:42 Pro Licensee

Try h4. it has plenty of ram and disk space. 199.249.188.97

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 01:21 Pro Licensee

Have you been able to reproduce and isolate the issue?

Creating is still running! I will take a look again in the morning..

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 01:26 Pro Licensee

It's a 100gb disk and I had 16gb ram on it. It takes about 20-30 min to create it.

So I created a VM called "jamietest" , and it does have the xen_filesystem_lv line in its config file.

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 01:32 Pro Licensee

Not sure what the deal is. I created that mysql-3 and mysql-4 and both had the same problem. I changed them and now it backs up. I'll see if yours fails or not this evening.

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 11:44 Pro Licensee

Ok, a bit frustrating. After I made those changes last night, mysql-4 backed up fine. The auto backup ran over night and produced the error again!

Backing up mysql-4.hldns.net to /backup/mysql-4.hldns.net.gz on host system .. Creating LVM snapshots for disks of mysql-4.hldns.net .. .. backup failed : All disks have been either excluded from the backup or are for swap

Not sure where to go from here.

Is that still happening for mysql-4.hldns.net ? Because its config looks OK.

Steffan's picture
Submitted by Steffan on Wed, 10/12/2016 - 22:33 Pro Licensee

It did that last night. I'll find out in the morning to see if it happens again after the backups run at midnight.

Steffan's picture
Submitted by Steffan on Thu, 10/13/2016 - 11:33 Pro Licensee

Ok, I'm flustered. Yesterday, MySQL-3 backed up fine and MySQL-4 did not. Now, neither do yet VMs I manually created one at a time worked fine.

Backing up mysql-3.hldns.net to /backup/mysql-3.hldns.net.gz on host system .. Creating LVM snapshots for disks of mysql-3.hldns.net .. .. backup failed : All disks have been either excluded from the backup or are for swap   Backing up mysql-4.hldns.net to /backup/mysql-4.hldns.net.gz on host system .. Creating LVM snapshots for disks of mysql-4.hldns.net .. .. backup failed : All disks have been either excluded from the backup or are for swap

Ok, let me take a look at the state of those VMs now..

So I just kicked off a backup with the command :

vm2 backup-systems --host mysql-3.hldns.net --dest host:/backup

and it seems to be running OK. How did you do that backup that you got the error from?

Steffan's picture
Submitted by Steffan on Thu, 10/13/2016 - 23:42 Pro Licensee

Automated nightly backups of all VMs.

Ok, let's see how the backup I'm currently running goes. I don't understand how a scheduled backup could behave differently from a manual backup though, as the code is the same.

Steffan's picture
Submitted by Steffan on Mon, 10/17/2016 - 01:09 Pro Licensee

I've changed the backups to run one at a time tonight. We'll see if that VM will auto back up this time.