Whats going on ?
-
I just started in a new company, i discovered the below statement in a job for a differnetial backup.
Why is the 'trunc. log on chkpt.' option being changed ? shouldnt 'trunc. log on chkpt.' be false if transaction log dumps are suppossed to be happening ?
why is the log being backed up in the differential backup job when it has its own job already ?
-- First, truncate the log
--BACKUP LOG dbname WITH TRUNCATE_ONLY
BACKUP DATABASE dbname TO [DIFFBKUP dbname ] WITH DIFFERENTIAL, INIT
-- initialize the LOG backup device after a differential backup
USE master
EXEC sp_dboption 'dbname', 'trunc. log on chkpt.', 'FALSE'
BACKUP LOG dbname TO [LOGSBKUP dbname] WITH INIT
-
Am i missing something here ?
-
Yes, trunc on checkpoint should be false if you're doing log backups. Only thing comes to mind is that they were trying to get the log to shrink, and just to be on the safe side were doing the differential first.
Andy
-
The process above is implemented on all production servers. Even though all documentation says that full log dumps are being carried out every 15 mins.
From what i can see full trasaction log dumps are not really being carried out at all ? am i right ?
USE master
EXEC sp_dboption 'dbname', 'trunc. log on chkpt.', 'FALSE'
BACKUP LOG dbname TO [LOGSBKUP dbname]
EXEC sp_dboption 'dbname', 'trunc. log on chkpt.', 'TRUE'
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply