021-3970 9999 info@vibicloud.com

Cloud Disaster Recovery with CloudEndure – INACO

About PT. Niramas Utama (INACO)

PT. Niramas Utama has established in 1990 and focus to supply coconut gel (nata de coco) in the middle of enormous demands of healthy foods and beverages. However in 1994, they diversified its products and created a commercial brand, INACO. PT. Niramas Utama (INACO)have focused on producing quality nata de coco and consistently developing different variants of mini jelly, mini pudding and puree. The objective was clearly to provide nutritious food for Indonesian children, while at the same time building a solid foundation and forces to be the market leader in this industry.

The Challenge

As the company grows every year, PT. Niramas Utama (INACO) depends on the constant availability of its back-end. After years of using a traditional on premise Disaster Recovery (DR), they realized the cost is getting higher. So, they decided it was time to look into leveraging the public cloud environment. They were attracted by the lower DR infrastructure costs afforded by the pay as you go cloud model. For the most important, cloud DR can provide backup and recovery for their critical server machines that host enterprise-level applications like SAP for business continuity and sustainability.

The Solution

Working closely with ViBICloud, PT. Niramas Utama (INACO) has several times assessment to build their DR blueprint, especially for SAP in application and database level. During the proof of concept (POC) using CloudEndure Disaster Recovery from AWS, they verified that their SAP workload could be replicated and recovered quickly on AWS Cloud without disruption or data loss. Given their tight budget, they was impressed that CloudEndure can continually replicates workloads into a low-cost of minimal EC2 compute instances. This allows PT. Niramas Utama (INACO) to use right-sized compute, only when disaster strikes or when performing to drill (do DR drill once a year). With estimated RPO (Recovery Point Objective) 10 minutes and RTO (Recovery Time Objective) 4 hours.
The project itself divided into 2 phases :

First phase :
Configure customer’s AWS account with best practices :

  • We set up Virtual Private Cloud on AWS
  • Configure and validate private/public subnets, ACL’s and security groups
  • Create EC2 instance on AWS
  • Configure IAM users, groups and policies for required access
  • Configure VPN site-to-site between on-premises and AWS site

Second phase :
Configure Hana Replication System to enable the secure replication of SAP HANA DB from customer’s on-premise environment to AWS
Configure AWS CloudEndure to enable the secure replication of data from customer’s on-premise environment to AWS
Topology Solution :

The Result

With the main goal of creating an effective DR site to protect their critical workload, the timing of this new DR strategy couldn’t have been better. Just weeks after POC, PT. Niramas Utama (INACO) feel satisfied with our solution. They can test their recovery point objective and recovery time objective highly accurate and seamlessly with CloudEndure tools.
They can quickly deploy dev-test environment without significant investments in additional hardware. This also enables shifting costs from non recurring (capital expense) to recurring (operational expense). They can save up to 50% of its DR costs annually compare with on-premise option.

Now that PT. Niramas Utama (INACO)’s critical workloads are protected and get monthly review by ViBiCloud’s team to adjust their needs as their business keep growing. Because in ViBiCloud, we have focus to become reliable partner to accompany clients in their digital transformation journey.

Optimization The Publicity And Effectiveness of PT. Arkadia Media Nusantara (Suara.com)

About Suara.com

Suara.com is a news portal that presents the hottest information on political, business, legal, football, entertainment, lifestyle, automotive, technology science to citizen journalism events. Packed with light language, straightforward and without prejudice. Information presented 24 hours, can be enjoyed via desktops, laptops to various gadgets or other mobile devices.

Spread Information Completely, Quickly, Clearly and Transparency

Present lately during online media, Suara.com is determined to provide new color for online media maps in Indonesia. In addition to the benefits of important news, it also presents interesting, unique news from various parts of the world. It is hoped that this diverse content can be enlightening, and inspire readers. Suara.com wants to disseminate information completely, quickly, clearly and clearly on all media platforms.
One support for this is the use of data servers. Suara.com still uses On-premise Server with the services it runs: NGINX, Redis, CMS, etc. So it is still not efficient and effective for the use of these services.

Migration and Modernize Workload Suara.com

ViBiCloud helps Suara.com to move the application environment and infrastructure of Suara.com to Amazon Web Service (AWS) Cloud.
The current environment will be migrated to AWS. The destination location will be in Singapore (South Asia). The process is divided into 2 (two) phases as follows:

