> From: John Stoffel [mailto:j...@stoffel.org] > > I think the root cause of your failure here is that you assume ONE > full backup is all you need. Instead you should be keeping multiple > full backups instead.
Oh - heheheh. At any given time, I have a full backup on the attached disk, and I have one offline full backup onsite, and another offsite. And also a backup of the config necessary to recreate from scratch. I didn't mention before, that the old VM was a VirtualBox guest, but after determining that the host machine was having hardware problems, I decided to move the VM to a different host, which is ESXi. So I rebuilt from scratch on ESXi, in order to get back into operation. Now the broken host hardware has been fixed, and I've restored the full onsite (cold) backup onto the fixed hardware, but configured it to just stay off, as it's been replaced with the ESXi guest. So yes, you're absolutely right. Agreed 100%. > Here is should be: send a NEW full source FS to dest FS, leaving > other Full(s) alone. Yeah, I thought of that, but there isn't enough space on the target, and sometimes it's normal to clobber. For example, rotate the backup media from offsite to onsite, the old snapshot is 3 months old, so there are no overlapping snapshots and therefore no possibility of doing an incremental. A full send with clobber is required. It turns out, in the situation where full send with clobber is required, the OS is silently doing the temp filesystem anyway - So the zfs receive can be atomically backed out, if the zfs receive fails for any reason. This means I end up running into disk space problems, and I have to manually zpool destroy anyway. So the automatic clobber never worked right, and I have to do a manual clobber anyway. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
