Reboot Compute Resource

To reboot a Compute resource:

  1. Go to your Control Panel's Compute resources menu (or click a Compute zone name underneath the main Compute resource menu link).
  2. Click the label (name) of the Compute resource you want to reboot.
  3. On the Compute resource details screen that follows, click the Tools button, then click Reboot Compute resource.
  4. A new screen will open asking for confirmation (via three checkboxes) before reboot:


    • Start running virtual servers after reboot? If this option enabled the system will initiate the failover process.

      The failover process will be initiated despite the Disable failover configuration for Compute resource or Compute zone.

    • Stop all virtual servers that cannot be migrated to another Compute resource? Check this box if you want VSs that cannot be migrated to be powered off. When a Compute resource is scheduled for a reboot, OnApp will first attempt to hot migrate all VSs it hosts. If hot migration is not possible for a VS, OnApp will attempt to cold migrate that VS. With this box checked, if cold migration fails, the VS will be stopped so the reboot may proceed. If you don't check this box, OnApp will attempt to hot and then cold migrate all VSs hosted by the Compute resource being rebooted – but will stop the migration process if any VS cannot be migrated.

    • Are you sure you want to reboot this Compute resource? A simple confirmation to confirm that you want the Compute resource to reboot.

  5. When you're certain you want to proceed with the reboot, click the Reboot button.

Reboot option is not available for VMware Compute resources.
If your backups disappear after rebooting the CloudBoot Compute resource with LVM storage which is used as a backup server , add mount command to CloudBoot backup server custom config after the reboot. This is a known issue which will be fixed in the future release.

To fix your custom config settings, use one of the following options provided in the examples below (you will have to specify your own device names):
  1. If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2)

    mkdir -p /onapp/backups

    mkdir -p /onapp/template

    s mount /dev/sda1 /onapp/backups

    mount /dev/sda2 /onapp/templates

  2. If you current array is detected as /dev/sda1 and currently everything is located in /onapp within templates and backup directories within:

    mkdir -p /onapp

    mount /dev/sda1 /onapp