This message was deleted.
# harvestera
adamant-kite-43734
12/06/2022, 9:46 PMThis message was deleted.
s
salmon-city-57654
12/07/2022, 2:45 PMHi @quaint-alarm-7893,
Did you mean you could not see the NFS backup target on the restore side? If yes, you could simply remove/add backup target again to trigger re-scan.
q
quaint-alarm-7893
12/07/2022, 10:22 PM@salmon-city-57654 yes, kinda. in v1.0.3 it wont let me delete / re-add. but it's okay, i just had to wait for it to show up. i was more wondering if there's a pod i could kill that makes it re-scan when it re-launches or something. #impatient 🙂
s
salmon-city-57654
12/08/2022, 3:13 AMHi @quaint-alarm-7893,
Could you try to
edit-configUse the default valuesalmon-city-57654
12/08/2022, 3:19 PM@quaint-alarm-7893, could I clarify this question again?
Do you mean that the backup sync is slow as this issue (https://github.com/harvester/harvester/issues/3253)?
Or do you mean that you can not see the backup target on the restore side?
q
quaint-alarm-7893
12/08/2022, 4:52 PM@salmon-city-57654 my specific case is with two clusters, backup on cluster a, then restore on cluster b.
if both clusters have the same NFS target already established, it takes a good while for cluster b to see a newly created backup that was made on cluster a.
quaint-alarm-7893
12/08/2022, 4:52 PMthat's what i think they mean by backup sync. how long it takes for one cluster to see backups made by another cluster.
s
salmon-city-57654
12/12/2022, 4:59 PMAh, how do we know the backup is completed? That’s what you need to know, right?
29 Views