-
标题
LiteSpeed's Log Shipping support a Monitor Server? Stored procedures include no parameters to configure a Monitor Server -
说明
Does LiteSpeed's Log Shipping support a Monitor Server?
We are configuring Log Shipping using LiteSpeed stored procedures and they include no parameters to configure a Monitor Server like we can when configuring using native SQL Server.We do see that the LiteSpeed stored procedures 'LogShipping_Add_PrimaryDatabase' and 'LogShipping_Init_Subscriber' do have alert related parameters such as @BackupAlertThreshold (the former) and @RestoreAlertThreshold (the latter). That's not a single instance for monitoring publisher and subscriber(s) though. Those procedures run on the Publisher machine and Subscriber machine, respectively.According to the documentation, none of the Log Shipping-centric stored procedures have any parameters for a Monitor Server.
We are configuring log shipping across multiple SQL instances and want to use a single SQL instance for monitoring. We don't have a LiteSpeed central repository, only a local one on each SQL instance.
When there are numerous instances configured for log shipping, it would be nice to only have to query a central location for errors.
Does Quest have recommendations on monitoring LiteSpeed log shipping (outside of the GUI) when multiple SQL instances are using log shipping? -
原因
LiteSpeed's log shipping does not support a Monitor Server. There's no option in the LiteSpeed Log Shipping configuration to specify a Monitor Server.
Litespeed log shipping uses the same alert system as native. It just does not support a monitor server. You can see these alerts using: exec sys.sp_check_log_shipping_monitor_alertWe have submitted enhancement request LS-1826: ability to monitor\query all log shipping jobs from a central location to alert off of -
解决办法
WORKAROUND
None while using extended stored procedures. We don't have any recommendations on that. However you can create agent jobs on each separate instance using log shipping. You can also run query exec sys.sp_check_log_shipping_monitor_alert against each SQL Server instance. You still don't have a central location to scan for issues.
Also the LiteSpeed UI screen: 'LogShipping' | 'Monitoring' tab, you can hover over and see information about the Publisher and the information about the Subscriber. One view bringing information about the Publisher and the Subscriber together like what the Monitor Server does.
STATUS
Enhancement request LS-1826: "ability to monitor\query all log shipping jobs from a central location to alert off of", has been submitted to Product Management and Development for consideration in a future release of LiteSpeed for SQL Server. -
缺陷ID
LS-1826 -
其他信息
This knowledgebase article below says that the greyed out section is expected behavior because a Monitor Server is not used in LiteSpeed log shipping: https://support.quest.com/litespeed-for-sql-server/kb/121938/sql-log-shipping-report-has-greyed-out-areas You may also wish to review the below: https://docs.microsoft.com/en-us/sql/database-engine/log-shipping/monitor-log-shipping-transact-sql?view=sql-server-ver15