Oh, recovery-in-place. I tend to hear people refer to that a lot more often as "instant recovery." The basic idea...
behind that is that one of the big barriers to disaster recovery is the amount of time it takes to recover data.
In the past, there was a really long wait while data was restored, so instant recovery -- or recovery-in-place -- sought to eliminate that recovery window by redirecting the user workload to the backup server.
Now, you don't want to connect the user directly to a backup copy of their virtual machine because the minute the user starts working on that backup virtual machine the backup is no longer in a pristine state.
So what happens instead is a snapshot gets created so the backup remains in a pristine state and all the user write operations get redirected to that snapshot, so users are able to work off of the backup virtual machine.
As soon as that happens, the recovery process begins in the background. Users are completely oblivious that the recovery is even going on, and once the recovery is finished, the user workload is redirected back to the original VM.
Don't back up. Learn instant recovery.
Searching for a better DR strategy
Data backup strategy from a DR perspective
Dig Deeper on Backup for virtual servers
Related Q&A from Brien Posey
Bloatware isn't just annoying -- it can negatively affect OS security, for example. Find out ways to get rid of Windows 10 bloatware once and for all... Continue Reading
Is your Google data protected? Make sure you are backing up G Suite files, because Google doesn't provide the comprehensive protection you'll need to... Continue Reading
Hyper-converged systems, like any other, require data protection. We describe using RAID and erasure coding for hyper-convergence to help you pick ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.