So how can you best test/debug the backup/restore/archive functionality?
If you use a Jenkins specific step, the only way to test is to run Jenkins jobs.
If you have a script you can run on your own machine, test/debug becomes easier.
To my mind, a Jenkins specific plugin should be about *reporting* what your build has done...
For example, you should not have a Jenkins plugin to *run* junit tests, but rather a plugin that *reports* the test results... oh look, that’s what there is.
So the question is really, what do you need to report about this restore/backup/archive of databases, and *if* anything other than success/failure *then* go looking for a plugin to assist (eg html publisher plugin could publish a report of the execution if the results can be formatted as html, etc)
Do not think “just running a shell script/batch file” is a failed Jenkins integration of your business requirements... it is enhancing your testability and debugability... Jenkins then provides the traceability by recording the actual use of those scripts as well as the coordination by orchestrating the execution within a larger sequence of tasks