From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Rico Dwi Setiawan <[email protected]>,
Yusuf Hadiwinata <[email protected]>,
Aldy Prastyo <[email protected]>,
Michael William Jonathan <[email protected]>,
Matthew Patrick <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>
Subject: Re: [## 346553 ##] Permohonan Backup NEO Lite
Date: Thu, 28 Mar 2024 04:36:02 +0700 [thread overview]
Message-ID: <CAFBCWQ+fO-=YozAE5Sk8jWS7ZnEw-JOgZGWOWBt8hax2HKfQ8A@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qNBqk_Bc4mzgHMHNhNY-QuyEnD_9xhQQCRAYrzdL13y4w@mail.gmail.com>
On Thu, Mar 28, 2024 at 4:27 AM Alviro Iskandar Setiawan wrote:
> Wew, lumayan ribet juga urusannya sampe pake kernel module. Emang
> lebih reliable langsung ambil snapshot VM nya, semua disk tambahan
> diduplicate di tempat lain gitu, ngga depend sama kernel yg jalan
> wkwkwk
Yeah, better solution. Di DigitalOcean backupnya juga pakai snapshot
gitu. Itu juga live, gak pernah ganggu service.
Urusan konsistensi data saya gak mendalami detailnya, tapi kemarin
ngobrol di LK ada metode snapshot yang pakai temporary area dulu kalau
call write ke disk di posisi backup, nanti readnya juga dari temporary
itu baru setelah backup selesai dirty writenya di flush ke disk
aslinya. Jadi hasilnya tetep konsisten, nggak terclobber secara
partial.
--
Ammar Faizi
next prev parent reply other threads:[~2024-03-27 21:36 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 14:36 Permohonan Backup NEO Lite Ammar Faizi
2024-03-27 14:51 ` Re:[## 346553 ##] " Muhamad Mulyadi
2024-03-27 15:05 ` [## " Ammar Faizi
2024-03-27 15:08 ` Muhamad Mulyadi
2024-03-27 15:18 ` [## " Ammar Faizi
2024-03-27 15:23 ` Muhamad Mulyadi
2024-03-27 15:31 ` [## " Ammar Faizi
2024-03-27 15:41 ` Muhamad Mulyadi
2024-03-27 15:59 ` [## " Ammar Faizi
2024-03-27 16:03 ` Muhamad Mulyadi
2024-03-27 16:11 ` [## " Ammar Faizi
2024-03-27 16:21 ` Muhamad Mulyadi
2024-03-27 17:38 ` [## " Ammar Faizi
2024-03-27 17:50 ` Rico Dwi Setiawan
2024-03-27 17:52 ` [## " Ammar Faizi
2024-03-27 18:03 ` Rico Dwi Setiawan
2024-03-27 19:40 ` [## " Ammar Faizi
2024-03-27 19:53 ` Rico Dwi Setiawan
2024-03-27 19:56 ` [## " Yusuf Hadiwinata
2024-03-27 20:02 ` Ammar Faizi
2024-03-27 20:09 ` Yusuf Hadiwinata
2024-03-27 20:17 ` Ammar Faizi
2024-03-27 20:33 ` Ammar Faizi
2024-03-27 20:42 ` Alviro Iskandar Setiawan
2024-03-27 20:45 ` Ammar Faizi
2024-03-27 21:00 ` Alviro Iskandar Setiawan
2024-03-27 21:06 ` Ammar Faizi
2024-03-27 21:13 ` Rico Dwi Setiawan
2024-03-27 21:21 ` [## " Ammar Faizi
2024-03-27 21:26 ` Rico Dwi Setiawan
2024-03-27 21:30 ` [## " Ammar Faizi
2024-03-27 21:27 ` Alviro Iskandar Setiawan
2024-03-27 21:36 ` Ammar Faizi [this message]
2024-03-27 21:44 ` Alviro Iskandar Setiawan
2024-03-27 21:47 ` Rico Dwi Setiawan
2024-03-27 21:55 ` [## " Ammar Faizi
2024-03-27 22:10 ` Rico Dwi Setiawan
2024-03-27 22:22 ` [## " Ammar Faizi
2024-03-27 22:32 ` Rico Dwi Setiawan
2024-03-27 22:37 ` [## " Ammar Faizi
2024-03-27 22:49 ` Rico Dwi Setiawan
2024-03-27 22:53 ` [## " Ammar Faizi
2024-03-27 23:01 ` Alviro Iskandar Setiawan
2024-03-27 23:03 ` Ammar Faizi
2024-03-27 23:08 ` Rico Dwi Setiawan
2024-03-28 13:58 ` [## " Ammar Faizi
2024-03-28 14:02 ` Alviro Iskandar Setiawan
2024-03-28 14:04 ` Ammar Faizi
2024-03-28 14:18 ` Alviro Iskandar Setiawan
2024-03-28 14:28 ` Ammar Faizi
2024-03-28 14:37 ` Alviro Iskandar Setiawan
2024-03-28 14:44 ` Ammar Faizi
2024-03-28 14:48 ` Alviro Iskandar Setiawan
2024-03-28 14:51 ` Ammar Faizi
2024-03-28 15:03 ` Muhamad Mulyadi
2024-03-28 16:34 ` [## " Ammar Faizi
2024-03-28 16:48 ` Fadil Roza
2024-03-29 0:04 ` Rico Dwi Setiawan
2024-03-29 1:39 ` [## " Ammar Faizi
2024-03-29 1:51 ` Rendy Wijaya
2024-03-29 3:28 ` [## " Ammar Faizi
2024-03-29 3:35 ` Rendy Wijaya
2024-03-29 6:25 ` Ammar Rafli
2024-03-29 6:40 ` [## " Ammar Faizi
2024-03-29 6:43 ` Ammar Rafli
2024-03-28 15:30 ` [## " Alviro Iskandar Setiawan
2024-03-28 16:34 ` Ammar Faizi
2024-03-27 21:09 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFBCWQ+fO-=YozAE5Sk8jWS7ZnEw-JOgZGWOWBt8hax2HKfQ8A@mail.gmail.com' \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox