This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Another Shut down a Core post

Is this even a topic of discussion in the product for any version? This has been a huge topic of discussion and anger since version 5 came out and zero progress has been made

And now in V6, it seems to be getting WORSE. 

1) It seems like the changes to the repository in v6, cause the checks that runs after a dirty shutdown to take longer (just a guess)

2) The unsupported powershell script that was provided by DELL for v5 does not work for 6 and Support just told me there is no script for 6 and never will be.

3) Long running jobs. With the introduction of cloud archives, exports etc, we are seeing massive jobs that run (and block other jobs like backups but that is another issue) for days, meaning scheduling a restart becomes even harder.

I am not even asking for the Core to be able to cleanly shutdown during an OS shutdown (something that every other application in the world seems to manage) But how is this not a single button(s) on the GUI "Prepare for Shutdown" and "Core has been restarted" (to un-pause jobs)

Or at the very least, a single supported powershell script to perform this basic function?

We have dozens of Cores in various geographic locations and managing simple shutdowns is such a massive problem for us.

Parents
  • Thank you for the info.

    Does "pausing current processes" mean a Core will be able to pause all types of jobs and resume them without issue after restart? There are several types of jobs that run so long and are not able to handle a restart currently, this would be a great feature.

    Is this planned to be a multi-step process or a single "Stop Core" (and Resume Core) function as far as the user is concerned?
Reply
  • Thank you for the info.

    Does "pausing current processes" mean a Core will be able to pause all types of jobs and resume them without issue after restart? There are several types of jobs that run so long and are not able to handle a restart currently, this would be a great feature.

    Is this planned to be a multi-step process or a single "Stop Core" (and Resume Core) function as far as the user is concerned?
Children
No Data