解决了

VSS失败在Veeam上

  • 2015年12月5日
  • 7个答复
  • 1715次观点
d
徽章 +5
大家好，

我想知道是否有人对如何获得Veeam和Nutanix的成功备份有任何见解，如果我有些东西忽略了。我知道我过于简单，但是我遵循了最佳实践设置，并已经检查了所有设置两次，但我仍然会遇到以下错误：

12/5/2015 1:30:11 pm ::无法分配处理资源。Error: Provider [{89300202-3cec-4981-9171-19f59559e0f2}] does not support shadow copies of volume [\LSSHARE01LIFE_NTNX01].--tr:Failed to add volumes to the snapshot set.--tr:Failed to perform pre-备份任务。

我可以发誓，如果将NOS添加到AD中，那么共享可以使用VSS。坦率地说，我找不到有关此信息的任何信息，而是从日志，帐户到验证存储空间。任何见解都将不胜感激。
图标

最好的答案普拉卡什2015年12月8日，00：53

\n
\nAs we expected, the ncc Kerberos check indeed showed Kerberos authentication failure.
\n
\nThe computer object representing the NOS cluster was indeed present in their AD. It's likely that the group policy configured for the OU had some password-specific setting that caused authentication to fail.
\n
\nAs a resolution we unjoined the NOS cluster from AD using the hidden ncli command. Then we tried joining the NOS cluster back to their AD using the GUI. But this step failed saying \"the server cannot handle directory requests\". Since we were not sure why this message is showing up and since we wanted to get the customer quickly take backups of their production VMs using Veeam, we resorted to a 2-step cli process.
\n
\n(1) First we created a computer object in AD using the New-NosClusterComputer Powershell command.
\n(2) Then we used hidden ncli cluster join-cluster-no-ad to configure the passord in NOS.
\n
\nThen after clearing the (stale, cached) Kerberos tickets, diskshadow started working.
\n
\nThe customer restarted the Veeam job that was earlier failing and the job now succeeds.","className":"post__content__best_answer"}">
查看原件
\n
\nI am wondering if anyone had any insights on how to get a succesful backup with veeam and nutanix and if there is something I am just overlooking. I know I am oversimplifying but I have followed the best practices setup and have checked all of the settings twice but somehow I still get the following error:
\n
\n12\/5\/2015 1:30:11 PM :: Unable to allocate processing resources. Error: Provider [{89300202-3cec-4981-9171-19f59559e0f2}] does not support shadow copies of volume [\\LSSHARE01LIFE_NTNX01].--tr:Failed to add volumes to the snapshot set.--tr:Failed to perform pre-backup tasks.
\n
\nI could have sworn that if NOS is added to AD then the share can use the VSS. I am frankly not finding any information on this and have gone from logs, to accounts, to verifying the storage. Any insights would be greatly appreciated.","quoteUsername":"dmendez","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

7个答复

p
秩
徽章 +2
你好，

如果VSS备份工作较早工作并突然停止工作，可能会发生一些事情：
（1）Nutanix群集的CVM中的时间可能已经与广告的同步脱离，从而导致Kerberos身份验证失败。
（2）代表AD/DC中代表Nutanix群集的计算机对象可能已被删除或禁用，或者如果已重置密码。

如果您正在运行NOS 4.5，则运行NCC将很快将您指向问题。即使您正在运行较旧的NOS版本，请运行NCC。

您也可以尝试使用群集中任何主机的DiskShadow来隔离问题。
\n
\nIf VSS backups were working properly earlier and had suddenly stopped working, couple of things could have happened:
\n(1) The time in the CVMs of the Nutanix cluster could have gone out of sync with the AD causing Kerberos authentication to fail.
\n(2) The computer object representing the Nutanix cluster in AD\/DC could have gotten deleted or disabled or could have had it's password reset.
\n
\nIf you are running NOS 4.5, running ncc will quickly point you to the problem. Even if you are running a older NOS release, please run ncc.
\n
\nYou can also try using diskshadow from any of the hosts in the cluster to isolate the problem.","quoteUsername":"Prakash","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +5
嗨

我将调查这些建议。问题在于，这并不是我们的理解。我确实运行了健康检查，并且确实显示了NOS群集计算机对象未在Active Directory中配置。我检查了CLSUTER帐户，并且在广告和主机上都在那里。

我已经看到了运行Hyper V主机脚本以检查是否需要将其读取到广告中的建议他们在星期一之前倒下。感谢到目前为止的建议。
\n
\nI will look into the suggestions. The problem is that this has not worked from our understanding. I did run the health check and it did show up that NOS Cluster computer object is not configured in Active Directory. I checked the clsuter account and it was there on AD as well as the hosts.
\n
\nI have seen suggestions to run the hyper v host script to check if they need to be readded into AD but I fear that this might convolut things, not to mention that it will require a reboot and frankly these are in production and would hate to bring them down before the monday. Thanks for the suggestions so far.","quoteUsername":"dmendez","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
p
秩
徽章 +2
你好

