Archive / Archiving: MSP 2003 Server Information

[Matt Piazza, PMP]

I found several messages that address this business need to a degree and
copied one reply below from Dale Howard. The process of creating a 2nd
instance makes sense and I believe copies everything, project, documents,
risks, issues, etc.

My question pertains to what process to use after creating the 2nd instance.
Say, one month later, I need to archive another project. I can save the
project (schedule) into an mpp file with no problem. But what about the
associated documents, risks, issues, and links between tasks and documents?
Does a process exist that saves each version of the document and who created
each version, when, and with version comments?
--
Matt Piazza in Flower Mound Texas

Extracted from thread titled: Archiving Projects 10/19/04
One approach is to create a new instance of Project Server using the
EditSite tool. You might call this instance Archived or something like
that. You would need to import the existing Enterprise Global file into the
instance, along with importing the resources from the Enterprise Resource
Pool. After doing this, you can save completed projects as .mpp files,
delete them from the production instance, and then import them into the
Archived instance. Just a thought. Hope this helps.

 

[Matt Piazza, PMP]

Russell,

Since I posted my question in early December, I did discover a way to keep
access to the project documents after deleting the project. My client is now
using the procedure of (1) recording the project number of a project to be
deleted, (2) archiving the project as a mpp file to a "Archives" folder in
the Public Documents Library, and (3) deleting that project with the option
(checkbox) to delete the subweb unmarked. When they want to access documents
for the deleted project, they enter the URL for the subweb and find the
documents. When they want to see the project schedule, they access the mpp
file.

I can provide more details, if requested. ([email protected])

Matt