6.5 Exchange Explorer - should it work with 6.1 backup?

[jpeake]

ESX 5.1
Backups taken using Veeam 6.1 running on WinSrv2012
Now have installed Veeam 6.5, trying Exchange Explorer against previous backups

Exchange Explorer fails will a jet error - db in dirty shutdown message.

I will try taking new fulls tonight with 6.5 to see if that fixes me up

Anyone else getting this?

[johnlong]

I extracted the veeam explorer for exchange and browsed to one of my 6.1 backups and was able to use it. I'm using 6.1 on server 2008 r2.

[poulpreben]

ESX 5.1
Backups taken using Veeam 6.1 running on WinSrv2012

Auch, this is unsupported. 5.1 and 2012 support was not added until the 6.5 release.

Now have installed Veeam 6.5, trying Exchange Explorer against previous backups
Exchange Explorer fails will a jet error - db in dirty shutdown message.

It should work. I have been using VEX on my 6.1 backups ever since the first beta was out. Please post your results when you have a successful 6.5 backup!

[jpeake]

Yeah I figured 2012 and 5.1 might be culprit. I am still in a trial phase, and have Backup Exec to tape still running until I am comfortable with Veeam.

Will wipe out my previous Veeam backups and start new fulls tonight.

[poulpreben]

Oh, right! Remember to disable the Exchange log truncation in either Backup Exec or Veeam to avoid errors in your Event Log

[jpeake]

Oh, right! Remember to disable the Exchange log truncation in either Backup Exec or Veeam to avoid errors in your Event Log

ahhh, good call

[Gmc85]

I'm getting the dirty database shutdown when trying exchange explorer with my 6.1 backups too - exchange server in question is on 2008 r2.

poulpreben wrote:
Oh, right! Remember to disable the Exchange log truncation in either Backup Exec or Veeam to avoid errors in your Event Log

Do you have to do this to use exchange explorer?

[Vitaliy S.]

No, you do not need to use this setting to use Exchange explorer.

[Gmc85]

Hmm not sure why I'm getting that dirty database shutdown error then - I'll see what happens when I try it with my next backup.

[patrickds]

Hmm not sure why I'm getting that dirty database shutdown error then - I'll see what happens when I try it with my next backup.

You are using the VSS integration to make sure you're getting a clean backup?

[Gmc85]

You are using the VSS integration to make sure you're getting a clean backup?

Of course - transaction logs are truncated after the veeam backup too, so I know it's working correctly.

[Vitaliy S.]

Hmm not sure why I'm getting that dirty database shutdown error then - I'll see what happens when I try it with my next backup.

More info about this behavior in the related discussion, please take a look > Exchange backup problem

[jpeake]

I'm having the same dirty shutdown error on a new fulls taken with 6.5.

If I have to extract the db and run eseutil /r every time, I might as well just use Exchange recovery DB.

[tsightler]

Are your Exchange logs available in the backup? It should be automatically performing the required recovery. You should probably open a support case.

[Gmc85]

They are indeed - Actually it works if I use file level recovery, open the exchange explorer then manually browse to the edb and logs directory (On separate volumes in our environment) in the veeamflr folder..

[jpeake]

Are your Exchange logs available in the backup? It should be automatically performing the required recovery. You should probably open a support case.

Yes, if i open the backup in "Backup Browser" I can see all the logs as well as edb's. On the live Exchange server, logs have been truncated.

I will look through the Veeam job log file, and open a support case

[zoltank]

I'm receiving the same error.

I have an Exchange 2010 DAG which I back up with Veeam 6.5 with application aware processing turned on. When I try to retrieve an item using Exchange Explorer I receive an error saying the database is dirty for each replicated database. However, the databases are fine and are clean when brought up in SureBackup. I suspect the problem might be the log files aren't located in the same folder as the EDB file since the EDB files and logs are located on separate drives per MS recommendations.

I have opened a case with support.

[jpeake]

That's my exact error message as well (the pic zoltank posted). And logs are in separate volume also. No DAG here.

[Rideout18]

I'm in the same boat with this error. Let me know what information I can provide to help out.

[tsightler]

Have you tried manually mounting the database and selecting the database and log folder?

[zoltank]

Have you tried manually mounting the database and selecting the database and log folder?

I don't know the procedure for that. I'm using the Exchange Explorer built into 6.5, and I don't see any way to do that.

[tsightler]

The default is that Explorer for Exchange tries to automatically identify and mount the databases, however, you can still manually perform the steps, simply do the following:

1. Start a Guest File Level restore of the Exchange server
2. Once the File Browser window comes up use the Windows Start menu to start Veeam Explorer for Exchange as a standalone program
3. Click the "Add Store" button and browse to the EDB and LOG files that you want to mount respectively, they should be mounted in the C:\WindowsFLR\<servername>

I have no idea if this will help, but I figured it was worth trying.

[zoltank]

The default is that Explorer for Exchange tries to automatically identify and mount the databases, however, you can still manually perform the steps, simply do the following:

1. Start a Guest File Level restore of the Exchange server
2. Once the File Browser window comes up use the Windows Start menu to start Veeam Explorer for Exchange as a standalone program
3. Click the "Add Store" button and browse to the EDB and LOG files that you want to mount respectively, they should be mounted in the C:\WindowsFLR\<servername>

I have no idea if this will help, but I figured it was worth trying.

That worked.

As I suspected, Exchange Explorer looked for the log files in the same folder as the EDB file. When it didn't see it it said it was dirty. However, once I pointed it to the log files folder it recovered the EDB and mounted it without problem.

This should probably be listed as a known issue along with this workaround.

[tsightler]

Sweet! At least we know it's something simple. I think we try to parse the log location, I can't imagine it just assumes the logs will be in the same directory as that's actually fairly rare. Still might be nice to open a support case and submit the logs.

[zoltank]

Sweet! At least we know it's something simple. I think we try to parse the log location, I can't imagine it just assumes the logs will be in the same directory as that's actually fairly rare. Still might be nice to open a support case and submit the logs.

I've already opened a support case and uploaded the logs. It's case #00150699.

[Vmaware]

Same for me guys. Doing the workaround of file restore then clicking open in explorer on toolbar. Once loaded manually launch veeam explorer for exchange from start menu worked for me. Hopefully a fix will come for launching it directly from exchange restore.

Thanks

[jpeake]

Same here, mount the backup in FLR, then manually mount Exchagne DB and logs in Explorer works fine. It's actually surprisingly fast.

Workaround is no problem for me, until patch is available. I see in the Veeam job logs that the backup engine is running eseutil /mh and parsing out the path info. Probably an easy fix the Veeam team.

[thavener]

I actually receive the same error after trying the workaround. Seeing this in the event viewer for the database having the issue, but the other two Databases mount fine.
as a result of a Windows version upgrade from 6.1.7601 SP1 to 6.0.6002 SP2. This message is informational and does not indicate a problem in the database.

[murda]

We have another error.

failed to open exchange store veeam ... too many instances ...

The problem is we can only open/mount 16 DB's and the remaining DB's are showing that error.
We need to use the same work around posted in this topic.

[foggy]

The problem is we can only open/mount 16 DB's and the remaining DB's are showing that error.

Do you have a single Exchange server with that big number of databases? There could be probably some limit on the number of mounted DBs. Need to see logs - please submit a case with technical support.