Step 1: Obtain the path of the affected database(s) To solve the problem, we must first obtain the path of the database with problems. This error is due to either the Veeam Backup for Microsoft Office 365 database not being stopped correctly, due to an unexpected shutdown of the computer, or the volume where the database is located has run out of free space available or experienced some other unexpected error. JetError -501, JET_errLogFileCorrupt, Log file is corrupt Here is a link to the default for the SQL system databases: (v=sql.105).If Veeam Backup for Microsoft Office 365 gives this error when trying to backup a job: One of my colleague ask if we changed all the databases to simple, and we did not only change the "master" system database. The log files look like this after the change.ġ7-09-2016 11:43:44 2792 Using account DOMAIN\Veeam_Serviceġ7-09-2016 11:43:44 2792 Database master: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database tempdb: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database model: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database msdb: skipped transaction log truncation.ġ7-09-2016 11:43:44 2792 Database BI-PRODUCTION: transation logs have been truncated. So it look like Veeam does not support changing that. Then i looked at the "master" system database on the instance and found the the customers SQL DBA had change the "Recovery model" for that system database to "Full".Īfter changing the Recovery model to Simple, with also is the Microsoft default, the warning disappeared. Use BACKUP DATABASE instead.ġ6-09-2016 22:19:08 3528 Database tempdb: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database model: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database msdb: skipped transaction log truncation.ġ6-09-2016 22:19:08 3528 Database BI-PRODUCTION: transation logs have been truncated. So i looked at the log files on the machine that has the SQL database instance, C:\ProgramData\Veeam\Backup\VeeamGuestHelper_XXXXXXXXX.txt and found this:ġ6-09-2016 22:19:08 3528 Using account DOMAIN\Veeam_Serviceġ6-09-2016 22:19:08 3528 Database master: failed to truncate transaction logs. This normally means that the account used for Application Aware backup is not a member of the role "sysadmin" on the instance, but I check and it was "sysadmin". I had a customer that contacted me to day because he got a warning that Veeam Backup was "Unable to truncate Microsoft SQL Server transaction logs.Details: Failed to process 'TruncateSQLLog' command.įailed to truncate SQL server transaction logs for instances: BI See guest helper log."
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |