The last DB update time may be related more to a time difference between the SQL server and the Orion server. That itself does look a little odd since that's saying that nothing new has been written to database in 500 minutes. Definitely a problem and not at all related to not being able to keep up. If Orion was unable to keep up it would still be collecting and writing to the database, but likely things would not be polled as frequently as you would like or have configured. The result would be a marginal delay in how often things get polled, but the Orion server would still be polling *something* constantly, trying to keep up.
I would argue that you are probably right on the cusp of needing an Additional Poller, but I don't think that's related to your database update delay.You can determine how close you are to needing an additional poller by looking at [Settings - Polling Engines] and seeing what the following percentages look like. The closer you are to 100% (or over) the more likely you are to need an Additional Poller.
| SAM Application Polling Rate | 11% of its maximum rate.» Learn more |
| Hardware Health Polling Rate | 0% of its maximum rate.» Learn more |
| Polling Rate | 4% of its maximum rate.» Learn more |
| VIM Hyper-V Polling Rate | 1% of its maximum rate.» Learn more |
| SAM Windows Scheduled Tasks Polling Rate | 0% of its maximum rate.» Learn more |