Phase 1: Lift and shift migration to AWS Elastic Compute Cloud (EC2)
This phase is moving the workload that was running on On-Premise to AWS cloud. This phase is the first to adjust to the current environment but there are different places to run it. Adjustments made on the infrastructure or application side can be said to be minimal.

Phase 2: Modernize workloads.

• Redis, using Amazon Elasticache.
• Elastic Search, using Amazon ElasticSearch.
• MySQL, using Amazon Relational Database Service (RDS) for MySQL.

This phase is the modernization phase of several workloads that were previously running on Infrastructure-as-a-Service (IaaS) leading to Platform-as-a-Service (PaaS). The workloads that can be modernized are as follows:
The advantage of using PaaS here is that the process of maintaining service availability has been handled by AWS as a cloud service provider.
The final results of the work on moving this environment are as follows:

Reducing Budget Expenditures For The Suara.com Infrastructure System

With the migration of On-Premise servers to AWS Cloud, it can help reduce the budget expenditures needed for traditional computer infrastructure systems. With the integration of cloud systems, the budget issued can be adjusted to the amount of usage. Because AWS Cloud allows for “Pay As You Use”, so the less cloud needs, the less you have to pay, and vice versa. This is very useful to reduce costs, because the need to buy hardware needs that have a high price, can certainly be suppressed. Besides, the cloud system is handled by ViBiCloud IT experts. And they’re already certified.

Makes it easier to manage important documents and data on Suara.com

AWS Cloud can help facilitate access to important data stored on cloud servers. Of course, this data can be accessed if the device used is connected to the internet. Authorized users can access data quickly, easily, anywhere, and whenever data is needed. The AWS cloud system also provides advantages such as the need for work collaboration. Data management can also be easily done through a cloud system.

Increase Publicity Suara.com

• On-Demand
AWS Cloud service is provided on-demand. When we need a resource from the cloud, it can be available in minutes, even seconds. Just a few clicks.

• Flexible
AWS Cloud also offers high flexibility and scaling both vertically and horizontally, can be done quickly and easily.

ViBiCloud Team and Suara.com still working together up until now, to maintain and improve the cloud technology utilization to keep up-to-date with latest proven technology available to adopt in AWS cloud platform.

Apa itu Business Continuity dan Disaster Recovery dan Manfaatnya Bagi Perusahaan?

Business Continuity dan Disaster Recovery atau BCDR adalah sebuah metode yang digunakan untuk memulihkan layanan bisnis ketika terjadi disaster, sehingga bisnis tetap berjalan. Business Continuity dan Disaster Recovery dibagi menjadi 2 komponen utama:

  1. Business Continuity
    Business Continuity terfokus pada operasional bisnis. Didalamnya terdapat kebijakan dan prosedur agar bisnis tetap berjalan meskipun terjadi disaster.
  2. Disaster Recovery
    Disaster Recovery terfokus pada teknologi infrastruktur untuk menjalankan layanan bisnis tetap tersedia walaupun terjadi disaster.

Disaster dapat dibagi menjadi 3 perspektif:

  1. Software
    Kerusakan pada software dapat terjadi karena terkena malware yang menyebabkan beberapa data menjadi corrupt, ataupun server tidak dapat menahan request yang sangat banyak dalam satu waktu (seperti DDOS), sehingga menyebabkan downtime atau bahkan tidak dapat di gunakan lagi sehingga perlu membangun environment yang baru. Downtime pada software juga dapat terjadi karena dilakukan maintenance atau update version pada OS, hypervisor, dan lain-lain.
  2. Hardware
    Kerusakan pada hardware dapat terjadi karena sudah end of life (lifecycle infrastruktur ±5 tahun), hardware terbakar, ataupun human error ketika mengoperasikan server.
  3. Bencana alam
    Kerusakan yang terjadi karena bencana alam dapat mengakibatkan downtime pada layanan bisnis. Dalam bencana alam, terdapat beberapa kategori berdasarkan luas lingkupnya:
    • Terjadi bencana pada 1 lantai dalam suatu datacenter (misal: pemadaman listrik)
    • Terjadi bencana pada 1 gedung datacenter (misal: pemadaman listrik)
    • Terjadi bencana pada 1 titik wilayah (Zone) dalam suatu negara (misal: pemadaman listrik atau gempa bumi)
    • Terjadi bencana pada 1 negara (Region) (misal: gempa bumi, tsunami)

Untuk mengatasi disaster tersebut, maka perlu di sesuaikan skenario BCDR yang tepat untuk di implementasikan. Terdapat source sebagai sumber datanya, dan target sebagai datacenter kedua nya ketika terjadi disaster.

