Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. This tip discusses five of the most common Backup Exec errors and how to resolve them.In this guide curated by the Search editors, you’ll evaluate and overcome the DR tradeoffs associated with Amazon S3, with guidance on solidifying an AWS backup plan and securing S3 buckets. This is probably the most common of all the Backup Exec error codes.Additional services may be required depending on how Backup Exec was installed.Oftentimes, you can force a service to start by right-clicking on it and choosing the Start command from the shortcut menu.The VSSADMIN command can be used to determine which VSS writer is causing your problem.This is one of the Backup Exec errors that can be caused by a variety of conditions. NET Framework will vary depending on the operating system used. NET Framework and removing the framework can cause those applications to break.
However, cleaning the tape drive rarely corrects the problem.Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting.You can check the permissions by entering at the server's Run prompt.Specifically, one of the VSS writers used to back up an application running on the server reported a status of failed, which caused Backup Exec to produce error E000FED1.
To troubleshoot this error, enter the command VSSADMIN LIST WRITERS in a Command Prompt window.
Windows will display a list of each VSS writer and note if it is in an error state.