On Fri, Sep 13, 2013 at 4:24 PM, Daniel Chenault <[email protected]> wrote: >>> That's the point of the "hot clone" (I'm stealing that). It's an exact >>> image of the running server including any changes such as you describe >>> current >>> up to the last transmitted packet. There is no restore. >> >> If there's no restore then why are you bothering cloning? > > I'm not completely sure how to answer that. I don’t' think you understand > how the process works that I've already outlined.
You say there's no restore. I presume you are "hot cloning" to *something*. Why bother doing that if you're never going to restore it to anything? Earlier you mention that it's cloning to a standby which you can have up and running in four minutes or so. That's a restore, is it not? The fact that your restore happens in four minutes doesn't mean it's not a restore. It's just a really quick one. And if you *are* going to restore it, then things get more complicated. If the system was kind enough to crash cleanly, e.g., you unplugged the power cord accidentally, or the CPU just killed itself and the system immediately bluescreen, then sure, restoring the system as it was is great. It's a beautiful thing. But what if the system got messed up by a software update, or scrambled a filesystem, or had a malware compromise, or what-have-you. Then you don't *want* to go back to the very last moment in time. You want to go back to the last-known-good. Then all the complications described previously still matter. -- Ben