Best Practice Business Continuity dan Disaster Recovery / BCDR.
Terdapat beberapa best practice dari solusi BCDR adalah berdasarkan kebutuhannya:

  1. Untuk proses transfer / sinkronisasi data yang lebih lancar, maka diperlukan bandwidth yang di dedikasikan secara khusus untuk BCDR dan tidak sharing untuk operasional lainnya. Hal ini juga tidak mempengaruhi experience user ketika perlu pengaksesan ke internet
  2. Besar bandwidth yang digunakan berdasarkan besar data yang digunakan. Namun berdasarkan pengalaman, rekomendasi dari artikel ini minimal 25 Mbps
  3. Metode backup-restore dan sinkronisasi dapat di kombinasikan sebagai best practice. Hal tersebut berdasar pada case berikut:

Pada metode sinkronisasi akan memberikan benefit low RPO dan RTO, sehingga dalam pemulihan layanan bisnis akan lebih cepat dan user tidak perlu mengalami hal yang signifikan. Namun ketika hasil sinkronisasi dari source server dan target server adalah sama, maka ketika data di source server terkena virus, virus tersebut juga ikut tersinkronisasi ke target server. Untuk mengatasi ini, kita perlu adanya backup data yang dengan penjadwalan backup sehari 1x, sehingga ketika source server terkena virus dan beberapa file corrupt, maka kita bisa melakukan pemulihan dari data di hari sebelumnya, dimana data belum terkena virus.

Kenapa perusahaan harus menggunakan Business Continuity dan Disaster Recovery / BCDR?

  • Meminimalisir Penggunaan Sumber Daya
    Disaster recovery ini biasanya menggunakan virtual asset di cloud computing , yang mana dapat menghemat penggunaan sumber daya.
    Jadi, jika sudah menggunakan layanan ini di penyedia layanan disaster recovery (seperti ViBiCloud) semua kebutuhan untuk mengamankan aset perusahaan akan disediakan.
  • Kemanan bisnis lebih terjamin
    Penyedia layanan sudah pasti akan menjamin setiap data yang ada, dalam bentuk fisik maupun secara digital. Selain itu, sebagai pemilik perusahaan juga bisa meminta laporan bagaimana kondisi disaster recovery di dalam perusahaan.
    Penggunaaan disaster recovery juga bisa dilakukan sebelum bencana, saat bencana, dan sesudah bencana. Jadi, tidak perlu khawatir jika tiba-tiba perusahaan tertimpa bencana.

Jadi, penggunaaan Business Continuity dan Disaster Recovery / BCDR adalah sangat penting untuk kelangsungan perusahaan dan meng-efisiensikan sumber daya yang digunakan.
Dengan plan tersebut maka dampak keseluruhan bencana dapat diminimalisir pada sistem dan sumber daya. Selain itu juga dapat memaksimalkan kemampuan suatu perusahaan atau organisasi untuk pulih dari bencana lebih cepat.

Better Integration, More Internal Use, and Increased Efficiency with Red Hat OpenShift – PT. Bank Commonwealth

About PT. Bank Commonwealth

PT. Bank Commonwealth (Commonwealth Bank) with more than 20 years of presence in Indonesia is a subsidiary of Bank Commonwealth of Australia (CBA), the largest service provider listed on the Australian Securities Exchange and is included the Morgan Stanley Capital Global Index. Commonwealth Bank today offers customers a variety of banking products in 25 cities across Indonesia such as savings, deposits, mortgage, various investment products and bancassurance, working capital credit for Small and Medium Enterprises (SME) and Safe Deposit Box (SDB), 24-hours Call Centre, as well as internet banking with special features that offer transaction flexibility.

In line with PTBC’s mission “to be the market leader in providing digital financial solutions for our Retail & SME target customers”, Commonwealth Bank has broken three records of Indonesian Record Museum (MURI) through Tyme Digital – the first end-to-end digital onboarding platform that allows customers to open bank account in less than 10 minutes –, KTA Tyme Digital – the first unsecured loan with its digital submission process and instant decision making –, and Commonwealth Bank’s Mobile Banking, as the first mobile banking application with investment features. Besides Tyme Digital, Commonwealth Bank also offers best in class customer experience through branch with digital capability that has been present in Kensington – Kelapa Gading, PIK, and WTC 6.

Develop Innovations and Improve PTBC Services

Commonwealth Bank is one of the banks in Indonesia which has a worldwide network. As a superior bank, banks need to increase their agility and flexibility to maintain their excellence. Migrating to the cloud has turned out to benefit Commonwealth Bank, by improving all its service processes.
Commonwealth Bank also wants to accelerate the development of new innovations by using DevOps.

CLOUD SERVER COMMONWEALTH BANK – OpenShift Container Platform Deployment

RedHat OpenShift Container Platform (OCP) will run on the Microsoft Azure Cloud Platform. OCP itself has the following main components:

  1. Master Nodes
    The Master Node is the main component to regulate the OCP lifecycle which consists of a data store to store the state of the OCP component, API controller, scheduler for pod positioning, replication controller to monitor pod status, and etcd. The main task of the master node is to manage the nodes in the Kubernetes cluster and arrange the placement of pods within the nodes.
  2. Infrastructure Nodes
    The infrastructure node will be used by the OpenShift registry and Router functions.The function of the router is to provide a path to access services within the OCP cluster. The router will provide a FQDN based hostname to be able to access applications inside the OCP cluster. each router will consist of route name, service selector, and service configuration.
    The OpenShift registry is used to store the docker image so that users can directly use the image to deploy applications. When a new image is generated and integrated into the internal registry, the registry will provide information to OpenShift about the new image so that it can be used by other users.
  3. Application Nodes
    Application nodes are used to run applications in the form of a Docker container. Types of applications that can be deployed include Java applications, PHP, Spring Boot, and others. Database implementations will be deployed outside of the OCP platform.
  4. Bastion Host
    Bastion node will be used to deploy / install the OCP platform on the cluster. OCP installation initiation using ansible is done through this server.
  5. Azure Disk & Storage
    Azure Disk will be used as a persistent volume of applications that need it and Azure Storage will be used by Infrastructure Nodes to manage and orchestrate the registry container.
  6. Azure Load Balancer
    Azure Load Balancer (LB) will be used as an access gate for Master Nodes, Infra Nodes, and Application nodes. Specifically, applications running on the OCP platform will be accessible through the Load Balancer component.
  7. Azure DNS
    Azure DNS will be used as the registrar naming access, doing translation from DNS names to public IPs from Load Balancer.

Bastion Host is a server to run OCP deployments. This server also acts as a workstation / jump host to administer the servers in the OCP cluster later. Whereas the LB Master and LB Router are made within the Azure resource group (availability sets), each of which functions to load-balancing the master and infra servers that contain a pod router.
The master node for each OCP cluster will consist of at least 3 master nodes to ensure that there are always sufficient number of master nodes to manage OCP clusters and that an odd number of master nodes is needed to meet the quorum requirements in the cluster master node. Infrastructure nodes are implemented at least 3 nodes for the needs of the Pod (container) Registry for image storage, routers for network layer service access, Grafana and Alert Manager for monitoring. 6 Application nodes in which each pod will have an application running.

The RedHat OCP Model of Use

  1. Platform-as-a-Service (PaaS) Model
    In this model, PTBC will be charged based on the number of containers that run within 1 (one) month. The container will be manufactured via ViBiCloud based on a request from PTBC. All containers made on this model will be charged a flat rate per month. The infrastructure will be managed by ViBiCloud as the provider and support of this service.
  2. Infrastructure-as-a-Service (IaaS) Model
    In this model, PTBC will be charged based on the current VMs to support this need. Cloud infrastructure will be managed by ViBiCloud.

Service Optimization and Innovation with DevOps

Commonwealth Bank is accelerating new solutions by developing DevOps. By combining development (Dev) and operations (Ops), DevOps can enhance collaboration and coordination between teams to deliver, and operate new solutions more quickly. With cloud the DevOps implementation becomes more efficient and faster.
However, to use the cloud, Commonwealth Bank must also comply with strict regulations from the financial services industry, as governed by the OJK (Indonesian Financial Services Authority). In this case ViBiCloud provides the most suitable solution using hybrid cloud.
By combining public cloud and private cloud, Commonwealth Bank is able to enhance flexibility and optimize premise infrastructure while still meeting regulatory compliance, and protecting security. ViBiCloud helps Commonwealth Bank migrate their datacenter to use cloud solutions. Now Commonwealth Bank has used container service on Red Hat OpenShift, which is used on Azure Cloud.
By utilizing service containers (OpenShift and Azure Kubernetes) to build their business applications and use a micro service architecture, companies can develop applications that are more flexible, efficient, and optimal.

The results of this transformation are enormous. In general, hybrid cloud solutions have enabled Commonwealth Bank to grow and remain in compliance with OJK regulations.