16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

782 Part IX: Maintaining a Server in Windows SharePoint Services<br />

Note If you have removed one or more of the installation prerequisites, you<br />

cannot repair the client components unless you disable the prerequisite check.<br />

You can disable the prerequisite check by adding DISABLEPREREQ=1 to<br />

the comm<strong>and</strong> line. To disable the prerequisite check in the preceding example,<br />

you would type E:\Client Files\setup” /f “E:\Client Files\SPSClient.msi”<br />

DISABLEPREREQ=1.<br />

Uninstalling SharePoint Portal Server<br />

If everything fails <strong>and</strong> SharePoint Portal Server is damaged beyond recovery, you<br />

can always remove SharePoint Portal Server. To fully remove SharePoint Portal<br />

Server, you must remove the following, in this order:<br />

1. SharePoint Portal Server<br />

2. Windows SharePoint Services<br />

3. SQL Server Desktop Engine (if installed)<br />

4. Backward-compatible document library (if installed)<br />

5. Internet Information Server (IIS)<br />

Warning Most files <strong>and</strong> subfolders located in installation folders will be<br />

removed. All <strong>Microsoft</strong> SQL Server databases will be detached, but not<br />

removed, from the database server. When you remove SharePoint Portal<br />

Server, all user data is left in the database files. These files are also<br />

left behind if you remove SQL Server Desktop Engine or <strong>Microsoft</strong> SQL<br />

Server.<br />

Writing a Disaster Recovery Plan<br />

You should write a disaster recovery plan that provides timely, accurate, consistent,<br />

<strong>and</strong> reusable solutions for emergency situations. Executing a consistent recovery plan<br />

in case of emergencies helps avoid wasting time, resources, <strong>and</strong> money, not to mention<br />

preventing a lot of stress. A disaster recovery plan should reflect a well-planned<br />

data protection strategy based on your customer’s specific data protection requirements.<br />

The primary objective of disaster recovery is to minimize downtime by providing<br />

the most reliable recovery plan to restore data in the event of a server crash,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!