This post comes to us courtesy of Mark Shea of our Office Assistance area.
This post will guide you through the Microsoft Office Project Server 2007 backup and restore process by using the the SharePoint Central Administration Web site.
If you do not already have a remote file share to store the backup files, you must set one up before backing up your environment.
Set up a remote file share
Note The central administrator pool and the Timer service use the same user account.
Note If you receive any errors during the backup or restore process, you must delete the failed “Backup/Restore” timer job before you can run the next backup or restore process. The URL for the Timer service jobs is:
Note You do not have to delete the Timer service job if you did the Project Server 2007 backup or restore by using the stsadm.exe command-line tool.
Note The server farm should be taken offline prior to backup.
To back up your Project Server 2007 installation, do the following:
This section guides you through the Microsoft Office Project Server 2007 restoration process using Central Administration. It describes how to restore over the original server farm. This document does not describe a migration of Project Server 2007 data.
My name is Dave Ducolon and I am a Program Manager for Microsoft Office Project/Project Server. It is my pleasure to write about and to discuss Resource Management and other related topics for the 2007 release.
Resource Management is at its best a hard job. And at the core is Capacity Management and Planning. As most of you know, the trouble is that while people or “work resources” are not a commodity such as bricks or lumber, neither are they fixed assets (ones with unlimited capacity). And if that doesn’t make Resource Management difficult enough, work resources can be augmented with external resources such as consultants or subcontractors. We on the Project team at Microsoft not only understand this challenge we experience it the same as anybody else that does project based work.
In 2007 we have taken significant steps to help mitigate the inherant difficulties of managing resources whether they are People, Material or even costs. Today I will give you an overview of how we see the Project 2007 system being used to accomplish this. This is a brief, yes very brief overview of some of the Resource Management features that will help you manage your resources end-to-end. In later posts, I will dive deeper into features.
To begin with, it is best to model organizational capacity and then to work on tactical level assignments. Generic resources, a legacy feature, are ideal to represent your organizational capacity as it pertains to resource capabilities. Then as work gets approved you can allocate these generic resources to a new 2007 feature in Project Server 2007 called Resource Plans.
Resource Plans allow you to manage resource needs for a project without requiring any task level detail. Then as the project and work become better defined you will be able to convert these Generic Resource Plan assignments into Resource Plan assignments for real employees. At which time you will undoubtedly need to view availability and verify that individuals do not get over scheduled.
Resource Leveling, a legacy feature, can be used to automate the task of managing allocations of work to individuals or you may want to make use of the Resource Availability graph, a legacy feature, in Project Server. Regardless of which method you choose, you will undoubtedly move on into the execution phase.
For this phase Project Server 2007 delivers functionality that allows customers to separate the effort spent on a project and its tasks from the actual work performed. Effort is normally what team members think of when they are reporting their progress on a task. It is not uncommon to hear people say “I am 60% complete and should finish by Friday”. This does not mean that they will use every available minute between the statement and Friday to complete the work and it also does not mean that they spent exactly 60% of the scheduled work for that task. Instead it means they have spent 60% of the effort they feel is needed on the task and that the other 40% should be able to be accomplished by Friday. Team Member Task tracking in Project Server has been able to capture that information since we first released Project Server back in 2000. In 2007 we have delivered a separate timesheet that allows team members to report their actual hours worked whether that be on a Project or on a specific Task.
It is through use of these features that you will be able to more accurately plan, estimate, track and manage your resources time and thereby improve your ability to manage resources. In my next Post, I will present and review the Resoruce Plan feature.
If you are interested in writing reports over the Project Server 2007 reporting database, Jim Corbin has published some documentation on the database. You can find it here: http://blogs.msdn.com/project_programmability/archive/2006/12/05/reporting-database-diagrams.aspx
I wanted to let the regular readers of this blog about a change in blog stewardship.
GOOD LUCK!Lidiane has relocated to Boston from Redmond for personal reasons and has joined another Microsoft team there. We wish her well and thank her for her great work on Project 2007 and the Project blog. As a result, she has passed on the blog coordination role to me.
INTRODUCTIONMy name is Treb Gatte and I'm also a Program Manager on the Project Server team. I've been with Microsoft a little over a year and have been a Project Server user since Project Server 2002 Beta.
One of our goals is to increase the number and regularity of posts such that you receive a steady diet of updates and new information. If there's a topic you would like to us to address, please add your request as a comment to this post. I can't guarantee that every submitted topic will be addressed. However, we can't improve our targeting unless we know what you, the reader, needs. Please spread the word about our effort.
EXPECTATIONSI feel it's very important that we inform you of some ground rules going forward.
LINKING.I wanted to address linking expectations from the Project blog, before I receive a request to link to someone’s site. You can use this as a general guideline for the Project Blog and the Programmability blog as our team does both.
You will note, as a service to our readers, we provide a list of Project Community Blogs. These sites were placed here as a result of web searches and not as a result of linking requests. These are blogs or sites which have created content that is freely shared with the Project Community. Most of these sites are either created by Microsoft employees or by our Project MVPs. A great deal of these authors also participate on the UseNet in performing community support for the Project forums there. Consequently, they are viewed as a valuable community resource.
If you have a Project related site and you wish to have us link to you, make it easy for us to find you. You will need to have freely available content that would be of interest to the Project community. You should also practice generally acceptable blogging practices of tagging such that your site will appear in a Technorati or other Blog related search engine. Finding you is worth one hundred requests to link to you.
If you are selling something in addition to the content, please note our link will be to the free content. Otherwise, we could be seen as endorsing your product/service/etc. which we simply can't do. As this process is subjective, we will be very conservative in our linking. If there's any doubts on our part, our default response will be to not link.
EMAILAs I'm now receiving all of the incoming email and trackbacks, I have a simple request. If you have a comment or question, please post it as a comment to an existing post. Many of the emails that I'm receiving are on topics for which I either can't answer or shouldn't answer. If you post your question as a comment, you can draw upon the wealth of Project community that visits the site for a more timely answer.
Again, thank you for your readership! Stay tuned as there's much more content to come.
Here's a couple of emails that were received that may be of interest to others.
We received a query regarding how to upgrade from Windows SharePoint Server 2.0 to Microsoft Office SharePoint Server(MOSS). As you should install MOSS prior to installing Project Server, you'll want to first upgrade your existing WSS content to MOSS.
I asked around and I was pointed to this article: http://technet2.microsoft.com/Office/en-us/library/b3e52231-16bf-4a46-a7e8-cb31b814627a1033.mspx?mfr=true There's a section on migrating from WSS 2.0 to MOSS.
The configuration can be found here: http://support.microsoft.com/kb/921116/en-us Yes, it is the same steps as you had to do for Project Server 2003. These steps are specific to the SQL Server version. Please make sure you follow each step carefully.
Then, for each client machine that will be using or creating Portfolio Analyzer views, have the Analysis Services 2005 (9.0) OLE DB Provider installed. http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en
UPDATE: Brian Smith of http://blogs.msdn.com/brismith fame pointed out there were two missing points to this section.
First, the account owning the SharePoint Timer Service is what is used to build the cube. Therefore, that account will need access to the Reporting Database.
The second point is for those workstations creating and accessing Portfolio Analyzer views. If they are using Internet Explorer 7, the setting to allow cross domain data access is disabled by default for Trusted Sites. So, you will need to change this setting when you add the server to the trusted sites section.
I've been meeting with Phil Smail, fellow program manager and resident Project Server security guru, on laying out the Project Server security configuration for a Project Server 2007 instance within Microsoft.
I was fairly familiar with the Project 2003 Security functionality so I knew basically what I wanted. However, it quickly became apparent to me that are several new and changed security functions in the new release. So, off to MSDN for a little light reading.
The following security article, which was written by Phil, provides a nice overview of the 2007 functionality. If you are looking to upgrade to or implement Project Server 2007, you might want to take a look at this article also.