This is a great event so far. Carlos has been sharing a bulk of useful information. Remember that we're also running a Spanish version of this event here: Pregunte al Experto: NetWorker Module for Microsoft (NMM) - Configuraciones, Soluciones y Mejores pr....
In addition, for those Networker aficionados a separate Networker ATE event started today: Ask the Expert: File System backups using NetWorker.
We're looking forward to more questions. Keep them coming!
This discussion has ended. Thanks to those who've participated, but special thanks for our expert who took the time to answer everyones's questions.
I have a question about HyperV on windows 2008 backing up with NMM3.0.1
I got a customer when 1 CSV VM save set fails, all the other CSV VM save sets backup fail as well and customer is upset about this.
There is nowhere in nmm log / daemon log could point out which particular VM save set(s) causing this failure.
He need to exam every VM in that HyperV host to find out which VM broken.
Is it by design that 1 VM saveset backup failure causing the other ones fail as well ? If so, is there anyway to find out which VM save set causing this failure ?
Thanks for your advise in advance.
Please note that the ATE event already finished, so I would like to invite you to post in the NetWorker support forum:
If you use the "top saveset", such as APPLICATIONS:\Microsoft Hyper-V then there is no granularity enough in terms of savegrp reporting that would point to the specific VM that is failing, so you can specify the savesets per each VM, and in that case you will see which VM is failing.
Anyway, once you identify the VM failing, what is the cause for the failure? Did you manage to solve that issue? Is always the same VM or is the failure random?
Also please note that NW 8.2+NMM 8.2 is already available, and this include many improvements, in particular savegrp reporting is improved a lot in this kind of cases where top saveset is used.