Regresar
-
Título
LiteSpeed's Log Shipping support a Monitor Server? Stored procedures include no parameters to configure a Monitor Server -
Descripción
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?
Debe iniciar sesión
Tiene que estar conectado y contar con un contrato de mantenimiento vigente para ver los artículos de conocimiento premium.