Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1516
  • Last Modified:

BIG Problem with Exchange 2007 Mailbox Database

Please help!!!

We have and Exchange 2007 server running on Windows Server 2003 R2 within a virtual enviroment (VMWare).

Recently BackupExec started failing to backup the store due to connectivity issues, however our clients could still connect without issue-sending and receiving messages.

The first storage group mailbox database is 99Gb.

I attempted a Microsoft Backup of the store which failed again due to a read error.

Prior to running ESEUTIL I really want a backup/copy of the database so I resorted to unmounting the database and undertaking a manual copy.  With 5 minutes of the copy to go, this failed with the following error in the Event Viewer:

Event Type:      Error
Event Source:      symmpi
Event Category:      None
Event ID:      9
Date:            21/02/2011
Time:            14:57:54
User:            N/A
Computer:      xxxxxx
Description:
The device, \Device\Scsi\symmpi1, did not respond within the timeout period.

Worrying that there was a problem with the disk a ran a Windows Disk Check, this reported no errors.

I then decided to clone the machine in the hope to have a backup prior to running ESEUTIL.  Sadly vSphere failed with the following error:

Error caused by file [Shared_DataStore1]Hermes/Hermes_1.vm-dk

No further detail was provided.

The server is back up and running again without any error and is receiving messages.  Obviously though there is something deeply wrong.

Any ideas as to how I could get a backup of the system in this cenario????

Yours...in panic
0
wilmslowhighcheshire
Asked:
wilmslowhighcheshire
  • 8
  • 4
  • 2
1 Solution
 
Randy_BojanglesCommented:
use the trial version of Veeam to see if that will do you a VMDK level backup

http://www.veeam.com/vmware-esx-backup.html
0
 
wilmslowhighcheshireAuthor Commented:
Hi,
Thank you for this.  I am just running a backup now (looks like it's going to take a while) and will let you know if it works.
I can then hopefully try and repair the exchange database with a degree of reassurance that I have a backup to fall back on.
0
 
Randy_BojanglesCommented:
Its a great product - use it with many of the schools and businesses we support with VM environments....

Not too expensive to an academic institution either - depending on your VM license
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
wilmslowhighcheshireAuthor Commented:
sadly this has also encountered errors, although I can't see that it failed to authenticate as it backed up 6gb before it failed...

Backing up object "[Shared_DataStore1] Hermes/Hermes_1.vmdk"
BackupDiskFull failed
Client error: Failed to open VDDK disk [[Shared_DataStore1] Hermes/Hermes_1.vmdk] ( is read-only mode - [true] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [vc];Port: 443;Login: [administrator];VMX Spec: [moref=vm-934];Snapshot mor: [snapshot-1013];Transports: [san]] failed because of the following errors:
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [vc];Port: 443;Login: [administrator];VMX Spec: [moref=vm-934];Snapshot mor: [snapshot-1013];Transports: [nbd]] failed because of the following errors:

Server error: End of file

0
 
coolsport00Commented:
Do you have any snapshots currently on this VM?

~coolsport00
0
 
wilmslowhighcheshireAuthor Commented:
sadly no.....
0
 
coolsport00Commented:
Well, from your Veeam log, we can see that something has a 'hold' on the VMDK, because it's only 'read only mode'. Do you have any .lck files in the VM's folder?

~coolsport00
0
 
wilmslowhighcheshireAuthor Commented:
the image shows all of the files in the datastore.  there is a vmdk file even with the server shutdown. Datastore
0
 
coolsport00Commented:
How many volumes are on your VM? Sometimes, snapshots are not referred to as 'delta' files, but the "_n" files (i.e. the '_1' files in your screenshot). So, I assume you don't see snapshots in Snapshot Mgr?
0
 
wilmslowhighcheshireAuthor Commented:
Hi, the VM has two volumes.  As you say, I don't see any snapshots in Snapshot Manager.
0
 
wilmslowhighcheshireAuthor Commented:
Thank you all for your help.  I have decided to add another virtual disk to the server (on a different datastore), I have created a new mailbox database and am currently moving all of the mailboxes to the new mailbox database.  I will then remove the virtual disk that is causing the problem and hopefully rectify the problem of not being able to backup the Exchange server....I will submit a post if this works......(finger crossed).
0
 
coolsport00Commented:
Good luck "wilmslowhighcheshire". Keep us posted!

~coolsport00
0
 
wilmslowhighcheshireAuthor Commented:
Thankfully I managed to move mailboxes except one to the new store.  Interestingly enough, every attempt to move this mailbox caused the timeout on the drive, however I was able to still retrieve messages through Outlook.
All working again now.
Thank you everyone for your help and advice.
0
 
wilmslowhighcheshireAuthor Commented:
I have flagged this as partial due to the fact that the problem was not fixed as such, simply worked around.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

  • 8
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now