Board index BackOffice Server

Exchange and Recovery

Exchange and Recovery

Post by S.H.F » Sun, 31 Dec 1899 09:00:00



If anyone can help me with this it would be greatly appreciated...
Situation:

I had a SBS server go down....no repair disk available....the customer
reloaded to a winnt directory and only got through the nt setup.  when I
finally got onsight, I reloaded back onto the winnt.sbs directory.

Everything seems to have loaded okay accept.  I cannot restore my backups
of Exchange Information Store....priv.edb and pub.edb.  I'm getting an
error when I run the isinteg -patch program.  The error goes like this...

the private store could not be updated.
DS_E_INSUFFICIENT_ACCESS_RIGHTS

I believe this problem has to do with the reload process and the way my
GUID and SAM files are now as compared to the way they were.

Is there any way around this problem?  I do not have a BDC on this network.
 I do however have a fairly large Information Store that I would like to
recover.

Thanks
John

 
 
 
Top

Exchange and Recovery

Post by Michel Bordelea » Sun, 31 Dec 1899 09:00:00


Not sure if this'll help your particular problem, but you do have to make
sure that your exchange server has the exact same site and organisation name
as on the backup.

--

Michel Bordeleau (MVP-SBS, ClubWin Team4 Captain)
IS Manager
Healthcare Information Technologies

http://www.hit-teleservice.com
(514) 932-3232


Quote:> If anyone can help me with this it would be greatly appreciated...
> Situation:

> I had a SBS server go down....no repair disk available....the customer
> reloaded to a winnt directory and only got through the nt setup.  when I
> finally got onsight, I reloaded back onto the winnt.sbs directory.

> Everything seems to have loaded okay accept.  I cannot restore my backups
> of Exchange Information Store....priv.edb and pub.edb.  I'm getting an
> error when I run the isinteg -patch program.  The error goes like this...

> the private store could not be updated.
> DS_E_INSUFFICIENT_ACCESS_RIGHTS

> I believe this problem has to do with the reload process and the way my
> GUID and SAM files are now as compared to the way they were.

> Is there any way around this problem?  I do not have a BDC on this
network.
>  I do however have a fairly large Information Store that I would like to
> recover.

> Thanks
> John


 
 
 
Top

Exchange and Recovery

Post by Darryl Pool » Sun, 31 Dec 1899 09:00:00


I'm not sure if you are starting with a fresh new copy of SBS, if so you
will have to follow instructions in this article for restoring only
information store because the service account is now different. I had to do
this exact same procedure last weekend. Here is the article

Article ID: Q170810

 
 
 
Top

1. Exchange Recovery Woes

*sigh* I think I got myself into some hot doodoo here.

A company that I used to work for has a SBS4.5 server. Recently the power
went out. When the power came back on and they went to turn the server back
on, it wouldnt - turns out the power supply died.
So they purchased a new power supply and installed it. When they brought the
server up, Exchange wouldnt come up. The guy then noticed that the drive
that the database files were on wasnt showing up in the drive list. So, he
shut the box down and saw the drive not connected (data wise). It was then
reconnected and the box powered back on. Well feces hit the fan and Exchange
didn't like the database anymore.
So he did some of his own research and backed up priv.edb and pub.edb and
reinstalled exchange and got the place back up and running without their old
email/contacts.

He then got in contact with me to see if I could solve the problem.

I went in today and ran ESEUTIL /P  to repair the database files.
I then ran ISINTEG -FIX on the database files afterwards. When the utility
hit step 5 or close to scanning the priv.edb file, it dumped out and
reported the following error: JET_errObjectNotFound.

I checked the integrity of the files and they turned out ok. I also used the
/mh switch (forget what that does exactly at the moment) and it reported
that the database files were consistent (they werent initially before I
started the repair process).

So I ignored the error and ran the ISINTEG -PATCH and reported the same
error.

So I ignored THAT error and tried to start the remaining stopped Exchange
services and it came back with Error 1011.

Does anybody have any suggestions on how to get everyones mail and contacts
back? I do not have a backup to lean back to (i know....*tsk tsk*)

Any help would be extremely appreciated. There are a lot of people crossing
their fingers for me.....

Russell

2. Sort by name doesn't stick

3. Exchange recovery from SBS 4.0

4. New upload to atari.archive

5. Exchange Recovery and Q272570

6. Busted Exchange

7. UPDATED: Exchange Disaster Recovery in a nutshell version 3.0!

8. IN NEED OF HELP!!

9. Documenting Exchange for Disaster recovery

10. exchange recovery

11. Exchange disaster recovery ?

12. Exchange-Server Database-Recovery

13. Exchange recovery


All times are UTC
Board index