EXCHANGE 2013 unable to attach edb

[mairiesuresnes]

Hello,

Here's the error after backing up my physical Exchange 2013 Server with Endpoint Backup.
No error during the backup.
Sent to Veeam Repository successfully.
When I run the Exchange Explorer, it successfully attaches 4 of 5 datastores (databases) but one of them fails:


Here's the part of log displaying the attempt to do it:

Code: Select all

29/05/2015 09:54:32    3 (6352) Error: Failed to open Exchange Server store.C:\VeeamFLR\APOLLO\Volume1\DATABASES\500MB-1\500MB-1.edb
29/05/2015 09:54:32    3 (6352) Stack:
29/05/2015 09:54:32    3 (6352) 
29/05/2015 09:54:32    3 (6352) Error: JetError -566, JET_errDbTimeTooOld, dbtime on page smaller than dbtimeBefore in record
29/05/2015 09:54:32    3 (6352) Stack:
29/05/2015 09:54:32    3 (6352)    at Veeam.Jet.Context.chk(Int32 jetRes)
   at Veeam.Jet.Instance.Init3(ICallback callback)
   at Veeam.Exchange.Storage.Common.Context.InitInstance(Action`1 progress)
   at Veeam.Exchange.Storage.Common.Context.Init(String filePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
   at Veeam.Exchange.Storage.Common.Store.OpenStore(String databasePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
29/05/2015 09:54:32    3 (6352) Looking for Jet Shadow Log files...
29/05/2015 09:54:32    3 (6352)   Shadow logs not found.
29/05/2015 09:54:32    3 (6352) Error: Failed to open Exchange Server store.C:\VeeamFLR\APOLLO\Volume1\DATABASES\500MB-1\500MB-1.edb
29/05/2015 09:54:32    3 (6352) Stack:
29/05/2015 09:54:32    3 (6352)    at Veeam.Exchange.Storage.Common.Store.OpenStore(String databasePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
   at Veeam.Exchange.Storage.Common.Store.Open(String databasePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
   at Veeam.Exchange.Explorer.Tasks.AsyncStoresLoader.TryOpenStore(StoreConfig config, StoreFactory storeFactory, IStore& store)
   at Veeam.Exchange.Explorer.Tasks.AsyncMounter.ProcessStore(StoreConfig currentConfig)
29/05/2015 09:54:32    3 (6352) Error: JetError -566, JET_errDbTimeTooOld, dbtime on page smaller than dbtimeBefore in record
29/05/2015 09:54:32    3 (6352) Stack:
29/05/2015 09:54:32    3 (6352)    at Veeam.Jet.Context.chk(Int32 jetRes)
   at Veeam.Jet.Instance.Init3(ICallback callback)
   at Veeam.Exchange.Storage.Common.Context.InitInstance(Action`1 progress)
   at Veeam.Exchange.Storage.Common.Context.Init(String filePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
   at Veeam.Exchange.Storage.Common.Store.OpenStore(String databasePath, String logsPath, String tempPath, String logsMask, Action`1 progress)
29/05/2015 09:58:17    1 (3720)   Request to keep permament mount (ID: e17d2fbb-0c3c-4fd9-b3e7-821a9070717e) sent to Veeam Backup and Replication.
29/05/2015 09:58:17    1 (3720) Export filter: .

I ran again a new incremental backup, but I still get the same error with the new recovery point.

It used to work fine with the last full backup.

Any idea if this issue comes from the Exchange Server of from the Veeam application or anywhere else?

Any help appreciated.
Yann

[mairiesuresnes]

Although everything seems normal on the server side:

[mairiesuresnes]

I've just done a full backup of the same server on different backup repository.
I can successfully attach all of the datastores, and then restore from them.

BTW, I had the "same kind of issue" with my SQL Server as I can successfully reattach databases from full backup but it fails with an incremental (http://forums.veeam.com/veeam-endpoint- ... 27878.html).

I am going to attempt a new incremental on this other backup repository just to eliminate the potential repository issue.

[mairiesuresnes]

Even worse after the new incremental:


2 databases faild to get attached correctly.

Is there anything to do to make it work every time?

Thanks for the advice

[Dima P.]

Hello Yann,
We need the full copy of your application logs, so, kindly, open a support case Endpoint’s Control Panel > Support and let me know the case ID. Thank you in advance!

[mairiesuresnes]

Case ID: 00930381

Thanks

[Dima P.]

Thanks – investigating. I’ll follow up shortly!

[Dima P.]

Hello Yann,
While investigating the logs for both cases (regarding SQL and Exchange) we noticed that restore fails from the incremental backup and in both cases backup files are located on the same repository. May I ask you to perform a backup to another backup storage and test the same restore scenario? We believe there may be an issue with your current backup storage device. Thank you in advance.

[mairiesuresnes]

Hello Dima,
I tried to backup the Exchange server locally on a USB HDD but it failed:

Code: Select all

08/06/2015 11:09:06 :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. VSS asynchronous operation is not completed. Operation: [Shadow copies commit]. Code: [0x8004230f]. 

although the USB drive was not listed in the control panel when choosing what to backup.

I'll try this afternoon with another Veeam repository that I need to create and configure.

I'll keep you posted.

[Dima P.]

Thanks! I’ll await for the updates then.

P.S. Did the backup to the USB drive fail during the first full backup or an incremental job run? Thanks

[mairiesuresnes]

The backup to the USB drive failed during the first full backup, but this was just a test and not a concern as I prefer using the Veeam repository anyway.

I've finished testing with a new Veem repository on a RAID5 (6 x 600 GB SAS) on a HP MSA 2312i, and this gives me the same result as I had on my Thecus (RAID 5) and my other HP MSA 2012i (RAID0 4 x 600 GB SAS) :
it works great on a full backup but it fails with an incremental.
This time, none of the databases could get attached.



Is this an issue that the next Update2a could help? or is this an issue with the EndPoint product?

[Dima P.]

Yann,
Unfortunately, I don’t have an answer right now – we need to wait for the investigation results from the QA team.

[mairiesuresnes]

FYI
I've just installed the Update2a on Veam B&R, but I still get the same issue.

[Dima P.]

Suresnes,
Thanks. I doubt its related to the VBR logic but thanks for the heads up – I’ll try to reach the QA team today in order to get any updates regarding your cases. Cheers!