This message was deleted.
# nebulas
Slackbot
09/26/2022, 11:48 AMThis message was deleted.
m
Munichandra Nageti
09/28/2022, 7:04 PMHi @wey, Can you please take a look at this issue, Thanks.
w
wey
09/29/2022, 1:27 AMDid you only do snapshot restore actions for storage? Snapshot for Meta data is still needed, too.
Copy code
usr/local/nebula/data/metam
Munichandra Nageti
09/29/2022, 5:42 AMYes, I did snapshot restoration for both meta and storage. I have copied the snapshot metadata to the actual metadata directory before restarting the services.
Copy code
ubuntu@my_host_2:/usr/local/nebula/data/meta/nebula/0/checkpoints/SNAPSHOT_2022_09_26_10_59_29$ sudo cp -r data/ wal/ ../../
cp: 'data/OPTIONS-000013' and '../../data/OPTIONS-000013' are the same file
cp: 'data/000009.sst' and '../../data/000009.sst' are the same file
cp: 'data/000015.sst' and '../../data/000015.sst' are the same file
cp: 'data/000017.sst' and '../../data/000017.sst' are the same file
cp: 'wal/0/0000000000000299579.wal' and '../../wal/0/0000000000000299579.wal' are the same file
cp: 'wal/0/0000000000000242239.wal' and '../../wal/0/0000000000000242239.wal' are the same fileu
青藤木鸟
09/29/2022, 9:50 AMthe metad should also be restored. Could refer: https://docs.nebula-graph.io/3.2.1/backup-and-restore/3.manage-snapshot/#restore_data_with_snapshots
m
Munichandra Nageti
09/29/2022, 10:48 AMYes, I did followed this steps only and tried restoring both meta and storage, but it's not working as expected
u
青藤木鸟
09/29/2022, 10:59 AMThere are some problems about your restore procedure:
1. you should first stop all services.
青藤木鸟
09/29/2022, 10:59 AM2. you should del the old wal and data, then copy the ones in checkpoints folder
❤️ 1
青藤木鸟
09/29/2022, 11:01 AM3. after created snapshot, you should move all the checkpoints data from the original place to some where your backup folder. For if you drop the space, the checkpoints will be dropped either.
m
Munichandra Nageti
09/29/2022, 11:05 AMokay, Thanks. let me try that
Munichandra Nageti
09/29/2022, 3:13 PMI have followed the above steps and copied the snapshot data to the actual location and restarted the services, but now the
metadE20220929 14:40:58.028486 39193 MetaDaemon.cpp:182] Parser God Role error:E_LEADER_CHANGEDu
阳子
09/30/2022, 4:31 PMThere's an annoying thing : Daemon can not read god user status so that it exits if leader change happend . This has been fixed in 3.3 version. But it only gives some retry times. If leader change still exist, then it should still exit. The best way to start meta is to fix leader change.
阳子
09/30/2022, 4:33 PMTry start meta in different order may help, else you have to try to compile a daemon to fix this.
❤️ 1
m
Munichandra Nageti
10/06/2022, 12:42 PMThanks. Tried starting the metad in different orders , but that didn't help
Munichandra Nageti
10/06/2022, 12:44 PMDo you have any instructions to compile a metad daemon ?
7 Views