RE: Switching Servers and upgrading to 2.0

"Dan Schreiber" <[email protected]> Thu, 26 Feb 2004 16:09:08 -0600
Newsgroups gmane.comp.version-control.sourcegear-vault.user
Message-ID <[email protected]>
Linda is right that choosing option 1 will be less time consuming if
everything goes right (which it should).

However, I would recommend option 2, in case anything goes wrong :)

If you are moving to a different machine, you may as well keep your current
setup intact, so you are guaranteed access to your database should the
upgrade fail.  If the upgrade fails on the new machine, you don't have to
use it until all the issues are resolved.

It might make sense for you to do a quick dummy install of Vault on the new
machine (either 1.2 or 2.0), just to make sure Vault installs smoothly on it
before going through the work of an upgrade.

-Dan Schreiber


> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Linda Bauer
> Sent: Thursday, February 26, 2004 3: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