Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Restore SharePoint 2003 Portal to another server as test machine

  Asked By: Fallon    Date: May 10    Category: Sharepoint    Views: 7236

I did search on this group and could not find what I am looking for.
I am trying to back up a production SharePoint 2003 Portal server
(single server with SQL Server 2000) and restore it to a virtual
server environment. I would like to have both server up and running
withouth conflicting with each other.

I would like to use the new restored virtual server as test machine.
According to my network administrator, they did restore to another
server but only could keep one running. When they tried to make both
co-exist in the same domain, some how both server knew each other and
generated errors.

The other questions, when I restore to a new server, I believe I
could give it a new URL so it would not conflit with the production
one, correct?

Share: 

 

9 Answers Found

 
Answer #1    Answered By: Allyson Burgess     Answered On: May 10

You can see a webcast on the premium content area of www.mindsharp.com
which will tell you how to move your portal  from one set of servers to
another (basically copy the content database and create a new farm)

If you give it a new url then this will indeed keep it separate from the
other portal and you should be fine

 
Answer #2    Answered By: Vinay Thakur     Answered On: May 10

I received from another user and followed his suggestions to use
database backup and restore  to recreate this portal  in a VM environment.

I installed SQL server  2000 and SP3a (the production is SP3), the
install Portal 2003, WSS SP2, post SP2 hot fix and Portal SP1 as
production installed.

I had three content databases restore with different name from the
original but keep SITE, PROF and SERV.

When I create a new portal with restore option and run for a while, I
received this error message:

Portal creation failed Microsoft.SharePoint.SPException: The database
schema is too old to perform this operation in this SharePoint cluster.
Please upgrade the database and try again. --->
System.Runtime.InteropServices.COMException (0x81070571): .........

There are more but I hope this is enough for anyone who saw this to
point me to the right direction.

 
Answer #3    Answered By: Elaine Mack     Answered On: May 10

You will get this error if the destination machine  does not have the exact
number of patches as the source machine. Check the version of wss and sps and
make sure they match and then check the patches installed.

 
Answer #4    Answered By: Baiju Hoskeri     Answered On: May 10

The exact patches you mentioned includes OS patches or just WSS and
Portal patch?

I checked the production machine  and saw both WSS SP1 and WSS SP2 and
I only added WSS SP2 to the VM. I should go back and re do SP1 and
then SP2?

 
Answer #5    Answered By: Kristy Hicks     Answered On: May 10

The same error happen to me recently
the fix:

There is an update that you have to remove, the hot fix for the daylight
savings time is the one you have to remove.
Hope this solves your problem.

 
Answer #6    Answered By: Alisha Itagi     Answered On: May 10

Thank you so much for this reminder. I thought I added the post-SP2
fix to VM but forgot.

Now I have it create successfully.

 
Answer #7    Answered By: Carey Everett     Answered On: May 10

Another question after portal  created.

I believe I have to copy the whole 60 hive from production to this VM
to replace existing to make it works? Since no pages are able to open.

 
Answer #8    Answered By: Anuj Lakhe     Answered On: May 10

Clearly you will need to install sps on the vm to have sps on the machine  or all
you will have are some sql databases.

 
Answer #9    Answered By: Lee Dickerson     Answered On: May 10

I did have SQL Server 2000 SP3 and SPS 2003
installed to created this portal  by restoring it. You mean I have to
redo the installation or portal creation?

 




Tagged: