Marc
Wed Jun 29 12:22:03 CDT 2005
Yeah...this is a bad deal. Stems from bad management and no backups going on
for the production machine. Basically, this system had the AD, SPS and SQL
Server host on one box (yes, I said that was a bad idea!) and on top of that
on one harddrive that was partitioned to c: and d: When the drive failed,
then the whole thing went up in flames. I am just trying to find what pieces
are left over and where that puts me in terms of recovery.
I have a feeling that im going to need a bigger boat!
One thing that is really worrying me is the AD. Does SPS tie its users to
AD via GUID? We may be looking at a situation were we have to recreate the
users in AD and they will not match up with the users in SPS via GUID.
"Shane Young" wrote:
> How did you have so much die at once? I think you have bigger problems than
> a simple newsgroup posting can help you with. If you have specific
> questions we can try but you have a lot of broken pieces right now.
>
> Sorry
>
> --
> Shane Young
>
http://www.lucruminc.com
>
> Writing SharePoint training classes is fun!
>
http://www.sharepointsolutions.com/advinfrastructure.html
>
>
> "Marc" <Marc@discussions.microsoft.com> wrote in message
> news:89F4B316-A42C-42E9-A604-77373EC834D3@microsoft.com...
> > So, the worst has happened and a production server with Sharepoint Portal
> > has
> > gone down. This is not a project that I am involved with and have very
> > little knowledge of the site but have been asked to help restore the
> > system.
> > As it stands, I know we have the following information in backup:
> >
> > C:\Program Files\Common Files\Microsoft Shared\web server extensions\60
> > folder with all the SPS information
> >
> > A stsadmin backup from the month of May.
> >
> > Custom web parts
> >
> > We lost the AD that was on the machine and held the users and at the
> > moment,
> > it looks like the SQL Server is gone as well. I am looking into the
> > posibility that someone did a manual backup of the SQL Server at some
> > point
> > but I am running under the assumption that the above is all we have. What
> > is
> > going to be the proceedure to follow to get he system back? Steps by
> > steps
> > to follow would be helpful as I will have to hand this off to other team
> > members.
> >
> > Thanks!
>
>
>