Re: Upgrade 2000 to 2005

Thanks Anthony...I've sent that info off to the customers hardware and O/S
team for their input

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Anthony Thomas" <ALThomas@xxxxxxxxx> wrote in message
news:uh9%23G$iPHHA.448@xxxxxxxxxxxxxxxxxxxxxxx
I would not due an in-place upgrade; they are dirty and they never end up
optimal.

So, given your hardware restrictions, here is the tact I would take.

Shut down all services and do a BMR backup. Yes, we have had to actually
use one of these for recovery before, and it isn't pretty, but it is
better
than a full reinstall.

Once you have a clean backup of the entire System State, Registry Hives,
and
file system, completely uninstall the SQL 2000 installation. Then install
SS2K5, using the same network addresses, virtual names, and instances.
Before you begin with the SS2K5, you will need to flush your DNS and AD;
otherwise, you will get installation errors.

You will also want to practice an SS2K5 clustered installation, even in a
VM, but the prerequisites are a little more complicated than your typical
SS2K installation. You need to be very familiar with these as I am sure
that the time-factor will be highly critical when it comes to the actual
production installation.

Sincerely,


Anthony Thomas


--

"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:utkdhr8OHHA.400@xxxxxxxxxxxxxxxxxxxxxxx
The nodes are about 3 months old. Not sure about the SAN. This place
leases hardware IIRC, so that would not be an issue.

Testing the restore is of course part of the plan :) but I always
appreciate
the reminder...

Still hoping to see if anyone has direct experience with imaging the
nodes
of the cluster and usnig that image as a restore....

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Edwin vMierlo" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eubG506OHHA.3268@xxxxxxxxxxxxxxxxxxxxxxx
I agree, I am not a big fan of upgrading clusters either, but I realise
sometimes there is no choice.
Ensure you have a *proven* backup and restore procedure, and backup
prior
to
your upgrade.
(*proven* = actually tested, else you might be in for a disaster)

Is your hardware still under warrantee / support ?
And for how long ?
( it might be time to think of building a new cluster with new
hardware... )



"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:u3hdLb2OHHA.4104@xxxxxxxxxxxxxxxxxxxxxxx
I have never been a big fan of a cluster upgrade. The rollback plan
basically becomes uninstall, reinstall, reload from backup. As a
safety
measure, I would detach the user databases, upgrade in place, and then
attach. That way, if there is a failure in the upgrade process, you
at
least save the restore step.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uF8ZqejOHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
New instance requires disk resources. I don't have disk resources
available. Or is 2005 that much different...

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Zekske" <Zekske@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14036779-7155-491E-AEB6-E431A07E05BF@xxxxxxxxxxxxxxxx
Never did a cluster upgrade yet but I can tell you that images of
clusternodes work.
What you also can do is install SQL 2005 as a new instance aside
your
SQL2000.
Then you can migrate your database from 2000 to 2005 keeping your
old
databases as rollback and without the need of new hardware

"Kevin3NF" wrote:

Gentlemen, geniuses, either or both....

My client has a multi-instance SQL 2000 SP3 (.818) cluster on
Win2K3.

He wants to upgrade both instances to 2005. Cool.

No extra drives/luns/whatever the proper term is are available in
the
SAN.

Am I stuck with an in place upgrade? I would have preferred to do
a
side by
side and move the databases but the hardware just aint there.

In this situation, what you do from a "rollback" perspective in
case
he
upgrade blows chunks and has to revert? For a standalone, I
assume
imaging
software would work...would a cluster image work just as well?

2005 upgrades are something I just haven't touched yet...:(

Thanks!

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com















.

Relevant Pages

  • Re: Best practice installing data/log files on other drive?
    ... Distributing I/O will improve performance if you have the hardware to do it. ... good source of information regarding hardware configuration is SQL Server ... > I am rather new to SQL Server installation procedures but I think I have ...
    (microsoft.public.sqlserver.setup)
  • Re: Upgrade 2000 to 2005
    ... I would not due an in-place upgrade; they are dirty and they never end up ... So, given your hardware restrictions, here is the tact I would take. ... completely uninstall the SQL 2000 installation. ... Real-world stuff I run across with SQL Server: ...
    (microsoft.public.sqlserver.clustering)
  • [NT] SQL Server Installation Process May Leave Passwords on System
    ... service pack for SQL Server 7.0 or SQL Server 2000, ... without having to actually perform an installation. ... to SQL Server 7.0 Service Pack 4, the passwords were stored in clear text. ... information in the setup.iss and log files would not allow any access. ...
    (Securiteam)
  • RE: Error Code: 1073807364 sql server 2005
    ... contain the files that are required during the installation of SQL Server ... In the D:\SQLServer2005 folder, ... Setup.exe to start the SQL Server 2005 Setup program. ...
    (microsoft.public.windows.server.sbs)
  • Re: [SLE] Cannot upgrade to 9.2
    ... > SCSI card, modem card and one of the two CD drives from my computer in ... end up changing out an uncooperative piece of hardware. ... successes involving a current kernel on this motherboard and/or SCSI ... Are there any comments in the release notes or installation ...
    (SuSE)
Loading