October 8, 2014 at 9:23 am
With standard log shipping, the transaction log is truncated just as in a normal backup process.
When setting up log shipping, the log backups take the place of the old log backups on an existing server.
Is it possible to setup log shipping without truncating the log, allowing the normal log backups to do truncate the log.
I don't think it is possible, because everytime the log shipping takes a non-truncated copy of the log, it will not be in sequence because the other log backup would of truncated the log already.
Just exploring options. We have a 3rd party tool(comvault) doing log backups and it is not possible to get a copy of those log backups in order to do manual log shipping to a remote server that doesn't have comvault.
October 8, 2014 at 10:41 am
all log operations are the responsibility of the LS agent job. I'd be highly surprised if comvault cant be told to skip databases. At the least just disable it and run your own TSQL agent jobs to backup. There are plenty of scripts around
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply