- Posts: 1
- Liked: never
- Joined: Aug 13, 2014 4:04 pm
- Full Name: Joel W. Culbreth
- Location: Alabama
The work around has been to clone the job that failed, map the cloned job to the current backup chain and then run the newly created cloned job. It finishes successfully.
I have also been able to just run an "Active Full" and it runs successfully.
I have also just recreated the failed job, mapped the newly created job to the current backup chain and the run the newly created job, which finishes successfully.
I had a case open #01997980, but the tech just confirmed my work around would work.
Is anyone else experiencing this behavior after the update?
Joel W. Culbreth, CISSP
Network Engineer II
Information Technology Support
Users browsing this forum: No registered users and 20 guests