Archive Project and the use of EditSite

[dave]

I have read that the best approach to archive older project 2003 projects is
to create a 2nd PSArchive database, then use EditSite to setup the second
instance.

These questions are related to the above process.

1.) How do you initially seed the PSArchive database? I can create a new db
with sql server however it is pretty much empty.

2.) I backed up my original projectserver database then i restored to the
archive database PSArchive. I used EditSite and everything tests ok. I can
connect to the archive through pwa now. When i created the new site with
EditSite I did not provide any wss information. I presume that I can do that
afterwards.

How do i use this archive instance of Project 2003 to maintain historical
Project schedules and related wss sites?

I have read that i can save projects as mpp files then import into the
psarchive database however that does not bring along any associated wss
sites. How am I to maintain the historical documents in the wss site?

3.) It has been suggested to me that i need to make all the resources
project authenticated in order to maintain these resources over a long period
of time.

a) how can make all resource change from windows auth to project auth?
b) if i import a mpp from a file how do the resource information come across?

I am really sorry for the questions but it appears that i am really missing
a few pieces to this puzzly.

Any help would be very much appreciated.

thx
dave

 

[Dale Howard [MVP]]

Dave --

#1 and #2 -- If you have backed up your production Project Server database
and restored it to the archive instance, then you have seeded the archive
instance with your current Enterprise Global file, your Enterprise Resource
Pool, and any production projects currently underway. This is very good and
saves you a lot of time getting the instance set up. At this point, you
could safely delete any of the projects in the archive instance.

#3 and #4 -- To change every resource to Project Server authentication in
your archive instance, first open your Enterprise Resource Pool and check
out all of the resources. In the Resource Sheet view, insert the Windows
User Account column to the right of the Resource Name column. Select and
delete the Windows User Account entries for every resource. Save and close
the Enterprise Resource Pool and Project Server will automatically reset
user authentication to Project Server authentication for every resource.

When you finish a project in your production instance, and are ready to
remove it from the production database, begin by saving the project as an
..mpp file. Then log into PWA and delete the project. Finally, import the
project into the archive instance using the Import Project to Enterprise
Wizard in Microsoft Project Professional. Hope these ideas help.

 

[dave]

Thank you for your quick response.

Can you provide guidance on the topic of the related windows sharepoint
services sites? How do you recommend that we archive this information so
that they will be still associated with the schedules? It was our hopes that
we could maintain quite a bit of project documentation like project scopes,
estimates etc. We would need to keep this documentation in a position where
it could be easily retrieved along with the schedule.

Thank you so much.
dave