• With a cloud service, customers expect an “always on” capability – “maintenance mode” and other activities should be minimised.
  • Moreover, with the advent of metered services, it’s important that available uptime (burning credits) is maximised – you don’t want the server burning credits if it’s not available for use.
  • On premises Essbase can easily be backed up with no downtime with some custom backup scripts – let’s get the cloud to do the same.
  • OAC essbase backups are somewhat CPU intensive
  • The 2x most common use cases are:
    • Restore an individual application
    • Restore the server and rebuild an application
  • This post shows you how to turbocharge your backups!