MOSS 2007 - Move config/content database to new server - Sharepoint

Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1

Detach the database from SQL and copy the .mdf and .ldf to the new SQL server.

Your users will get a generic “Cannot connect to content database” error
when visiting their site.

Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1
–databaseserver SQLServerA

Reattach the database in SQLServerB

Stsadm –o addcontentdb –url http://demo –databasename demo_content_1
–databaseserver SQLServerB



"Doug" wrote:

> I have been searching, but unable to find any decent information from
> Microsoft on how to move the SharePoint 2007 databases to a new server.
> I need to move the database for the farm configuration, along with all
> of the content, ssp and search databases. These will be moving from a
> SQL 2000 server to SQL 2005 on a different server (with a new name).
>
> I have no problem handling the SQL side of things, but I'm not sure how
> to update SharePoint to point at the new location.
>
> My single front end server will not be changed, and it currently runs
> my SharePoint site, SSP and all other services.
>
> Any tips would be helpful...thanks!
>
> --
>
>

What about the Config database? I cannot see anyway to move this short of
removing the web front end from the Farm, creating a new farm and resotring
the old database over the top of the new ones.


"Goncalo Feijao" wrote:

> Stsadm –o preparetomove –contentdb SQLServerA:demo_content_1
>
> Detach the database from SQL and copy the .mdf and .ldf to the new SQL server.
>
> Your users will get a generic “Cannot connect to content database” error
> when visiting their site.
>
> Stsadm –o deletecontentdb –url http://demo –databasename demo_content_1
> –databaseserver SQLServerA
>
> Reattach the database in SQLServerB
>
> Stsadm –o addcontentdb –url http://demo –databasename demo_content_1
> –databaseserver SQLServerB
>
>
>
> "Doug" wrote:
>
> > I have been searching, but unable to find any decent information from
> > Microsoft on how to move the SharePoint 2007 databases to a new server.
> > I need to move the database for the farm configuration, along with all
> > of the content, ssp and search databases. These will be moving from a
> > SQL 2000 server to SQL 2005 on a different server (with a new name).
> >
> > I have no problem handling the SQL side of things, but I'm not sure how
> > to update SharePoint to point at the new location.
> >
> > My single front end server will not be changed, and it currently runs
> > my SharePoint site, SSP and all other services.
> >
> > Any tips would be helpful...thanks!
> >
> > --
> >
> >

Apparently "by design" you aren't supposed to be able to move the
congif data. Cuz, ya-know, database servers never go down or need to
be renamed. :-)

Well after completly screwing up by site by trying to use the "stsadm.exe
-setconfig" command, I managed to move it by running the config wizard,
removing the site from the farm, then restoring the last backup (sps backup
not sql) to another server and then reconnecting the site to the farm. Worked
pretty well in the end. Then I came across this article on Database Mirroring
(go.microsoft.com/fwlink/?LinkId=83725&clcid=0x409) which seems to say it's
straightforward using this command

stsadm.exe -o renameserver -oldservername <oldserver> -newservername
<newserver>

I havn't tried it yet as it's all working again and if it ain't broke...

"RobertSeattle" wrote:

> Apparently "by design" you aren't supposed to be able to move the
> congif data. Cuz, ya-know, database servers never go down or need to
> be renamed. :-)
>
>

Ross wrote:

> Well after completly screwing up by site by trying to use the
> "stsadm.exe -setconfig" command, I managed to move it by running the
> config wizard, removing the site from the farm, then restoring the
> last backup (sps backup not sql) to another server and then
> reconnecting the site to the farm. Worked pretty well in the end.
> Then I came across this article on Database Mirroring
> (go.microsoft.com/fwlink/?LinkId=83725&clcid=0x409) which seems to
> say it's straightforward using this command
>
> stsadm.exe -o renameserver -oldservername <oldserver> -newservername
> <newserver>
>
> I havn't tried it yet as it's all working again and if it ain't
> broke...
>
> "RobertSeattle" wrote:
>
> > Apparently "by design" you aren't supposed to be able to move the
> > congif data. Cuz, ya-know, database servers never go down or need to
> > be renamed. :-)
> >
> >

Well, it looks like the stsadmn -o renameserver does the trick. I
successfully ran this on our test system and production servers. The
only issue I ran across was that I had to reapply the account settings
for the search service (crawler account). This may have been a problem
cause by my migration from SQL 2000 to SQL 2005 rather than the
'renameserver' command.

All-in-all, it was a fairly painless process....I'm just suprised this
isn't documented better my Microsoft.

--