Re: Need help urgently please!

For your recovery you will need to restore from tape to recover your server
and transaction logs. The only problem with using the databases currently
on the RAID is that they are missing transanctions from the log files that
are gone now and can only be restored from tape. So best way to restore is
to do a complete Tape restore although I would move the existing databases
off RAID to a temporary location just in case the Tape backup fails for some
reason. For reading emails in the VS queue folder you can use Outlook
Express for .eml files.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2006
Microsoft Certified Partner

"John Riddle" <thrillsoftathotmaildotcom> wrote in message
news:eRUNxO8yGHA.996@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

Today the C: drive of the sole server in our remote office crashed and we
may not be able to get it back. We have daily backup that was most recent
last night about 5AM. The server they had in that office is a DC with RAS,
DNS and Exchange. There are about 10 exchange mailboxes on that server.
The databases are on a RAID array that should be fine, but the log files
were also on the C: Drive that crashed. Our MX records are set up to list
their server as primary for their domain (they have their own .com
addresses) and our as secondary mail server. So emails since the crash are
piling up in our local server in the queue. The users down there are
frantic to be able to read the emails that they missed all day, but are in
our server. I created a temporary mailbox and have set forwarding from
their mailboxes to the temp "catch all" mailbox. This works for new mail
coming in now, but there are still hundreds of messages in the queue from
before I set up the forwarding. I looked in the vs 1 queue folder for them
to drag into the pickup folder, but there are no messages in the queue
even though there shows hundreds of messages in the queue on ESM. How can
I get these queued messages into the temp folder quickly so that these
users can view via OWA?

Also, can someone suggest the best recovery procedure for rebuilding the
remote server assuming that the server won't recognize the C drive.We're
getting a new drive first thing in the AM and want to know what the best
method assuming the log files are on the bad drive. I'll try to mount it
as a slave drive after rebuilding the server and restoring that way from
the backup. If my databases are good, can I just point to my RAID array as
the location of my databases and try to move the log files to to
over-write the default log files when exchange is freshly installed?

Thanks for any help

John



.

Relevant Pages

  • Re: AS2005 ... what is wrong with it?
    ... What I have seen is that the dev server is *faster* than the prod server ... And does your dev server also have all 6 databases with all these roles? ... When I restore the "PROV" i got approx 20 sec. ... Starting from an empty data folder should show if this theory is true ...
    (microsoft.public.sqlserver.olap)
  • Re: Copying WSS to another Server
    ... the data in sync I back the SQL databases up and restore them to the replica ... It already has WSS installed. ... > on one server and copy it to another for dev/test purposes, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: AS2005 ... what is wrong with it?
    ... I have 6 OLAP databases on the server. ... When I restore the "PROV" i got approx 20 sec. ...
    (microsoft.public.sqlserver.olap)
  • Re: E2K3 restore onto bu server
    ... When you are restoring the data to the recovery server, ... it will mount without the need to play in any log files. ... For future restore attempts, remember to remove the log files before ... > The test n/w is identical to the live, domain name, same users, etc, E2K3 ...
    (microsoft.public.exchange2000.admin)
  • Re: Exchange DR, what to do
    ... setup blank databases on theDRexchangeserver, ... data out of the RSG, it tries to restore it to the original server, ... the cluster exchange virtual server name was, ...
    (microsoft.public.exchange.admin)
Loading