I have TFS backup job hangs for several hours without any errors.
I have tried Restart of SQL server.
On the monitoring page of TFS it looks ok without any errors.
TFS 2018.1
SQL SERVER 2016 STD
Windows Server 2012 R2
Backup was working good as scheduled for almost 1 year.
Related
So I'm upgrading a TFS 2018.3 on premises deployment to the new Azure DevOps Server 2019. After I installed the new server when I get to the screen to select SQL Server instance/DB I get the above error. After that the config wizard stalls completely and I have to kill it from Task Manager.
The Application Layer is on a Windows Server 2012 R2 server, fully patched.
The DB layer is on Windows Server 2012 R2, SQL 2017 (14.0.2002.14).
Nothing useful in the Event Log or the the upgrade logs.
Does anyone experienced this problem or has an idea for a workaround?
Turns out the server wasn't upgraded to TFS 2018.3 and this was causing problems. After upgrading to the latest TFS 2018 the update worked.
We are trying to upgrade our TFS 2013 Update 5 to TFS 2018 Update 2. I have checked this thread to make sure we meet the prerequisites.
From the list, it looks like we met the prerequisites, but when i run the TFS2018 installer it gives me an error saying there is no direct upgrade path from 2013 to 2018. Im not sure why we are getting this error when i looked at the Microsoft site, there is a direct upgrade from TFS2013 update 5 to TFS2018. What am i missing?
Here are our specs on our TFS 2013:
SQL: SQL Server 2016 SP2
OS: Windows Server 2012 R2
TFS: TFS 2013 Update5
P.S. we moved the databases to a SQL server 2016 from a 2014 SQL just to comply with the prerequisites.
Ahh yes, the added error message makes sense. What the TFS installer is telling you is that it can't perform the upgrade while TFS 2013 is installed and running on that server.
You first have to uninstall the Application Tier and Build Services on the machine. This doesn't impact your databases in any way.
Then you can install TFS 2018.2 or 3 directly into that server, point it to the existing SQL databases and it will ask you whether you want to upgrade those.
You'll need to verify a few server settings, plus decide whether you want to enable SSH and Search on this machine.
After the integrity check the installer will install the TFS Application tier and start the database upgrade process.
Only of you're on TFS 2005 or 20008 do you need to perform this step multiple times. first with the 2010 installer before you can take it to 2018. This is what's meant by 'not possible to do a direct upgrade' in some parts of the docs and which confused me at first.
When upgrading TFS 2015.1 to TFS 2017.2 do I leave SQL Server 2014 Always On turned on? We have TFS 2015.1 running on SQL Server 2014 with Always on and everything is working fine. Upgrading to TFS 2017.2 and assume I just leave the database server as is. Can I upgrade TFS with Always on running?
Thanks
If you leave TFS pointed at the AG, you need to make sure you have enough space for potential log file growth because the database will be left in FULL recovery mode. TFS does warn you about this during the upgrade.
If you disable the AG and point TFS at a single node, it will upgrade in Simple recovery mode, and you will need to resetup the AG after the upgrade.
Depending on how big your TFS Collection databases are and the amount of free space you have for your logs (and maybe the data files too) depends which you need.
2 days ago I did the following test upgrade from TFS 2005 to 2010 then to 2012 (I am not configuring Reporting or Sharepoint)
Backed up the 6 TFs 2005 databases
Restored them on the Sql 2008 server used by TFS 2010
Ran TFSconfig setup uninstall:ALL on the TFS 2010 application server (as I had a test site setup)
Opened the TFS 2010 admin window and did an upgrade
Detached my TFS2010 collection and did an import process to TFS2012
Yesterday, I wanted to try the process again to make sure that I had all the steps down.
So I did some initial cleanup
Deleted all the databases on the TFS 2010 Sql server
Detached the test collection on TFS 2012 and then delete the associated database
and then I restarted the steps but it gets stuck at step #4
Backed up the 6 TFs 2005 databases
Restored them on the Sql 2008 server used by TFS 2010
Ran TFSconfig setup uninstall:ALL on the TFS 2010 application server
Opened the TFS 2010 admin window and did an upgrade
The error I get on step #4 is
TF254024: No database for Team Foundation Serer that can be upgraded were found on the following instance... Verify that you specified the correct name of the server and the instance.
I've double checked the name of the server & instance.
Made sure that the account that is running the upgrade has full permissions.
I'm not sure what else to do. My searching hasn't proved that fruitful.
I figured out the issue.
When I was testing out the deploy the first time, we were trying to do a migration instead of an upgrade. We had added 2 extended properties to the master table from the TFSIntegration database (based on another error).
I removed both those extended properties and I was able to start the upgrade.
edit 1-
I tried the process again (restore database and try to do the upgrade). The extented properties were back again.
so running this script fixed the process.
USE TfsIntegration;
GO
EXEC sp_dropextendedproperty
#name = N'TFS_DATABASE_CATEGORIES';
GO
EXEC sp_dropextendedproperty
#name = N'TFS_INSTANCE';
GO
I have TFS 2015 in Windows server 2008r2, for the disaster recovery and some precautions I would like to do the existing TFS backup and restoring them to another server, what is the best way to do this ?
TFS version is 2015 update 4 and SQL server 2014.
Please suggest me something.
It is a well documented process that is pretty prevalent online.
The official documentation is here
You will backup databases (config and collection)
Restore
Install and configure TFS app tier only and point it to the restored databases.