Migration and Upgrade

I'm looking to get some thoughts on what might be the recommended way to upgrade and/or migrate our ProGet server. Currently, we are running v3.5.5 on Windows 2008R2 with SQL Server 2005 Express running. We are looking to replace this single server with two servers running Windows Server 2012R2 with SQL Server 2012 as the new database engine.

What I was sure of was how should I go about doing the upgrade.

My initial thought was to upgrade the current instance, migrate the database to the new database server, update the compatibility mode to be SQL 2012, then install ProGet on the two web nodes and point them to the new database server.

Has anyone done a similar upgrade and could comment on if this worked for them or did they run into issues? I'm also open to suggestions on other ways to do the upgrade that might be better then what I've spelled out.

Thanks in advance!

Product: ProGet
Version: 3.5.5

Hi TJ,

That upgrade path is fine, and quite common; as long as the shared storage is the same (I assume it's already a UNC path), then when you start everything up again (webserver, indexing service), it should be the same.

There isn't so much risk going from 3.5 -> 4.0, but please do read the ProGet upgrade notes just to see what's coming.

Just make sure to do a quick test on the current (2005/single server) set up as 4.0 before moving that to new servers. You can always rollback if there is a realy big issue (though, we haven't seen any yet!)

Best,
Alana