1) We are having a configuration using 4.1.4 vault. In this version, there is a repository that we want to migrate to a separate vault system.
2) Separate vault system has a brand new Vault server and brand new sql server. I am planning to install latest vault server version and using the 4.1.4 vault database, then will delete off all the extra repository that got carried over. Is that possible? if so, can you please give me the steps? Or do you have any better approach? Please advise me
Thanks!
upgrade to latest vault using 4.1.4 database
Moderator: SourceGear
Re: upgrade to latest vault using 4.1.4 database
You should be able to do this. However any time you move the database to a new installation, always have the database in place and then install Vault server. The server installer will upgrade the database, create the necessary database user information, and create the associations between the database and Vault server.
So uninstall your existing installation, restore a copy of the 4.1.4 database to the new SQL Server, and reinstall Vault. Then you can delete the repositories your team does not need any more.
So uninstall your existing installation, restore a copy of the 4.1.4 database to the new SQL Server, and reinstall Vault. Then you can delete the repositories your team does not need any more.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: upgrade to latest vault using 4.1.4 database
Thank you so much. I am able to use the copy of 4.1.4 db and install brand new web application (latest version) on a brand new vault server.
I think i remember somewhere in the document says that I need to modify the web.config file if i use the SQL authentication to connect to the db (which is on separate physical sql server). I can't find that document anymore. So, i tried to compare the connection string line between the 4.1.4 and the one with 5.x version. I see that the line
<identity impersonate="true" userName="username" password="pwd"/>
v5.x - not comment out
v4.1.4 - commented out
<!-- <identity impersonate="true" userName="username" password="pwd"/> IMPERSONATEPROCESS- -->
That is the difference I saw between the web.config of two versions. The reason for me to compare the 2 web config files, is I ran into problem complaining about invalid username or password error when I tried to access the Vault Admin website. So, I went ahead to comment out the above line in v5.x, then i can login to Vault Admin website successfully.
I am not sure if that is correct way doing/fixing the problem, but that is why i tried and it "solved" my problem.
I think i remember somewhere in the document says that I need to modify the web.config file if i use the SQL authentication to connect to the db (which is on separate physical sql server). I can't find that document anymore. So, i tried to compare the connection string line between the 4.1.4 and the one with 5.x version. I see that the line
<identity impersonate="true" userName="username" password="pwd"/>
v5.x - not comment out
v4.1.4 - commented out
<!-- <identity impersonate="true" userName="username" password="pwd"/> IMPERSONATEPROCESS- -->
That is the difference I saw between the web.config of two versions. The reason for me to compare the 2 web config files, is I ran into problem complaining about invalid username or password error when I tried to access the Vault Admin website. So, I went ahead to comment out the above line in v5.x, then i can login to Vault Admin website successfully.
I am not sure if that is correct way doing/fixing the problem, but that is why i tried and it "solved" my problem.