Hi Steven.
Bad catalog access messages normally indicate that DP's message catalog file is out of date and that an underlying module is sending a message for which no translation is available. The bad catalog access should not cause your operations to fail, but it will hide the underlying problem. My suggestion would be to install the latest Core patches on all hosts involved in this backup - the CS, the DA, the MA and the GUI hosts. This should fix the bad catalog error and let you know the actual problem.
Regards,
Shishir