Collected transaction logs do not match any existing full da

Availability for the Always-On Enterprise

Re: Collected transaction logs do not match any existing ful

Veeam Logoby JaYaKaAzZ » Tue May 12, 2015 3:14 pm 1 person likes this post

I opened a Case 00915509

Will inform about the results...

Best Regards
JaYaKaAzZ
Influencer
 
Posts: 24
Liked: 4 times
Joined: Mon Feb 03, 2014 8:01 am
Full Name: Artur Schneider

Re: Collected transaction logs do not match any existing ful

Veeam Logoby JaYaKaAzZ » Tue May 26, 2015 11:43 am 1 person likes this post

So here is a update

In my Case there were some strange translating errors in the Transaction Log Backup Log :) because the SQL Server was installed in German Language as the whole environment.

Code: Select all
[13.05.2015 09:28:13] <27> Error    Manche oder alle Identitätsverweise konnten nicht übersetzt werden. (System.Security.Principal.IdentityNotMappedException)
[13.05.2015 09:28:13] <27> Error       bei System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
[13.05.2015 09:28:13] <27> Error       bei System.Security.Principal.NTAccount.Translate(Type targetType)
[13.05.2015 09:28:13] <27> Error       bei System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
[13.05.2015 09:28:13] <27> Error       bei System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule)
[13.05.2015 09:28:13] <27> Error       bei Veeam.Backup.Core.CSqlBackupTransportUsage.TryUse(ISqlBackupTransport transport)
[13.05.2015 09:28:13] <27> Error       bei Veeam.Backup.Core.CSqlConveyorAcquireProxyOperation.AcquireTransport(ISqlBackupTransport[] transports, CSqlBackupLogManager logManager, CSqlDbBackupTask dbTask)
[13.05.2015 09:28:13] <27> Error       bei Veeam.Backup.Core.CSqlConveyorAcquireProxyOperation.DoExecute(CSqlConveyorCtx ctx)


The Colleagues from Support gave me few days later a hotfix, I had to replace some .dll files and now its working perfectly !

Thanks to Gabriela Aloyan great Support !
JaYaKaAzZ
Influencer
 
Posts: 24
Liked: 4 times
Joined: Mon Feb 03, 2014 8:01 am
Full Name: Artur Schneider

Re: Collected transaction logs do not match any existing ful

Veeam Logoby JXBold » Wed Jun 17, 2015 8:47 am

Hello,

same behavior at our customers site. It worked for once but then... We build the whole Veeam Backup Server new from scratch but with no effort. On the SQL Server Site it looks like that the Databases are backed up from Veeam.

Case 00932704.
Version 8.0 Build 2029

Regards...
JXBold
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jun 17, 2015 8:18 am
Full Name: Joerg Bold

Re: Collected transaction logs do not match any existing ful

Veeam Logoby ShallowTech » Wed Jul 22, 2015 3:02 pm

Does anyone have an update to this issue? We just started doing the SQL log backups and we are getting this error on some servers but not others. However, all servers were being backed up in the same jobs prior to enabling log backups.
ShallowTech
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jul 22, 2015 2:30 pm
Full Name: Michael Bedwell

Re: Collected transaction logs do not match any existing ful

Veeam Logoby v.Eremin » Thu Jul 23, 2015 9:39 am

Hi, Michael,

Unfortunately, the case is in German, so, I can't make sense of it. I'd recommend opening your own one and letting our support team investigate it directly.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13075
Liked: 949 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Collected transaction logs do not match any existing ful

Veeam Logoby AptlyBill » Tue Aug 04, 2015 1:14 pm

Is anyone who is having this issue noted whether you get this message on the daily incremental backups: "SQL Server version used by the backup server is older than the one installed in this VM. Upgrade is recommended to avoid issues with application items restore." It does not generate a failure or warning, but is just listed in the log for the daily incremental of the server. I wonder if this can cause an issue with matching the transaction logs with the stored backup of the database. I am seeing the same issue as noted above with a server getting successful daily incremental backups, but the hourly SQL backups for that server get the error mentioned in this post.
AptlyBill
Lurker
 
Posts: 1
Liked: never
Joined: Tue Aug 04, 2015 1:00 pm
Full Name: Bill

Re: Collected transaction logs do not match any existing ful

Veeam Logoby LaurentZ » Tue Aug 25, 2015 12:11 pm

I have the same issue since yesterday.
With Veeam B&R 8.0.0.2030, Full Backup OK, Incremental OK, and Transaction Logs every 60 minutes.
Everything worked well and suddenly, "Collected transaction logs do not match any existing full database" appeared on 1 database. Other db's still work.

