locked
Server 2003, SQL 2005, Raid Array, memory availability problem RRS feed

  • Question

  • My server has used 40GB of C-Drive partition and I am out of memory in that partition. I have over 500 GB on the D drive. I am running exchange server as well. I need help in figuring out what the memory hogs or memory loss is coming from. I have lots of the $NtUninstallKB97....$ and I have read that I can move those to the D Drive or delete them to get some room but I am not sure if this is correct?

    Is the default share points that I am reading about the problem? If so, how do I find where they are being written and how do I move them to the D partition? or delete older share points?

    Monday, August 9, 2010 12:24 PM

Answers

  • Download and install the WinDirStat utility.  Run it against your C:\ drive partition and it will list all folders and files and tell you how large each one is.  In the Options for the utility, there is a selection to show unknown - turn that on to see how much space is being used by 'unknown' files.  If you have a lot of space being used here - it could be the system restore allocation.
     
    If it is the system restore allocation, you can reset the max size so it won't get too large and/or remove older restore points.  You could even turn this off on the server, but - make sure you have good backups of the server to restore from if you need to.
     
    Jeff
    "ChunSong Feng -MSFT" wrote in message news:320ef5e5-525f-44df-8cb5-1acf83cf594a...

    Hi,

    Based on my understanding, the SQL Server is not the main application which eats up the disk space since total size of databases is very small (86MB and 52MB). Also, as you described that the Symantec Back Up Exec 12 for Windows Server occupy large size of disk space which might have many back up data.

    To resolve this issue, please check which applications (like System Back Up Exec 12 for Windows Server) consumes the most of the disk space. And then delete those data if you can make sure that you don’t need them anymore, or move those application data to other disk drive like drive D.

    However, for a long term, I would suggest you configure the application data location to the other drives rather than default system drive. For example, you can configure SQL Server user databases to drive D, thus the entire user database would be stored in the system drive. Besides, you can add more disk space to the drive C.

    Thanks,
    Chunsong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Tom Li - MSFT Tuesday, August 17, 2010 8:49 AM
    Wednesday, August 11, 2010 2:12 AM
  • Hi,

    Based on my understanding, the SQL Server is not the main application which eats up the disk space since total size of databases is very small (86MB and 52MB). Also, as you described that the Symantec Back Up Exec 12 for Windows Server occupy large size of disk space which might have many back up data.

    To resolve this issue, please check which applications (like System Back Up Exec 12 for Windows Server) consumes the most of the disk space. And then delete those data if you can make sure that you don’t need them anymore, or move those application data to other disk drive like drive D.

    However, for a long term, I would suggest you configure the application data location to the other drives rather than default system drive. For example, you can configure SQL Server user databases to drive D, thus the entire user database would be stored in the system drive. Besides, you can add more disk space to the drive C.

    Thanks,
    Chunsong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Tom Li - MSFT Tuesday, August 17, 2010 8:49 AM
    Wednesday, August 11, 2010 2:02 AM

