IMPLEMENTASI SISTEM DISASTER RECOVERY BERBASIS SOFTWARE DEFINED NETWORK PADA DATABASE MONGODB

Sri Anggraeni, - (2024) IMPLEMENTASI SISTEM DISASTER RECOVERY BERBASIS SOFTWARE DEFINED NETWORK PADA DATABASE MONGODB. S1 thesis, Universitas Pendidikan Indonesia.

Baca Full Text klik disini
[img] Text
S_SISTEL_2007550_Title.pdf
Download (572kB)
[img] Text
S_SISTEL_2007550_Chapter1.pdf
Download (208kB)
[img] Text
S_SISTEL_2007550_Chapter2.pdf
Restricted to Staf Perpustakaan
Download (352kB)
[img] Text
S_SISTEL_2007550_Chapter3.pdf
Download (292kB)
[img] Text
S_SISTEL_2007550_Chapter4.pdf
Restricted to Staf Perpustakaan
Download (749kB)
[img] Text
S_SISTEL_2007550_Chapter5.pdf
Download (191kB)
[img] Text
S_SISTEL_2007550_Appendix.pdf
Restricted to Staf Perpustakaan
Download (3MB)
Official URL: https://repository.upi.edu/

Abstract

Database harus dijaga semaksimal mungkin dari adanya ancaman yang bisa mengakibatkan downtime atau bencana baik dilakukan secara sengaja maupun tidak disengaja. Oleh karena itu perlu adanya sistem backup data yang baik dan benar sebagai penerapan penanggulangan bencana atau disaster recovery. Penelitian ini melakukan live migration virtual machine dengan model stop and-copy sebagai sistem disaster recovery pada database MongoDB dengan parameter Recovery Time Objective dan Recovery Point Objective. Sebagai fungsi tools tambahan, MongoDB di monitoring menggunakan Prometheus dan Grafana dengan parameter utilisasi server dan kueri MongoDB_exporter_build_info. Hasil sistem monitoring yang diperoleh pada penelitian ini yaitu pada parameter utilisasi server, komponen CPU yang digunakan bernilai 1,5%, komponen RAM yang digunakan yaitu 31,5%, komponen uptime yaitu 22,3 menit dan kueri MongoDB_exporter_build_info mempunyai nilai 1. Dari grafik mengenai hasil live migration virtual machine yang diperoleh pada penelitian ini, Nilai rata – rata waktu RTO yaitu 6,15 detik sedangkan RPO memiliki rata- rata waktu 473 detik. Selisih waktu RPO dan RTO pada penelitian ini yaitu sebesar 466,855 detik dimana Recovery Time Objective (RTO) memiliki waktu yang lebih cepat dibandingkan Recovery Point Objective (RPO). ----- Databases must be protected as much as possible from threats that can cause downtime or disasters either intentionally or unintentionally. Therefore, it is necessary to have a good and correct data backup system as an application of disaster recovery. This research performs live virtual machine migration with the stop-and-copy model as a disaster recovery system on the MongoDB database with Recovery Time Objective and Recovery Point Objective parameters. As an additional tool function, MongoDB is monitored using Prometheus and Grafana with server utilization parameters and MongoDB_exporter_build_info queries. The results of the monitoring system obtained in this study are in the server utilization parameter, the CPU component used is 1.5%, the RAM component used is 31.5%, the uptime component is 22.3 minutes and the MongoDB_exporter_build_info query has a value of 1. From the graph regarding the results of live virtual machine migration obtained in this study, the average value of RTO time is 6.15 seconds while RPO has an average time of 473 seconds. The difference the time between of RPO and RTO in this study is 466.855 seconds where Recovery Time Objective (RTO) has a faster time than Recovery Point Objective (RPO).

Item Type: Thesis (S1)
Additional Information: https://scholar.google.com/citations?hl=en&user=MJWlmokAAAAJ ID SINTA Dosen Pembimbing Galura Muhammad Suranegara: 6703764 Ahmad Fauzi: 6122861
Uncontrolled Keywords: disaster recovery, SDN, MongoDB, Live migration, virtual machine,
Subjects: T Technology > T Technology (General)
Divisions: UPI Kampus Purwakarta > S1 Sistem Telekomunikasi
Depositing User: Sri Anggraeni
Date Deposited: 26 Aug 2024 06:39
Last Modified: 26 Aug 2024 06:39
URI: http://repository.upi.edu/id/eprint/120887

Actions (login required)

View Item View Item