No Collection Data within Monitor, or Collection Stops Updating.

Data collection stops within Monitor, or there is no longer any new data from a certain point. 

This is due to the following database error involving lack of space in the primary file group for the database (.mdf file).  Here is a snippet from the Monitor Logs that you will see in the "VeeamDCS.log" or "VeeamDCS.number.log" where number is a generated number for separating the log files.

01/17/12 13:36:54 Inform  0x0BC0 alarms        "A database error (code:0x80040E14, ) has occured in context of { ? = CALL sp_triggered_alarm_save;1 (?, ?, ?, ?, ?, ?, ?) }. Error information follows"
01/17/12 13:36:54 Inform  0x0BC0 alarms        "Error record 1 of 1: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
01/17/12 13:36:54 Inform  0x0BC0 alarms        "Throwing exception."
01/17/12 13:36:54 Error   0x0BC0 alarms        "IDispatch error #3092 (Source: Microsoft SQL Native Client, Description: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)"

There are a couple things to check to fix this issue. 

1.  Check the hard drives of the SQL server to make sure they are not overloaded or full.  If the drive for the primary file group (.mdf file extension) is full, please free up some disk space to resolve Monitor collection.  The default file path for SQL files is "C:\Program Files\Microsoft SQL Server\MSSQL10_50."YourInstanceName"\\MSSQL\DATA"

2. Enable Auto growth within SQL.  Follow the directions below on how to do this. 

1. Open Microsoft SQL Server Management Studio.  This software may need to be installed separately as it is not always default within SQL installations. 
2. 
3. Connect to the SQL server that has the Monitor database.  ("server\instance" if needed)
4. 
5. Once connected, expand to the Monitor database.  Default name is "VeeamMonitor".
6. 
7. Right Click, Properties on the Monitor database. 
8. 
9. Click Files Tab
10. 
11. Enable Auto growth.  This option might be scrolled to the right.  Default Auto growth settings are 1 MB, unrestricted.
12. 
13. Once this is set, the primary file group (.mdf file) will start growing in size according to the Monitor collections again. 

Contact Support if these strategies do not help resolve your issue.