Hello, On Mon, May 11, 2026 at 09:57:40PM +0200, Arno Lehmann wrote: > my actual experience was with things such as block size detection and > alignment the file system "inherits" from the LV properties and which > may not necessarily be identical to what can be found in a different > LVM environment or when dumping a snapshot's block dump to a physical > disk. Or partition.
Okay yes I have had problems moving data from a snapshot of a block device with 512-byte sectors to one with 4k sectors. Although I haven't yet come across a 4k drive that can't be told to emulate 512B for compat purposes. > Which allows me to circle back to the original question: Besides the backup, > which could be a dump of /something/, you'll always need a bit of > infrastructure, tools and a plan and when you start solving those, the > question of how the original backup is done is usually of secondary > importance. > > Is that something you could agree with? ;-) Hmm, somewhat 😀 I think we agree that taking a snapshot is the easy part! And yes I agree that you have to have a plan, before you start - before you provision the original server(s). I think it can be quite a simple plan though. Just planning to have (or have access to) similar hardware as to what is in production is going to work quite well if that duration of outage is acceptable, and the limitations of snapshots are factored in. For me that sort of thing covers concerns about the hardware and base OS. For any important application data as I said I think it does need a proper backup process anyway and so restoring from that would be part of my plan as well. Someone else's plan might decide that is out of scope. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
