Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > System Center Data Protection Manager Forums > Data Protection Manager - SQL Protection > DPM2010 - reducing transaction log file size

Answered DPM2010 - reducing transaction log file size

    •  
      Sunday, March 20, 2011 9:32 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      we are using DPM2010 to backup our SQL2008 databases. Currently our transaction log files grew up to about 384GB.

      How can I reduce transaction log file size during the DPM backup process?

      Martin Kulov
      www.kulov.net

      Microsoft Regional Director
      VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker
       

    Answers

    • Monday, March 21, 2011 12:25 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      SQL will truncate the logs files after each DPM Synchronization (incremental backup). However truncation is not the same as shrinking. Once a log file grows, you will need to shrink it manually.  If the time between synchronizations is set for something like 12 or 24 hours, then the log file has already grown and you will need to shrink it manually, then reduce the synchronization period to keep it to a resonable size.  If the synchronization selection is ‘Just before a recovery point’ then incremental backups won’t get scheduled. This option is a way of telling DPM, that the user is interested only in express full backups and not incremental backups.

      Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Friday, May 20, 2011 10:27 PM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi Martin,

      From DPM configuration stand point, no, we just backup SQL and truncate the logs (create empty space inside the transaction log).

      The Shrink process needs to be done manually or through a SQL Maintenance job

      You can also create a post-backup script to deal with the shrink process.

      More information about Pre-Backup/Post-Backup script can be found in the link below

      http://technet.microsoft.com/en-us/library/bb808870.aspx

      http://blogs.technet.com/b/dpm/archive/2010/10/13/how-to-use-a-pre-backup-or-post-backup-script-to-reset-the-archive-bit-in-system-center-data-protection-manager.aspx

       

      Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
       

    All Replies

    • Monday, March 21, 2011 12:25 AM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      SQL will truncate the logs files after each DPM Synchronization (incremental backup). However truncation is not the same as shrinking. Once a log file grows, you will need to shrink it manually.  If the time between synchronizations is set for something like 12 or 24 hours, then the log file has already grown and you will need to shrink it manually, then reduce the synchronization period to keep it to a resonable size.  If the synchronization selection is ‘Just before a recovery point’ then incremental backups won’t get scheduled. This option is a way of telling DPM, that the user is interested only in express full backups and not incremental backups.

      Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Friday, May 20, 2011 9:43 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi Martin,

       

      Just checking if the response given by Mike Jacquet answered your question.

      Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
       
    • Friday, May 20, 2011 10:11 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi Wilson,

      Not really. I did not get it if there is a way to shrink the files or not. I understood that there is a manual way of doing this. I can expect that. However I am curios if the product support that out of the box, can it be extended to do so or is there any other trick to implement it?

      Thanks,

      Martin

      Martin Kulov
      www.kulov.net

      Microsoft Regional Director
      VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker
       
    • Friday, May 20, 2011 10:27 PM
      Moderator
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      Hi Martin,

      From DPM configuration stand point, no, we just backup SQL and truncate the logs (create empty space inside the transaction log).

      The Shrink process needs to be done manually or through a SQL Maintenance job

      You can also create a post-backup script to deal with the shrink process.

      More information about Pre-Backup/Post-Backup script can be found in the link below

      http://technet.microsoft.com/en-us/library/bb808870.aspx

      http://blogs.technet.com/b/dpm/archive/2010/10/13/how-to-use-a-pre-backup-or-post-backup-script-to-reset-the-archive-bit-in-system-center-data-protection-manager.aspx

       

      Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
       
    • Friday, May 20, 2011 10:37 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      got it!

      thanks!

      Martin Kulov
      www.kulov.net

      Microsoft Regional Director
      VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker