Comments
Sort by recent activity
Hi Dan, Ok that makes sense. Thanks for your help. Regards, Jason. / comments
Hi Dan,Ok that makes sense. Thanks for your help.Regards,Jason.
Hi Dan, Thank you, that is very helpful. I've set the jobs up as you say and I only get two conflicts; one at 01:15 and one at 01:30. These conflicts are between the full backups and the transaction log backups. I think I'm correct in saying the software is estimating how long the full backup of each database will take and it is determining (correctly) that the full backups and transaction log backups will overlap at those times. I'm thinking these conflicts probably aren't that big of a deal and are probably unavoidable in certain cases anyway. Would you agree with that? Finally, could you confirm my understanding of the conflicts, please? My understanding is that there is fundamentally no problem at the SQL level with running a full backup and a transaction log backup at the same time, and that the conflicts in the SQL Backup Pro software are simply saying I won't be able to use the SQL Backup Pro timeline to restore the backups to the times where the conflicts occurred, but I will still be able to restore the backup manually via SQL to those time points. Is that correct? Thanks, Jason. / comments
Hi Dan,Thank you, that is very helpful. I've set the jobs up as you say and I only get two conflicts; one at 01:15 and one at 01:30. These conflicts are between the full backups and the transaction...