从谷歌云到Azure的azcopy刚刚挂起



我正在尝试使用azcopy从谷歌云复制到Azure。我在这里遵循说明,我可以在生成的日志中看到,与GCP的连接似乎很好,SAS令牌很好,它创建容器也很好(请参阅它出现在Azure Storage Explorer中),但它只是挂起。输出为:

INFO: Scanning...
INFO: Authenticating to source using GoogleAppCredentials
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

如果我查看日志,它显示:

2022/06/01 07:43:25 AzcopyVersion  10.15.0
2022/06/01 07:43:25 OS-Environment  windows
2022/06/01 07:43:25 OS-Architecture  amd64
2022/06/01 07:43:25 Log times are in UTC. Local time is 1 Jun 2022 08:43:25
2022/06/01 07:43:25 ISO 8601 START TIME: to copy files that changed before or after this job started, use the parameter --include-before=2022-06-01T07:43:20Z or --include-after=2022-06-01T07:43:20Z
2022/06/01 07:43:25 Authenticating to source using GoogleAppCredentials
2022/06/01 07:43:26 Any empty folders will not be processed, because source and/or destination doesn't have full folder support

正如我所说,SAS令牌没有过期的错误,或者找不到GCP凭据,或者诸如此类的错误。它只是挂着。如果我尝试复制单个命名文件或递归目录副本,它就会执行此操作。任何东西

有什么想法吗?

•我建议您查看这些AzCopy事务的日志,以了解有关此场景的更多详细信息。CCD_ 1。AzCopy为每个作业创建日志和计划文件,因此您必须通过分析这些文件来调查和解决与此场景有关的任何潜在问题。

•由于您在传输文件的作业执行过程中遇到AzCopy实用程序的挂起问题,这可能是网络波动问题、超时问题或服务器繁忙问题。请记住AzCopy retries upto 20 times in these cases and usually the retry process succeeds。尝试在日志中查找'UPLOADFAILED'、COPYFAILED'或DOWNLOADFAILED'附近的错误

•以下命令将从相关日志文件中获取"UPLOADFAILED">状态的所有错误:-

Select-String UPLOADFAILED .<CONCERNEDLOGFILE GUID>.log

要按与作业ID相关的状态显示作业,请执行以下命令:-

azcopy jobs show <job-id> --with-status=Failed

•使用"--no check certificate'参数从本地系统执行AzCopy作业执行命令,这将确保在接收端没有针对系统证书的证书检查。确保root certificates for the network client device or software are correctly installed on your local system as they are the only ones to block your jobs while transferring files from on-premises to Azure

此外,once the job starts initially without any parameters, then when it hangs, just press CTRL+C to kill the process and then immediately check the logs in AzCopy as well as in the event viewer for any system issues. It will help you know the exact issue regarding this. It really shows why the process failed and got hung

有关更多信息,请参阅下面的文档链接:-

https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-configure

https://github.com/Azure/azure-storage-azcopy/issues/517

令人沮丧的是,在与微软支持部门进行了多次通话后,将之前失败的具有完全相同SAS令牌等的完全相同的命令演示给另一个人时,才开始工作。我讨厌"自我修复"的问题,因为这意味着它很可能会再次发生。

感谢KartikBhiwapurkar MT的详细回复。

相关内容

  • 没有找到相关文章

最新更新