Rapid Recovery

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.

  • 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.
  • We all know what the powershell approach is. I mentioned the issues with powershell in my original post. So when you respond with powershell as the answer, it makes me worry that no one at Quest is listening to our feedback or understands what our issues are

    - This post is from 2014 ... and nothing has changed.

    en.community.dell.com/.../

    - Powershell is un-supported. So your suggested method to power down your product is to use unsupported commands and scripting.

    - You want every single customer to build their own script to power down your product.

    - When a change is made that breaks our script, you want every one of us individually to spend our time to fix the script that powers down your product.

    - Just look at the amount of work above. Name one other product that takes this much individual work, all on the customers shoulders to build and manage, to simply power down.

    - Look at the debacle with Windows 2012 and the "hidden" windows key to shut down the OS. The process to shut down Windows was a bit harder but no where near this and yet MS changed it after the feedback in the next release, R2.

    - "The issue with shutting down a core graciously arouse from the jobs that are running at that time"

    I know what the issue is, but why is this our problem? Why cant you guys write some code that handles shutting down your product. Pause jobs, wait till jobs are done and then send a message to the terminal that the Core is ready.

    Lastly, I would like to say that the fact we are still talking about basic things like a supported method to reliably and easily power down your product takes away time and energy that we could use to talk about real issues with the product.
  • Hi scashman:
    Don't shoot the pianist (support engineer). :)
  • Never. I feel your pain. But this issue is so obvious and has been going for so long. I would love to see someones input that has the power to address it vs everyone just brushing it aside and saying powershell

    #Gina? (does this work here?)

    Who else should I tag

    When I talk to most new admins, they typically don't even know that the product needs some type of external power-down, they assume it acts like every other application in the world and works with an OS power down.

    I wonder how much data loss (repo corruption) occurs just because of this simple issue
  • These are all very good points.

    I can tell you that we have evaluated each of the concerns you listed above, and we will be addressing the majority of them in the next major release of Rapid Recovery.

    Also, we will be implementing a customer facing ideation portal in the next week or so. This will allow you to submit ideas directly for consideration, as well as vote on ideas for prioritization.

    We have many additional exciting new changes coming to Rapid Recovery this year. Stay tuned.