Titanic WSS3.0 problem... recovering sites w/o old AD it was setup on

By PharCry ·
There is a server running 2003 R2 Standard, Windows Sharepoint Services 3.0 and SQL Server 2005. Long story short, the domain had one DC with all AD information and it decided to crash BOTH system drives (RAID mirror config) over the weekend, thereby stranding users trying to login to the Sharepoint site.

At this point it would just be nice to get some of the information back that was stored on the site, if not actually regain full access (although I'm growing more and more doubtful of this happening).

So I guess my question is how to I regain access to the sites that had AD user authentication or how can I recover any data from those sites in SQL server?

Also note that WSS and SQL are not my forte, I'm simply posting this up as no one else here has sought outside help yet. It may take me a little while to check back in here but ANY help would be appreciated. I'll be glad to provide any further info that is required.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

if both hard drives died at the same time

by CG IT In reply to Titanic WSS3.0 problem... ...

and you don't have a recent backup, gotta pay the big bucks to get the data.

but if you have recent backups, simply do a restore from backup although restoring Sharepoint from a backup from NTBackup or BackupExec often doesn't work. Sharepoint is weird that way because it's a web site. and restoring IIS from backup doesn't always restore the site. many backup the sharepoint web site seperately.

But you ought to get everything else back up to the time of the last backup.

Collapse -

Recover just data?

by PharCry In reply to if both hard drives died ...

I was afraid of that, but is the data held in the SQL DB still accessible? The site layout and everything we're not that concerned about, mainly documents and a sort of timesheet area (fill out a form with customer info, etc, and it's added into the site). If we can just get access to that stuff it would be enough.

Just to be clear, the server that crashed is not the one WSS or SQL were on, that server is still fine. The one that crashed was only a DC with a few other services being used (I do realize how drastic it is to lose all AD info though). I can still access the Sharepoint Central Addmin site (via the server's local admin logon info), but can't make any changes to the old domain admin account or login to the the site we are trying to get into (although it shows up in the application pool area of the admin page).

So if there's even a convoluted way (ie hacking UID info in WSS to grant access to another user) it would be better than nothing. Just want to make sure all the bases are covered here before making a final call.

Also, when you said paying big bucks to get data recovered, are you referring to HDD recovery or some sort of service/software that will pull the info we need from SQL or get the Sharepoint site back up?

Thanks again for the assistance.

Collapse -

Big bucks was referring to data recovery.

by seanferd In reply to Recover just data?

As far as accessing your other servers with the domain down, I hope someone has a good idea.

Collapse -

insufficent information on DC and Active Directory

by CG IT In reply to Recover just data?

if your domain controller crashed, then you need to get a domain controller back on the network.

What services are hosted on the domain controller besides the server simply being a domain controller?

You do not want to go in to sharepoint and change admin accounts or passwords, nor the same with SQL. Active Directory controls the accounts and that is the domain controller. Changing SA & admin accounts and passwords to some other account that is not in active directory will set permissions differently than those established in active directory. To go through and reset all permissions is a pita.

Also, what server is IIS for sharepoint hosted? if sharepoint is hosted on a server somewhere [not the DC] then the web sites and web parts files should be accessible as well as documents uploaded to the sites

Best course of action is to get the domain controller back on the network.

Collapse -

Some more data

by PharCry In reply to insufficent information o ...

We have a new DC in place already, new domain, etc. As far as IIS it was being hosted on another server so all in all, IIS, WSS and SQL had no pieces hosted on the original DC. If it is indeed possible to somehow log into the site in question that would be great(I've tried local admin and new domain admin accounts but neither have worked, assuming because domain has changed). The local admin password on SQL gets me into the central admin page but not the site our data is on.

If having a new domain setup (same name, but obviously the old server kicked the bucket) will affect access let me know. Thanks again

Collapse -

no new domain

by CG IT In reply to Some more data

if you have backups,restore them to the new server than only has the base operating system installed eg if this is windows 2003 server you simply install windows 2003 server, then from there, do your restore.

if you create a new domain, you lose all security identifiers therefore workstations have to be joined to the new domain, user accounts will have to be create then profiles migrated and all your security on SQL, and sharepoint will have to be redone [meaning that if SQL was a member server of the old domain, then you have to join it to the new domain which you then lose all account prvileges [so reset all the local machine server passwords before you reboot after joining the new domain].

seriously, if the DC takes a dive, get new hardward, install Windows Server operating system, then restore from backups [ far far less headache than having to recreate everything from scratch].

if you didn't do backups, well ooops but know you know why backups are necessary in an Active Directory domain.

note: if sharepoint IIS is hosted on the SQL server [why??] then everything done on sharepoint is on the SQL server. you just have to search the HDD for the files you want. WSS I wouldn't even worry about. I'd actually just start from scratch. maybe more work, but it's a lot more work trying to recover or fix the existing install than just reinstall WSS, sync with Update, configure and have workstations register.

Related Discussions

Related Forums