Exchange Explorer taking hours to mount Databases.

[Hevros]

Hi,

I have a support case for Veeam explorer for exchange taking hours to open, specifically 2.5 hours to get the databases mounted in the browser.
we initially thought it might be a RAM issue on the backup server. the support engineer came back and said he agreed based on this entry in the client logs

Code: Select all

[08.06.2015 15:57:47] < 41268> Adjusting system file cache limit (25 percent)
[08.06.2015 15:57:47] < 41268>   Total physical memory instaled: [32733 MB], available: [24600 MB].
[08.06.2015 15:57:47] < 41268> WARN|Truncating new file cache limit. Calculated: [8183 MB], maximum possible: [4095 MB].
[08.06.2015 15:57:47] < 41268> WARN|Original file cache settings cannot be retrieved (arithmetic result exceeded 32 bits) (WoW64?).
[08.06.2015 15:57:47] < 41268> Maximum system file cache size is now [4095 MB]

based on this the customer doubled the ram in the server to 64GB and rebuilt the server with 2012 R2
and now we still have the same issue. I sent the feed back to support this morning but the case seems to be closed
it looks to me that the explorer client may only be able to address a 32bit cache size of 4095MB
case 00939723

any help on getting this case looked into urgently would be great.

[foggy]

Stephen, could you please give more details on the actual setup (backup server, repository, connections between them, etc.). Meanwhile, I recommend opening a new case and make reference to the old one for proper treatment. Thanks.

[Hevros]

Hi,

the backup server and repository is on one server.
HP DL380 Gen8
24 cores
64Gb RAM
backup target is local disk
3 raid5 arrays all on separate controllers with 2GB write back cache each.
each array is roughly 6TB with 1TB 2.5inch 7.2k disks
it is on v8 update 2b

the production is
three esx hosts with p2000 storage
all fibre attached.

[Hevros]

new case number 00957195.

[foggy]

Ok, so you have everything locally, that doesn't confirm my first guess. Please continue investigating with support.

[chrisdearden]

Are you using explorer against a primary copy of the exchange db ? if not, is it possible you have a lagged copy?

[Hevros]

yes we are using explorer to open the primary backup on the local disk,
Also I have checked another customer and they have the same issue. it takes a long time to open and they have the same entries in the logs.
I then checked the third customer as the first two are both on v8, the third customer has no issue at all and they are on v7. I will continue to check other customers.

[Hevros]

I have checked some further customers and all that are on v8 have the log entry and some of them run fine, so support initially sold us a dummy there and made us upgrade the customers RAM based on an entry that is in every log weather there is an issue or not.