Purge logs of mirrored DB

Our Citrix Xendesktop DB is mirrored between servers at 2 sites. As such the recovery model is set to Full. Even though we successfully run full backups on that DB each night, the logs for the database don't get purged and are 30GB for a DB that is about 100mb or less. FWIW we're using Netbackup.

How can i purge these logs without reducing our ability to fully restore if need be?
LVL 8
akalbfellAsked:
Who is Participating?
 
Eugene ZConnect With a Mentor Commented:
and
you should set frequent trans log backups: every 15 -30 minutes.
this will help to keep trans log backup size

--
also if Trans log backup and shrink  log file is not helping,
check if anything using it by running  

select log_reuse_wait_desc from sys.databases where name = 'yourPrimcipalDBname'
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

Quick way is to set recovery model to simple, run backup and turn back to full once finished. The logs will be gone.
0
 
akalbfellAuthor Commented:
Recovery model can't be set to simple for a mirrored DB
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
arnoldConnect With a Mentor Commented:
You likely have an active transaction preventing the log from shrinking.
run
dbcc opentran(database)

on a mirrored DB, the transaction log does not actually shrink unless you have a setting to shrink logs/databases

You may want to setup a more frequent transaction log backup to manage the transaction log size.  i.e. if you backup once a day, then the transaction log will grow based on the number of transactions within 24hours.  if you perform, 2 or 3, 4 or more transaction log backups, the process of the transaction log backup will free up the space within the transaction log for new transactions.
100MB database with a 30GB transaction log may mean that you have a "service" that creates an active transaction that only clears on server reboot.
Find the transaction and you will be closer to solving your issue.

Had such an application at a site, a service monitoring a DB for events created a transaction that kept the transaction log growing and growing, until the service was restarted or the server was restarted.
0
 
Eugene ZCommented:
please clarify: are you talking about principal OR mirror db?

if principal-- make sure you are running trans log backups

for the mirror - just after trans logs of the principal DB made small and  after the new backup
was used to reset mirror db  - you will get small trans logs on the mirrored DB
0
 
akalbfellAuthor Commented:
I am talking about shrinking the principal, not the mirror.
I have done transaction log backups which finish successfully but the file doesn't change in size.
0
 
Eugene ZCommented:
try after trans log backup to shrink
0
 
akalbfellConnect With a Mentor Author Commented:
I tried a few things but still the log files haven't shrunk.

I disabled mirroring first of all
I tried running a full backup with the mode set to simple, that didn't work
I tried running a full backup with the mode set to full then a transaction log backup, that didn't work... Both times the jobs ran just fine but the logs still haven't shrunk.

Any ideas?
0
 
akalbfellAuthor Commented:
Finally got it going. Ended up breaking the mirror, running some backups (which didn't seem to help immediately) then shrinking the logs. Then just had to rebuild the mirror.
0
All Courses

From novice to tech pro — start learning today.