Azure备份-KB3119587-新的脱机策略 [英] Azure Backup - KB3119587 - New Offline Policy

查看:53
本文介绍了Azure备份-KB3119587-新的脱机策略的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是Azure的新手,希望有人能够为离线种子作业提供一些清晰度,让他们无法等待作业完成.

我遵循了Azure备份中脱机备份工作流中包含的文档.初始暂存位置是连接到VM的外部驱动器.完成后,将外部驱动器转移到运输驱动器所在的其他物理服务器上 准备没有问题.该驱动器已发送到Azure,已导入,并且看起来一切都很好,除了工作卡住了.

进一步(KB3119587),原始名称与导入作业名称不匹配.我删除了第一个脱机备份策略,并尝试按照知识库文章中的建议设置新的脱机备份策略,Azure通知我备份已删除. 在设置新策略时,要求提供暂存位置(首先是外部驱动器).这是我不清楚的地方.我是否需要再次重新运行该过程以更正此错误?如果是这样,请删除Azure存储Blob和 重新开始?完全不清楚.....

如果有人可以为此问题提供一些指导,我将不胜感激!!  

解决方案

是.   您将必须删除存储Blob并重新开始.

如果旧的脱机备份策略未删除,我们可以提供一种解决方法以使该过程进一步进行而无需 重新做整个流程

参考 Azure备份中的脱机备份工作流.

-------------- -------------------------------------------------- ----------------------------------

如果此答案有帮助,点击"标记为答案"或 投票.要提供有关您的论坛体验的其他反馈,请单击 在这里


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!!  

解决方案

Yes.  You would have to delete the Storage Blobs and start over.

If the old offline backup policy was not deleted, we could have given a workaround to make the process happen further without re-doing the entire flow

Refer Offline- backup workflow in Azure backup.

--------------------------------------------------------------------------------------------------

If this answer was helpful, click "Mark as Answer" or Up-Vote. To provide additional feedback on your forum experience, click here


这篇关于Azure备份-KB3119587-新的脱机策略的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