Replicate encountered third-party backup files during preliminary processing.

[MoeE]

Hi,

A client of ours has experienced this warning message after migrating their SQL Server source to an AWS EC2 instance:

"Replicate encountered third-party backup files during preliminary processing. As the 'Use third-party backup device' option is currently disabled, these files will not be processed for changes."

I've looked into it and found these two links:

1) A quite helpful Qlik Community article

2) A Qlik Community question

They describe that we can ignore this warning if "virtual backups exist, but they are not related to the regular transaction log backup process, and those backups don’t contain any changes that are relevant to replication, or they are done as "COPY_ONLY" (as mentioned in link 1).

My client has informed us that they are able to replicate data, and that the changes are going through to the target successfully.

My questions is - Since replication is still functioning, can this message be ignored? 

Help on this is appreciated. Thank you.

Kind regards,

Mohammed

[DesmondWOO · Accepted solution]

Hi @MoeE ,

Thank you for reaching out to the Qlik Community.

I believe it should be fine. If the customer still has concerns, you can enable verbose logging on SOURCE_CAPTURE to verify if Replicate can read online TLOG and backup files properly.

Regards,
Desmond

[MoeE]

Hi Desmond,

Thanks for the response. I also looked into this a bit. I agree it should be fine as long as the transaction log files aren't being archived by the third party software (into their own format), because if Replicate needs to read the archived transaction log files from the third party format then it may fail.

Thanks.

Regards,

Mohammed