Red Gate forums: Log Shipping Monitor

RE: Problem with Monitor

Centura — Mon, 02 May 2011 06:05:20 GMT

Hi,

no, I didn't get any reaction until now.

Regards,
Volker Bachmann

RE: Problem with Monitor

howardyeo — Sun, 01 May 2011 12:23:28 GMT

Hi Centura,

Have you received any reply from them yet? My friend was planning to use Redgate Backup 6.4 for log shipping as well. However, he is also facing the problem. Any idea whether there is a newer version or something?

Regards

RE: comments and suggestions

mariaparacha20 — Mon, 25 Apr 2011 11:33:06 GMT

An option to display the backup sizes in something other that bytes (user selectable) would be useful, I have logs over night that display as 9308685824, which is hard to equate by eye to 8.7 Gb

When I closed down last night while the app was minimised to the tray, it (the app) crashed! Confused

Problem with Monitor

Centura — Mon, 16 Aug 2010 12:27:58 GMT

Hello,

we are about using the Redgate Backup 6.4 for log shipping.
I've found this Monitoring tool for the log shipping and it would be nice to get it to work.
But after creating a Group we don't see any reaction in the tool
No data to display in every chart, no server status, no database status - nothing.
What could we do?

We use SQL Server 2005 SP2, Windows7, XP and Windows Server 2003 as "Clients" and Windows Authentication or Sql Server authentication - that makes no difference.

Any help would be great!

Regards,
Volker Bachmann

RE: alert notifications

gethowell — Fri, 18 Sep 2009 04:19:45 GMT

Just wanting to echo Karl's comments from this thread, and to ask if there was any further update on the capability to send SMTP alerts from the LSM?

