I’m currently backing up a SQL VM via the Veeam SQL Plugin to a datastore within my production environment, at the same time I’m replicating said VM via CDP to my DR site.
I’ve currently setup the following schedule via the Veeam SQL Plugin:
15 minute transaction / log backup
Daily differential backup @ 18:30 (except Sunday)
Weekly full backup (Sunday) @ 18:30
The differential backups are failing when the CDP is enabled; the CDP runs 24-hours a day as we need near-zero dataloss.
Any ideas how I can have these two running at the same time without the errors above?
Many thanks,
LGH
Best answer by MicoolPaul
Hi,
I believe you’ve got application aware processing enabled within your CDP job.
Apologies if I’m telling you things you already know here, but the purpose of the transaction log shipping you’re performing is to have a periodic full database backup and then tracking just the changes (transactions) on the database between the full backups. Each subsequent transaction log shipping event that takes place must contain every transaction between the previous log shipping session and the current session, otherwise your database restoration would be transactionally inconsistent and you’d have malformed records at best.
The reason I mention this is that only one job should be handling any log truncation, but I suspect you have application aware processing enabled and configured in one of the following ways:
I believe you’ve got application aware processing enabled within your CDP job.
Apologies if I’m telling you things you already know here, but the purpose of the transaction log shipping you’re performing is to have a periodic full database backup and then tracking just the changes (transactions) on the database between the full backups. Each subsequent transaction log shipping event that takes place must contain every transaction between the previous log shipping session and the current session, otherwise your database restoration would be transactionally inconsistent and you’d have malformed records at best.
The reason I mention this is that only one job should be handling any log truncation, but I suspect you have application aware processing enabled and configured in one of the following ways:
