As noted in a previous article I was tasked by a client with figuring out why their Retrospect Backup software for Windows was not working properly. Since I was not familiar with Retrospect I had to troubleshoot from the beginning. I started troubleshooting on the Windows 2003 R2 server running Retrospect and was able to easily see the log files showing the errors backing up one of the companies Exchange servers. When I attempted to manually backup a single mailbox on the Microsoft Exchange server I was receiving the same errors. Below I describe the Retrospect backup error and then explain step by step how I was able to resolve the error.
Earlier while troubleshooting an issue for a customer I needed to start at the bare minimum of troubleshooting because the issue at hand was a bit out of my area of expertise. The problem as reported existed on a Windows 2003 R2 server running backup software called Retrospect. The backup software was reporting via email to the IT staff that it was no longer working and they needed me to locate the issue and resolve. The first thing I needed to do was to see how long the server had been up, if any patches had been applied recently, and if anything else had changed since the last successful backup. Again since this is out of my area of expertise I first needed to see how long the server had been up which luckily is almost as easy to do on Windows 2003 R2 as it is on Linux. Below I provide to examples of how to check server uptime on Windows.