Backup Summary Report


Author
Message
ds845835
ds845835
New Member
New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)New Member (2 reputation)
Group: Forum Members
Posts: 1, Visits: 3
Please consider in the future to add even offline computers to the email Backup Summary Report.  We have so many computers and servers it is difficult to tell when a backup is missed.  For the last 2 days a server has failed incremental backup with this error "Timed out waiting for agent cleanup" but it didn't show up in the backup summary report and it didn't log an error under other tasks, view logs.  It would be nice to see any computer in the backup summary report that had no log or even if it was offline.  Then we would know to investigate or reboot the server.
Alex
Alex
Macrium Representative
Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)Macrium Representative (26 reputation)
Group: Moderators
Posts: 24, Visits: 219
ds845835 - 29 November 2017 5:32 PM
Please consider in the future to add even offline computers to the email Backup Summary Report.  We have so many computers and servers it is difficult to tell when a backup is missed.  For the last 2 days a server has failed incremental backup with this error "Timed out waiting for agent cleanup" but it didn't show up in the backup summary report and it didn't log an error under other tasks, view logs.  It would be nice to see any computer in the backup summary report that had no log or even if it was offline.  Then we would know to investigate or reboot the server.

Hi,
Usually the error 'Timed out waiting for agent cleanup' happens when the backup has finished and generated a backup log, but the agent has taken too long to complete and exit, so the server has timed out to prevent one badly behaved agent from holding up other backups. This does not necessarily mean that the backup has failed - If a backup is started and the log generated for the backup shows no errors, then the backup was successful, even if the server itself generates a scheduler error.
We recently found a bug in the server software which caused the agent cleanup error to be generated incorrectly - this has been fixed and will be released in the next Site Manager software release.
I've opened a case for our development team to look at making these errors clearer and to reviewing the email reports to ensure that any errors or failures to run scheduled backups are highlighted clearly.
Regards,
Alex Stevenson,
Macrium Software
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search