Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Moving Sharepoint to a new server

  Asked By: Lavanya    Date: Feb 24    Category: Sharepoint    Views: 4802

I am setting up a fresh dedicated server for Sharepoint. Up to now
I've been running the trial version. As I have already done a lot of
configuration and folder security setting work I'd like to move the
whole portal to the new server. Does anyone have a document
explaining how to do it or a good link?

Also I'd like the "web links" web part to be uneditable
(no 'organize' and 'new') is there a way to do it?



10 Answers Found

Answer #1    Answered By: Tom Pruitt     Answered On: Feb 24

I will recommend using the Import/Export tools from the SPS Resource Kit


Check the workspace import and export utility.

You could also restore the WSS from a backup but I will be concerned of
issue as you are using the Eval version  of Sharepoint.

Finally you could use the package function of Office XP developer and WSS
Resource Kit (Part of Exchange 2000 utilities). (Didn't try this option yet)

As far as web  link part, you should (have verify yet) only see organize  and
new if you are an author of the workspace.

Answer #2    Answered By: Sammie Lancaster     Answered On: Feb 24

I would suggest that you developed another web  part to display the
web links. i have tried editing the "web links" web part  but to no
avail (programming skills not good  enough yet!). Will be trying to
develop a new web part myself to display web links.

Or can anybody else help out?

Answer #3    Answered By: Aron Kirk     Answered On: Feb 24

I am in the process of moving  to a new server  and I am in the
middle of exporting the current SharePoint configuration and data to an XML
file using the SharePoint Export tool. The reason I am moving to the new
server is the old one is really old: a Dual PentiumPro 200 mhz, with 500 MB
of RAM and about 32 GB of disk drive space. Because the machine is so slow,
the export process has been going now for about 20 hours or so (since
yesterday at 3:30 PM EST). Also, the resulting XML file is growing
alarmingly, to about 1.7 GBs at this point. If it gets much bigger, it will
fail as the drive space left on that drive is shrinking.

If it does fail, does anyone on the list have suggestions about making this
work better? Of course the server is the reason it's going so slow, and
there's not much I can do about that really. If anyone else has done this
before and can offer suggestions and tips, I'd be very much appreciative.

Answer #4    Answered By: Hailey Clark     Answered On: Feb 24

I faced the same problem. But it didn't happen when I
Was exporting from a server, but when importing
The xml output along with the documents to another
Sharepoint server.
Stop all the indexing service running  on sharepoint.
Make sure you also delay all the scheduled task on
Sharepoint till the export is completed.

You can see numerous sharepoint  scheduled task on the
System. Make sure you delay all this task till your
Export or import is completed.

Make sure the process store.exe is using most of the
Cpu process. If any process like dllhost.exe is
Hogging more than 60% of your resource, then it could be
The problem

Answer #5    Answered By: Nisarg Shahane     Answered On: Feb 24

You could also use backup/restore (will be a lot  faster). The only issue I
see is using the Eval version  and restoring this to a full version.

I will suggest the following alternative scenario
1. Run the Microsoft Hot fix
2. You could upgrade your test server  to a full license copy
3. backup your test server
4. Copy the backup file to the new server
5. Restore it

Although the import/export is a lot cleaner, this could work  as an

Answer #6    Answered By: Naimish Misra     Answered On: Feb 24

Actually, we have successfully done the back-up and restore. The problem was
that the source box had the service pack 1 installed but the destination
server did not. So, our server  administrator guy installed the service pack,
and then ran the restore procedure from the back up, and, voila! I have my
complete workspace on the new server. It would appear that EVERYTHING
transferred in the process, better than I expected--all documents, all
settings, everything. This is especially good  news since the old server is
now almost entirely non-functional because of the export process I started
on it. Even when you stop the export process, the HUGE XML file created
there appears to remain bound to some process. It's impossible to delete the
XML file created in this process, at least this is so if you stop the export
process before it finishes.

By the way, while the Export tool created a very large XML file, that in my
case never finished, the Backup and restore process created a file that is
about 80 percent smaller. It would seem that back up and restore is the
preferred way to move sharepoint  from one server to another.

The big lesson here: never install SharePoint portal  Server on a server
machine that does not have sufficient resources or that does not meet the
minimum requirements (or close to the minimum requirements) as defined by

Answer #7    Answered By: Terence Thornton     Answered On: Feb 24

One problem I had that was similar was solved by using a tool called
iisexport to rebuidl my IIS metabase from an different server. It is free
for one server  use.

Also, don't foget to backup your IIS metabase via the built in metabase
backup method!

Answer #8    Answered By: Alka Sarabhai     Answered On: Feb 24

I don't know if anybody else offered this, and for you it's too late, but
msdmback CAN send the backup data to a UNC location (over the network).
(Back up the old server  to a file share on the new server an use msdmback
THERE to restore.

And you're right, Portal server has a GREAT backup/move/restore
process...now if it had a better 'undelete'...

Answer #9    Answered By: Eashan Nadkarni     Answered On: Feb 24

I was also saved with the backup/restore tool a while back. It is
very fast!

While we are still on this topic, I have a question - I read
somewhere that the backup tool doesn't backup discussions. I noticed
that any customization of the dashboard, including web  parts, are not
restored. This is ok, because you just need to add these later.

Then, how about the discussions - or items in the public folder  (if
you implement Outlook OWA)? Does anyone know or write how to backup
these? I'm a little bit hesitant to use discussion because of this.

Answer #10    Answered By: William Odom     Answered On: Feb 24

Although I agree that msdmback is the preferred method to move  workspace
from one server  to the other, it doesn't offer any granularity and if you
are trying to move one workspace only, you can't.

Does anyone has any experience with Veritas Backup Exec agent for Sharepoint
? Can we backup/restore with better flexibility ?

Didn't find what you were looking for? Find more on Moving Sharepoint to a new server Or get search suggestion and latest updates.