Fix SQL Server Memory Leak During Backup Operations

draft · backup-and-recovery sql-memory-leakbackup-restoreperformance-tuning

Generated by docuprocessor (prompt article/v3) · 2026-04-22 05:20

Source thread

thread_id: spaces/AAAA05BdS6s/threads/JHSvaW8iB5Y · 12 msgs · first 2024-03-07 · participants: Tech ATech BTech C

Tech A 2024-03-07 18:17

Hey guys, I'm having some issues with Ez-3Di at HERSHMAN office. They are saying that sometimes works properly,sometimes not... I see that the server is running a backup rn, and the memory is 94% used :(

image/png image.png

**Task Manager – Windows Server 2012 (Build 6.3.9600, 64-bit)** CPU usage is at **11%** and memory usage is critically high at **94%** (**29.8 GiB / 31.6 GiB used**). Top memory consumers visible include: **Service Host: Local System (15)** at 537.5 MB, **Host for Endpoint Security** at 434.8 MB, **SQL Server Windows NT – 64 Bit** at 296.5 MB, **ppped.exe (32-bit)** at 287.3 MB, and **Domain Name System (DNS) Service** at 259.0 MB. System is logged in as **Administrator** on host **SERVER2012**, uptime **7 days 16 hrs 52 mins**, Service Tag **2TNCKQ2**; no network or gateway values are displayed (**\**).

Tech A 2024-03-07 18:17

The weird thing is that I don't understand why memory is 94%, doesn't look like that in the task manager

Tech A 2024-03-07 18:18

found it already

image/png image.png

**Windows Resource Monitor – Process and Physical Memory View** The process list shows **sqlservr.exe (PID 3324)** with its Commit (KB) value highlighted in **magenta/pink at 24,728,700 KB**, significantly higher than all other listed processes. Physical memory summary indicates **30,582 MB In Use**, **1,796 MB Available**, **15 MB Modified**, **375 MB Hardware Reserved**, and **0 MB Free**, out of **32,768 MB Installed (Total: 32,393 MB)**. The **Used Physical Memory gauge reads 94%**, with the Commit Charge graph in the upper-right panel showing a near-maximum sustained load.

Tech A 2024-03-07 18:21

Is it normal to have 94% memory used on this server? I see that they use DSN Practice management there

Tech A 2024-03-07 18:21

And backups running at production times?

Tech B 2024-03-07 18:23

it happens time ot time, first step would be to restart the server to see if this fixes the issue with the SQL memory leak

Tech B 2024-03-07 18:24

if it fails the night before, we rerun it manually

Tech A 2024-03-07 18:24

Should be wait for novabackup to finish first?

Tech A 2024-03-07 18:36

maybe not?

image/png image.png

**NovaBACKUP software Status tab** is displayed, showing a backup operation in progress with **1,426,766 selected files (3,415.48 GB)**, **4,302 completed files (55.86 GB)**, and **1,326,678 skipped files (1,082.96 GB)**. Elapsed time reads **9:07:39**, with an estimated time remaining of **278:05:50**, and an estimated completion time of **3/13/2024 at 4:41 AM**. The target device is identified as **xSP device.0**.

Tech C 2024-03-07 18:38

Lol, you can try pausing it to see if it will improve, then post it in backups chat so they can resume it after hours

Tech A 2024-03-07 18:40

But if we restart the server the backup will be cancelled I assume, right?

Tech B 2024-03-07 18:54

Correct

---
title: "Fix SQL Server Memory Leak During Backup Operations"
category: backup-and-recovery
tags: ["sql-memory-leak", "backup-restore", "performance-tuning"]
source_thread_id: "spaces/AAAA05BdS6s/threads/JHSvaW8iB5Y"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T05:20:33"
participants: ["Tech A", "Tech B", "Tech C"]
---

# Fix SQL Server Memory Leak During Backup Operations

## Problem

A client office experienced intermittent performance issues with Ez-3Di imaging software on Windows Server 2012. Investigation revealed SQL Server consuming 24.7 GB of memory (94% of total system memory) during NovaBACKUP operations. The SQL Server process (sqlservr.exe PID 3324) showed excessive memory usage that was not immediately visible in Task Manager's standard view but was apparent in Resource Monitor. The backup operation was running during production hours with an estimated completion time extending well into the next day.

## Resolution

1. Open Resource Monitor to confirm SQL Server memory consumption if Task Manager doesn't show the full picture
2. Pause the running NovaBACKUP operation to potentially improve performance temporarily
3. Restart the server to resolve the SQL memory leak - this will cancel any running backup operations
4. Coordinate with the backup team to reschedule the backup to run after hours
5. If the backup fails during its scheduled nighttime run, manually restart it the following day

Note: Restarting the server will cancel any active backup operations, so coordinate timing appropriately with business operations and backup schedules.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/JHSvaW8iB5Y`
- Attachments:
  - ![image.png](../attachments/JHSvaW8iB5Y.JHSvaW8iB5Y/image.png) — **Task Manager – Windows Server 2012 (Build 6.3.9600, 64-bit)**

CPU usage is at **11%** and memory usage is critically high at **94%** (**29.8 GiB / 31.6 GiB used**). Top memory consumers visible include: **Service Host: Local System (15)** at 537.5 MB, **Host for Endpoint Security** at 434.8 MB, **SQL Server Windows NT – 64 Bit** at 296.5 MB, **ppped.exe (32-bit)** at 287.3 MB, and **Domain Name System (DNS) Service** at 259.0 MB. System is logged in as **Administrator** on host **SERVER2012**, uptime **7 days 16 hrs 52 mins**, Service Tag **2TNCKQ2**; no network or gateway values are displayed (**\<n/a\>**).
  - ![image.png](../attachments/JHSvaW8iB5Y.ezAMBvWwpW8/image.png) — **Windows Resource Monitor – Process and Physical Memory View**

The process list shows **sqlservr.exe (PID 3324)** with its Commit (KB) value highlighted in **magenta/pink at 24,728,700 KB**, significantly higher than all other listed processes. Physical memory summary indicates **30,582 MB In Use**, **1,796 MB Available**, **15 MB Modified**, **375 MB Hardware Reserved**, and **0 MB Free**, out of **32,768 MB Installed (Total: 32,393 MB)**. The **Used Physical Memory gauge reads 94%**, with the Commit Charge graph in the upper-right panel showing a near-maximum sustained load.
  - ![image.png](../attachments/JHSvaW8iB5Y.sIpTq98Su6w/image.png) — **NovaBACKUP software Status tab** is displayed, showing a backup operation in progress with **1,426,766 selected files (3,415.48 GB)**, **4,302 completed files (55.86 GB)**, and **1,326,678 skipped files (1,082.96 GB)**. Elapsed time reads **9:07:39**, with an estimated time remaining of **278:05:50**, and an estimated completion time of **3/13/2024 at 4:41 AM**. The target device is identified as **xSP device.0**.

Generated article

draft