Veeam exchange backup not truncating logs
Greetings,
I have a veeam job that is not truncating the exchange log files. All settings are correct in the job settings (process transaction logs with job, require successful processing, and under SQL truncate logs). I have been asked to determine if the recovery model is full or simple. I am not familiar with that in Exchange, only SQL. First, is that a component of an exchange database? If so, how do I confirm whether its full or simple?
Thanks a lot
I have a veeam job that is not truncating the exchange log files. All settings are correct in the job settings (process transaction logs with job, require successful processing, and under SQL truncate logs). I have been asked to determine if the recovery model is full or simple. I am not familiar with that in Exchange, only SQL. First, is that a component of an exchange database? If so, how do I confirm whether its full or simple?
Thanks a lot
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Is the issue with Exchange or SQL, or both ?
ASKER
Just the Veeam Exchange backup. Veeam support asked me to check the recovery model of the Exchange database since if it is simple the Veeam job won't truncate logs even if it is set to do so. The Veeam job does show it successfully truncated the logs.
Exchange version ?
I've only heard Full and Simple recovery, when referred to SQL databases.
Did they mean Circular logging ?
I've only heard Full and Simple recovery, when referred to SQL databases.
Did they mean Circular logging ?
ASKER
Exchange 2016. That's what I thought - SQL databases. I don't think they meant circular logging, which isn't set. They did a remote session and I got them the logs for the job from the Veeam server as well as the Exchange server so they are clear that it is Exchange.
From Veeam support "Thank you for the logs. Please find here some information on how to find the recovery model of the EXchange eDBs: https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/view-or-change-the-recovery-model-of-a-database-sql-server?view=sql-server-2017 Please, Let us know the recovery mode set on the DBs."
From Veeam support "Thank you for the logs. Please find here some information on how to find the recovery model of the EXchange eDBs: https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/view-or-change-the-recovery-model-of-a-database-sql-server?view=sql-server-2017 Please, Let us know the recovery mode set on the DBs."
You best go back to Veeam then and ask them how that link they've pasted, applies to Exchange 2016 and Exchange Dbs
because at the top of that Link it states
THIS TOPIC APPLIES TO:
SQL Server Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse
because at the top of that Link it states
THIS TOPIC APPLIES TO:
SQL Server Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse
ASKER
Ha yeah I noticed. I emailed them about it but they haven't yet replied.
I've only heard the terms Full and Simple, with reference to SQL.
and Circular Logging with reference to Exchange.
and Circular Logging with reference to Exchange.
I dont think this is your problem but posting incase it might help.
i was having problems with another product where it wasnt truncating the logs. Turns out the VSS writers weren't right. (cmd prompt Vssadmin list writers) the exchange one wasnt in an ok state.
Restarting the information store after hours solved this . verified writers were ok again after information store was restarted. Im assuming you may have already restarted the server which should sort the writers anyway
i was having problems with another product where it wasnt truncating the logs. Turns out the VSS writers weren't right. (cmd prompt Vssadmin list writers) the exchange one wasnt in an ok state.
Restarting the information store after hours solved this . verified writers were ok again after information store was restarted. Im assuming you may have already restarted the server which should sort the writers anyway
ASKER
Sorry for taking a while to get back to this.
Daryl, thanks for the info. I had checked the vss writers. The Exchange writer showed retryable error but I was told this would not prevent the backup from running.
After scouring Veeam forums and Google searches returning websites and blog posts, I got it working. So, despite Veeam support questioning the backup mode of an Exchange server (my issue was not with SQL so this made no sense to me, or Andrew), I was able to see that Veeam was getting the command to Exchange but it was failing there. I apologize but I am on a different computer today so don't have the link to the post that shows how to prove Veeam is handing off the truncate command to Exchange. Further troubleshooting and reading posts brought me to an obscure post in a Veeam forum where it was stated that perhaps a dismounted database was causing issues with a Veeam backup. Our client did indeed have a dismounted database. I was unable to mount it then realized they are in Exchange Std., not enterprise, and already had 5 databases mounted. Since the database was going to be used for archiving, and with nothing on it yet (not to mention the fact that it wouldn't have mounted anyway when the in-house admin would go to mount it), I deleted it. After doing so the Veeam job ran without issue and truncated the logs.
Daryl, thanks for the info. I had checked the vss writers. The Exchange writer showed retryable error but I was told this would not prevent the backup from running.
After scouring Veeam forums and Google searches returning websites and blog posts, I got it working. So, despite Veeam support questioning the backup mode of an Exchange server (my issue was not with SQL so this made no sense to me, or Andrew), I was able to see that Veeam was getting the command to Exchange but it was failing there. I apologize but I am on a different computer today so don't have the link to the post that shows how to prove Veeam is handing off the truncate command to Exchange. Further troubleshooting and reading posts brought me to an obscure post in a Veeam forum where it was stated that perhaps a dismounted database was causing issues with a Veeam backup. Our client did indeed have a dismounted database. I was unable to mount it then realized they are in Exchange Std., not enterprise, and already had 5 databases mounted. Since the database was going to be used for archiving, and with nothing on it yet (not to mention the fact that it wouldn't have mounted anyway when the in-house admin would go to mount it), I deleted it. After doing so the Veeam job ran without issue and truncated the logs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.