3/30/2024 0 Comments Veeam logs![]() I need to figure out how to get things back to working how they're supposed to.Įdit: Issue resolved. Veeam is showing that the backups are completing successfully so the guys in charge of them are pushing back that the problem has to do with the Exchange server even though nothing identifiable changed in the time frame that the database stopped recognizing full backups. We upgraded our Exchange to the latest CU at the end of April, so the timeline doesn't line up for that causing a problem, and general Windows Updates were previously applied to the server in February.Ĭan anyone explain how the awareness between the Veeam and Exchange works so that after the backup takes place the logs are supposed to be cleaned up? Is there anything that I can check to see if or why this trigger is not being recognized? This job has been the same since we upgraded to our Exchange 2019 server but according to the Exchange Powershell script that queries the database backup information, Exchange has not registered a full backup since early April. Veeam is configured with Applaction-aware processing enabled, with the General tab Require successful processing and Process transactionlogs with this job both selected. ![]() We just discovered that our Exchange logs are not truncating after Veeam full backups run, so just had an incident where our logs partition filled up and crashed our server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |