FULL and TRANSACTION LOG at the same time?

Last post 02-20-2019, 11:17 AM by Boberic. 5 replies.
Sort Posts: Previous Next
  • FULL and TRANSACTION LOG at the same time?
    Posted: 01-28-2019, 1:44 PM

    What happens to a SQL backup when:

     

    * Set FULL SQL backups at 7PM SUNDAYS;

    * ALSO SET TRANSACTION LOG backup DAILY at 7pm.

     

    On SUNDAY at 7PM Does it only do a FULL, or does it do both? If both, which order and is that configurable? 

  • Re: FULL and TRANSACTION LOG at the same time?
    Posted: 01-29-2019, 1:14 PM

    It will do both.  Logs won't be truncated while the full is running.  Then they will truncate once the next t-log kicks off after the full completes.  This is by design in SQL incase a full fails and you won't break the chain.  

  • Re: FULL and TRANSACTION LOG at the same time?
    Posted: 01-30-2019, 9:15 AM

    ZCameron:

    It will do both.  Logs won't be truncated while the full is running.  Then they will truncate once the next t-log kicks off after the full completes.  This is by design in SQL incase a full fails and you won't break the chain.  


    Thanks. Which order does it do them in though? Or does that not matter? 

  • Re: FULL and TRANSACTION LOG at the same time?
    Posted: 02-14-2019, 4:24 PM

    There really isn't an order.  The T-logs will continue to run until the full completes.

  • Re: FULL and TRANSACTION LOG at the same time?
    Posted: 02-14-2019, 5:24 PM

    ZCameron:

    There really isn't an order.  The T-logs will continue to run until the full completes.

     

    Thanks

  • Re: FULL and TRANSACTION LOG at the same time?
    Posted: 02-20-2019, 11:17 AM

    Is there a reason you have to schedule it that way?  If you can't have it skip the 7pm transaction log backup, what if you instead have it run the transaction log backup at 5 mins past the top of the hour?

    Here's what I mean.  Let's say you're running hourly transaction log backups.  You could have those run at 5 mins past the hour so you're never trying to run both at the same time.  

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy