Installing SharePoint 2003 And Restoring a Backup
For the purpose of this guide I’m going to assume that you own a copy of SQL Server 2000 or SQL Server 2005. I don’t recommend using the MSDE engine due to its severe limitations. Any organization no matter how small has the ability to reach MCDE’s database size limit. Just don’t use it.
- Install IIS6, .NET 2.0 Framework, and ASP.net and reboot
- Install SQL Server 2000 and reboot
- Install SQL Server 2000 Service Pack 4 and reboot
- Start SharePoint setup wizard and accept all defaults up to that Database Selection screen. Pick Install Without Database Engine. You do this because you already have SQL Server 2000 installed
- Under the Account Information screen type the credentials of the current local administrator (RECOMMENDED: If you like to harden your installs, read the Microsoft guide and only assign the minimal necessary permissions for SharePoint services to run under)
- Finish the main setup and reboot
- Install the latest SharePoint 2003 service packs, rebooting after each one
- Launch the SharePoint Central Administration and you will be greeted with the friendly blue Configure Server Farm Account Settings screen. Use the same credentials you used in step #5. Again, feel free to harden.
- Next you’ll see the Specify Configuration Database Settings for X. Choose the Create configuration database option and click OK
- On the next screen, fill in your contact information and proxy settings
- The setup will bounce you back to a general screen. On this screen in the bottom right you’ll see a Configure Components button. Select that.
- In the Change Component Assignments screen, check all options under Component Assignment and select your server under the Job Server Component
- Open the SharePoint Portal Server 2003 Backup and Restore and select the Restore tab. Select your manifest file, select all components under the restore, select Edit on the right side and accept all defaults.
- Start the restore and if it doesn’t error out right away then just walk away for a few hours because it may be a while.
Installing SharePoint Portal Server 2003:Once the restore is complete, your server is back. Now all you have to do is figure out the 1,000 errors which prevent it from working properly. I could go over all of them but that would take entirely too much time. Good luck.
2008-01-18 Update: I’ve recently had the pleasure of playing with SharePoint 2003 on almost a daily basis. Let me just say that if you’re doing a SharePoint install, make absolutely sure that you have at least 100 GB on your C:\ drive. While I didn’t deploy the current SharePoint server at my workplace, having a limited space on my root partition really made things very difficult for me.
July 9th, 2008 at 11:29 am
What is the best way to automate a Sharepoint 2003 backup free or cheap of course.
Anthony
July 9th, 2008 at 3:45 pm
It all depends on just how automated you want the backup to be. If you’re OK with purchasing a USB drive and backing up to it throughout the week and then taking it offsite, then you can easily set that up.
The automated backup process itself is fairly simple. I’ll write a post on how to do it in the upcoming days.
September 25th, 2008 at 9:26 am
I have the SQL 2000 server installed on the same box that I will be installing SharePoint 2003 (eventually this will be upgraded to 2007). Do I select Server Farm or Typical? If I select Typical will it give me the option to not install the WMSDE and then specify the database later as described by the friendly blue Configure Server Farm Account Settings screen above?