SQL backed up twice (with truncate!)

[pkelly_sts]

I recently became aware that a second legacy SQL native backup job was still running even though we have a Veeam job with Transaction backups.

I believe this is a very bad situation from a backup perspective due to breaking backup chains in both sides etc. so have had the local job disabled but am trying to figure out what, if anything, I should do to "reset" things within the Veeam SQL backup to get things back on an even keel.

Ideally I'd like to avoid an active full as it's a large server and we're dependent on getting off-site backups over-the-wire so would prefer to avoid a 350gb network transfer if I can.

So, any advice as to the options, or will things just naturally take care of themselves now I've stopped the native backup?

[foggy]

Hi Paul, full backup is not required. The chain will be fine after next backup job run (be it either full or incremental). Thanks!

[pkelly_sts]

Ah, thanks for the confirmation foggy!