a quiesced snapshot failed because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
I understand the semantics of the error message. It is not clear to me how the snapshot operation exceeeded the time with out user intervention.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Aug 26, 2009 1:24 pm
- Full Name: Gary Elkins
- Contact:
-
- VP, Product Management
- Posts: 27371
- Liked: 2799 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Releasing VM files CreateSnapshot error
Hello Gary,
This error states that when you freeze your VM there is a timeout for holding VM in a freezed state, and if the operation of creating the snapshot exceeds this timeout due to some reasons (latency issues, VC/ESX host high load e.t.c), then VM unfreezes and the snaphost fails.
To help you in resolving this can you tell me please do you experience this issue everytime or it happens randomly when you run the job? Also it'll be great to hear how you've configured your jobs (do you have VC or ESX connections only), as well as how long does it take to make a snapshot manually for the VM with this issue?
Thank you.
This error states that when you freeze your VM there is a timeout for holding VM in a freezed state, and if the operation of creating the snapshot exceeds this timeout due to some reasons (latency issues, VC/ESX host high load e.t.c), then VM unfreezes and the snaphost fails.
To help you in resolving this can you tell me please do you experience this issue everytime or it happens randomly when you run the job? Also it'll be great to hear how you've configured your jobs (do you have VC or ESX connections only), as well as how long does it take to make a snapshot manually for the VM with this issue?
Thank you.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Aug 26, 2009 1:24 pm
- Full Name: Gary Elkins
- Contact:
Re: Releasing VM files CreateSnapshot error
Backup completed with no problems last night. This site experienced a building power fail recently; I believe the timeout problem might have been related to this. I will monitor this system and update this entry.
Who is online
Users browsing this forum: FLHXS and 137 guests