Hi to all of you,
We're currently running in big troubles ...
For the backup side, our architecture is supported by an ARCServe R15 backup Domain, composed of 1 of Master server and 2 member servers. All are running Windows 2003R2SP2 32bits (ENU). All are running the same version of ARCServe (build 6300). The 2 members are dedicated to SAN related backups, with SAN option, fibre attachments, and running fine. The primary server is dedicated for LAN backups, wich includes the VMWare backups, by network.
For the VMWare side, we're running 2 ESXi5 associated with a VCenter 5.0.0.16964, managed via VSphere Client 5.0.0.16964 and VMWare Vcenter Converter Standalone 5.0.0.470252.
There is no fibre attachment between the VMWare architecture and our SAN.
What we're trying to do: because of production constraint, we can't play other backup types than RAW backups with ARCServe.
This means for us, the primary server to play as proxy server, with VDDK 5.0.0.427917 and ARCServe Backup Agent for Virtual Machines (in addition to the standard Backup Agent for Windows) installed on it. No VCB installed (since it's no more supported in ESXi 5), no converter tool, noting else.
RAW backups are running fine: between 4 and 6 GB/min average throughput, on LTO4 and LTO5 tapes.
But that's not the same for restore jobs ...
At this time, we are not abble to restore any of those RAW backups. Whatever we try/do, we always get the same result in ARCServe:
"AE0579 Failed to create Virtual Machine [VM_Name] on ESX server [ESXI_Name]. For more information refer RecoverVM.log available in the log folder under the client agent installation directory."
OK, here's what we got in the RecoverVMlog:
"4/05/12 14:21:10 [10324.37] -------------------------------------------------
4/05/12 14:21:10 [10324.37] JobID: 10324 Session#: 37 VMName: [VM_Name]
4/05/12 14:21:10 [10324.37] DoCreateVM operation in progress
4/05/12 14:21:10 [10324.37] -------------------------------------------------
4/05/12 14:21:10 [10324.37] Failed to get protocal registry name value pair
4/05/12 14:21:10 [10324.37] Trying to connect Host https://[ESXi_Name]/sdk ...
4/05/12 14:21:10 [10324.37] VCB_COM Log Cache begins
Connected to https://[ESXi_Name]/sdk
Log Cache ends
4/05/12 14:21:10 [10324.37] VCB_COM Log Cache ends
4/05/12 14:21:10 [10324.37] Connected successfully to the Host https://[ESXi_Name]/sdk ...
4/05/12 14:21:10 [10324.37] Calling CreateVM module ...
4/05/12 14:21:10 [10324.37] Overwrite existing VM option enabled for VM UUID 420bef6b-3ba4-711a-3518-92cdc088c795
4/05/12 14:21:14 [10324.37] Deleted the VM ([VM_Name])
4/05/12 14:21:18 [10324.37] VCB_COM Log Cache begins
CreateVM : Datacenter Name is ha-datacenter.
CreateVM : Datastore Name is Datastore2-(LUN1201).
createVMusingConfigSpecfromInfo : Network Name = VM Network
createVMusingConfigSpecfromInfo : Host Name = [ESXi_Name]
createVMusingConfigSpecfromInfo : vmConfigSpec is created
createVMusingConfigSpecfromInfo : MappedVMDiskURL is created
createVMusingConfigSpecfromInfo : VM TaskMor is created
Virtual Machine creation failed
Fault : Vim25Api.NotSupported
Message : Access to resource settings on the host is restricted to the server 'VCenter_IP_address' which is managing it.
Log Cache ends
4/05/12 14:21:18 [10324.37] VCB_COM Log Cache ends
4/05/12 14:21:18 [10324.37] CreateVM Failed with error msg - "Err_code: -113 CreateVM: Exception Raised - Virtual Machine could not be created."
4/05/12 14:21:18 [10324.37] After calling GetLogMsg
4/05/12 14:21:18 [10324.37] Trying to disconnect from Host https://[ESXi_Name]/sdk ...
4/05/12 14:21:18 [10324.37] Successfully disconnected from Host https://[ESXi_Name]/sdk ...
4/05/12 14:21:18 [10324.37] End of DoCreateVM operation
"
We've been dealing with CA for a fix they send us, T5OV072, supposed to fix our problem:
(from the .txt file description)
"Recovery of a VM using VDDK fails with following
error message:
createVm Failed with error msg - "Err_code: -113
CreateVM: Exception Raised - Virtual machine
could not be created.
Identified Faulting module :
Virtual Machine creation failed
Fault : Vim25Api.InvalidDeviceSpec
Message : Invalid configuration for device '3'.
Currently this issue is observed with VMXNET3 and
E1000 network adapter configured on virtual
distributed switch(vDS).
This fix will not add the device to the restored
VM but will ensure that the recovery is
successful. Configure the device manually after
recovery of the VM.
"
Nevertheless, we still have the same problem, nothing had been solved with it.
To my mind, as far as I know (I've been browsing the net for the week to find fix to this), the problem seems to come from the VMWare side, not the ARCServe side.
I mean, ARCServe seems not to be the only manufacturer to experiment issues withVCenter 5, right ?
I've found a solution on ARCServe boards too:
https://support.ca.com/irj/portal/anonymous/solndtls?aparNo=RI37863&os=WINDOWS&actionID=3
Allright, let's see ... What ?! Oh no, this isn't even thinkable ! We choosed to associate ESXi's to VCenter for HA protection, and the only solution provided would be to dissociate them manually ? That's a crazy thing ... and it's no possible for our production environnement !
Are any of you eperiencing the same problems ?
Does anyone has a valid solution on this problem ?
Would the upgrade of ARCServe to R16 fis this ?
We have asked CA to find us a solution, but at this time ... 