An issue with single database in a DAG cluster

[Dmitrii the False2nd]

Description of the problem
At a (already) past job, we had a problem with Veeam 11a (last patch, so on) and DAG on Exchange 2019 (last CU, last pacthes).
Configuration: standard, but one MDB on one server was NOT in the availability group.
Backup: agent inside the VM

An issue
When adding two servers as a DAG
- backup task did not clear Exchange MDB logs for this single DB
- because it did not see the second copy of the MDB.

When adding Exchange as a single server, the task determined that a DAG was present and also did not execute
clearing the Exchange MDB logs

Unfortunately, logs unavailable, and the next week I do not think that I will try to reproduce the problem.

Temporary solution: logs in this database were not needed, so we enabled cyclic cleaning (configured circular logging ).

[Mildur]

Hi Dmitrii

Please follow our user guide on how to backup an Exchange DAG:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

You must have the Veeam agent on each DAG Member. Just using it on one single server will not work.

If you still see issues, a case with our support team is required. Please do not post your log files to the forum (against our forum rules). We cannot effectively analyze your log files.

Thanks,
Fabian

[Dmitrii the False2nd]

You must have the Veeam agent on each DAG Member. Just using it on one single server will not work.

If you still see issues, a case with our support team is required.

I had have the Veeam agent on each DAG Member, and other MDB's logs were truncated.
So I will try to reproduce this case in a home lab. In time.
Thanks

[Mildur]

Hi Dmitrii

Ok, please let me know about the outcome.
Log truncation should still be possible for a database without a passive copy.

An issue
When adding two servers as a DAG
- backup task did not clear Exchange MDB logs for this single DB
- because it did not see the second copy of the MDB.

Is this a error message in the console?

Thanks
Fabian

[Dmitrii the False2nd]

I resigned from the job where the problem was discovered. I could not quickly reproduce the problems at my home stand. Since the original problem database was, in fact, archival, they simply turned on cyclic logs on this database.