We need to upgrade vault from 3.5.1 to 4.1.1. Is this possible? or do we need to do incremental upgrades?
The person who installed this to begin with is not here so what information do we need before we start this?
Other than backing up the database are there any other backups that need to be done?
Upgrading from 3.5.1 to 4.1.1
Moderator: SourceGear
You don't need to upgrade in steps from that version. You are correct that you should backup your database. Read through the Install Guide.
Things to ask yourself:
1) Is the SQL server on the same machine as Vault?
2) Will shadow folders be used, and, if so, will they be residing on the same machine?
3) Are you currently or going to use Active Directory authentication with Vault?
Things to ask yourself:
1) Is the SQL server on the same machine as Vault?
2) Will shadow folders be used, and, if so, will they be residing on the same machine?
3) Are you currently or going to use Active Directory authentication with Vault?
1 ) SQL Server is on a different machine from where vault is hosted
2) what are shadow folder? how do i find if they are currently beign used or not?
3) We have individual logins to vault client. Does that help? does that mean we are using active directory?
4) we will be backing up the databases.How do we back up the physical file repository??? what is the upgrade fails and we have to rollback to old data,will just having the db backup suffice?
2) what are shadow folder? how do i find if they are currently beign used or not?
3) We have individual logins to vault client. Does that help? does that mean we are using active directory?
4) we will be backing up the databases.How do we back up the physical file repository??? what is the upgrade fails and we have to rollback to old data,will just having the db backup suffice?
1) That means that you may get better results by using SQL authentication during the install.
2) Log into the admin tool. On the Repository Options page is a link to where shadow folders are configured. Check there. If nothing is entered, then they aren't set up.
3) If your Vault client login EXACTLY matches your Windows login and when you log into Windows, you are logging into an Active Directory domain, then you might be using AD authentication. Another way to tell is to look in Vault admin tool under Server Options. That is where that feature is configured. If empty, then it's not currently in use.
4) Everything you need is in the database. Just backup sgvault and you are good to go. Once you get on version 4.x, then you need to remember that Vault becomes 2 databases and you need to backup sgvault and sgmaster.
Do you know the login for 'admin' on Vault? That is needed as well. If you don't know it, then you will want to perform an uninstall (keeping the database) and a reinstall (use same database) of the next version to both upgrade and to reset the admin password.
2) Log into the admin tool. On the Repository Options page is a link to where shadow folders are configured. Check there. If nothing is entered, then they aren't set up.
3) If your Vault client login EXACTLY matches your Windows login and when you log into Windows, you are logging into an Active Directory domain, then you might be using AD authentication. Another way to tell is to look in Vault admin tool under Server Options. That is where that feature is configured. If empty, then it's not currently in use.
4) Everything you need is in the database. Just backup sgvault and you are good to go. Once you get on version 4.x, then you need to remember that Vault becomes 2 databases and you need to backup sgvault and sgmaster.
Do you know the login for 'admin' on Vault? That is needed as well. If you don't know it, then you will want to perform an uninstall (keeping the database) and a reinstall (use same database) of the next version to both upgrade and to reset the admin password.
1) OK. So how do i figure what authentication vault is using on SQL Server? I do see a sgvaultuser on the SQL Server. Does this mean SQL authentication was used last time? I see at one point the installation it asks you to "connect to SQL Server"
2) Checked this,no shadow folders are configured
3) Active Directory is not configured under Admin>Server Options.
4) Noted!
More questions..
5) I think we do know the admin login but i will confirm.
6) How do i find out how the IIS process model was confgured the last time? Machine,System or Custom.
2) Checked this,no shadow folders are configured
3) Active Directory is not configured under Admin>Server Options.
4) Noted!
More questions..
5) I think we do know the admin login but i will confirm.
6) How do i find out how the IIS process model was confgured the last time? Machine,System or Custom.
1) That could be the case. The best way to know is by checking the vault_install.log located in %username%\local settings\temp. If you are prepared to use SQL authentication, then it might be easier to just go that route.
6) The install log will tell you, or you can look in your Vault Server Log. If you see NT Authority/Network service, then machine was chosen. If you see <domain name>/<some user>, then it's custom. For System, I think it's <domain>\< machine>$, but that one is only for special cases and rarely ever used.
6) The install log will tell you, or you can look in your Vault Server Log. If you see NT Authority/Network service, then machine was chosen. If you see <domain name>/<some user>, then it's custom. For System, I think it's <domain>\< machine>$, but that one is only for special cases and rarely ever used.