Enable/Disable Debug for Netapp SnapManager for SQL

Came across a rogue debug log that was generating 500mb of log every time the backup job ran. To initially alleviate the disk filling up Logging was disabled which has to be done via the Registry. I am using SnapManager version

If using SnapManager for SQL 5.X, change the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Network Appliance\SnapManager for SQL Server\Server\EnableDebug 
Set to 1 to enable, 0 to disable.

In most cases, the SnapManager Service does NOT need to be restarted after setting this value. You DO need to close and reopen the SnapManager for SQL Management console GUI. The additional debug logs will be saved in a subdirectory of the configured ‘report’ directory called Debug [ServerName]. For example:
C:\Program Files\NetApp\SnapManager for SQL Server\Report\Debug [myserver1]

In case you are still using an OLDER SnapManager for SQL versions (1.x through 2.x), follow those steps: 
To enable debug logging for SMSQL, two steps are required:

1. In the Windows Registry, locate the value LoggingLevel in the subkey path 
HKEY_LOCAL_MACHINE\SOFTWARE\NetApp\SnapManager for SQL Server\Debug
Change the value data to 0x00000001 (1)

2. Next, the SnapManagerdebug.exe program must be executed and be a running process.

To disable debug logging, kill the running process SnapManagerDebug.exe from Windows Task Manager GUI, or Windows 2003 cli tasklist / tskill and/or change the value data of the above registry sub key back to the default of 0x00000000 (0)


Netapp Support KB ID: 1011946 Version: 3.0 Published date: 01/31/2013


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: