I’m new to Azure and hoping that someone can provide some clarity to the offline seeding job being stuck at waiting for job to complete.
I followed the documentation contained in the offline-backup workflow in Azure backup. The initial staging location was an external drive connected to VM. Once completed, the external drive was taken to a different physical server where the shipping drive
was prepared without issue. The drive was sent to Azure, imported and looked like all was good except for the job being stuck.
Looking further (KB3119587) the original name doesn’t match the import job name. I deleted the first offline backup policy and I’m attempting to setup a new offline backup policy as suggested in the KB article, and Azure informed me the backup had been deleted.
In setting up the new policy it’s asking for the staging location which was the external drive to begin with. This is where it becomes unclear to me. Am I going to have re-run the process again to correct this? And if so, delete the Azure storage blob and
start completely over? Completely unclear…..
I’d be greatly appreciative if someone could please provide some guidance with this issue!!