In my limited experience backing up 35 files should take seconds or perhaps minutes.
Thank you for the post.
I responded to your other post here:
This is a different issue but still related to backups, so is this the same server having both of these issues? If so, I would uninstall and reinstall and rebuild all schedules.
If this is a different server, then what happens if you delete that backup schedule and recreate it? Ideally, schedule full backups when users are not in production.
This is a different issue on the same server. The progressive backup issue has now been resolved.
The backup job is still showing as "Running" after 38 hours from when it started. I was able to create a new backup job without verifying or cloning enabled and run immediately. It completed in 15 minutes.
How can I kill this "running" job?
This server supports a hospital so the hosted databases are in production use 7 x 24. There is no time when users don't have one or more of the hosted databases open to do the backup. How can I kill scheduled jobs without closing all databases and stopping the FMS services?
Thank you for the reply and I apologize for the delay.
I wanted to get clarification before replying and a knowledge base article needed updating.
"How can I kill scheduled jobs without closing all databases and stopping the FMS services?"
The only way I am aware of would be to terminate the Script Engine process (fmsase.exe); however, please note that this will also terminate any currently running scripts.