We are focusing on cindernative at the moment.

Regarding your issue with Ceph backend for cinder-backup, I wanna try to propose solution for it in coming days.

On Thu, 21 Aug 2025, 08:40 Nguyễn Hữu Khôi, <nguyenhuukhoinw@gmail.com> wrote:
Hi,

I have changed to swift as the backend for cinder backup, Everything works as I expect, Could you share with me which kind of backup in your pre prod system, cinder or cindernative?

Nguyen Huu Khoi


On Wed, Aug 20, 2025 at 11:28 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Sorry, I have read your email and I missed it. I will try with swift rgw as cinder backup backed.

Nguyen Huu Khoi

On Wed, Aug 20, 2025, 11:16 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Ah, Did u use s3 for cinder backup backend or ceph? I use ceph as backup backend.

Nguyen Huu Khoi

On Wed, Aug 20, 2025, 11:05 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
I changed to Swift with Ceph RGW but still encountering above errors:



Nguyen Huu Khoi


On Wed, Aug 20, 2025 at 3:03 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Yes,
I am using CephBackupDriver and backup pool on Ceph is "backups". I am passing --container because It required for s3 and ssh storage, I don't have Swift for testing. Will we resolve it in the future? I can do some tests on this project to make it work nicely.
Nguyen Huu Khoi


On Wed, Aug 20, 2025 at 2:46 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
Am I right to assume that you are using CephBackupDriver as a backup driver for Cinder?

What pool are you using for backups? Or better say - can you try passing `--container <pool-name>` as an argument to freezer? As it seems that the passed container is treated by cinder-backup as a target pool, which is kinda wrong.
I also frankly tested only with Swift backend (implemented through Rados RGW) for cinder-backup so far. But it's good to ensure all cases are working properly for sure.

ср, 20 авг. 2025 г. в 09:29, Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com>:
I have checked the cinder-backup and I can back up my volume but I don't know why I cannot go with cindernative. I change to 

freezer-agent   --mode cindernative  --cindernative-vol-id  fcc22b9f-ef01-4d16-bfde-83af6312bce9  --log-file k.log --debug --storage s3 --container freezer-container --noincremental

backup can create but I see in cinder-backup log:




I changed to --storage ssh and this still happens, I see that cinder-backup was created but with errors. I have attached logs.




Nguyen Huu Khoi


On Wed, Aug 20, 2025 at 1:51 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
cindernative driver does leverage cinder-backup component to create backups. Usually, when this error occurs, it means that cinder-backup is misconfigured.

For instance, default backup driver for Cinder is set to Swift in many cases, though you are likely not having the expected service type in your endpoints catalog, or, region for cinder-backup to look for Swift/RGW backend is set incorrectly.

ср, 20 авг. 2025 г. в 05:31, Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com>:
Hello.

I am using openstack 2025.1 and freezer 2025.1 to test. I can backup and restore using cinder.
but I won't do it with cindernative, could you tell me that we need swiff to use this mode? This is my command:

freezer-agent   --mode cindernative  --cindernative-vol-id  fcc22b9f-ef01-4d16-bfde-83af6312bce9  --log-file k.log --debug

Critical Error: Endpoint for object-store not found - have you specified a region? 

Thank much.

Nguyen Huu Khoi