mdfnorthern.blogg.se - Veeam sql server backup best practices

OSQL Commands to set 768MB to Veeam SQL Instance This is what the commands look like in the CMD window:

With that in hand we open an elevated command prompt (CMD) and run the following commands making sure to set the correct host name: This can be done via command line or in Services.MSC: The first thing to do is to discover the instance name. Note that in this case we default to using the built-in OSQL commands to manage memory so there’s no need to download and install SQL Studio Management Express for this one task. So, what do we do to deal with this? We draw upon our Small Business Server (SBS) experiences! 😉 Recycling the service brought its memory usage right down and all of a sudden the RD session host picked-up and started responding normally.

That in turn was causing an excessive amount of swap file usage. The next step was to check and see what the host was doing.Īs it turns out, the SQL instance running on the host for the Veeam setup was consuming an excessive amount of memory on the host.

Remote Desktop Session Host at 20GB vRAMįrom the looks of things, there should be no issues whatsoever.

Remote Desktop Broker/Gateway/Web at 2GB vRAM.

(8) 1.2TB Intel SSD DC-S3520 series SSDs in RAID 6.

Intel Server System R1208SPLSHOR 1U with dual hot-swap power supplies.

The host is no slouch as far as the hardware setup goes. The performance drags were happening throughout the day with no correlation to any scheduled tasks in-guest or on the host. The main application running on the session host can be a bit finicky so we ran the gamut troubleshooting within the guest OS. One of our standalone Hyper-V hosts was experiencing performance issues with the Remote Desktop Session Host that provides the company’s primary user environment.