I have open a case: 01004625

Thanks,
LaurentZ
Lurker
 
Posts: 2
Liked: never
Joined: Tue Feb 05, 2013 3:46 pm

Re: Collected transaction logs do not match any existing ful

Veeam Logoby john.heimiller » Thu Oct 01, 2015 8:32 pm

How do I tail this issue "01004625" so I get updates when action is taken....I'm new to Veeam and the Support interface.

We are getting this message as well but according to MSDB backup history the Database backups are being done. I am also able to restore to point in time using that tlog (and backup)....so its a bug.

Additionally, the message is inconsistent fro tlog backup to tlog backup...reports for some DBs one time and others the next...some log backups the message doesn't appear for any DBs....if it were true we would get it for every tlog backup for the same set of DBs until the next full Backup.

Thanks
john.heimiller
Novice
 
Posts: 4
Liked: 2 times
Joined: Thu Oct 01, 2015 3:11 pm
Full Name: John Heimiller

Re: Collected transaction logs do not match any existing ful

Veeam Logoby foggy » Fri Oct 02, 2015 12:22 pm

John, your best bet is to open your own case. As mentioned above, hotfix for this issue is available, so contact technical support to verify whether this is the same issue and get the hotfix.
foggy
Veeam Software
 
Posts: 14560
Liked: 1060 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Collected transaction logs do not match any existing ful

Veeam Logoby mobin.qasim » Sun Nov 29, 2015 3:24 pm

Hi Guys,

Any update on the mentioned error? I was testing Logs Truncate periodically every 60 minutes and was getting the same error for a couple of databases. I'm using Veeam 8.0.0.2084 so after that error I had disable Log Truncate so it doesn't mess anything else.

Could someone please help me out here.

Cheers
mobin.qasim
Enthusiast
 
Posts: 55
Liked: never
Joined: Wed Jun 19, 2013 7:23 pm
Full Name: Mobin Qasim

Re: Collected transaction logs do not match any existing ful

Veeam Logoby v.Eremin » Mon Nov 30, 2015 8:30 am

Have you already opened a support ticket? Thanks.
v.Eremin
Veeam Software
 
Posts: 13075
Liked: 949 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Collected transaction logs do not match any existing ful

Veeam Logoby mobin.qasim » Wed Dec 02, 2015 5:32 am

Yes, one of the support team members is looking into this issue and I'll update here once he gets back to me.

Cheers
mobin.qasim
Enthusiast
 
Posts: 55
Liked: never
Joined: Wed Jun 19, 2013 7:23 pm
Full Name: Mobin Qasim

Re: Collected transaction logs do not match any existing ful

Veeam Logoby v.Eremin » Wed Dec 02, 2015 10:24 am

Got it, kindly, keep working with the support engineer on addressing that, and update the topic, once the resolution is found. Thanks.
v.Eremin
Veeam Software
 
Posts: 13075
Liked: 949 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Collected transaction logs do not match any existing ful

Veeam Logoby mobin.qasim » Mon Dec 07, 2015 2:58 am

I've native SQL Job setup which backups up DBs once a day, so if I disabled native job everything looks fine. This is what Veeam engineer said:

"According to the log files, transaction logs didn`t match the DB, so we`ve failed.

Unfortunately not much we can do in this situation and you can use only one backup solution, this limitation comes to us from Microsoft SQL server architecture, so we are able to use only matching logs to be able to restore from. And if you will backup SQL DBs using other solution logs and will be in a different state."


I've tested one thing so want to share it with you guys as I'm not a SQL expert. if I disable native job and let Veeam truncate logs periodically at configured interval everything looks fine. But as soon as you manually commit transactions using following query, it throws the same error.

begin tranwhile (select size from sysfiles where fileid = 2) <= 1024 update TestTable set a = replicate ('a',8000)gocommit tran

I had to disable logs truncate option as it didn't workout as I expected.

Regards,

Mobin
mobin.qasim
Enthusiast
 
Posts: 55
Liked: never
Joined: Wed Jun 19, 2013 7:23 pm
Full Name: Mobin Qasim

Re: Collected transaction logs do not match any existing ful

Veeam Logoby v.Eremin » Mon Dec 07, 2015 9:25 am

The explanation provided by the engineer is valid, as only one solution can manage SQL logs. Having more than one application taking care about them would certainly lead to different failures, similar to the one reported in this thread. Thanks.
v.Eremin
Veeam Software
 
Posts: 13075
Liked: 949 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

PreviousNext

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google [Bot] and 23 guests