Duplicate backup sets following a job - doing this on a copied job

[Nick_Terry]

Has anyone come across this scenario? You create a standard backup job to disk and then create a duplicate job to tape using the 'duplicate backup sets following a job' option (policies are not used). You then copy the standard backup job and modify the copy as per your needs. You then go to create a duplicate job to follow from this newly copied job but you get the error message:

'To duplicate backup sets following a job, the backup job must be scheduled to run and must not be associated with any other duplicate backup set jobs. Currently, there are no jobs that meet this criteria.'

Please correct me if I'm wrong but it seems as though this is a bug. It is as though the copied job is somehow still associated with the existing duplicate job. Does anyone know of a work around to this other than having to create the new job from scratch and manually inputting the settings you want from the existing backup job? If it is a bug is there any chance of a fix to it?

Thanks.

[Rucha_Abhyankar]

Hi Nick,

This is a normal phenomenon. If you run the backup job first and then choose to duplicate it using "Duplicate backup sets following a job" then you need to schedule the same as the first option is valid only for duplicating the backup job as soon as the Backup-to-disk job is over.

In order to avoid this situation you can set this up using the policy feature.

==============