What is the difference between a traditional file-level backup and a virtual machine backup?
Most traditional client/server architecture remains the same in the server virtualization environment where the client has an agent installed. However, this can become cumbersome. We still have to manage agents. There’s processor overhead, which can be an issue, agent-based backup and virtual machines. This is especially true if multiple virtual machines are running on a single physical server, which is very much the case in a virtualized world. If those virtual machines all kick off the backup process at the same time, that CPU can be hit pretty hard and affect the applications. So, an alternative is to use a different technology to perform the backup of the virtual machine disk image directly. This requires the virtual machine to be suspended so that a consistent capture of the virtual machine can be performed. Once the machine is suspended, the backup process can take place and then it can be restarted again. This works well, but suspending the virtual machine is an issue because ta
Related Questions
- What is the difference between EVC and the old CPUID masking feature (accessed from the Virtual Machine Settings dialog box, Options tab, CPUID mask option)?
- What is the process of converting a backup to a virtual machine? Is there some kind of utility?
- What is the difference between the SENSEO® Coffee Machine and a traditional coffee machine?
