Update 2 includes over 300 enhancements and bug fixes

[Hoegimator]

Hello Veeam Team

Is there a detailed documentation about Update 2 and its "over 300 enhancements and bug fixes" ? I would love to read more about it...

Thanks
Joerg

[veremin]

Our support has access to the internal database with details on every bug fixed, but we're not trying to make a public facing document out of this due to the sheer number of fixes. They can check on the specific bugs for you though.

Thanks.

[Hoegimator]

Ok, thanks for the answer. I was particular curious if there are enhancements with Exchange 2016 DAG Backup.
Is it possible to provide some information about that?

Thanks.

[veremin]

As far as I'm concerned, nothing crucial has been changed for this matter. However, may I ask you whether you've encountered particular issues while backing up Exchange DAG 2016? Thanks.

[Hoegimator]

Yes we have an issue, but I didn't open a case yet.

We have 3 Exchange 2016 server in a DAG (with 2 passive copies), together in one Backupjob. On the end of the job, one or two of the servers get that warning (in VeeamLog):

Code: Select all

16.08.2016 19:12:07 :: VSS: Backup job failed.
Cannot notify writers about the 'BACKUP FINISH' event.
A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{8d11d617-05f6-4bfe-b2d3-454ce5e13259}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f3]. 

And the VSS Writer is in that state:

Code: Select all

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {8d11d617-05f6-4bfe-b2d3-454ce5e13259}
   State: [12] Failed
   Last error: Retryable error

In the Event log are 2 Application Errors (EventID 2140 & 2026)

I did tests with the "VSSTester.ps1 script" and everything works fine.

Do you have any input about that? Should I open a Support Case to investigate?

Thanks.

[veremin]

Correct, you'd better let support team investigate the issue directly. Thanks.

[BGA-Robert]

We opened a case with Veeam on the Exchange/VSS issue. I understood it to be a MS issue from Veeam support. We have yet to resolve it. Tick#01759945. Please post your solution when you get one...

[Hoegimator]

I opened a case last week (#01882676) and will post the solution as soon as we could fix it.

[Hoegimator]

It seems Veeam Support is not able to fix this. Their workaround is to create 1 Backupjob per Exchange DAG node.
I'm not very happy with that, because of the deduplication ratio and about the increase of the total number of backupjobs.
With Exchange 2010 DAG we had no problems whatsoever....

[Hoegimator]

Now the support tells me "they doubt that the problem is with exchange 2016" and to backup only the passiv database copy to save space, but with still 1 job per exchange.

I'm not very happy with that workaround. Anyone has a better solution?

Thank
Joerg