Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Archive > 2018Jan03 - Deletes > LastTimeUp variable will be an hour off in alerts

LastTimeUp variable will be an hour off in alerts

Table of contents

Updated 9-1-2016


Alerts using LastTimeUp variable may be off by an hour. The LastTimeUp variable is internally converted to local time. Alerting expects all values in UTC. Unfortunately, there is not a workaround for the time difference.


  • NPM 11.5 and later
  • SAM 6.2.X and later
  • Orion 2015.1 and later


When using the LastTimeUp property in alerts, be ware the value will be an hour off in notification emails. The variable converts to the local system time through the Orion Platform. Alerting expects all time values in UTC. This causes the values to report an hour off.




Last modified