Forum Discussion

DeliBoy's avatar
DeliBoy
Level 2
15 years ago
Solved

Problem with Scheduled Duplicate Jobs

Thanks for reading this. I've been trying for a few days now to troubleshoot a scheduling problem I'm having with a policy / template. Background: - The policy consists of 1 backup job and 3 duplicate jobs. - The 3 duplicate jobs are supposed to start when the backup job is completed. They use the "Run only according to rules for this template" option, per documentation. - The backup job is scheduled to run every Saturday. Problem: - The duplicate jobs only run the first time the backup job runs. They do not repeat on subsequent weekends, though the backup job does. - The duplicate jobs do not appear on upcoming calendar dates, while the backup job does. More Information: - The initial backup job is D2D, and the duplicate jobs are D2T. This is probably irrelevant; I can duplicate the problem in strictly D2D tests. - The first time the backup -> duplicate jobs run, everything works properly. - This is on a fully patched Backup Exec 12.5 install running on a Windows Server 2003 box. - I have used BEUtility.exe to repair the database, rebuild indices, and to check database consistency. - I've recreated this problem on a different Backup Exec 12.5 box I have. Does Symantec think that no one would ever need to schedule a reoccurring duplicate job?
12.x and Earlier
Backing Up
Backup and Recovery
Backup Exec
Troubleshooting
  • DeliBoy's avatar
    DeliBoy
    15 years ago
    Dev, thanks for your post. The duplicate jobs are not scheduled to run, but set to "Run only according to rules for this template". This is supposed to start the job after the first job finishes. I prefer this to scheduling it because a backup completion time varies by a few hours.

    In any respect, I think I found the solution to my problem: Even though the duplicate jobs do not show in the calender view, they start anyway as they should. They show afterward in the calender. Strangely, the tests that I ran did not indicate that this would happen. The real word backups that I have to make can only be done once a week and for a short window (this is probably true for a lot of us), so I don't have a lot of trial-and-error oppurtunities.

    I'm not sure why Symantec did not think to make this display properly; perhaps this is fixed in BE 2010.

    Thanks for reading,
    DeliBoy
  • Dev_T's avatar
    Dev_T
    Level 6
    15 years ago
    -- The 3 duplicate jobs are supposed to start when the backup job is completed.
    The 1st duplicate job runs fine.........

    Did you configure the other duplicate jobs to run at a specific time?

    I think you need to create 2 more duplicate job and associate the job with the primary job and schedule them accordingly, NOT after the original job is over.

  • DeliBoy's avatar
    DeliBoy
    Level 2
    15 years ago
    Dev, thanks for your post. The duplicate jobs are not scheduled to run, but set to "Run only according to rules for this template". This is supposed to start the job after the first job finishes. I prefer this to scheduling it because a backup completion time varies by a few hours.

    In any respect, I think I found the solution to my problem: Even though the duplicate jobs do not show in the calender view, they start anyway as they should. They show afterward in the calender. Strangely, the tests that I ran did not indicate that this would happen. The real word backups that I have to make can only be done once a week and for a short window (this is probably true for a lot of us), so I don't have a lot of trial-and-error oppurtunities.

    I'm not sure why Symantec did not think to make this display properly; perhaps this is fixed in BE 2010.

    Thanks for reading,
    DeliBoy