Re: [Openstack] nova backup - instances unreachable

Adding disable_libvirt_livesnapshot = false to the nova.conf enabled live snapshots. Thanks everyone for the help. ___ John Petrini NOC Systems Administrator // *CoreDial, LLC* // coredial.com // [image: Twitter] [image: LinkedIn]

Re: [Openstack] nova backup - instances unreachable

Hi Eugen, disable_libvirt_livesnapshot is not present in the nova.conf. During the snapshot the nova logs says "Beginning cold snapshot". I read about this option in the nova documentation but did not realize it was the default. In fact I assumed it wasn't since it's in the workarounds section. I

Re: [Openstack] nova backup - instances unreachable

Have you enabled live snapshots in nova.conf? The default for this option is "true", so you should check that: disable_libvirt_livesnapshot = false Is it really a live snaphot? What's in the nova-compute.log? It should say something like [instance: XXX] Beginning live snapshot process Reg

Re: [Openstack] nova backup - instances unreachable

Hi All, Following up after making this change. Adding write permissions to the images pool in Ceph did the trick and RBD snapshots now work. However the instance is still paused for the duration of the snapshot. Is it possible to do a live snapshot without pausing the instance? Thanks, John On

Re: [Openstack] nova backup - instances unreachable

Thanks, for anyone interested in this issue, I filed a bug report: https://bugs.launchpad.net/nova/+bug/1656242 Regards, Eugen Zitat von Mohammed Naser : It is likely because this has been tested with QEMU only. I think you might want to bring this up with the Nova team. Sent from my i

Re: [Openstack] nova backup - instances unreachable

It is likely because this has been tested with QEMU only. I think you might want to bring this up with the Nova team. Sent from my iPhone > On Jan 12, 2017, at 11:28 AM, Eugen Block wrote: > > I'm not sure if this is the right spot, but I added some log statements into > driver.py. > First,

Re: [Openstack] nova backup - instances unreachable

I'm not sure if this is the right spot, but I added some log statements into driver.py. First, there's this if-block: if (self._host.has_min_version(MIN_LIBVIRT_LIVESNAPSHOT_VERSION, MIN_QEMU_LIVESNAPSHOT_VERSION,

Re: [Openstack] nova backup - instances unreachable

Yes, I truncated the file and uploaded it: http://dropcanvas.com/ta7nu (First time I used this service, please give me feedback if this doesn't work for you) I see the "Beginning cold snapshot process" message, but I don't know why. Any help is appreciated! Regards, Eugen Zitat von Moha

Re: [Openstack] nova backup - instances unreachable

Would you be able to share the logs of a full snapshot run with the compute node in debug? Sent from my iPhone > On Jan 12, 2017, at 7:47 AM, Eugen Block wrote: > > That's strange, I also searched for this message, but nothing there. I have > debug logs enabled on compute node but I don't see

Re: [Openstack] nova backup - instances unreachable

That's strange, I also searched for this message, but nothing there. I have debug logs enabled on compute node but I don't see anything regarding ceph. No matter, what I do, my instance is always shutdown before a snapshot is taken. What else can I try? Zitat von John Petrini : Mohammed,

Re: [Openstack] nova backup - instances unreachable

Mohammed, It looks like you may be right. Just found the permissions issue in the nova log on the compute node. 4-e8f52e4fbcfb 691caf1c10354efab3e3c8ed61b7d89a 49bc5e5bf2684bd0948d9f94c7875027 - - -] Performing standard snapshot because direct snapshot failed: no write permission on storage pool

Re: [Openstack] nova backup - instances unreachable

Hi John, It just works for us with Mitaka. You might be running with issues regarding permissions where the Nova user might not be able to write to the images pool. Turn debug on in your nova compute and snapshot a machine on it, you'll see the logs and if it's turning it off, it's probably b

Re: [Openstack] nova backup - instances unreachable

Have you or anyone else implemented this in Mitaka? Yes, we are also running Mitaka and I also read Sebastien Han's blogs ;-) our snapshots are not happening at the RBD level, they are being copied and uploaded to glance which takes up a lot of space and is very slow. Unfortunately, that's w

Re: [Openstack] nova backup - instances unreachable

Hi Eugen, Thanks for the response! That makes a lost of sense and is what I figured was going on but I missed it in the documentation. We use Ceph as well and I had considered doing the snapshots at the RBD level but I was hoping there was someway to accomplish this via nova. I came across this Se

Re: [Openstack] nova backup - instances unreachable

Hi, this seems to be exptected, the docs say: "Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk." So if the VM is not shut down, it's freezed to prevent data loss (I guess). Depending on your storage backend, there are other ways to perform

[Openstack] nova backup - instances unreachable

Hello, I've just started experimenting with nova backup and discovered that there is a period of time during the snapshot where the instance becomes unreachable. Is this behavior expected during a live snapshot? Is there any way to prevent this? ___ John Petrini _

Re: [Openstack] nova backup

okay. I tested cinder backup to 2nd ceph cluster.  1. I created full backup 2. I created incremental backup But on 2nd ceph cluster I see two full size backup (each 20G) Do anybody know why? rbd --cluster bak -p backups du warning: fast-diff map is not enabled for volume-46a306ae-2454-4425-a6f7-

Re: [Openstack] nova backup

Hi, I haven't used nova backup yet, I only tested cinder backup. But obviously you launched that instance via boot-from-volume, so your instance's image resides within a volume, and volumes are handled by cinder. So these instances should be backed up via cinder. Eugen Zitat von K K :

[Openstack] nova backup

Hello. When I try to create backup: nova backup testdeb testdeb_bak daily 2 nova-api said: ==> nova/nova-api.log <== 2016-04-21 16:40:14.828 2814 INFO nova.compute.api [req-e89878e7-9d26-4e6e-8922-8aa9bba56b72 8d384cc45d0c467eb46ef3f980cf314d 3029462986ac400ca2c2c6ac4c9af5a7 - - -] [instance: a