BR version: v3.7.1
Nebula version: 3.8
Host: Ubuntu 22.04 dedicated host (standalone)
From the logs it seems br restore failed to stop storage or get storage status on standalone nebula. I would assume BR used these commands.
/usr/local/nebula/scripts/nebula.service stop all
/usr/local/nebula/scripts/nebula.service status all
Would it be possible BR used these commands instead? These would get errors since /usr/local/nebula/bin/nebula-storaged doesn't exist on a standalone nebula.
/usr/local/nebula/scripts/nebula.service stop storaged
/usr/local/nebula/scripts/nebula.service status storaged
root@nebulagraph:/home/ubuntu# /usr/local/nebula/bin/br restore full --meta "Host IP:9559" --storage "local://Backup directory" --name BACKUP_2025_04_28_10_47_36
{"level":"info","meta address":"Host IP:9559","msg":"Try to connect meta service.","time":"2025-04-28T14:00:24.118Z"}
{"level":"info","meta address":"Host IP:9559","msg":"Connect meta server successfully.","time":"2025-04-28T14:00:24.120Z"}
{"level":"info","meta address":"Host IP:9559","msg":"Try to connect meta service.","time":"2025-04-28T14:00:24.120Z"}
{"level":"info","meta address":"Host IP:9559","msg":"Connect meta server successfully.","time":"2025-04-28T14:00:24.120Z"}
{"host info":"map[Host IP:Host IP:9779[STORAGE]: (data: /var/lib/nebula, root: /usr/local/nebula) | Host IP:8888[AGENT]: (data: , root: ) | Host IP:9669[GRAPH]: (data: , root: /usr/local/nebula) | Host IP:9559[META]: (data: /usr/local/nebula/data/meta, root: /usr/local/nebula)]","level":"info","msg":"Get cluster topology from the nebula.","time":"2025-04-28T14:00:24.121Z"}
{"backup":"BACKUP_2025_04_28_10_47_36","level":"info","msg":"Check backup dir successfully.","time":"2025-04-28T14:00:24.123Z","uri":"local://Backup directory/BACKUP_2025_04_28_10_47_36"}
{"dir":"/usr/local/nebula","host":"Host IP","level":"info","msg":"Stop services.","role":"STORAGE","time":"2025-04-28T14:00:24.132Z"}
{"error":"get service status in host Host IP failed: agent, get service status failed: rpc error: code = Unknown desc = get STORAGE status by daemon failed: exit status 1","level":"info","msg":"Get dead services failed, try times=1.","time":"2025-04-28T14:00:24.165Z"}
{"error":"get service status in host Host IP failed: agent, get service status failed: rpc error: code = Unknown desc = get STORAGE status by daemon failed: exit status 1","level":"info","msg":"Get dead services failed, try times=2.","time":"2025-04-28T14:00:25.179Z"}
{"error":"get service status in host Host IP failed: agent, get service status failed: rpc error: code = Unknown desc = get STORAGE status by daemon failed: exit status 1","level":"info","msg":"Get dead services failed, try times=3.","time":"2025-04-28T14:00:27.193Z"}
Fix failed when restore failed get service status in host Host IP failed: agent, get service status failed: rpc error: code = Unknown desc = get STORAGE status by daemon failed: exit status 1
Error: stop cluster failed: stop services in host Host IP failed: agent, stop service failed: rpc error: code = Unknown desc = exit status 1
General Question
Does BR restore work with standalone nebula?
From the logs it seems br restore failed to stop storage or get storage status on standalone nebula. I would assume BR used these commands.
Would it be possible BR used these commands instead? These would get errors since /usr/local/nebula/bin/nebula-storaged doesn't exist on a standalone nebula.
Here are the logs: