Page tree

The Advanced Debug Settings display additional debug selections for troubleshooting the Backup Agent running on the selected SQL Server computer. You can also set the log file characteristics and maximum size depending on what issue you want to troubleshoot. It is recommended that you change these settings based on guidance from IDERA support.

A rolling log allows you to create a log files that "roll" when they reach the maximum file size or the service is restarted, meaning that when the max size/restart occurs, it deletes the oldest information and logs the newest. This feature helps you avoid a large, cumbersome log file.

To change the debug settings:

  1. In the navigation pane, click SQL Safe Agents.
  2. Right-click the appropriate SQL Server instance.
  3. Click Properties from the context menu.
  4. Click Advanced.
  5. Make the necessary changes, and then click OK.

How do I access debug settings?

To manage your debug settings, click SQL Safe Agents in the navigation pane. Right-click the name of the SQL Server instance for which you want to manage debug settings, and then select Properties. Click the Advanced button.

Once you make the appropriate changes, click OK on the Advanced Debug Settings. Make sure to select Enable Debug Mode on the SQL Safe Agent Properties, and then click OK or debugging is not enabled.

What log file settings can I change?

If you enable debug mode, SQL Safe creates a log file based on the settings in the Roll Log fields. You can choose one of the following options for the log file

No

Maintains the debug log as a single file that is unlimited in size. This option allows SQL Safe to capture diagnostic information over an extended period of time. Your log file may become very large and should be monitored to avoid any issues with file size.

Do not enable No  unless absolutely necessary. Use No only when the problem being diagnosed occurs very infrequently and is not noticed in a timely manner. In almost all cases, increasing the size or number of files is sufficient for troubleshooting an issue and an unlimited file size is unnecessary.


Yes and keep n file(s)

Maintains the debug log as a series of files that are limited in size and quantity. This option allows SQL Safe to capture diagnostic information over a limited period of time, depending on the size and quantity of files kept. When a log file reaches the size limit or the service is restarted, SQL Safe renames the file and starts a new log file. The older the log file, the higher the digit that exists at the end of the file name. For example, file  x.log.3 is more recent than  x.log.4 . When the log file rolls over and reaches the maximum quantity, SQL Safe deletes the oldest file and the next oldest file takes its place. Because the amount of space used by the logs is limited, this setting does not require you to monitor the log files.

Yes  option is the recommended setting. Be aware that the amount of history retained is limited, and it may be possible for a problem being diagnosed to be missed. If this may be the case, first increase the quantity of files retained, then increase the size if necessary. Increasing quantity before size helps to maintain log files that are smaller and easier to view and send to IDERA support.

SQL Safe is a high-performance backup and recovery solution for your SQL Servers. Learn more > >