RE: Switching Servers and upgrading to 2.0

Funny, I am in the process of the same thing as well. :)

We are getting a dedicated machine as well and I have a scenario 3 for it.
We currently are running 1.2.2.  I had the worst time getting 1.2.2 to
install correctly on any of our machines.  I ended up literally installing
the product manually by copying files and running sql scripts from a few
step-by-steps sent to me by support.  I would prefer to not even try to
either upgrade the current machine or install 1.2.2 on the new machine and
upgrade that.

What if I simply restored the 1.2.2 Vault database to the new machine and
then installed Version 2 as a new installation?  Would the installer pick up
the database and upgrade it properly without having a previous version of
the program itself installed? This would be my much preferred scenario 3.

BTW, I did a few test runs of the version 2 install (clean install, no
upgrading) on some of our test beds and it worked beautifully!!! Kudos for
fixing whatever issues were in the old installer.

-----Original Message-----
From: Linda Bauer [mailto:[email protected]] 
Sent: Thursday, February 26, 2004 4:32 PM
To: Chris Mullins; Vault-List
Subject: Re: [vault-list] Switching Servers and upgrading to 2.0

Hi, Chris,

Either would work, but I'd suggest upgrading first and then moving Vault. 
Your old machine is already configured correctly and the Vault 2.0 install 
should go smoothly, provided you select the same options you did the first 
time.

Then you can install Vault 2.0 on the new machine. In case there are 
configuration issues on the new machine, the Vault 2.0 installer does a 
much better job of reporting what's happening (or not) during the 
installation than the 1.x installer.

For more details on moving Vault see this KB article:

http://support.sourcegear.com/viewtopic.php?t=228

Linda Bauer
SourceGear
Technical Support

visit our support forum at
http://support.sourcegear.com


At 03:14 PM 2/26/2004, Chris Mullins wrote:
>This weekend we're planning on migrating to Vault 2.0. Our new dedicated 
>machine from Dell has arrived, so at the same time we do this, we're going 
>to move the vault database to the new machine.
>
>What's the best way to go about doing this?
>
>Scenario 1:
>-                      Upgrade existing machine to vault 2.0
>-                      Backup Database using Vault tools
>-                      Install Vault 2.0 onto new machine
>-                      Restore database onto new machine using vault tools
>
>Scenario 2:
>-                      Install vault 1.2.x on the new machine
>-                      Backup db on old machine, and restore on new machine
>-                      Upgrade new machine to vault 2.0
>
>Scenario 3
>-                      Is there a scenario 3?
>
>
>Which of these methods will work the best?
>
>Scenario 2 seems the best to me, as I don't have to install new software 
>on the old machine (which is waaaaaaaay overloaded, and is going to have 
>Vault and SQL Server removed from it as soon as the upgrade is done).
>
>--
>Chris Mullins
>

_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list