Best Practices to Decommision a Project Server Instance

[irish_archer68]

Hello, I have been asked to come up with the Best Practice Steps to
Decommission a Project Serevr Instance that has some customization to
it but is no longer being used.

I come up the following general steps, but am searching for any Best
Practice Documentation on decommissioning:

1. Backup Enterprise Global
2. Archive/Backup Database Image
3. Offload schedues into document management system (client specfic)


Are there additional steps I am not thinking about?

Please advise.

Best regards and thanks for any help on this question.

Sean

 

[Ben Howard]

Can I ask
Which version?
What other applications are on the server?
What other applications are linked in?

What information do you need to keep (projects, documents etc)

 

[irish_archer68]

Can I ask
Which version?
What other applications are on the server?
What other applications are linked in?

What information do you need to keep (projects, documents etc)
--
Thanks, Ben.http://appleparkltd.spaces.live.com/











- Show quoted text -

Thanks for the response!

We are using MS Project Server 2003.
We use WSS for Risk/Issue Management
We use the documment management feature as well.

There are not any other applications which link to MSPS (that I know
of).

I look forward to your response.

 

[Ben Howard]

I guess it all depends on what you want to save...

Definitely worth saving the schedules to mpp files.
If the risks and issues required to be kept then then I'd export them to
excel.
I'd also save any documents to a file share.

That should save all the data that you can...

Then to decommission the server, uninstall Project Server, then WSS, then
SQL or MSDE. Remember to modify the Project Pro desktops so that they are
not connecting to Project Server.

 

[irish_archer68]

Can I ask
Which version?
What other applications are on the server?
What other applications are linked in?

What information do you need to keep (projects, documents etc)
--
Thanks, Ben.http://appleparkltd.spaces.live.com/











- Show quoted text -

Thanks again for your response.

I know there is a seperate MSPS and WSS DB. If you back them up
seperately, can they be accessed at a future time or is that why you
recommended copying them to a Excel file?

Please advise and thank you again for your feedback.

 

[Ben Howard]

Now there's a question. Everything in computers is either a 1 or a 0, so you
could rebuild everything.... However, for practical purposes, you cannot
access them, hence, back everything up to Excel/Project.

 

[irish_archer68]

One more question - though having the MPP files locally would
eliminate the need to back up the Project Server DB, what is the most
'efficient' means of producing local MPP files if I have a MSPS
instance with well over 8000 schedules in it?

Is there a mpp creation utility or is simply backing up the MSPS
database and reconnecting to it in the future if required the best
approach.

AS always - thank you for your thoughts.

Sean

 

[Gary L. Chefetz [MVP]]

Sean:

We have a FAQ on our Projectserverexperts site that can lead you to a
solution for your problem. Follow the same pattern and alter the macro to
save your projects as files.

http://www.projectserverexperts.com/Shared Documents/ApplyFormulaToAllProjects.htm

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com