Re: Need help moving Sharepoint Portal & Content from Server A to

Greg,

I am not aware of the issue with SPSBackup.exe and SQL 2005. We are
thinking about upgrading to SQL 2005 sometime next year. Hopefully someone
can help so that I know what to expect also or do when we do upgrade to SQL
2005.

"Greg" wrote:

Thanks for taking the time to write that out for me. I was able to utilize
the spsbackup.exe for backing up the old server, but unfortunately there is a
known issue with spsbackup.exe and SQL 2005 when performing the restore. So
my options are extremely limited as to how I am able to put my data back.

Any ideas...?

Thanks

"chang" wrote:

Hello Greg,

Here's what I did:
-------------------------------------------------------------------------------------------------
1) Install OS and applied updates

2) Install SQL Server 2000 and SP3

3) Install SPS 2003 and WSS 2.0 and update SP1 (make sure it's same as old
server. So if you haven't update from old server, don't update SP1 or SP2 on
new server).

4) Use the Backup and Restore utility from Sharepoint to backup database.

5) Copy the folder "60" if you did any modification. Also make sure you
copy the web.config file in your Inetpub folder.

6) From the new server, go to Sharepoint Administration and delete the
portal by going to "List and Manage Portal sites".

7) Delete the 3 databases (manually) or follow Lutt's steps: Central
Admin->WSS->configure virtual server settings->Select your
server->manage content database. (Note: Leave configuration database intact)

8) Go to the Backup and Restore tool and do a restore.

9) Browse to the XML file-->click on Edit Parameter

10) Make sure you specify the IIS Virtual Server and same database names.
(I get an error, but regardless i continued) Reset when done restoring.

11) Go into Sharepoint Administration and Create a Portal Site

12) Click on "Restore a Portal" and type in the databases. Example
NewSite1_SITE,
NewSite1_PROF, NewSite1_SERV.

13) Replace the "60" folder with the one you copied over from the old
server and also replace the web.config file if you made any changes to that
file.

14) Reboot.
-------------------------------------------------------------------------------------------------

That seems to work for me. Your step 5 that you list "use SQL 2005 to
restore the databases", try using the Backup and Restore utility to restore
the databases.

Let me know if you are stuck in any of the steps or needs clarification. It
took me a while, but what a relief to finally get it to move. Otherwise it
could take me weeks trying to rebuild the portal due to so much customization
involve.


"Greg" wrote:

Chang - I am not able to get the "exact" replica of what I lost. I have all
of the data, but maybe I am unclear as to a "step-by-step" procedure for
restoring the site, data, etc. Here is what I have done:

re-build the OS
install IIS
install SQL
install Sharepoint
use SQL 2005 to restore the databases
configure sharepoint topology
restore portal via the sharepoint utility and point to IIS default site

...and I got nothing, even though I can look at SQL and see the data in STS,
etc.

Thanks in advance for any help you are willing to provide!

Greg

"chang" wrote:

Thanks Lutt. I deleted the databases manually from Enterprise Manager, but
was able to get it to work regardless of the error. Not sure what difference
this will make in the future. What I did after I deleted the Portal from
Sharepoint Administration and then manually deleted the 3 databases from
Enterprise Manager, I was able to do the restore but with the error. However
I went and recreate the portal and point to those databases. Reboot the
server and everything is there how I want it to be. An exact duplicate of
the portal within the old server.

Thanks again for your help.

"Lutt" wrote:

Did you delete the content database using SharePoint central admin
page? You cannot delete them from sql manager.

Central Admin->WSS->configure virtual server settings->Select your
server->manage content database.

Ting
chang wrote:
Thanks for the fast response.

Did as you suggested. Deleted the new portal from Server B, and then delete
the 3 databases. Did a restore and all seems good. Then half way through
the process I get the error. "ERROR: Exception of type
Microsoft.SharePoint.Portal.Insatll.DuplicateDirectoryException was thrown."

Any ideas?

"Lutt" wrote:

At step 5, you need to delete the new portal on server B, then Delete
content database instead of detach them.

Ting

chang wrote:
I need help in moving Sharepoint Portal from an old server (Server A) to a
new server (Server B). I had tried moving it to a test machine without no
success. I had followed many documentation on how to move databases from the
old server (Server A) to the new server (Server B), but the problem is that
Sharepoint keeps telling me that the database I had is different.

Here's the step that I had done so far:
1) Install SQL Server 2000 and update to SP3 on new server (Server B)
2) Install SPS 2003 and WSS 2.0, update to SP1 (Old server has SP1)
3) Backup the files from "C:\Progrm Files\Common Files\Microsoft Shared\web
server extensions\60" and any files that I had modified from old server
(Server A)
4) Use SPSBackup.exe to backup the entire Portal and WSS site collections
(Server A)
5) Detach databases NewSite1_SITE, NewSite1_PROF, NewSite1_SERV from new
Server (Server B) that it has created when first going to Sharepoint
Administration page
6) Go to Sharepoint Backup and Restore utility to restore Portal and WSS
within new server (Server B)
7) From Restore tab, browse to XML file to do the restore
8) Go to edit parameter for new server
9) No IIS Virtual server available.

This is one way I try to move the portal and databases. So when I get to
step 9, since there's no virtual server I can't do anything else here.

Other steps I had taken is detaching the databases from old server and
attaching it to the new server and then go to Sharepoint Administration from
new server and try to set the databases content and virtusl server settings,
but still no luck.

Anyone that has successfully move one portal from an old server to a new one
including databases and branding of portal, please help me out? I'm pretty
sure there is something I must be missing, because no matter what I do, I
always end up with some kind of errors.

Thanks in advance.




.

Relevant Pages

  • Re: Side-by-side upgrade - moving master, msdb and model
    ... MVP - Windows Server - Clustering ... "In some cases, you may want to copy the system databases, including ... from the source SQL Server 2000 instance to the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: BizTalk Server 2004 ConfigFramework.exe error
    ... one BizTalk is installed on? ... machines (both for SQL and DTC) is not blocked by firewalls and new MSDTC ... Multi-computer configuration using Windows Server 2003 or Windows XP ... >>all associated databases. ...
    (microsoft.public.biztalk.general)
  • Re: AS2005 ... what is wrong with it?
    ... What I have seen is that the dev server is *faster* than the prod server ... And does your dev server also have all 6 databases with all these roles? ... When I restore the "PROV" i got approx 20 sec. ... Starting from an empty data folder should show if this theory is true ...
    (microsoft.public.sqlserver.olap)
  • RE: Clustering a standalone SQL server + storage array
    ... working as expected with out error your ready to install sql server. ... log files to the data and log shared drives you setup as part of the cluster. ... Our apps team look after a trading system that uses an HP DL360 server ... running SQL 2000 SP3a with a few small databases on it. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Side-by-side upgrade - moving master, msdb and model
    ... MVP - Windows Server - Clustering ... "In some cases, you may want to copy the system databases, including the ... from the source SQL Server 2000 instance to the SQL ...
    (microsoft.public.sqlserver.clustering)
Quantcast