Yes, the standard GUI contains SMTP alerting (I'm using v5.3), however, I am finding that log shipping on large DBs often hangs within the SQL Agent Job itself - this appears to coincide with full SQL backups being performed early in the morning - and the SQL job just continues to report "Executing..." The problem here is that the Redgate job does not report a warning or failure, and hence no alert is sent from the GUI.

I can fix the problem with a restart of the SQL Agent Service (SQL 2000), but I have to manually check the status to discover the problem. An alert from the Log Shipping Monitor if there has been no activity for a certain amount of time would be a more all encompassing way to monitor the process in my opinion.

Thanks!

Shipping

Anonymous — Thu, 02 Jul 2009 06:08:59 GMT

Is there any person ,having any problem related to shipping ???

Monitor Installation

mleisse — Fri, 27 Mar 2009 16:46:20 GMT

I have a few questions about the installation:

1. If I installed the monitor software on the Destination server, does this install anything on the Source server?

2. Does .NET 2.0 have to be installed on both the Source and Destination servers? Or just the server that the monitor is installed on?

3. Are there any known issues if the Source and Destination are in different domains?

Thank you

mleisse

The timeout period elapsed prior to completion..

Rajnish Awasthi — Wed, 07 Jan 2009 09:29:21 GMT

Hi,
Most of the time I am getting the following error:-

1/7/2009 11:21:00 AM - Alert code: ERR_DATABASE_NONEXISTENT

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Becuase this log shipping monitor get referesh shortly so this time out error should also get refereshed the same time, as far i am doing this task manually every time by clicking on 'delete all alert'.

Thanks & Regards
Rajnish Awasthi

Availability Matrix ??

patrick_R — Fri, 19 Dec 2008 09:23:53 GMT

Hi ,

Perharps i miss it but is there any availability matrix for this product ?

Windows NT 4.0 Server, SP 6 No
Windows NT 4.0 Enterprise Server, SP6 No
Windows 2000 Server/Advanced, SP2 Yes
Windows 2000 Server/Advanced, SP4 Yes
Windows Server 2003, SE, EE SP1 Yes
Windows Small Business Server 2003 Yes
Windows XP Professional, SP2 Yes

Sommething like that , Or by SQL release

Have you got an idea?

regards,

Patrick_R

RE: Exception always occurs after the app runs for a day or two

Jason Cook — Mon, 23 Jun 2008 17:07:52 GMT

Hi Willow,
Thank you for reporting this to us. I've passed the information on to the developer of the tool who should resolve it in a future release.

Unfortunately, because it's a 'labs' tool, I don't have an estimation to when such a release would occur, but we will announce it here if one becomes available.

Thanks,
Jason

Exception always occurs after the app runs for a day or two

willow_techie — Mon, 02 Jun 2008 13:57:44 GMT

First of all, thanks for such a useful program.

I do, however, get this error after leaving the application open for a day or two. It happens if I click on the production server in the server group from the tree list. Once this happens, I can't view any server properties anymore.

I am running Windows 2008.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: The min value of the axis range (6/1/2008 9:52:09 AM) should be less than its max value (5/30/2008 3:11:40 PM).
at DevExpress.XtraCharts.AxisRange.CheckRange(Object minValue, Object maxValue)
at DevExpress.XtraCharts.AxisRange.set_MinValue(Object value)
at LogShippingMonitor.ucDisplayTrend.DisplayTrend(ServerConfig server, TrendInterval trendInterval, TrendData trendData, Boolean showDate)
at LogShippingMonitor.ucServerSummary.Display(ServerConfig server)
at LogShippingMonitor.frmMain.DisplayData(Int32 groupID, Int32 serverID, Boolean alwaysUpdateAlerts)
at LogShippingMonitor.frmMain.tvGroups_AfterSelect(Object sender, TreeViewEventArgs e)
at System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
at System.Windows.Forms.TreeView.WmNotify(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
LogShippingMonitor
Assembly Version: 1.0.1.0
Win32 Version: 1.0.1.0
CodeBase: file:///C:/logshippingmonitor/LogShippingMonitor.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
DevExpress.XtraCharts.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraCharts.v6.3.DLL
----------------------------------------
DevExpress.XtraCharts.v6.3.UI
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraCharts.v6.3.UI.DLL
----------------------------------------
DevExpress.Utils.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.Utils.v6.3.DLL
----------------------------------------
DevExpress.Data.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.Data.v6.3.DLL
----------------------------------------
DevExpress.XtraEditors.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraEditors.v6.3.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
-xudwyjn
Assembly Version: 1.0.1.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
glxfvbda
Assembly Version: 1.0.1.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

RE: comments and suggestions

j.salmon — Mon, 03 Mar 2008 17:58:22 GMT

Make it possible to launch any of the log shipping jobs from the monitor. I know it's monitor, but it'd be nice that if you see in the monitor that a job failed, that you can force it to run.

If you have time and if its "doable", it be a nice touch.

RE: comments and suggestions

j.salmon — Thu, 21 Feb 2008 14:57:11 GMT

I'm having a couple problems.

1.

jkz999 wrote:

1. I cannot see any restore history, the chart says No data to display. Is this because my monitor server is not on my production server?

petey wrote:

Re 1:
You need to link a SQL Server agent job and job step to the standby server. This is because SQL Server does not store the duration of restores in the backup history tables. Hence the information needs to come from the SQL Server Agent job step.

I'm having problems with this as well. I'm not quite following your suggestion. Our setup does not include a monitoring server.

Per the documentation on the wiki, I'm supposed to select a job for the standby database so that the restore duration data can be filled in. When I select the ... button, I can see the jobs on the server, but I am unable to select any (or is the job field ever enabled)?

The backup duration is displayed properly.

2. I cannot get the freespace alerts to work on either server. I purposely specified 1 gig so that both would immediately get triggered. The commands were accepted and saved correctly, but they don't appear to work - meaning no alerts are triggered?

3. Since I'm at it......... I'll add something else for future enhancements.
When your adding alerts, it would be nice to not keep up with all the keywords. Granted, they aren't hard or anything, but it would be nice to eliminate the need to know them (esp. if more are added in future updates). So I propose, you add functionality that would add the alerts for the user when he/she right clicks in the alerts area or clicks an Add/Delete button.

In the case if you right click, you would have a menu such as:
Free space
Last backup
Last restore, etc (format how you want).

So, the user right clicks and selects free space - the app should bring up a small dialog with a text box for the drive letter and a text box for the size.
Press ok or enter button and the command properly formatted is added for the user.

Pressing a different menu option would show different options required for setting up that alert. Pressing ok/enter - automatically puts the alert in the alerts box formatted correctly.

4. One more thing.................honest.....
Would it be possible to get data on the copy job? As duration, success/failures? I'm assuming you could use the log_shipping_monitor_history_detail table for this info?

Not sure if there's room on the summary page for it, or maybe add something (another tab, button) for viewing extended data.

5. Petty change request: Add an X to close the groups tab. Add a view menu or File menu option to view the tab again. In our case, we only have 1 group for log shipping. It would be nice to get the extra screen space. You guys did a nice job of the UI on the right side, so it's still easy to navigate the servers without need the tree view on the left (in this type of setup).

RE: comments and suggestions

j.salmon — Thu, 21 Feb 2008 14:21:23 GMT

petey wrote:

Thanks for the feedback.
Re 2:
Yes, it is not user friendly to display everything in bytes. LSM will display both bytes and a user friendly size (rounded to nearest Kb, MB, GB) in a future version.

That would be nice.

If possible, could you fix this:
When creating a new group and are on the standby databases tab, the server and database fields are automatically enabled. You can enter values in them (and the DB combo actually populates), and hit save. But the standby server is not saved (because you didn't press ADD first). It makes the process a little deceiving at first.

RE: Copy duration etc ..

j.salmon — Thu, 21 Feb 2008 14:17:44 GMT

>>" Possibly an option to have to app start with windows"
Yes this would be nice.

>>- a couple of times I have just wanted to get a quick idea over the current status. I have found myself hovering over the tray icon to get a quick summary, so that would be a useful addition
This would also be a nice feature, but would need to be some what customizable as to the information it displays.