-
- Novice
- Posts: 4
- Liked: never
- Joined: Sep 02, 2011 1:06 pm
- Full Name: Tom Handley
- Contact:
Issues after upgrading to ESXi 5.0
I upgraded my vCenter to v5.0 (was 4.1) and also rebuilt my host with 5.0 (was 4.1u1). I removed the old server and vCenter from the Servers list, created new jobs however when I tried to run the new job I get the following error:
Backing up object "[OS_1] Tom-VC01/Tom-VC01.vmdk"
BackupDiskFull failed
Client error: Failed to open VDDK disk [[OS_1] Tom-VC01/Tom-VC01-000001.vmdk] ( is read-only mode - [true] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [192.168.1.40];Port: 902;Login: [root];VMX Spec: [moref=2];Snapshot mor: [2-snapshot-101];Transports: [hotadd]] failed because of the following errors:
Server error: End of file
Any clues as to what I can do to fix this please?
Thanks
Backing up object "[OS_1] Tom-VC01/Tom-VC01.vmdk"
BackupDiskFull failed
Client error: Failed to open VDDK disk [[OS_1] Tom-VC01/Tom-VC01-000001.vmdk] ( is read-only mode - [true] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [192.168.1.40];Port: 902;Login: [root];VMX Spec: [moref=2];Snapshot mor: [2-snapshot-101];Transports: [hotadd]] failed because of the following errors:
Server error: End of file
Any clues as to what I can do to fix this please?
Thanks
-
- Veeam Software
- Posts: 21133
- Liked: 2140 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Issues after upgrading to ESXi 5.0
Tom, vSphere 5 is not currently supported, it just became available last week and we need time to perform thorough testing against it. Please track this forum for updates on this. Thanks.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Sep 02, 2011 1:06 pm
- Full Name: Tom Handley
- Contact:
Re: Issues after upgrading to ESXi 5.0
Happy to beta test
-
- Enthusiast
- Posts: 31
- Liked: never
- Joined: Jul 06, 2010 9:06 pm
- Full Name: Jamie Andrews
- Contact:
Re: Issues after upgrading to ESXi 5.0
Is there an ETA? This is the only thing holding us back from going to 5.0.
-
- Veteran
- Posts: 282
- Liked: 26 times
- Joined: Nov 10, 2010 6:51 pm
- Full Name: Seth Bartlett
- Contact:
Re: Issues after upgrading to ESXi 5.0
It looks like you are using hotadd mode and backing up a VM that may be 2008 R2. There is a known issue with hot-add/quiescence causing failures. You could try turning quiescence off and using VSS instead.
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Sep 02, 2011 1:06 pm
- Full Name: Tom Handley
- Contact:
Re: Issues after upgrading to ESXi 5.0
This has fixed the error but what do I lose by disabling quiescence?Sethbartlett wrote:It looks like you are using hotadd mode and backing up a VM that may be 2008 R2. There is a known issue with hot-add/quiescence causing failures. You could try turning quiescence off and using VSS instead.
-
- VP, Product Management
- Posts: 27356
- Liked: 2788 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Issues after upgrading to ESXi 5.0
Your VM backups will be in crash consistent state. If you're backing up windows VMs you want to enable "application-aware image processing" as it is recommended in the sticky F.A.Q. topic.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Sep 02, 2011 1:06 pm
- Full Name: Tom Handley
- Contact:
Re: Issues after upgrading to ESXi 5.0
Hopefully this will be fixed in the next product update?
-
- Chief Product Officer
- Posts: 31766
- Liked: 7266 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Issues after upgrading to ESXi 5.0
Possibly. But still, as it was already mentioned before, we highly recommend enabling application-aware processing to ensure correct Microsoft applications processing during backup and recovery. If you use VMware queiscense only, VMs will not be processed in the application-aware manner. Enabling application-aware processing is the only way to make image-level backup and recovery processes meet Microsoft's application requirements. Backup and recovery processes not following these requirements are not supported by Microsoft. Just something to keep in mind when making the decision.
For more information with Microsoft Exchange as an example, you can view the Running Exchange on VMware webinar.
For more information with Microsoft Exchange as an example, you can view the Running Exchange on VMware webinar.
Who is online
Users browsing this forum: Google [Bot] and 28 guests