IMHO it is cleaner, clearer, to just delete versus truncate as it might as well not be there at all. Such backup would not be useful for SQLserver itself, nor for Replicate. Veeam truncates the log files as part of its backup strategy.įor real? That's a corruption strategy, not a back strategy. That's likely the consequence of a truncation. > LSN '001f611b:00003584:0003' could not be retrieved as it is located in the backup logs, while the endpoint is configured to access the online logs only That's possible a table which was deleted before the archive log was processed. > mssql_approve_table_full_logging_setup(.) failed in checking PK presence for table identified by ID '1954106002' Replicate is willing to help some with the 'advanced' endpoint options like 'Select virtual backup device types' and 'Backup folder preprocessing command:' but ultimately it is dependent its environment to restore a valid archive log. > What is the best way to configure replication when using a third party backup solution such as Veeam?Īsk the third party for support, or money back!
> Veeam truncates the log files as part of its backup strategy.įor real? That's a corruption strategy, not a backup strategy.
