• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 28 subscribers
  • Views 11331 views
  • Users 0 members are here
Options
Related
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

Emte
over 7 years ago

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
  • 0 over 7 years ago
    Hi scashman:
    The issue with shutting down a core graciously arouse from the jobs that are running at that time. Assuming that there are no stuck or in-cancellable jobs, a "template" to shut down the core graciously via Powershell would look as below:

    # disable core service
    set-service RapidRecoveryCore -StartupType Disable
    # suspend snapshots
    suspend-snapshot -all
    # if incoming replication is present
    suspend-replication -incoming all
    # cancel all active jobs (you need to wait at least 30 sec. after no active jobs are reported)
    for(;;){stop-activejobs -all}
    # stop core service
    stop-service RapidRecoveryCore
    # when the core service stopped, find out what other services are still running
    get-service Dell*,Rapid*
    # stop those services either separately or as a block
    stop-service Rapid*,Dell*

    When you restart the core, you need to use sc.exe to re-enable the core service as PowerShell does not have a command to enable a service in delayed-start mode.
    sc.exe config RapidRecoveryCore start= delayed-auto
    (note a space after the "=" sign)
    # start the core service
    start-service RapidRecoveryCore

    Only the core service needs to be started (assuming that RapidRecoveryMongod starts together with the core)
    # Wait for the repository check to finish and enable snapshots
    resume-snapshot -all
    # resume incoming replication if present
    resume-replication -incoming all

    Hope that this helps.
Reply
  • 0 over 7 years ago
    Hi scashman:
    The issue with shutting down a core graciously arouse from the jobs that are running at that time. Assuming that there are no stuck or in-cancellable jobs, a "template" to shut down the core graciously via Powershell would look as below:

    # disable core service
    set-service RapidRecoveryCore -StartupType Disable
    # suspend snapshots
    suspend-snapshot -all
    # if incoming replication is present
    suspend-replication -incoming all
    # cancel all active jobs (you need to wait at least 30 sec. after no active jobs are reported)
    for(;;){stop-activejobs -all}
    # stop core service
    stop-service RapidRecoveryCore
    # when the core service stopped, find out what other services are still running
    get-service Dell*,Rapid*
    # stop those services either separately or as a block
    stop-service Rapid*,Dell*

    When you restart the core, you need to use sc.exe to re-enable the core service as PowerShell does not have a command to enable a service in delayed-start mode.
    sc.exe config RapidRecoveryCore start= delayed-auto
    (note a space after the "=" sign)
    # start the core service
    start-service RapidRecoveryCore

    Only the core service needs to be started (assuming that RapidRecoveryMongod starts together with the core)
    # Wait for the repository check to finish and enable snapshots
    resume-snapshot -all
    # resume incoming replication if present
    resume-replication -incoming all

    Hope that this helps.
Children
No Data