Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Migrate from single server to web farm with SQL 2005 cluster

  Asked By: Dario    Date: Apr 17    Category: Sharepoint    Views: 1383

I am currently migrating a single sharepoint server to a web farm
running on 1 web/search frontend, 1 index server as well as a database
backend running on SQL 2005 cluster. The challenges are:

1. A different domain
2. A different server name
3. SQL 2005 cluster (Sept CTP)

I have succeeded in setting up the configuration databases, of which
the next thing I wish to do is migrate the data via spsbackup.
However, I am getting an error which relates to SQL connectivity. I
have little understanding of how spsbackup communicates with SQL.
SPSBackup requires SQL 2000 client tools to operate. How can I replace
that with SQL 2005 Server Management Studio or SQL SMO? Appreciate if
any experts here can shed some light.

Acquired search lock on server spsindexsvr at 2005/11/03 01:32:28<BR>

Monitor Progress Thread HeartBeat<BR>

BackupSQL now in progress: Restore=True, Server=sql2005cluster,

SQL Restore called with Server=sql2005cluster, Database=SPS_SITE,

Connecting to SQL Server sql2005cluster ...<BR>

Connection to SQL Server sql2005cluster FAILED<BR>

Failed ConnectToServer<BR>

[Microsoft][ODBC SQL Server Driver][SQL Server]To connect to this
server you must use SQL Server Management Studio or SQL Server
Management Objects (SMO).<BR>

[Microsoft][ODBC SQL Server Driver][SQL Server]To connect to this
server you must use SQL Server Management Studio or SQL Server
Management Objects (SMO).<BR>

Exception in BackupSQL: Source=SQLBkMgd, Message=The operation failed
on server sql2005cluster. For more information, see the Microsoft
Windows Event Log on that server.<BR>

BackupSQL Thread setting its status to completed and exiting<BR>

Portal site http://spswebnsearchsvr/ does not exist. INDEX cannot be
Released search lock on server spsindexsvr<BR>

ProgressThread set completed status and is now exiting<BR>



4 Answers Found

Answer #1    Answered By: Dakota Shaffer     Answered On: Apr 17

if you are moving domains... the best way to back up and restore to the new
domain is to use smigrate..

dont attempt cross domain backup/restore ANY other way.

as to your issue with sql  2005, we work just fine in our staging environment
with it. the only problem prior to sps sp2 was that it didnt know how to
communicate with the FT indexes on the sql databases.

Answer #2    Answered By: Ted Gilmore     Answered On: Apr 17

But I experienced smigrate losing the security
settings as well as the member list during site

Answer #3    Answered By: Monte Cooley     Answered On: Apr 17

That is a feature of smigrate. The original purpose of the tool assumed you
would have new security either through inheritance or configuration.

Answer #4    Answered By: Guadalupe Bullock     Answered On: Apr 17

your greatest challenge is the fact that you are moving domains. oh yeah and the fact that you are using a non-production version of sql server  - it comes out in 7 days..

www.microsoft.com/.../stsf12.mspx - in my experience you cant use stsadm or spsbackup to backup and restore to other domains. this documentation even speaks of smigrate as the "site migration tool"