I'll keep that in mind. As it turns out, a rebuild of
exchange from scratch and PST imports may be in order.

What is PSS? (Pardon my ignorance)

Cheers
--- Great Cthulhu Jones <[EMAIL PROTECTED]>
wrote:
> FDISK and reinstall's always been kind to me. Your
> mileage may vary.
> 
> What did PSS say?
> 
> (:=
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On
> Behalf Of Darrkon
> Sent: Tuesday, August 27, 2002 10:15 PM
> To: Exchange Discussions
> Subject: RE: Exchange Disaster Recovery Issues
> 
> 
> A brilliant deduction!
> This leads to my next question
> 
> "How do we fix it???"
> 
> Cheers :)
> 
> 
> --- Great Cthulhu Jones <[EMAIL PROTECTED]>
> wrote:
> > Probably whatever made it crash in the first
> place.
> > 
> > (:=
> > 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Darrkon
> > Sent: Tuesday, August 27, 2002 7:08 PM
> > To: Exchange Discussions
> > Subject: RE: Exchange Disaster Recovery Issues
> > 
> > 
> > We will definantly stop OST users from getting on
> > the
> > exchange server until a PST dump has been
> performed
> > from their OST file.
> > 
> > Just further to this issue.
> > 
> > The damn thing started working and saved us
> > rebuilding
> > the whole exchange server using PST export/import
> at
> > 7pm on a Tuesday night.
> > The problem now is that each mailbox CAN be
> accessed
> > but ONLY by the user who initially owned the
> > mailbox.
> > (ie JBloggs is the only user account that can
> access
> > the Joe Bloggs mailbox)
> > No matter what permissions we set on any mailbox
> > that
> > still remains, only the initial owner of the
> mailbox
> > can use it, this includes administrator being
> unable
> > to view the mailboxes.
> > 
> > Any ideas what might have caused this to occur?
> > 
> > Thanks for the advice :)
> > 
> > Luke
> > 
> > --- Tim Ault <[EMAIL PROTECTED]> wrote:
> > > Perhaps. But I don't believe PSS hires
> > necromancers.
> > > 
> > > Luke, are any of the users OST Outlook clients?
> If
> > > so, disable their NT
> > > accts before answering my question. Tell them to
> > > export their mailbox to a
> > > PST. You'll at least preserve what mail was
> synced
> > > locally prior to the
> > > "incident".
> > > 
> > > -----Original Message-----
> > > From: Chris Scharff
> > > [mailto:[EMAIL PROTECTED]] 
> > > Sent: Tuesday, August 27, 2002 11:17 AM
> > > To: Exchange Discussions
> > > Subject: RE: Exchange Disaster Recovery Issues
> > > 
> > > 
> > > For quite some time.
> > > 
> > > > -----Original Message-----
> > > > From: Martin Blackstone
> > > [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, August 27, 2002 9:54 AM
> > > > To: Exchange Discussions
> > > > Subject: RE: Exchange Disaster Recovery Issues
> > > > 
> > > > 
> > > > Sounds like a call to PSS is in order.
> > > > 
> > > > 
> > > > -----Original Message-----
> > > > From: Luke Cassar [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, August 27, 2002 12:32 AM
> > > > To: Exchange Discussions
> > > > Subject: Exchange Disaster Recovery Issues
> > > > 
> > > > 
> > > > Hi,
> > > > a client of ours recently deleted several log
> > > files for
> > > > exchange. The result was that exchange stopped
> > > working. The 
> > > > client has run several utilities ISINTEG and
> > > ESEUTIL in no 
> > > > particluar order and we were called in to fix
> > the
> > > problem. We 
> > > > continued running these utilities in a
> > particular
> > > sequence. 
> > > > The end result was working exchange, but with
> a
> > > lot of data 
> > > > missing from mailboxes. A directory import was
> > > performed 
> > > > using an export from an oversease exchange
> > server.
> > > This was 
> > > > imported and restored most of the mailboxes.
> We
> > > tried the 
> > > > consistency adjuster for mailboxes to try and
> > find
> > > orphaned 
> > > > data in the information store, but the size of
> > the
> > > database 
> > > > files is significantly reduced. (eg. from 20GB
> > to
> > > 5GB for 
> > > > priv.edb) We have gotten to the point where we
> > are
> > > writing 
> > > > off any chance of recovering the data from the
> > > database 
> > > > itself and are reverting to restoring
> partially
> > > from backups 
> > > > (backups had not been working for a
> significant
> > > time). The 
> > > > problem we are now encountering is that
> > mailboxes
> > > that have 
> > > > shown up as being empty (ie, all data lost)
> can
> > no
> > > longer be 
> > > > accessed by any user (administrator or
> > otherwise).
> > > We have 
> > > > re-assigned server and site permissions
> > > appropriatley and 
> > > > given permission to the user for this mailbox
> > but
> > > still the 
> > > > user cannot log on. (even re-mapping the
> profile
> > > does not 
> > > > help). If we delete and re-create the mailbox,
> > > users still 
> > > > cannot access them.
> > > > 
> > > > Are there any known issues along these lines
> and
> > > what would
> > > > be the best course of action for this
> situation.
> > > > 
> > > > Help is appreciated.
> > > > 
> > > > Regards,
> > > > Luke Cassar
> > > > 
> > > >
> > >
> >
>
_________________________________________________________________
> > > > List posting FAQ:      
> > > http://www.swinc.com/resource/exch_faq.htm
> > > > Archives:              
> > > http://www.swynk.com/sitesearch/search.asp
> 
=== message truncated ===


=====
"Dare to be indifferent"
           -Sabre-

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to