结合NOS群集的域不应重新启动任何群集组件。因此，如果您需要帮助，请用Nutanix提交支持票，我们将帮助备份。
\n
\nDomain-joining the NOS cluster should not require reboot of any of the cluster components. So if you need help with this, please file a support ticket with Nutanix and we'll help to get the backups going.","quoteUsername":"Prakash","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
p
秩
徽章 +2
帮助使用Veeam备份。

正如我们预期的那样，NCC Kerberos检查确实显示了Kerberos身份验证失败。

代表NOS群集的计算机对象确实存在于其广告中。为OU配置的组策略可能具有某些特定于密码的设置，导致身份验证失败。

作为一个分辨率，我们使用隐藏的NCLI命令从AD上脱离了NOS群集。然后，我们尝试使用GUI将NOS群集加入他们的广告。但是此步骤失败了说“服务器无法处理目录请求”。由于我们不确定为什么会出现此消息，并且由于我们希望使用Veeam快速获得其生产VM的备份，因此我们求助于2步CLI流程。

（1）首先，我们使用new-nosClusterComputer PowerShell命令在AD中创建了一个计算机对象。
（2）然后，我们使用了隐藏的NCLI群集JOIN-CLUSTER-NO-NO-AD来配置NOS中的Passord。

然后清理了（陈旧的，缓存）Kerberos的门票后，Diskshadow开始工作。

客户重新启动了较早失败的Veeam作业，现在该工作成功了。
\n
\nAs we expected, the ncc Kerberos check indeed showed Kerberos authentication failure.
\n
\nThe computer object representing the NOS cluster was indeed present in their AD. It's likely that the group policy configured for the OU had some password-specific setting that caused authentication to fail.
\n
\nAs a resolution we unjoined the NOS cluster from AD using the hidden ncli command. Then we tried joining the NOS cluster back to their AD using the GUI. But this step failed saying \"the server cannot handle directory requests\". Since we were not sure why this message is showing up and since we wanted to get the customer quickly take backups of their production VMs using Veeam, we resorted to a 2-step cli process.
\n
\n(1) First we created a computer object in AD using the New-NosClusterComputer Powershell command.
\n(2) Then we used hidden ncli cluster join-cluster-no-ad to configure the passord in NOS.
\n
\nThen after clearing the (stale, cached) Kerberos tickets, diskshadow started working.
\n
\nThe customer restarted the Veeam job that was earlier failing and the job now succeeds.","quoteUsername":"Prakash","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +5
是的。这确实是问题。感谢您今天的所有帮助。很高兴备份现在正常工作。
d
徽章 +1
你好

我也有Veeam 9，NOS和Hyper-V 2012 R2的问题。

对于某些VM（安装了数据库引擎的VM），备份失败了。

异步操作错误的未知状态在尝试处理指定的操作时，影子复制提供商出现了出乎意料的错误。错误-tr：无法创建VSS快照。错误 - tr：无法执行前回复任务。（System.Exception）

我已经审查并尝试了所有Veeam KB，还遵循了Nutanix，Veeam和Hyper-V的最佳实践文件。每个主机都安装了Hyper-V VSS作者。

备份作业没有配置为使用VSS，但仍尝试执行此操作。

感谢任何反馈/想法

谢谢
\n
\nI'm having also a issue with Veeam 9, NOS and Hyper-V 2012 R2.
\n
\nFor some VMs (those that have a database engine installed) the backup fails with the message
\n
\nUnknown status of async operation Error The shadow copy provider had an unexpected error while trying to process the specified operation. Error --tr:Failed to create VSS snapshot. Error --tr:Failed to perform pre-backup tasks. (System.Exception)
\n
\nI had reviewed and tried every Veeam KB and also followed the Best Practices document for Nutanix,Veeam and Hyper-V. Each host has the Hyper-V VSS Writer installed.
\n
\nBackups jobs are not configured to use VSS, but still try to do it.
\n
\nWe appreciate any feedback\/idea
\n
\nThanks","quoteUsername":"davosplatz","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +1
你好：

好吧，感谢Nutanix支持该问题。Nutanix在SMB 3.0共享中支持不超过1,000个文件，并且客户忘了提到他们在那里的“一些”文件与VHDX共享空间。好吧，该份额中大约有153,000个文件，因此一旦客户将其移出，备份就成功完成了。

谢谢。
\n
\nWell, thanks to Nutanix Support the issue was solved. No more than 1,000 files are supported by Nutanix in a SMB 3.0 share and the customer forgot to mention that they have \"some\" files there sharing space with the VHDX. Well, there were roughly 153,000 files in that share, so once the customer moved them out, the backup completed successfully.
\n
\nThanks.","quoteUsername":"davosplatz","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu