HI GIO DRaaS (Disaster Recovery as a Service) HI GIO DRaaS (Disaster Recovery as a Service) is a secure data synchronization solution to another region (e.g., on-premises to HI GIO Cloud, HI GIO Cloud HCM to HI GIO Cloud HN, or vice versa) to regain access and functionality in case of a disaster. Moreover, the minimum RPO (Recovery Point Objective) is 5 minutes, suitable for critical business systems.

Our Key Advantages

Pay as you go

It only incurs a monthly management fee, and payment is only made for this service when a disaster occurs and the business starts using the service.

Training & Risk prevention

Support for training and disaster readiness demonstration to test the data recovery capabilities immediately after an incident occurs.

Quick Installation

Install the DRaaS application onto the HI GIO Cloud platform, and all cloud-based applications are quickly configured with this feature.

Recovery Time

Achieve SLA service commitments with reliable recovery

Professional advisory

Including Business Continuity Plan – BCP and Disaster Recovery – DR plan consulting for your business.

Our Key Advantages

Pay as you go

It only incurs a monthly management fee, and payment is only made for this service when a disaster occurs and the business starts using the service.

Quick Installation

Install the DRaaS application onto the HI GIO Cloud platform, and all cloud-based applications are quickly configured with this feature.

Training & Risk prevention

Support for training and disaster readiness demonstration to test the data recovery capabilities immediately after an incident occurs.

Recovery Time

Achieve SLA service commitments with reliable recovery

Professional advisory

Including Business Continuity Plan - BCP and Disaster Recovery - DR plan consulting for your business.

Getting started with HI GIO DRaaS

Setting up the Replication Environment This involves the installation and configuration of essential components and vSphere Replication Once the environment is established, you can select the virtual machines to protect and configure replication settings for each one.

When replicating a virtual machine to the cloud, a copy is created in the cloud environment. This copy remains synchronized with the on-premises system using vSphere Replication (VMware Cloud Director Availability), a continuous replication feature ensuring that changes made to the protected virtual machines are synchronized with the cloud copies in real-time. This provides a Recovery Point Objective (RPO) of the most recent state within 5 mins before a disaster for your business.

In the event of a disaster, you can initiate failover to the cloud copy of your virtual machines. This involves redirecting user traffic to the cloud copy of your workload, causing minimal to no disruption for users. Once the disaster is resolved, you can commence failback to the on-premises infrastructure, bringing your workload back to its original location.

Getting started with HI GIO Private Cloud

Setting up the Replication Environment This involves the installation and configuration of essential components and vSphere Replication Once the environment is established, you can select the virtual machines to protect and configure replication settings for each one.

When replicating a virtual machine to the cloud, a copy is created in the cloud environment. This copy remains synchronized with the on-premises system using vSphere Replication (VMware Cloud Director Availability), a continuous replication feature ensuring that changes made to the protected virtual machines are synchronized with the cloud copies in real-time. This provides a Recovery Point Objective (RPO) of the most recent state within 5 mins before a disaster for your business.

In the event of a disaster, you can initiate failover to the cloud copy of your virtual machines. This involves redirecting user traffic to the cloud copy of your workload, causing minimal to no disruption for users. Once the disaster is resolved, you can commence failback to the on-premises infrastructure, bringing your workload back to its original location.