Team foundation server reports not updating
Transactions created after the most recent transaction mark will be lost when the data is restored.TFS relies on these transaction marks to keep the databases synchronized.If you perform a typical SQL Server backup, the resulting files will be missing the transaction marks on the various tables. Companies often fail to realize that the backups are not working because they do not test the recovery process.Consequently, TFS is unable to verify that the records are logically consistent when the backups are restored. The team only notices the problem when they are forced to recover from an actual failure.
When the database is restored, the marks ensure the data is consistent to the same moment in time.If you’ve ever tried to backup a Team Foundation Server by hand, you have can appreciate not having to do that task in Visual Studio Team Services (VSTS).Unfortunately, there are often compelling reasons to keep some your servers on-premise.If you are doing the backups manually, follow those steps to ensure the databases can be recovered.If you’re running TFS 2012 or better, there is a built-in wizard which automates the backup process and creates a recoverable archive of your entire system.
Search for team foundation server reports not updating:
This would include a weekly full backup and daily differential backups.