Occasionally an Amicus Attorney by CARET automatic backup fails to complete. There are multiple reasons that the backups may fail to complete.
When an Amicus Attorney by CARET automatic backup fails, all Amicus Administrators are notified by a Sticky Note.
The following are potential reasons the Amicus Automatic backups failed:
The backup destination in the configuration, is not accessible.
There is not enough space in the backup destination.
The backup destination doesn't have the required permissions.
The SQL Server Agent (Amicus) service isn't running on the Amicus Application Server.
- The automatic backup location has been configured in Amicus Attorney by CARET, but that location doesn't exists on the server. If the location does not exist, from the server, create a new folder on a local drive and direct the backup location to that folder.
- There is enough space to backup to this location.
- Within Amicus Attorney go to Help > Show Logs.
- Ensure the Select Server log file is selected, and select the Date of the log relating to when the last backup attempt failed.
- Locate the time in the log when the backup is scheduled for. If this mentions the issue being lack of space, check the drive where the backups are being created and confirm there is enough space remaining. There must be enough free space to make 1 extra backup, as the backup feature creates the newest copy before deleting the oldest backup.
- The backup folder doesn't have the required read\write access to that location.
This issue typically prevents backups from being deleted but can also prevent the new backups from being created.
The permissions must be configured for the Windows account which the SQL Server and Amicus application were installed under.
- The SQL Server Agent (AMICUS) service isn't running. If you can perform a manual backup through Amicus successfully but the Amicus automatic backups are failing, this indicates an issue with the SQL Server Agent (AMICUS) service.
- On the Amicus Application server, in the Windows Search type services.msc, and select the Services item from the list.
- Scroll down and locate the SQL Server Agent (AMICUS). Confirm that shows as Running under the status column.
- If the service shows as Running, select the service and click Restart the service on the upper left. Sometimes a Windows service may show as running but somewhere in the past something interfered with the service and it is not performing the function as designed.
For space issues and security assess\setup to the backup location, contact your IT department.
Comments
0 comments
Please sign in to leave a comment.