Amyd80 wrote: We will have a two-node Hyper-V WS2012 cluster, with 8 VMs stored on a SAS SAN
Amyd80 wrote:Are there any specific CBT performance bottlenecks in terms of hardware or software configuration that we can tweak to make sure the impact of the driver is as low as possible? Like, is for instance the speed of the system drive of the cluster nodes the limiting factor, or something else entirely? And am I right in assuming that this small performance hit is only present when writing to the VMs, that is, read operations do bypass the CBT driver entirely, right?
Amyd80 wrote:To point 2, just to make sure I understood correctly: just schedule two simultaneous backup jobs with two different backup targets, both using as source container the entire cluster, and then use the exclude option to respectively kick out one half of the VMs for the one job and the other half for the other, right? That makes sense, but one quick follow-up question: since the container is dynamic, does this mean that adding at a later date a VM to the cluster will cause this new VM to be backed up twice automatically, unless we remember to exclude it from one of the jobs?
Users browsing this forum: No registered users and 1 guest