-
タイトル
ApexSQL Log is not showing all the transactions for the day full backup was created -
説明
In these cases the following errors can be found in ApexSQL Log log files:
2022-07-13 11:03:03.990 5980 10832 INFO : Opening 'E:\****_***.ldf' log source. Its size is: 75,254,333,440
2022-07-13 11:03:11.474 5980 10832 INFO : Found 33,259 raw transaction log operations from 2020-03-23 18:02:38.090 to 2022-07-07 10:00:12.500
2022-07-13 11:03:11.474 5980 10832 WARN : Gap in log source detected between 00029B0A:0001FFD4:0001 and 00029D29:0000C23C:0001
2022-07-13 11:03:11.474 5980 10832 INFO : Statistics for log operations:
2022-07-13 11:03:11.474 5980 10832 INFO : Total log operations: 67,082
2022-07-07 19:09:42.747 6160 10260 WARN : Skipped operations at 29000100:9F003000:7700 since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.747 6160 10260 WARN : Skipped operations at 00D300D3:013E00DA:013E since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.747 6160 10260 WARN : Skipped operations at 00000000:00000000:0000 since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.747 6160 10260 WARN : Skipped operations at 00E400E4:014E00EA:014E since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.762 6160 10260 WARN : Skipped operations at 00D300D3:013E00DA:013E since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.762 6160 10260 WARN : Skipped operations at 00000000:00000000:0000 since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.762 6160 10260 WARN : Skipped operations at 00D300D3:013C00D8:013C since they don't belong to 00000200:00401300:0400
2022-07-07 19:09:42.762 6160 10260 WARN : Skipped operations at 00D300D3:014100DD:0141 since they don't belong to 00000200:00401300:0400
The above errors indicate that ApexSQL Log wasn't able to find the regularly updated t-log backup chain to successfully recover its data.
-
対策
To solve this issue simply add full transaction log chain when adding transaction logs in "Select data sources" step.
To do so, please consult following article for more info:
Create and maintain the full chain of transaction log backups
Reason that tool occasionally hangs is very much related to a missing full t-log chain.
Additionally, regularly taken transaction log backups must be sequential so tool don't end up performing auditing with gaps in data.
This cause ApexSQL Log to hangs cause it is trying to read something that isn't there at the time.
This is not a bug, it is the expected behavior of the tool.
Please note that only adding full backup is not enough to ensure all the transactions are in them, same goes for reading only online transaction logs.
Regularly taken transaction logs are mandatory so no gaps in data will occur.