Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Rebuild server - tips on migrating?

Asked By: Christopher Scott Date: Oct 25, 2009 Category: Sharepoint Views: 417

I've been encountering a lot of stability and usability problems on our
Sharepoint server, which are detailed below. I've "sold" the company on
Sharepoint and many people love it and would like to embrace it more, but
it's been so unstable. Their first complaint of course is speed, but I
already have it on a 4-CPU box w3GB RAM and I think everyone agrees that SPS
is just slow (anyone get < 5 seconds on initial page load?)

So, I want to backup are current workspace, install new SPS on a new box,
SP1, install tweaks and such, customizations, restore the workspace, test,
and then rename the box to the old name. Is there anything major I need to
know before doing this?

Key points:
- New server will be physically identical except 4GB RAM
instead of 3GB RAM. The disks might also be faster
disks spanned on more controllers, but the drive letters
and mount points will be the same.
- Current server is SP2; new will be SP3
- I want to enable an extranet workspace - should I do it
before restoring the other workspace? I currently do not
have an extranet. I want to use extranet and SSL.

Tagged:rebuild server tips on migrating

3 Answers Found

Answer #1 Answered By: Kamal Mayachari Answered On: Oct 25, 2009

You may already know this but use the MSDMBack.vbs script to complete
your Sharepoint Backup and Restore.

Just out of curiosity, how many Sharepoint users are you supporting?

I support a small group of about 50 users and I have no where near the
server horsepower you've described.

Answer #2 Answered By: Kelsie Terrell Answered On: Oct 25, 2009

Does anybody know if SharePoint uses more of the processor or more of
the memory during the backup and restore process? I need to account for
the hardware configuration.

Answer #3 Answered By: Puneet Shiwde Answered On: Oct 25, 2009

I have < 100 users. I'd say only 20 people really use it right now, and
probably only an hour or two during the day each. The system is very much
NOT used. I index a couple content sources (file-based, mainly).

Sharepoint is the slowest thing I've ever seen. My best case ever is 5
seconds for initial page loadup. Copying files, doing pass profile changes,
searching ,etc -- it literally feels like I'm running this on a 50Mhz 386
sometimes.

Of course, when I'm on the box itself (termserv or console) or running other
things like filesharing or the other IIS web pieces running on the box, it's
a workhorse.

Didn't find what you were looking for? Find more on Rebuild server - tips on migrating? Or get search suggestion and latest updates.