Ghosting SQL Server 2000 Running on NT40

Hello,

Is it possible to Ghost SQL Server 2000 running on NT4.0 and then restore
that image on another server with different hardware configuration and
operating system(likely Windows 2003)???

The currentl SQL Server have DTS packages, Linked Services, Jobs, etc...

If possible, what would be the best steps to take to ensure a successful
image.
Are there any documentations on Ghosting SQL Server???

Thank You
Scott Yu

No.

--
Mike
Mentor
Solid Quality Learning
http://www. solidqualitylearning
.com


"Scott Yu" <ScottYu@discussions.microsoft.com> wrote in message
news:161D3054-7195-414E-A814- 5B60B8B82624@microso
ft.com...
> Hello,
>
> Is it possible to Ghost SQL Server 2000 running on NT4.0 and then restore
> that image on another server with different hardware configuration and
> operating system(likely Windows 2003)???
>
> The currentl SQL Server have DTS packages, Linked Services, Jobs, etc...
>
> If possible, what would be the best steps to take to ensure a successful
> image.
> Are there any documentations on Ghosting SQL Server???
>
> Thank You
> Scott Yu

Why?  I need to give an answer to my manager and client.

"Michael Hotek" wrote:

> No.
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www. solidqualitylearning
.com
>
>
> "Scott Yu" <ScottYu@discussions.microsoft.com> wrote in message
> news:161D3054-7195-414E-A814- 5B60B8B82624@microso
ft.com... 
>
>
>

I assume that by 'ghosting', you mean creating a disk image of all installed
SQL Server components and databases.  This is not feasible for a number of
reasons.  For example, much configuration data is stored registry and this
would need to be properly merged to the target system.

Is there some reason you must use a 'ghosting' technique to move the
installation?  The normal way to accomplish this is to install SQL Server on
the target server (same version/SP/hotfix level as source), restore system
databases and then restore (or attach) user databases, much like you might
do in a disaster recovery scenario.  Restoring master and msdb will move
your DTS packages, Linked Services, Jobs, etc.  See
http://support.microsoft.com/kb/307775/en-us for a list of DR articles.

--
Happy Holidays

Dan Guzman
SQL Server MVP

"Scott Yu" <ScottYu@discussions.microsoft.com> wrote in message
news:19023EF9-09A7-4FF1-AE24- 7C268426F612@microso
ft.com...
> Why?  I need to give an answer to my manager and client.
>
> "Michael Hotek" wrote:
> 

Thank you Dan,

Management wants to use Ghost, I don't.  I figure Ghost was not a solution,
but I wasn't 100% sure.  I'll proceed the way it should be done,
re-installing SQL Server and then restore the various components.

Now I have a good reason to let management know why Ghosting is not a quick
fix solution.

Thank you so much.

Scott Yu

"Dan Guzman" wrote:

> I assume that by 'ghosting', you mean creating a disk image of all install
ed
> SQL Server components and databases.  This is not feasible for a number of
> reasons.  For example, much configuration data is stored registry and this
> would need to be properly merged to the target system.
>
> Is there some reason you must use a 'ghosting' technique to move the
> installation?  The normal way to accomplish this is to install SQL Server 
on
> the target server (same version/SP/hotfix level as source), restore system
> databases and then restore (or attach) user databases, much like you might
> do in a disaster recovery scenario.  Restoring master and msdb will move
> your DTS packages, Linked Services, Jobs, etc.  See
> http://support.microsoft.com/kb/307775/en-us for a list of DR articles.
>
> --
> Happy Holidays
>
> Dan Guzman
> SQL Server MVP
>
> "Scott Yu" <ScottYu@discussions.microsoft.com> wrote in message
> news:19023EF9-09A7-4FF1-AE24- 7C268426F612@microso
ft.com... 
>
>
>

Do you want to duplicate only your SQL Server 2000 databases
on another server with a newer OS? If yes then backup your
databases on the server, install a SQL Server 2000 on a new one,
restore the databases.
If you want to upgrade the OS then backup all of the SQL Server 2000
databases, put the backups on a safe place, deinstall the SQL Server 2000,
upgrade the OS or install one from scratch, install a fresh installation of
SQL Server 2000, and restore your databases.

See the following links for more detail:

http://vyaskn.tripod.com/moving_sql_server.htm

http://www.karaszi.com/SQLServer/ i...n
ame.asp

Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071

Moving Databases between Servers
http://www.support.microsoft.com/?id=314546

Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465

How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133

Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897

Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp

How to Resolve Permission Issues When a Database Is
Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872

User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001

Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
---
Andrey Odegov
avodeGOV@yandex.ru
(remove GOV to respond)

In article <161D3054-7195-414E-A814- 5B60B8B82624@microso
ft.com>,
ScottYu@discussions.microsoft.com says...
> Hello,
>
> Is it possible to Ghost SQL Server 2000 running on NT4.0 and then restore
> that image on another server with different hardware configuration and
> operating system(likely Windows 2003)???
>
> The currentl SQL Server have DTS packages, Linked Services, Jobs, etc...
>
> If possible, what would be the best steps to take to ensure a successful
> image.
> Are there any documentations on Ghosting SQL Server???

Ghost doesn't restore files, it's an IMAGE of the Drive / Partition.
Sure you can pull individual files using Ghost Walker, but it's designed
to make a instance image of a DRIVE and restore the entire thing to
another drive.

You want to MIGRATE based on your description - Ghost has nothing to do
with a Migration, unless you want to migrate the existing OS/Data to
another hardware, fix it, get it working perfectly, then upgrade the OS
- this would leave the old system running until needed.

The new system could have the same name as the old system (as long as
you don't put them on the network at the same time, even the same IP,
but you would have to do the upgrade manually.

--

spam999free@rrohio.com
remove 999 in order to email me