Post reply

Downgrading backup log buffers from 1024K to 64K

  • April 5, 2011 at 2:13 pm

    #237945

    Hi everybody,

    My server goes down 2- 3 weeks and I can't figure out what is causing it. I found this in error

    Downgrading backup log buffers from 1024K to 64K. What does it mean?

    I have:

    OS Name Microsoft(R) Windows(R) Server 2003, Enterprise Edition

    Version 5.2.3790 Service Pack 2 Build 3790

    System Model PowerEdge 2850

    System Type X86-based PC

    Processor x86 Family 15 Model 4 Stepping 3 GenuineIntel ~2992 Mhz

    Processor x86 Family 15 Model 4 Stepping 3 GenuineIntel ~2992 Mhz

    Processor x86 Family 15 Model 4 Stepping 3 GenuineIntel ~2992 Mhz

    Processor x86 Family 15 Model 4 Stepping 3 GenuineIntel ~2992 Mhz

    BIOS Version/Date Dell Computer Corporation A05, 1/9/2006

    SMBIOS Version 2.3

    Windows Directory C:\WINDOWS

    System Directory C:\WINDOWS\system32

    Boot Device \Device\HarddiskVolume2

    Locale United States

    Hardware Abstraction Layer Version = "5.2.3790.3959 (srv03_sp2_rtm.070216-1710)"

    Total Physical Memory 12,287.06 MB

    Available Physical Memory 6.06 GB

    Total Virtual Memory 23.78 GB

    Available Virtual Memory 17.73 GB

    Page File Space 12.00 GB

    Page File C:\pagefile.sys

  • April 5, 2011 at 2:37 pm

    #1307714

    Google terms: Virtual memory fragmentation. MemToLeave

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • April 5, 2011 at 3:54 pm

    #1307751

    Do I need to re start all my exchange servers

  • April 5, 2011 at 4:00 pm

    #1307752

    What does Exchange have to do with anything?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • April 5, 2011 at 6:49 pm

    #1307774

    I was reading wrong article

    The best solution get upgrade it to 64

    But what else can be done?

  • April 5, 2011 at 11:33 pm

    #1307813

    Find out what's using MemToLeave, increase the size of that reserved mem (and reduce the buffer pool by a like amount), restart SQL regularly. Not much really.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • April 6, 2011 at 7:21 am

    #1308006

    Find out what's using MemToLeave

    How can I do that?

    reduce the buffer pool by a like amount ? What anount?

    restart SQL regularly

    How often?

    Thank you for your help

  • October 7, 2011 at 10:47 am

    #1391868

    Is there a solution to this?

    I am also seeing the same issue whenever my log backup runs. It hasn't brought down SQL for me yet. And this all started when I started to do log shipping.

    I found an article that suggest setting the maxtransfersize could resolve this but how do I do that with log shipping?

    Any feedbacks would be greatly appreciated.

    Thanks.

  • July 26, 2012 at 11:01 am

    #1518071

    Hi

    We love the way you reply for all issues , but can you give little bit more details , I show you all posts , all are shorts and sweet , can you given some additional information , because guys who all

    are asking this question are not MVPs .

    Thanks

  • July 26, 2012 at 11:12 am

    #1518075

    Did you try searching for the terms Gail gave you? The first hit on Google is an article that explains the issue and offers some troubleshooting advice.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply