Hi Lisa, We have already completed the effort to enable upstream cinder backup and replace the current functionality provided by the custom backup API. Cinder backup service will be started along with the other Cinder services when Cinder is enabled. I anticipate we’ll deliver this functionality in the coming weeks. Once delivered, we’ll still need to retire the custom API code for volume import and volume/snapshot export to align with upstream. We will then be in a position to look at expanding support for backing up to other storage backends. Regards, Bob From: "Li, Xiaoyan" <xiaoyan.li@intel.com> Date: Tuesday, July 24, 2018 at 2:18 AM To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Replace WR backup with Cinder upstream backup Hi all, Currently in StarlingX, it uses WR backup to backup volumes into local folders. On the other side, Cinder provides its own backup service to backup volumes to kinds of backend storages, including local folders, Ceph etc. This is already in Pike release. I am going to replace WR backup with Cinder upstream backup service, and it provides more choice to do backup. To do the change, except work in StarlingX/Cinder, it also needs update in the component std-config. In Cinder upstream, backup service is a standalone service. And in WR backup, it is in volume service. As a result, we need to allow admins to enable/start backup service when installing StarlingX. This needs to be update in std-config. Anyone is working on std-config? Best wishes Lisa