Solved

Move SharePoint 3.0 Website to New Server

Posted on 2012-03-20
9
1,134 Views
Last Modified: 2012-03-31
I have a SharePoint 3.0 server that I would like to move to another server. there is nothing special or out of the ordinary about this server so everything is generally "out of the box" setup.   Can anyone tell me how I can move this to another server? BTW, both servers are Server 200 R2 and use the embedded database. The current server was migrated from a SBS 2003 server.
0
Comment
Question by:MortonTA
  • 6
  • 3
9 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 37746898
If you need remote assistance, I'm available.

There is definitely more than one way to do it.  High level steps would include.....

-Installing same version of SharePoint / SQL on the new server
-Run config wizard and join the new server to the existing farm
-Backing up current databases
-Copying them to new server and restoring
-Verifying/updating SQL permissions on the databases
-Running stsadm -o renameserver to rename the old server to the new server in the config database (do this on both servers)
-Updating DNS to point to new sever
-Running config wizard on the old server to remove it from the farm
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37749170
I am being told that this was setup as a standalone server and not a farm. Are the steps different? I am assuming so since I am not able to connect to the database or anything.
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 37749222
Yes that changes things.

You will still do everything the same as far as SQL, you need to copy and restore to the new server.

Since everything is pretty "out of the box", I would just deploy your new farm.  Make sure this time around you do Advanced - Complete installation.  Then create a web application(s) with the URL of your current site(s) and use the database name of your restored content database from your old farm.  This way the new web app will connect to the restored db.

Then update DNS to point to the new server.

