For larger server(s) that potentially take longer than expected RTO time, Customers typically prefer to have a pre-provisioned target and periodically SYNC to it, resulting in the TARGET VM in OCI to be kept online.

Keeping the Target ONLINE invokes OCI related VM costs, which sometime may be quite substantial depending on the OS, SHAPE, # & size of disks, # of NIC’s, etc. (may also vary depending on each cloud/region)

To strike a balance between the OCI costs vs preferred RTO, Rackware provides an easy, customizable, yet cost effective alternative to work around this situation, as documented in this procedure.

The objective is to offer Customers guidance with a Pre-Provisioned Target/DR Solution (for the VMs of their choice) a way to power them on only during a SYNC to it (for example once a week – also configurable) and keep them powered off at other times, thereby significantly reducing the OCI VM costs.

The procedure described herein, uses a set of 3 scripts (attached), all needed for each Target VM, essentially does the following:

  • Script-1 – 01_VM_power_cycle.py – Powers on/off the Target instance in OCI (called from Script-2)
  • Script-2 – 02_VM_power_cycle.sh – Checks/waits to ensure Stage-1 SYNC completes before proceeding
  • Script-3 – 03_VM_S2_Sync.sh:
  • Once Target VM is powered on, checks if RMM can passwordlessly SSH to the TARGET
  • If successful, performs a Stage-2 SYNC, using RMM server crontab task, at the configurable time
  • Upon successful Stage-2 SYNC completion (or failure), powers off the TARGET server (via Script-1)



Notes:  

  • Script(s) & value(s) shown herein are for example/guidance purposes ONLY, contains hypothetical values & does NOT depict any Customer data that we are aware of.   Any resemblance to any Customer data anywhere is purely coincidental.
  • Customer can configure any/all parameters/scripts used herein to suit their requirements and/or optionally bring in their own Custom script that can “do the stuff”.
  • RMM Support is NOT responsible for either the implementation of these scripts (both Customer owned or our provided) at Customer site, and/or debugging the issues associated with such scripts, and/or any error triggered due to the script execution and/or failure of the script itself.  These are provided as a sample/guidance purpose only and hence fully outside of scope of RMM Support.

(more details, please see the attached PDF and the 3 scripts)