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:

  1.  In Backup Exec, navigate to Configuration and Settings > Job Defaults > (source job type that is having this issue)
  2. Select Test Run in the left list
  3. Untick the box to Enable test run then select OK.
  4. Tick the box to Enable test run then select OK.
  5. Attempt to create the backup job that experienced the prior behavior.

Solution per job:

  1. Create the job that is experiencing this behavior.
  2. In the Backup Definition Properties, click Edit under the right Backup options window.
  3. Select Test Run in the left list
  4. In the right Test run options,  change the Job Name.
  5. Select OK to save and exit the Backup Options.
  6. 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."