All replies

  • Hi

    $NtUnistallkB97xxxx$ folders are related to installation. If you want to rollback a KB(patch)  Windows will get installation details from this folder. If you remove $NtUnistallkB97xxxx$folders you cant uninstall properly. yes You can remove $NtUnistallkB97xxxx$ folders.


    Ramesh S
    www.sequalserver.com
    Monday, August 9, 2010 12:39 PM
  • thank you. do you know anything about the restore points being a problem?
    Monday, August 9, 2010 12:45 PM
  • Out of storage and out of memory are TWO completely different things. I assume you mean out of storage.

    Although what I'd really be doing is seeing what caused my disk to fill up and stop that problem because it's going to happen again.

    One thing I would look at is your pagefile and see how it's configured. That you could move with relative ease.

    What do you mean by share points?

     


    Allan Hirt Blog: http://www.sqlha.com/blog Author: Pro SQL Server 2008 Failover Clustering (out now!)
    Monday, August 9, 2010 3:17 PM
  • Microsoft Share Point is a default configuration on server 2003 as I understand it. I also understand that these sharepoints can be stored on the C drive and suck up memory. I do not know if mine is on or off or has the 3 GB thing.

    I agree, I want to solve the problem as to why the 40 GB have been sucked up.  I do not know why. We do run Symantec Back Up Enterprise software as well.

    As for the page file, please tell me how to get this to you and I will get it posted.

    Monday, August 9, 2010 10:18 PM
  • Hi,

    Select My computer, choose aAdvanced option ---> performance--> Settings --> Advanced --> Virtual Memory --> Change --> Set required drive and assign proper value. This activity required Server reboot.


    Ramesh S
    www.sequalserver.com
    Monday, August 9, 2010 10:44 PM
  • If there is NO MORE space available, how can this help? It is already set to 2046 MB. thanks for the thought though.

    Tuesday, August 10, 2010 12:32 AM
  • This forum is about SQL Server so its not the best place to ask this question. Unless you know specifically  that sql server is the cause of your disk space issues (i.e. I assume you mean disk space when you say memory.  memory refers to RAM, but you are talking about space on partitions) If sql server is the problem then you can move you database to your D drive   although this is only part of the problem.  It sounds like your real problem is that your c drive partition was sized too small, especially since it seems all your application data is stored there. 

    What i would do is resize your partitions so that you either eliminate or reduce your D drive and put that free space onto C. There are many ways of doing this and it depends on your particular circumstance.

    If there is one big RAID volume configured then you can delete the D drive partition and extend the volume .

    If you have separate volumes defined by the RAID controller configured then you'll have to backup your partition either with something like Clonezilla or a commercial tool like Ghost   re-configure your RAID volume as one big drive then restore your partition.


    IMHO you're probably dealing with something that's out of your league and it's best to get a professional involved.  These are risky operations for the novice and you risk losing all your data if you make a mistake.

    Tuesday, August 10, 2010 1:01 AM
  • Thanks, I would agree with you on several aspects. I initially posted this elsewhere and was told to repost it here? So I did. The Raid has four other HDs plus the D-Drive. the Raid backs up the D drive. In theory, nothing is suppose to be writing to the C Drive, but I can not figure out why the C drive is slowly getting bigger???

    I understand changing partitions on a drive is not ideal and somewhat risky.

    I would really like to figure out why it is getting bigger. It seems like most other boards blame the SQL 2005?? You are right, I do not know. It seems like most do not know either, so I am trying to get a handle on this somehow.

    I will not be repartitioning the drive. It is out of my league.

    Tuesday, August 10, 2010 1:58 AM
  • If you have a default install of SQL Server, Exchange, most other software EVERYTHING will write to the C drive.

    If sql server is to blame for the space glut then you will find .mdf/.ndf  or .ldf in are taking up a large amount of space, typically under a directory like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.  Is this the case? What version of SQL Server are you running and what are you using it for? Was it installed for a specific reason or is it part of an SBS server install?

    There is a great utility out there called TreeSize .  This will help you discover what files/directories are to blame for your storage glut.

     

     

    Tuesday, August 10, 2010 5:46 AM
  • Here are 2 Different LOG folder, error files from different folders. The first is from the LOG folder of MS$Sharepoint folder, most recent error file. The second error file is a recent error but a large file of 96 MB, from the LOG folder, in the MSSQL FOLDER. I do not know if there will help.

    It seems like I have two different SQL server builds? the 2000 version to run the sharepoint, and the 2005 version incharge of the SQLBackup?

     

    2010-08-09 08:57:29.46 server    Microsoft SQL Server  2000 - 8.00.2055 (Intel X86)
     Dec 16 2008 19:46:53
     Copyright (c) 1988-2003 Microsoft Corporation
     Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)

    2010-08-09 08:57:29.53 server    Copyright (C) 1988-2002 Microsoft Corporation.
    2010-08-09 08:57:29.54 server    All rights reserved.
    2010-08-09 08:57:29.54 server    Server Process ID is 2496.
    2010-08-09 08:57:29.54 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
    2010-08-09 08:57:29.71 server    SQL Server is starting at priority class 'normal'(4 CPUs detected).
    2010-08-09 08:57:30.03 server    SQL Server configured for thread mode processing.
    2010-08-09 08:57:30.09 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
    2010-08-09 08:57:30.98 spid3     Starting up database 'master'.
    2010-08-09 08:57:31.82 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
    2010-08-09 08:57:31.82 spid5     Starting up database 'model'.
    2010-08-09 08:57:31.92 spid3     Server name is 'BROWN01\SHAREPOINT'.
    2010-08-09 08:57:31.92 spid3     Skipping startup of clean database id 4
    2010-08-09 08:57:31.92 spid3     Skipping startup of clean database id 5
    2010-08-09 08:57:31.92 spid3     Skipping startup of clean database id 6
    2010-08-09 08:57:31.92 spid3     Starting up database 'STS_brown01_1'.
    2010-08-09 08:57:32.12 server    SQL server listening on Shared Memory.
    2010-08-09 08:57:32.12 server    SQL Server is ready for client connections
    2010-08-09 08:57:32.60 spid5     Clearing tempdb database.
    2010-08-09 08:57:33.06 spid5     Starting up database 'tempdb'.
    2010-08-09 08:57:37.09 spid3     Recovery complete.
    2010-08-09 08:57:39.74 spid51    Starting up database 'STS_Config'.
    2010-08-09 08:57:50.21 spid3     SQL global counter collection task is created.
    2010-08-09 23:00:23.16 spid52    Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
    2010-08-09 23:00:24.30 spid52    Starting up database 'msdb'.
    2010-08-09 23:00:24.66 spid52    Starting up database 'STS_OEMSBSCN-3935_1'.

    This following information is from the MSSQL/LOG folder, this is the largest error

    2010-07-26 08:38:57.70 Server      Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
     May 26 2009 14:24:20
     Copyright (c) 1988-2005 Microsoft Corporation
     Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

    2010-07-26 08:38:57.73 Server      (c) 2005 Microsoft Corporation.
    2010-07-26 08:38:57.73 Server      All rights reserved.
    2010-07-26 08:38:57.73 Server      Server process ID is 2460.
    2010-07-26 08:38:57.73 Server      Authentication mode is WINDOWS-ONLY.
    2010-07-26 08:38:57.73 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2010-07-26 08:38:57.73 Server      This instance of SQL Server last reported using a process ID of 2376 at 7/23/2010 9:12:58 AM (local) 7/23/2010 1:12:58 PM (UTC). This is an informational message only; no user action is required.
    2010-07-26 08:38:57.73 Server      Registry startup parameters:
    2010-07-26 08:38:57.75 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2010-07-26 08:38:57.75 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2010-07-26 08:38:57.75 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2010-07-26 08:38:57.84 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2010-07-26 08:38:57.84 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2010-07-26 08:38:58.54 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2010-07-26 08:39:00.48 Server      Database mirroring has been enabled on this instance of SQL Server.
    2010-07-26 08:39:00.96 spid4s      Starting up database 'master'.
    2010-07-26 08:39:03.47 spid4s      SQL Trace ID 1 was started by login "sa".
    2010-07-26 08:39:03.66 spid4s      Starting up database 'mssqlsystemresource'.
    2010-07-26 08:39:03.97 spid4s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
    2010-07-26 08:39:05.61 spid8s      Starting up database 'model'.
    2010-07-26 08:39:05.73 spid4s      Server name is 'BROWN01\BKUPEXEC'. This is an informational message only. No user action is required.
    2010-07-26 08:39:05.77 spid4s      Starting up database 'msdb'.
    2010-07-26 08:39:05.96 Server      The certificate was successfully loaded for encryption.
    2010-07-26 08:39:06.07 Server      Server is listening on [ 'any' <ipv4> 51208].
    2010-07-26 08:39:06.09 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BKUPEXEC ].
    2010-07-26 08:39:06.09 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$BKUPEXEC\sql\query ].
    2010-07-26 08:39:06.11 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
    2010-07-26 08:39:06.15 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2010-07-26 08:39:06.35 spid8s      Clearing tempdb database.
    2010-07-26 08:39:07.69 spid8s      Starting up database 'tempdb'.
    2010-07-26 08:39:08.41 spid4s      Recovery is complete. This is an informational message only. No user action is required.
    2010-07-26 08:39:11.81 spid11s     The Service Broker protocol transport is disabled or not configured.
    2010-07-26 08:39:11.85 spid11s     The Database Mirroring protocol transport is disabled or not configured.
    2010-07-26 08:39:15.14 spid11s     Service Broker manager has started.
    2010-07-26 08:39:52.93 spid51      Starting up database 'BEDB'.
    2010-07-26 08:39:53.43 spid52      Starting up database 'BE_DLO'.
    2010-07-26 08:39:54.82 spid51      Starting up database 'BEDB'.
    2010-07-26 08:39:57.79 spid51      Starting up database 'BEDB'.
    2010-07-26 08:41:17.12 spid63      Starting up database 'BE_DLO'.
    2010-07-26 08:41:18.21 spid53      Starting up database 'BE_DLO'.
    2010-07-26 08:41:20.60 spid63      Using 'XPDLOShareu.dll' version '0003.01.338' to execute extended stored procedure 'sp_shadow_get_report_list'. This is an informational message only; no user action is required.
    2010-07-26 23:00:12.94 spid55      Using 'xplog70.dll' version '2005.90.4035' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2010-07-26 23:19:21.81 spid55      I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    2010-07-26 23:19:21.82 spid56      I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    2010-07-26 23:19:21.82 spid63      I/O is frozen on database BEDB. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    2010-07-26 23:19:21.82 spid64      I/O is frozen on database BE_DLO. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    2010-07-26 23:19:21.82 spid57      I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
    2010-07-27 08:54:34.87 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 300, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 08:54:35.12 spid78      Using 'dbghelp.dll' version '4.0.5'
    2010-07-27 08:54:35.16 spid78      **Dump thread - spid = 78, PSS = 0x0946B2D0, EC = 0x0946B2D8
    2010-07-27 08:54:35.16 spid78      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0004.txt
    2010-07-27 08:54:35.16 spid78      * *******************************************************************************
    2010-07-27 08:54:35.16 spid78      *
    2010-07-27 08:54:35.16 spid78      * BEGIN STACK DUMP:
    2010-07-27 08:54:35.16 spid78      *   07/27/10 08:54:35 spid 78
    2010-07-27 08:54:35.16 spid78      *
    2010-07-27 08:54:35.16 spid78      * Latch timeout
    2010-07-27 08:54:35.16 spid78      *
    2010-07-27 08:54:35.16 spid78      * Input Buffer 124 bytes -
    2010-07-27 08:54:35.16 spid78      *    d b o . [ A u t  14 00 64 00 62 00 6f 00 2e 00 5b 00 41 00 75 00 74 00
    2010-07-27 08:54:35.16 spid78      *  o C l e a r A l e  6f 00 43 00 6c 00 65 00 61 00 72 00 41 00 6c 00 65 00
    2010-07-27 08:54:35.16 spid78      *  r t ]     &        72 00 74 00 5d 00 00 00 00 00 26 04 04 00 00 00 00 00
    2010-07-27 08:54:35.16 spid78      *   o  À   (^Ó   ç.   00 6f 08 08 c0 9d 00 00 28 5e d3 00 00 00 e7 2e 00 09
    2010-07-27 08:54:35.16 spid78      *     2. R E J U V E  04 00 01 32 2e 00 52 00 45 00 4a 00 55 00 56 00 45 00
    2010-07-27 08:54:35.16 spid78      *  N 8 U \ a d m i n  4e 00 38 00 55 00 5c 00 61 00 64 00 6d 00 69 00 6e 00
    2010-07-27 08:54:35.16 spid78      *  i s t r a t o r    69 00 73 00 74 00 72 00 61 00 74 00 6f 00 72 00
    2010-07-27 08:54:35.16 spid78      * 
    2010-07-27 08:54:35.16 spid78      * *******************************************************************************
    2010-07-27 08:54:35.16 spid78      * -------------------------------------------------------------------------------
    2010-07-27 08:54:35.16 spid78      * Short Stack Dump
    2010-07-27 08:54:35.19 spid78      Stack Signature for the dump is 0xE890A222
    2010-07-27 08:54:41.08 spid78      External dump process return code 0x20000001.
    External dump process returned no errors.

    2010-07-27 08:59:41.07 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 600, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:03:36.43 spid76      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28988 : 0, waittime 300, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:04:41.07 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 900, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:08:36.43 spid76      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28988 : 0, waittime 600, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:09:41.07 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 1200, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:12:38.01 spid80      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28E38 : 0, waittime 300, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:13:36.43 spid76      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28988 : 0, waittime 900, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:14:41.07 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 1500, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:17:38.00 spid80      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28E38 : 0, waittime 600, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:18:36.43 spid76      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00A28988 : 0, waittime 1200, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:19:41.06 spid78      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x00CD4A78 : 0, waittime 1800, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-07-27 09:21:39.58 spid81      Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x0099AB68 : 0, waittime 300, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.

    edited down, there are the similiar type of line items for quite a bit, then it finally ends with the following.

    2010-08-02 09:17:21.96 spid234     Time out occurred while waiting for buffer latch -- type 2, bp 02C8BD70, page 1:1511, stat 0x2c00109, database id: 5, allocation unit id: 364450339028992/82975362318336, task 0x087C9018 : 0, waittime 441000, flags 0x1a, owning task 0x00A2E7A8.  Continuing to wait.
    2010-08-02 09:17:22.45 spid57      Error: 18210, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 spid57      BackupVirtualDeviceFile::TakeSnapshot:  failure on backup device 'BE_SQLAgent-master__afb9b83e_d7ff_47e7_8e79_a6f653f83248_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    2010-08-02 09:17:22.45 spid55      Error: 18210, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 spid55      BackupVirtualDeviceFile::TakeSnapshot:  failure on backup device 'BE_SQLAgent-msdb__d23d57ad_1717_4e4a_8da5_fb385ba9f373_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    2010-08-02 09:17:22.46 spid56      Error: 18210, Severity: 16, State: 1.
    2010-08-02 09:17:22.46 spid56      BackupVirtualDeviceFile::TakeSnapshot:  failure on backup device 'BE_SQLAgent-model__a50d0e1e_2c09_4736_bf8c_3e648ad7a9e1_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    2010-08-02 09:17:22.46 spid63      Error: 18210, Severity: 16, State: 1.
    2010-08-02 09:17:22.46 spid63      BackupVirtualDeviceFile::TakeSnapshot:  failure on backup device 'BE_SQLAgent-BEDB__f8ee94dc_82ff_44d8_bdc6_06f9957786b2_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    2010-08-02 09:17:22.46 Backup      Error: 3041, Severity: 16, State: 1.
    2010-08-02 09:17:22.46 Backup      BACKUP failed to complete the command BACKUP DATABASE BEDB. Check the backup application log for detailed messages.
    2010-08-02 09:17:22.45 Backup      Error: 3041, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 Backup      BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
    2010-08-02 09:17:22.45 Backup      Error: 3041, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 Backup      BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
    2010-08-02 09:17:22.45 Backup      Error: 3041, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 Backup      BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
    2010-08-02 09:17:22.45 Backup      Error: 3041, Severity: 16, State: 1.
    2010-08-02 09:17:22.45 Backup      BACKUP failed to complete the command BACKUP DATABASE BE_DLO. Check the backup application log for detailed messages.
    2010-08-02 09:17:22.47 spid55      I/O was resumed on database msdb. No user action is required.
    2010-08-02 09:17:22.47 spid56      I/O was resumed on database model. No user action is required.
    2010-08-02 09:17:22.47 spid57      I/O was resumed on database master. No user action is required.
    2010-08-02 09:17:22.47 spid63      I/O was resumed on database BEDB. No user action is required.
    2010-08-02 09:17:22.55 spid64      Error: 18210, Severity: 16, State: 1.
    2010-08-02 09:17:22.55 spid64      BackupVirtualDeviceFile::TakeSnapshot:  failure on backup device 'BE_SQLAgent-BE_DLO__f5b8ec46_2719_4856_8859_d63787701779_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
    2010-08-02 09:17:22.55 spid64      I/O was resumed on database BE_DLO. No user action is required.
    2010-08-02 09:17:22.55 spid4s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2010-08-02 09:17:22.55 Server      The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x862, state: 3. Administrator should deregister this SPN manually to avoid client authentication errors.

    Tuesday, August 10, 2010 12:51 PM
  • PLEASE SEE ABOVE MESSAGE TOO!

    I looked at the MDF files and there are a few different versions of .mdf files, the entire data folder is 86 MBs. That does not seem too large, the largest is mssqlsystemresource.mdf and it is 39 MBs.

    In the SQL Sharepoint folder, the largest .mdf is master.mdf and it is 20 MBs. The entire data folder is 52 MBs.

    so neither folder is too large? correct?

    Tuesday, August 10, 2010 1:02 PM
  • Your DBs are not consuming your disk space - they're pretty small. So something else is filling your disk, which in turn is causing issues with SQL I'm sure.

    Those errors are backup errors. What are you using to back up the DBs?


    Allan Hirt Blog: http://www.sqlha.com/blog Author: Pro SQL Server 2008 Failover Clustering (out now!)
    Tuesday, August 10, 2010 7:15 PM
  • The backup as far as I can tell is Symantec Back Up Exec 12 for Windows Server. It does have a large folder.
    Tuesday, August 10, 2010 10:04 PM
  • Hi,

    Based on my understanding, the SQL Server is not the main application which eats up the disk space since total size of databases is very small (86MB and 52MB). Also, as you described that the Symantec Back Up Exec 12 for Windows Server occupy large size of disk space which might have many back up data.

    To resolve this issue, please check which applications (like System Back Up Exec 12 for Windows Server) consumes the most of the disk space. And then delete those data if you can make sure that you don’t need them anymore, or move those application data to other disk drive like drive D.

    However, for a long term, I would suggest you configure the application data location to the other drives rather than default system drive. For example, you can configure SQL Server user databases to drive D, thus the entire user database would be stored in the system drive. Besides, you can add more disk space to the drive C.

    Thanks,
    Chunsong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Tom Li - MSFT Tuesday, August 17, 2010 8:49 AM
    Wednesday, August 11, 2010 2:02 AM
  • Download and install the WinDirStat utility.  Run it against your C:\ drive partition and it will list all folders and files and tell you how large each one is.  In the Options for the utility, there is a selection to show unknown - turn that on to see how much space is being used by 'unknown' files.  If you have a lot of space being used here - it could be the system restore allocation.
     
    If it is the system restore allocation, you can reset the max size so it won't get too large and/or remove older restore points.  You could even turn this off on the server, but - make sure you have good backups of the server to restore from if you need to.
     
    Jeff
    "ChunSong Feng -MSFT" wrote in message news:320ef5e5-525f-44df-8cb5-1acf83cf594a...

    Hi,

    Based on my understanding, the SQL Server is not the main application which eats up the disk space since total size of databases is very small (86MB and 52MB). Also, as you described that the Symantec Back Up Exec 12 for Windows Server occupy large size of disk space which might have many back up data.

    To resolve this issue, please check which applications (like System Back Up Exec 12 for Windows Server) consumes the most of the disk space. And then delete those data if you can make sure that you don’t need them anymore, or move those application data to other disk drive like drive D.

    However, for a long term, I would suggest you configure the application data location to the other drives rather than default system drive. For example, you can configure SQL Server user databases to drive D, thus the entire user database would be stored in the system drive. Besides, you can add more disk space to the drive C.

    Thanks,
    Chunsong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Tom Li - MSFT Tuesday, August 17, 2010 8:49 AM
    Wednesday, August 11, 2010 2:12 AM