As far as connecting to your SQL instacne, use this as the connection string:  

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37754172
So, I have tried your suggestions and looked up a few more, all to no avail :(

It has been suggested to me by another coworker (who is just as naive to WSS and I am) that I start over on the new server. So, i have installed Windows Server 2008 R2 and SQL 2008 R2 doing just a basic install. Then I ran my SharePoint 3 install and configured a new farm, taking all the defaults (database server: cweb database name:SharePoint_Config Username:global Password: *****************). then i took my backup from the old server using the following command:

stsadm -o backup -url https://tchcdc02.tchcdom.pri -directory C:\spbackup -backupmethod full -percentage 10 -backupthreads 3

The backup finished with 0 errors and 0 warnings... Looks good i say to myself.

Then i copy the backup to my new server and run the following restore command

stsadm -o restore -hostheaderwebapplicationurl http://cewb.tchcdom.pri -directory c:\spbackup -restoremethod new -username tchcdom\global -password ************* -newdatabaseserver sql2008

Everything looked ok and i answered some questions when prompted. NO GO - 0 warnings and 2 errors. Below is the output that was captured... Any thoughts?





Verbose: Using directory: c:\spbackup\spbr0000\.
Verbose: Starting OnPreRestore event.
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Initializing SPPersistedObject State
Verbose: Adding Farm to Restore list.
Verbose: Adding Windows SharePoint Services Search to Restore list.
Verbose: Adding Search instance to Restore list.
Verbose: Adding WSS_Search_TCHCDC02 to Restore list.
Verbose: Adding Windows SharePoint Services Web Application to Restore list.
Verbose: Adding SharePoint - 80 to Restore list.
Verbose: Adding WSS_Content to Restore list.
Verbose: Adding WSS_Administration to Restore list.
Verbose: Adding Web Application to Restore list.
Verbose: Adding SharePoint_AdminContent_0cb75dd0-0251-4272-afae-56c7d41c6289 to Restore list.
Verbose: Adding Farm to Restore list.
Verbose: Adding SharePoint_Config_fd325bd8-fb47-4dcb-9ac6-73d80ea6a8ba to Restore list.
Verbose: Adding Windows SharePoint Services Search to Restore list.
Verbose: Adding Search instance to Restore list.
Verbose: Adding WSS_Search_TCHCDC02 to Restore list.
Verbose: Adding Windows SharePoint Services Web Application to Restore list.
Verbose: Adding SharePoint - 80 to Restore list.
Verbose: Adding WSS_Content to Restore list.
Verbose: Adding WSS_Administration to Restore list.
Verbose: Adding Web Application to Restore list.
Verbose: Adding SharePoint_AdminContent_0cb75dd0-0251-4272-afae-56c7d41c6289 to Restore list.
Change location/name for: Farm\Windows SharePoint Services Search\Search instance\WSS_Search_TCHCDC02
        New server name (default: TCHCDC02\Microsoft##SSEE): cweb\Microsoft##SSEE
        New directory name (default: C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\): C:\Program Files\Microsoft SQL Server\MS
SQL10_50.MSSQLSERVER\MSSQL\DATA
        New database name (default: WSS_Search_TCHCDC02): WSS_Search_CWEB
The database you have chosen is already in use. Specify a different database name.
        New server name (default: TCHCDC02\Microsoft##SSEE): WSS_Search
        New directory name (default: C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\): C:\Program Files\Microsoft SQL Server\MS
SQL10_50.MSSQLSERVER\MSSQL\DATA
        New database name (default: WSS_Search_TCHCDC02): WSS_Search
Change location/name for: Farm\Windows SharePoint Services Web Application\SharePoint - 80
        New web application URL (default: http://tchcdc02/): http://cweb
        New web application name (default: SharePoint - 80): SharePoint - 80
Change location/name for: Farm\Windows SharePoint Services Web Application\SharePoint - 80\WSS_Content
        New server name (default: TCHCDC02\Microsoft##SSEE): cweb\Microsoft##SSEE
        New directory name (default: C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\): C:\Program Files\Microsoft SQL Server\MS
SQL10_50.MSSQLSERVER\MSSQL\DATA
        New database name (default: WSS_Content): WSS_Content
The database you have chosen is already in use. Specify a different database name.
        New server name (default: TCHCDC02\Microsoft##SSEE): cweb\Microsoft##SSEE
        New directory name (default: C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\): C:\Program Files\Microsoft SQL Server\MS
SQL10_50.MSSQLSERVER\MSSQL\DATA
        New database name (default: WSS_Content): WSS_Content_1
Verbose: The backup/restore process included the following objects:
    Farm\
        [SharePoint_Config_fd325bd8-fb47-4dcb-9ac6-73d80ea6a8ba]\
        Windows SharePoint Services Search\
            [Search instance]\
                [WSS_Search_TCHCDC02]\
        Windows SharePoint Services Web Application\
            SharePoint - 80\
                WSS_Content\
        [WSS_Administration]\
            [Web Application]\
                [SharePoint_AdminContent_0cb75dd0-0251-4272-afae-56c7d41c6289]\

Progress: Starting Restore.
Start Time: 3/22/2012 11:45:23 AM.
Verbose: Requested by TCHCDOM\global.
Verbose: Backup/Restore Settings:
        Restore
        Backup Method: Full
        Top Component:
        Directory: c:\spbackup
        Progress updated: 5
        Restore Method: New
        Preserve content database change log: False

Verbose: Starting OnRestore event.
Verbose: Starting object: Farm.
Verbose: [Farm] The configuration database and central administration content database components cannot be restored.
Progress: [Farm] 50 percent complete.
Verbose: Starting object: Windows SharePoint Services Search.
Progress: [Windows SharePoint Services Search] 50 percent complete.
Verbose: Starting object: Search instance.
Progress: [Search instance] 50 percent complete.
Verbose: Current object: WSS_Search (previous name: WSS_Search_TCHCDC02).
Verbose: [WSS_Search_TCHCDC02] SQL Server Connection String: Data Source=WSS_Search;Initial Catalog=WSS_Search;Integrated Sec
urity=True.
Error: Object WSS_Search (previous name: WSS_Search_TCHCDC02) failed in event OnRestore. For more information, see the error
log located in the backup directory.
        SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. Th
e server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to a
llow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Verbose: Starting object: Windows SharePoint Services Web Application.
Progress: [Windows SharePoint Services Web Application] 50 percent complete.
Verbose: Starting object: SharePoint - 80.
Verbose: [SharePoint - 80] Trying to connect to Web application http://cweb.
Verbose: [SharePoint - 80] Creating a new Web application.
Verbose: [SharePoint - 80] Provisioning a new Web application.
Progress: [SharePoint - 80] 50 percent complete.
Verbose: Current object: WSS_Content_1 (previous name: WSS_Content).
Verbose: [WSS_Content] SQL Server Connection String: Data Source=cweb\Microsoft##SSEE;Initial Catalog=WSS_Content_1;Integrate
d Security=True.
Verbose: [WSS_Content] SQL command started at: 3/22/2012 11:45:50 AM. This command may take a while to complete and without n
otification.
Verbose: [WSS_Content] SQL Server Command:
IF EXISTS ( SELECT * FROM master..sysdatabases WHERE has_dbaccess(name)=1 AND name=@db_name )
BEGIN
    SELECT 1 as ErrorCode
END
ELSE
BEGIN RESTORE DATABASE [WSS_Content_1] FROM DISK=@db_location WITH STATS=5, FILE=1, MOVE @db_OldName TO @db_NewFile, MOVE @db
_OldLogName TO @db_NewLogFile, NOREWIND, NOUNLOAD, RECOVERY
END

        @db_location=c:\spbackup\spbr0000\0000000F.bak, @db_OldName=WSS_Content, @db_NewFile=C:\Program Files\Microsoft SQL S
erver\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_1.mdf, @db_OldLogName=WSS_Content_log, @db_NewLogFile=C:\Program Files\Mi
crosoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_1_log.ldf, @db_name=WSS_Content_1
Verbose: [WSS_Content] SQL command timeout is set to 1.00 hours.
Error: Object WSS_Content_1 (previous name: WSS_Content) failed in event OnRestore. For more information, see the error log l
ocated in the backup directory.
        SqlException: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::Vali
dateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_1.mdf'.
File 'WSS_Content' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content
_1.mdf'. Use WITH MOVE to identify a valid location for the file.
The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation'
 on 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_1_log.ldf'.
File 'WSS_Content_log' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Con
tent_1_log.ldf'. Use WITH MOVE to identify a valid location for the file.
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
RESTORE DATABASE is terminating abnormally.
Verbose: Starting object: WSS_Administration.
Progress: [WSS_Administration] 50 percent complete.
Verbose: Starting OnPostRestore event.
Verbose: Starting object: Farm.
Progress: [Farm] 100 percent complete.
Verbose: Starting object: Windows SharePoint Services Search.
Progress: [Windows SharePoint Services Search] 100 percent complete.
Verbose: Starting object: Search instance.
Verbose: Starting object: Windows SharePoint Services Web Application.
Progress: [Windows SharePoint Services Web Application] 100 percent complete.
Verbose: Starting object: SharePoint - 80.
Progress: [SharePoint - 80] 100 percent complete.
Verbose: Starting object: WSS_Administration.
Progress: [WSS_Administration] 100 percent complete.
Verbose: Notifying third parties that the restore completed.
Verbose: The IIS Web Site has been extended.  You may need to use iisreset.exe to restart IIS before your site becomes access
ible.
Finish Time: 3/22/2012 11:45:51 AM.
Progress: Completed with errors, please refer to the log file for details.
Verbose: The backup/restore process included the following objects:
    Farm\
        *[SharePoint_Config_fd325bd8-fb47-4dcb-9ac6-73d80ea6a8ba]\
        Windows SharePoint Services Search\
            [Search instance]\
                *[WSS_Search_TCHCDC02]\
        Windows SharePoint Services Web Application\
            SharePoint - 80\
                *WSS_Content\
        [WSS_Administration]\
            *[Web Application]\
                *[SharePoint_AdminContent_0cb75dd0-0251-4272-afae-56c7d41c6289]\

Completed with 0 warnings.
Completed with 2 errors.
Restore failed for Object WSS_Content_1 (previous name: WSS_Content) failed in event OnRestore. For more information, see the
 error log located in the backup directory.
-------------------------------------------------
The restore job failed. For more information, see the error log that is located in the backup directory.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 38

Accepted Solution

by:
Justin Smith earned 500 total points
ID: 37754231
So what you are doing is different than what I told you.  You are trying to do a site level backup and restore.  I had you restoring the entire database.

If you want to do a site level, don't use the -hostheaderwebapplication flag.  It should just be

stsadm -o restore -url http://whateveryoururlis -filename"path\file.bak" -overwrite

THis assumes you have already created the http://whateveryoururlis web application.
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37754254
Here's another... Used a snapshot of my server (WOOT for vmWare). ran the same backup and restore commands. This time i created a folder on the root of c: called WSSDatabase.

This time 0 warnings and 1 error....  I attached the error log for your reference.
sprestore.txt
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37754259
Sorry, i didn't see your post above... Sorry. i will try your new suggestion
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37761533
Thanks ACH1LLES, I was able to get this to work in my test lab! I am writing up my documentation/steps on how I got this done and will award your point here in a day or so when I close this out and post my results.
0
 
LVL 1

Author Comment

by:MortonTA
ID: 37791828
Here are the steps that I took to move the SP server:

New Server:
Install SP v3 taking the default setup values (did not run the config wizard at the end)
Install SP v3 Sp3 - When this finishes, the config wizard ran and I took all of the defaults and only did the basic setup for a single server. if i tried to do anything else other than the single server setup, the process would never work correctly)
Reboot

Current Server:
stsadm -o backup -url http://CurrentSPServer -filename "C:\SPBackup\SPBackup.bak" -overwrite
move C:\SPBackup folder to the New Server

New Server:
Run stsadm -o restore -url http://NewSPServer -filename "C:\SPBackup\SPBackup.bak" -overwrite
iisreset

DNS Server:
Change CName/A Records that pointed from the old SP Server to the new SP Server

Old Server:
Shutdown and decommission server

This process is actually very simple now that you helped me with the whole site restore! Thank you Ach1lles for your help!
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Article by: Leon
Software Metering within our group of companies has always been an afterthought until auditing of software and licensing became a pain point. Orchestrator and SCCM metering gave us the answer and it was an exciting process.
Technology opened people to different means of presenting information, but PowerPoint remains to be above competition. Know why PPT still works today.
Viewers will learn how to maximize accessibility options in an Excel workbook for users with accessibility issues.
The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…

912 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now