Lars Wirzenius on Nostr: Another backup software requirement: performance. When restoring, the bottleneck ...
Another backup software requirement: performance. When restoring, the bottleneck should be network or disk bandwidth. If I have a backup store on a local NVMe drive in a USB enclosure, connected over USB 3.2 Gen2, and I'm restoring to a local NVMe drive, the restore should happen at close to the linear read speed from the backup drive.
I've said this before. This time it's triggered from waiting hours to restore data to a re-installed laptop, at a fraction of the potential speed.
Published at
2024-11-18 06:29:10Event JSON
{
"id": "7b34be7e63133a77b7198886d9fda0c14049c039c58bdb962a1c42a0922d236b",
"pubkey": "b10dc1f389e232d431638f9ab5e479818b1bfab197d62e420c170baf0bec09cb",
"created_at": 1731911350,
"kind": 1,
"tags": [
[
"proxy",
"https://toot.liw.fi/users/liw/statuses/113502542256286750",
"activitypub"
]
],
"content": "Another backup software requirement: performance. When restoring, the bottleneck should be network or disk bandwidth. If I have a backup store on a local NVMe drive in a USB enclosure, connected over USB 3.2 Gen2, and I'm restoring to a local NVMe drive, the restore should happen at close to the linear read speed from the backup drive.\n\nI've said this before. This time it's triggered from waiting hours to restore data to a re-installed laptop, at a fraction of the potential speed.",
"sig": "cc15ee805045e1568832082596fa53ec928cb7e8eca5e47007b017b2842f6e03dbeeae2fb41e4e6f88590976bca482c29b0fe69402acb96094825586319fdfdf"
}
