|
|
We are running WSUS 2 with a backend MS sql server 2000. Now I want to move
that database to a new SQL2005 server. On the backend server WSUS are
installed but are there anything running there except for an ordanary
database ?
I would like to do like this
1. Stop the Update Service on my frontend server
2. On the frontend server change the registry values under
HKEY_Local_Machine\SOFTWARE\Microsoft\Update Services\Server\Setup for
SqlServerName to the new sqlserver
3. restore a copy of the SUSDB on the new sql-server
4. Remove the WSUS software from the backend server
5. Start the Update Service on the frontend server
Will this work ?
Sincerely
\\Jonas B
|
|
"jonte[ at ]bson.se" <jonasberthelsson[ at ]hotmail.com> wrote in message
news:%23G0nXywSJHA.1908[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > We are running WSUS 2 with a backend MS sql server 2000. Now I want to
> move that database to a new SQL2005 server. On the backend server WSUS are
> installed but are there anything running there except for an ordanary
> database ?
Either I'm misunderstanding your question, or my answer must be: "I haven't
the foggiest idea what else might be running on your backend server".
> I would like to do like this
>
> 1. Stop the Update Service on my frontend server
> 2. On the frontend server change the registry values under
> HKEY_Local_Machine\SOFTWARE\Microsoft\Update Services\Server\Setup for
> SqlServerName to the new sqlserver
> 3. restore a copy of the SUSDB on the new sql-server
> 4. Remove the WSUS software from the backend server
> 5. Start the Update Service on the frontend server
>
> Will this work ?
Not quite...
[a] You need to remove the WSUS software from the back-end server as the
very first step.
[b] Backup/Restore of the SQL2000 SUSDB database is an option, but an easier
option is to simply detach/copy/attach the database.
[c] Since you don't mention upgrading to WSUS 3.0, you need to verify that
your front-end server has WSUS 2.0 SP1 applied.
[d] You really *should* complete the upgrade to WSUS 3.0. The only reason
*not* to do the upgrade is if your front-end server is still running Windows
2000 Server, and if that be the case, then my sharp-tongued response would
be to focus your efforts on upgrading the server operating systems, not the
back-end WSUS database. <g>
On the other hand, if SQL 2000 was the only reason you couldn't upgrade to
WSUS 3.0, then this resolves that issue and you'd be much better off doing
the whole thing in one shot, than in two separate events.
From a reply I just posted in the Windows Server 2008 WSUS forum a few
minutes ago on the same question...
http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/9df8c40d-1a9f-4d7c-8675-fb087f0e8385
1. Uninstall WSUS 2.0 from the back-end database server.
2. Install SQL Server 2000 plus service packs on the new database server.
3. Stop the Update Services service on the front-end server.
4. Detach the SUSDB from the current back-end server and reattach to the new
server (running SQL 2000).
*5. Upgrade the new server from SQL Server 2000 to SQL Server 2005 SP1.
*6. Upgrade the front-end server from WSUS 2.0 to WSUS 3.0 SP1.
*Steps 5 and 6 would not be required if you're not upgrading to WSUS 3.0.
Another alternative to this, which avoids the "Install SQL2000/Upgrade to
SQL2005" scenario on the new back-end server is:
1. Uninstall WSUS 2.0 from the back-end database server.
2. Install SQL Server 2000 plus service packs on the front-end server.
3. Stop the Update Services service on the front-end server.
4. Detach the SUSDB from the current back-end server and reattach to the
front-end server (running SQL2000).
5. Reconfigure the front-end server (using Appendix C of the WSUS2
Deployment Guide) to use the local instance of SQL 2000.
*6. Upgrade the front-end server from WSUS 2.0 to WSUS 3.0 SP1. This step
will then cause the installation of the Windows Internal Database onto the
front-end server, as well as effect the upgrading of the database from
SQL2000-mode to SQL2005-mode.
7. Install SQL Server 2005 SP1 on the new back-end server.
8. Detach the SUSDB from the front-end server and reattach to the back-end
server.
*9. Reconfigure the front-end server (using Appendix B of the WSUS3
Deployment Guide) to use the new back-end instance of SQL 2005.
*10. Uninstall Windows Internal Database from the front-end server.
11. Uninstall SQL Server 2000 from the front-end server.
*Steps 6, 9, 10 would not be required if you're not upgrading to WSUS 3.0
Whether you feel avoiding the SQL Server 2000/SQL Server 2005 upgrade on the
back-end server is worth the extra work in the alternative methodology is
really a question of how pure you want your SQL Server 2005 installation to
be. For the answers to that question, I will refer you to the published
literature and documentation on upgrading SQL Server 2000 to SQL Server 2005
to determine if your organization will have any issues with that
methodology.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
I used the following steps to move backend Db from 2000 to 2005 and then
upgraded from 2.0sp1 to 3.0 sp1 and it seem to work just fine
"> [a] You need to remove the WSUS software from the back-end server as the
[Quoted Text] > very first step.
> [b] Backup/Restore of the SQL2000 SUSDB database is an option, but an
> easier option is to simply detach/copy/attach the database.
> [c] Since you don't mention upgrading to WSUS 3.0, you need to verify that
> your front-end server has WSUS 2.0 SP1 applied.
>. On the frontend server change the registry values under
>> HKEY_Local_Machine\SOFTWARE\Microsoft\Update Services\Server\Setup for
>> SqlServerName to the new sqlserver
> [d] You really *should* complete the upgrade to WSUS 3.0. The only reason
> *not* to do the upgrade is if your front-end server is still running
> Windows 2000 Server, and if that be the case, then my sharp-tongued
> response would be to focus your efforts on upgrading the server operating
> systems, not the back-end WSUS database. <g>"
My frontend-server was a 2003 server.
Thank's for all help !
\\Jonas B
"Lawrence Garvin (MVP)" <lawrence[ at ]news.postalias> skrev i meddelandet
news:e74cAC6SJHA.4372[ at ]TK2MSFTNGP04.phx.gbl...
> "jonte[ at ]bson.se" <jonasberthelsson[ at ]hotmail.com> wrote in message
> news:%23G0nXywSJHA.1908[ at ]TK2MSFTNGP04.phx.gbl...
>> We are running WSUS 2 with a backend MS sql server 2000. Now I want to
>> move that database to a new SQL2005 server. On the backend server WSUS
>> are installed but are there anything running there except for an ordanary
>> database ?
>
> Either I'm misunderstanding your question, or my answer must be: "I
> haven't the foggiest idea what else might be running on your backend
> server".
>
>> I would like to do like this
>>
>> 1. Stop the Update Service on my frontend server
>> 2. On the frontend server change the registry values under
>> HKEY_Local_Machine\SOFTWARE\Microsoft\Update Services\Server\Setup for
>> SqlServerName to the new sqlserver
>> 3. restore a copy of the SUSDB on the new sql-server
>> 4. Remove the WSUS software from the backend server
>> 5. Start the Update Service on the frontend server
>>
>> Will this work ?
>
> Not quite...
>
> [a] You need to remove the WSUS software from the back-end server as the
> very first step.
> [b] Backup/Restore of the SQL2000 SUSDB database is an option, but an
> easier option is to simply detach/copy/attach the database.
> [c] Since you don't mention upgrading to WSUS 3.0, you need to verify that
> your front-end server has WSUS 2.0 SP1 applied.
> [d] You really *should* complete the upgrade to WSUS 3.0. The only reason
> *not* to do the upgrade is if your front-end server is still running
> Windows 2000 Server, and if that be the case, then my sharp-tongued
> response would be to focus your efforts on upgrading the server operating
> systems, not the back-end WSUS database. <g>
>
> On the other hand, if SQL 2000 was the only reason you couldn't upgrade to
> WSUS 3.0, then this resolves that issue and you'd be much better off doing
> the whole thing in one shot, than in two separate events.
>
> From a reply I just posted in the Windows Server 2008 WSUS forum a few
> minutes ago on the same question...
> http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/9df8c40d-1a9f-4d7c-8675-fb087f0e8385
>
> 1. Uninstall WSUS 2.0 from the back-end database server.
> 2. Install SQL Server 2000 plus service packs on the new database server.
> 3. Stop the Update Services service on the front-end server.
> 4. Detach the SUSDB from the current back-end server and reattach to the
> new server (running SQL 2000).
> *5. Upgrade the new server from SQL Server 2000 to SQL Server 2005 SP1.
> *6. Upgrade the front-end server from WSUS 2.0 to WSUS 3.0 SP1.
>
> *Steps 5 and 6 would not be required if you're not upgrading to WSUS 3.0.
>
> Another alternative to this, which avoids the "Install SQL2000/Upgrade to
> SQL2005" scenario on the new back-end server is:
>
> 1. Uninstall WSUS 2.0 from the back-end database server.
> 2. Install SQL Server 2000 plus service packs on the front-end server.
> 3. Stop the Update Services service on the front-end server.
> 4. Detach the SUSDB from the current back-end server and reattach to the
> front-end server (running SQL2000).
> 5. Reconfigure the front-end server (using Appendix C of the WSUS2
> Deployment Guide) to use the local instance of SQL 2000.
> *6. Upgrade the front-end server from WSUS 2.0 to WSUS 3.0 SP1. This step
> will then cause the installation of the Windows Internal Database onto the
> front-end server, as well as effect the upgrading of the database from
> SQL2000-mode to SQL2005-mode.
> 7. Install SQL Server 2005 SP1 on the new back-end server.
> 8. Detach the SUSDB from the front-end server and reattach to the back-end
> server.
> *9. Reconfigure the front-end server (using Appendix B of the WSUS3
> Deployment Guide) to use the new back-end instance of SQL 2005.
> *10. Uninstall Windows Internal Database from the front-end server.
> 11. Uninstall SQL Server 2000 from the front-end server.
>
> *Steps 6, 9, 10 would not be required if you're not upgrading to WSUS 3.0
>
> Whether you feel avoiding the SQL Server 2000/SQL Server 2005 upgrade on
> the back-end server is worth the extra work in the alternative methodology
> is really a question of how pure you want your SQL Server 2005
> installation to be. For the answers to that question, I will refer you to
> the published literature and documentation on upgrading SQL Server 2000 to
> SQL Server 2005 to determine if your organization will have any issues
> with that methodology.
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
>
|
|
|