Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
m
mysterious-rose-43856
12/15/2022, 4:24 PMSo I came into Longhorn 1.3.2 and a faulted DR volume. This happens often enough, so I delete it and setup a new DR volume. It created and attached the volume right away, but has not started the restore process itself for 10+ minutes at this point.
I have tried to restore the same volume as just "restore latest backup" and it seems to be doing the same thing.
Okay, so they EVENTUALLY started. The DR faulted during the restore, seemed to happen when a new backup was ready (meaning the "Last Backup at" incremented, then the volume faulted)
I'm re-doing some of this and see the same large lag on the start of the restore.
20+ min now and it hasn't started the actual restore
a
aloof-hair-13897
12/16/2022, 12:42 AMHi, Would you like to provide the support bundle for us to investigate what happened?
Do you use two cluster or one cluster to make this DR volume?
Any abnormal log related to this DR volume or backup volume?