Backup job with "Test Run" enabled in job defaults may experience the error: "A Job with the same name already exists."
book
Article ID: 100013959
calendar_today
Updated On:
Description
Error Message

Cause
When the Test Run job is created according to default settings, the naming convention logic is not utilized and a generic job name is created.
Resolution
There are two solutions to this issue:
Permanent solution:
- In Backup Exec, navigate to Configuration and Settings > Job Defaults > (source job type that is having this issue)
- Select Test Run in the left list
- Untick the box to Enable test run then select OK.
- Tick the box to Enable test run then select OK.
- Attempt to create the backup job that experienced the prior behavior.
Solution per job:
- Create the job that is experiencing this behavior.
- In the Backup Definition Properties, click Edit under the right Backup options window.
- Select Test Run in the left list
- In the right Test run options, change the Job Name.
- Select OK to save and exit the Backup Options.
- Select OK to save and exit the Backup Definition Properties.
Issue/Introduction
When creating a new job with a unique name, the job will fail to be created. An error message pops stating:
"The server was unable to complete the requested operation." and "A Job with the same name already exists."
Was this article helpful?
thumb_up
Yes
thumb_down
No