Discussions specific to the VMware vSphere hypervisor
Post Reply
pkelly_sts
Expert
Posts: 568
Liked: 62 times
Joined: Jun 13, 2013 10:08 am
Full Name: Paul Kelly
Contact:

SQL backed up twice (with truncate!)

Post by pkelly_sts » Apr 27, 2018 2:22 pm

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
Veeam Software
Posts: 17931
Liked: 1512 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL backed up twice (with truncate!)

Post by foggy » Apr 27, 2018 3:52 pm 1 person likes this post

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
Expert
Posts: 568
Liked: 62 times
Joined: Jun 13, 2013 10:08 am
Full Name: Paul Kelly
Contact:

Re: SQL backed up twice (with truncate!)

Post by pkelly_sts » Apr 30, 2018 8:01 am

Ah, thanks for the confirmation foggy! :)

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 15 guests