Skip to main content
commvault.com commvault.com
Solved

VM backup failed - VM is not in a connected state

D
Byte
Forum|alt.badge.img+15

Hi there!

I would like to discuss the following backup job issue. There are some VMs, that failed to be backed up due to the failure reason - VM is not in a connected state. In fact, these VMs are powered off in the vcenter. I was looking for how to cope with this type of issue, but I didnt find any relevant resources.

So, my question is how to deal with this situation. The VMs should be powered off, but backups should be running as usual. Is there any workaround in the CV?

Best answer by Mike Struening RETIRED

@drPhil , are you looking at how to handle powered off vms, or how to ensure the vm gets backed up on the next round?

For the latter, this option to Backup Failed VMs should help:

https://documentation.commvault.com/11.24/expert/94778_backing_up_failed_virtual_machines.html

View original
Did this answer your question?
If you have a question or comment, please create a topic

3 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@drPhil , are you looking at how to handle powered off vms, or how to ensure the vm gets backed up on the next round?

For the latter, this option to Backup Failed VMs should help:

https://documentation.commvault.com/11.24/expert/94778_backing_up_failed_virtual_machines.html

https://www.linkedin.com/in/michael-struening
D
1 person likes this
  • D
    drPhil
D
Byte
Forum|alt.badge.img+15
  • drPhil
  • Author
  • Byte
  • 110 replies
  • April 1, 2022

Hi @Mike Struening, I am sorry for a later reply due to overwhelming with other incidents. To be honest, I was digging through the documentation and try to find something relevant to the already mentioned failure reason:

 

VM is not in a connected state - what does it mean?

In the vcenter I see for this VM following alert

 

 

Thus, I assume, if the VM is not in a connected state, there could be something wrong with network adapter settings within the vcenter. It sounds quite intelligently, doesnt it?

D
Vaulter
Forum|alt.badge.img+8
  • Dan WhiteVaulter
  • Vaulter
  • 54 replies
  • April 1, 2022

@drPhil That can absolutely be the case.

 

Some other causes:

 

  • The datastores are inaccessible
  • The ESX host is non-responsive or not licensed properly.
  • VM is not on the VM network
"If you give a man a fish, you feed him for a day. If you teach a man to fish, they will probably burn your spot"
D
L
2 people like this
  • D
    drPhil
  • L
    Laurent

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings