Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 High Availability (2005)
 Logshipping restore file is not reflecting

Author  Topic 

ksr39
Posting Yak Master

193 Posts

Posted - 2012-01-17 : 09:29:11
Hi Experts,

I need a small help as in one of my server we configured logshipping and the Alert job is enabled, Here I got an alert stating that the

AMS:b14f1818-da55-494d-8fcf-e67f0d408cfc:ABCD\KSR11DBCI01 01/13/12 12:54 vFoglight Alert See KB Doc #425942 VMware vFoglight fgAlertTrap Alert: fgSeverity: Warning fgHostName: VMS01DB07 fgHostIP: 10.227.85.215 fgHostMAC: N/A fgAgentTypeName: DBSS_Agent_Model fgAgentId: 0fc3ed61-7d07-4a56-ae8e-38b5fab7517e fgAgentName: DBSS- VMS01DB07 fgRuleId: 74047b37-29e3-43ad-a16c-95d0cb81205d fgRuleName: DBSS_-_Long_Running_Job fgTopologyObjectId: e638190a-b1ff-41e6-9426-dba349ecd34f fgTopologyObjectName: LSBackup_ABC_Auditing01
FgTrapMsg: Job LSBackup_ABC_Auditing01 has been running for 2.00 seconds, which is (125.54%) longer than the average running time of 1.59 seconds. SDTicketType=I SDTemplate='NSM_TicketCreate' SDSummary='vFoglight Alert on LSBackup_ABC_Auditing01 Severity Warning' SDRequestArea='Core Technology.Monitoring.Unicenter.Bus App Generated' SDPriority=3

But when I logged into the server and rerun the jobs manually the backup job, copy job and restore job they are running fine and the time in the transaction report status is changed for backup and copy jobs but not for restore and the LSN number for the restore is not changed. So what might be the problem what I need to check.
   

- Advertisement -