Comment 3 for bug 1228223

The issue here is that there's currently no way for the backup manager to interpret the multiple volume hosts. It relies only on the base default config option which in the case of multi-backends will grab the unscoped entry for backend or the default (cinder-volumes)

2013-09-20 23:34:55.716 DEBUG amqp [-] Start from server, version: 0.9, properties: {u'information': u'Licensed under the MPL. See http://www.rabbitmq.com/', u'product': u'RabbitMQ', u'copyright': u'Copyright (C) 2007-2011 VMware, Inc.', u'capabilities': {u'exchange_exchange_bindings': True, u'consumer_cancel_notify': True, u'publisher_confirms': True, u'basic.nack': True}, u'platform': u'Erlang/OTP', u'version': u'2.7.1'}, mechanisms: [u'PLAIN', u'AMQPLAIN'], locales: [u'en_US'] from (pid=16943) _start /usr/local/lib/python2.7/dist-packages/amqp/connection.py:706
2013-09-20 23:34:55.720 DEBUG amqp [-] Open OK! from (pid=16943) _open_ok /usr/local/lib/python2.7/dist-packages/amqp/connection.py:592
2013-09-20 23:34:55.720 DEBUG amqp [-] using channel_id: 1 from (pid=16943) __init__ /usr/local/lib/python2.7/dist-packages/amqp/channel.py:70
2013-09-20 23:34:55.723 DEBUG amqp [-] Channel open from (pid=16943) _open_ok /usr/local/lib/python2.7/dist-packages/amqp/channel.py:420
2013-09-20 23:34:55.724 INFO cinder.openstack.common.rpc.common [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Connected to AMQP server on localhost:5672
2013-09-20 23:34:55.725 DEBUG cinder.service [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Creating Consumer connection for Service cinder-backup from (pid=16943) start /opt/stack/cinder/cinder/service.py:371
2013-09-20 23:34:55.742 INFO cinder.backup.manager [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Starting volume driver LVMISCSIDriver (2.0.0)
2013-09-20 23:34:55.744 DEBUG cinder.openstack.common.processutils [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name from (pid=16943) execute /opt/stack/cinder/cinder/openstack/common/processutils.py:142
2013-09-20 23:34:56.369 ERROR cinder.brick.local_dev.lvm [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Unable to locate Volume Group cinder-volumes
2013-09-20 23:34:56.373 ERROR cinder.backup.manager [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Error encountered during initialization of driver: LVMISCSIDriver
2013-09-20 23:34:56.374 ERROR cinder.backup.manager [req-edd476a4-9de2-435f-9ae1-c7562bf3b2a6 None None] Bad or unexpected response from the storage volume backend API: Volume Group cinder-volumes does not exist
2013-09-20 23:34:56.374 TRACE cinder.backup.manager Traceback (most recent call last):
2013-09-20 23:34:56.374 TRACE cinder.backup.manager File "/opt/stack/cinder/cinder/backup/manager.py", line 104, in init_host
2013-09-20 23:34:56.374 TRACE cinder.backup.manager self.driver.check_for_setup_error()
2013-09-20 23:34:56.374 TRACE cinder.backup.manager File "/opt/stack/cinder/cinder/volume/drivers/lvm.py", line 95, in check_for_setup_error
2013-09-20 23:34:56.374 TRACE cinder.backup.manager raise exception.VolumeBackendAPIException(data=message)
2013-09-20 23:34:56.374 TRACE cinder.backup.manager VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Volume Group cinder-volumes does not exist
2013-09-20 23:34:56.374 TRACE cinder.backup.manager