Buen día reciban cordial saludo.
De su amable ayuda, los backups de 16 máquinas virtuales salen con errores o con backup fallidos y necesitamos consultarles si es posible configurar a Commvault para que realice esos backups sin tener en cuenta el tema de los snapshot ?
Los errores que arroja el sistema son como los siguientes:
(Es un tema que no no es posible resolver desde el área de Infraestructura por temas de capacidad y obsolescencia de los equipos).
Best answer by Jace Ross
Hi Maria,
Unfortunately I don’t speak spanish but using a translator it appears you are having issues with VM backups and you’d like to know how to rectify the pictured errors without creating additional snapshots due to storage limitations. (Please correct me if my translation is incorrect).
1) Failed to enable Changed Block Tracking, this is a Hypervisor limitation, the VM mentioned has snapshots associated to it so CBT cannot be enabled. This isn’t a failure it just means the entire disk needs to be read to know what has changed on the VM.
2) A production checkpoint not being created means that the VM could not quiesce the guest file system. This could be an issue with Hyper-V integration tools or VSS on the guest operating system.
3) The 3rd error is stating that you are using a virtual Fibre Channel HBA on the VM. It is warning that the hypervisor cannot create a snapshot of a vFC HBA device so that device will be excluded from the backup. It does state the backup was failed though but this would not be why.
4) This states the same as the previous error but also that application aware was skipped. No further details are provided so their may be a few things happening with that VM.
5) This is a combination of error 1 and 2. The same applies for this failure.
If you’d like to investigate deeper into some of these issues I would recommend raising a support incident to do so.
Regards,
Hi Maria,
Unfortunately I don’t speak spanish but using a translator it appears you are having issues with VM backups and you’d like to know how to rectify the pictured errors without creating additional snapshots due to storage limitations. (Please correct me if my translation is incorrect).
1) Failed to enable Changed Block Tracking, this is a Hypervisor limitation, the VM mentioned has snapshots associated to it so CBT cannot be enabled. This isn’t a failure it just means the entire disk needs to be read to know what has changed on the VM.
2) A production checkpoint not being created means that the VM could not quiesce the guest file system. This could be an issue with Hyper-V integration tools or VSS on the guest operating system.
3) The 3rd error is stating that you are using a virtual Fibre Channel HBA on the VM. It is warning that the hypervisor cannot create a snapshot of a vFC HBA device so that device will be excluded from the backup. It does state the backup was failed though but this would not be why.
4) This states the same as the previous error but also that application aware was skipped. No further details are provided so their may be a few things happening with that VM.
5) This is a combination of error 1 and 2. The same applies for this failure.
If you’d like to investigate deeper into some of these issues I would recommend raising a support incident to do so.
Regards,
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
