我的 TFS2010 备份/恢复是否已完成？
我最近设置了一个沙箱 TFS 来测试 TFS 特定的功能，而不干扰生产 TFS。我很高兴我比我想象的更早完成了这件事——我没有从 SSRS 备份加密密钥，并且在恢复报告数据库时，它们仍然处于非活动状态，需要只能通过应用加密密钥来进行初始化。当我备份 TFS 数据库后删除分区时，所述加密密钥丢失了。
我似乎唯一的选择就是删除加密数据。我对此很满意，因为一开始就没有太多内容，但是一旦删除它们，我不太确定如何配置 TFS 以识别这些服务的新安装，同时使用所有内容的恢复版本别的。不幸的是，TFS 帮助文件似乎没有解释这种状态。有没有办法从根本上重建报告和分析数据库？或者他们已经永远消失了？
I recently set up a sandbox TFS to test TFS-specific features without interfering with the production TFS. I was happy I did this sooner than I thought--I hadn't been backing up the encryption key from SSRS and upon restoring the reporting databases, they remained inactive, requiring initialization that could only come from applying the encryption key. Said encryption key was lost when I nuked the partition after backing up the TFS databases.
The only option I seemed to have is to delete the encrypted data. I'm fine with this, since there wasn't much in there to begin with, however once they're deleted I'm not quite sure how to configure TFS to recognize a new installation of these services while using the restored versions of everything else. Unfortunately, the TFS help file doesn't seem to account for this state though. Is there a way to essentially rebuild the reporting and analysis databases? Or are they gone forever?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您是否尝试过从 TFS 管理控制台进入应用程序层下方的报告部分？有一个“开始重建”选项，它应该根据 TFS 数据库中当前的内容重建您的仓库、模型和报告。
如果这不起作用，您可以随时尝试停止作业，删除数据库，然后重新启动作业。我相信届时它将从头开始重建它们。我只启动并运行了 2010 年生产实例，不再是开发平台，否则我会为您测试一下。
From the TFS Admin console, have you tried going into your Reporting section underneath the Application Tier? There is an option for "Start Rebuild", which should rebuild your warehouse, models, and reports based upon what is currently in the TFS database(s).
If that does not work, you could always try stopping the jobs, deleting the databases and then starting the jobs back up. I believe that it will rebuild them from scratch at that point. I only have my production 2010 instance up and running, and not a development rig anymore, otherwise I would test this for you.