Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Problem with restoring the site

  Asked By: Gaurang    Date: Sep 23    Category: Sharepoint    Views: 983

I need to shift my entire site from one server machine to another server.
For this i used the "sharepoint portal server backup and restore" from program
files and took bakup and after installing everything in another machine i tried
to restore the backup in that machine.i was able to see that site in the
database (sqlserver 2000) in sites table. But my url contains eg:
"http://<ipaddress of my old machine>:8081/sites/<site name>".

This is not able to open and my doubt is "will the ip address change if we
restore the site in another machine"

what are the actual steps to follow for restoring and opening the site?



8 Answers Found

Answer #1    Answered By: William Odom     Answered On: Sep 23

Try backup  and restore  option in sharepoint  designer

Answer #2    Answered By: Mia Scott     Answered On: Sep 23

The best way to restore  sites in sharepoint  is to restore them via
command line using stsadm.exe. Go to a command prompt and run
stsadm.exe from c:\program files\common files\microsoft shared\web
server extensions\12\bin and type stsadm.exe -o backup  and press
enter. You will see the command line switches to use.

Answer #3    Answered By: Kristian Chaney     Answered On: Sep 23

Detailed info is avaliable from MS-


Answer #4    Answered By: Alicia Scott     Answered On: Sep 23

Thanks for the best option given..but my doubt is when i take a back up in one
machine containing one localhost/ip in the url ..and now try to restor it in
another machine  containing another domain/localhost /ip will my url change and
by what url name is my restored site  save / created...
Do i need to recreate the site after restoring  with the backup  information?

Answer #5    Answered By: Mike Lamb     Answered On: Sep 23

Make sure that the both environments are identical in terms of version
and service-packs.

You can also backup  / restore  using Central Admin. I prefer Central
Admin over STSADM because restore options are supplied in a web-form
instead of having to enter in command-line mode. Remember to put
MySites under different port to MOSS site  otherwise you'll get errors
if you're using this method.

To make it even easier you can change the URL of the site and SQL
Server by editing the backup.xml file in the backup folder before

Forgot to mention: You do not have to edit the XML file but it makes it
easier because you can search / replace old server  names with new ones
and repeat several times. I'm not sure if this is the recommended
approach but I find it easier.

I'm assumming you are doing this using MOSS 2007.

Answer #6    Answered By: Jose Scott     Answered On: Sep 23

Atlast i sucessfully retored my site  to another using the command-line
technique.Thanx for the reply..I'm currently using SPS 2003 not 2007.
But i one experince problem  ..the dynamic webpart i developed are not
restored to another machine..i agian need to copy the required dll's and dwp
files to another machine..
Can i find any way to solve this or i have to obey the preocess?

Answer #7    Answered By: Taylor Clark     Answered On: Sep 23

You cannot restore  WebParts. Most of SPS content is held in databases
but not WebParts and related resources / files. The recomended
technique is to backup  the SharePoint folder (known as '12' hive in
MOSS) also so that one can restore everything correctly.

If the WebParts are developed correctly then installing  them should
not be a problem.

Answer #8    Answered By: Anthony Rutledge     Answered On: Sep 23

Also back up web.config files because some WebParts require config
info stored in them (you might require those config values).

Sometimes WebParts deploy DLL files into C:\Windows\assembly (also
called the GAC) and therefore it's always a good idea to install them
instead of backup  / restore.

Didn't find what you were looking for? Find more on Problem with restoring the site Or get search suggestion and latest updates.