Hi all,
I'm trying to use an VDR to backup. I have error on all esx/esxi - "Trouble reading files, error -3946 (disk open failed)".
VDR can backup only vm on ESX where VDR placed.
VDR v1.1.0.707
vSphere v4.0.0 build 208111
ESXi 4.0.0, 219382
ESX 4.0.0, 208167
Thanks in advance!
VDR VM need to see the vmdk of the VMs that you need to backup.
If VMs are on a local storage, you have to put VDR directly on the target ESX.
Andre
I have 9 ESX with local storage's and 1 iSCSI. I must use 9 VDR appliance?
http://www.vmware.com/products/data-recovery/features.html
Broad range of storage support. Protects your virtualized environment utilizing any type of storage. (Fibre Channel, iSCSI, NAS, or local storage)
I must use 9 VDR appliance?
Yes... if you have VMs on all of 9 local datastores.
Or you have to use other solutions like VCB, vRanger, Veeam, ...
Andre
I think you wrong. I read all specification about VDR and I don't find any limitation about local storage. VDR for SMB. SMB use local storage, not SAN.
Source vmdk disk must be accessible by the VDR VM, cause it will mount them (during the backup).
Destination disk for the VDR backups could be also a NAS.
Andre
VMware Data Recovery Administrator's Guide
"Data Recovery is built on the VMware vStorage API for Data Protection"
So, vStorage API can work only with local or SAN/NFS disk?
Andre, Please show me vmware doc with this limitation.
Sorry, but I want to hear about VDR limitation from vmware employer
VDR is writting the limitation.
See your error message:
VDR can backup only vm on ESX where VDR placed.
VDR make VM backup by mounting the vmdk of the VM and than make a copy of the data.
But if the VM cannot reach the vmdk, than it fails.
Andre
error message - "Trouble reading files, error -3946 (disk open failed)"
This is not completely accurate. The rule of thumb is if the VM is in the VC inventory's datacenter, then a VDR appliance in the same datacenter should be able to protect that VM.
Note that each VDR appliance is capped at protecting up to 100 VMs, so typically the only reason that you would deploy multiple appliances are if you need to protected more than this limit or if the ESX hosts in the same datacenter are geographically distributed and you can want to keep the backups "local" to each location.
VDR uses a variety of transports to move the data (i.e snapshot) from the VM to its dedupe store - the most efficient is by using SCSI hot add. There are a few requirements for use of SCSI hot add, one of which is visibility of source datastore from the VDR appliance. However, if VDR is unable to perform a SCSI hot add, then it will cycle through the various other methods, ending with a network file copy.
In terms of the -3946 error, some questions:
0) Assume you are running VDR 1.1 - if not, please upgrade
1) Has VDR ever able to backup this VM? Is this problem with all VMs?
2) If yes, what happens when you attempt to manually snapshot the same VM (Make sure to uncheck memory state and check quiesce guest file system option when attempting the manual snapshot since this will mimic the snapshot operation that VDR initiates.)
0) I use VDR v1.1.0.707 Build 207380
1) VDR can backup only VM on ESX host where VDR placed. Yes This problem with all VMs in Cluster.
2) I try and everything fine. I create and delete Snapshot without any errors
Are you filtering any of these TCP ports? 443 and 902
VDR needs to be able to establish a connection to the WebServices interface of the VC Server. By default, this server is listening on TCP port 443. (Same port that the vSphere Client connects to). Also, for accessing virtual disk metadata, we need to be able to establish NFC connections to all the ESX hosts running VMs it is protecting. -- NFC on ESX is listening on TCP port 902.
To sum it up, my recommendation would be to make sure that the following ports are open so that VDR can get to them:
+) TCP port 443 on the VC Server
+) TCP ports 443 and 902 on the ESX hosts running VMs you are protecting with VDR.
I check firewall and everything is fine. (I check in ESX firewall and I try telnet connection to 443 and 902)
All ports is open.
Then I would recommend opening up an SR. Thanks!
All all the ESX hosts in the same physical datacenter? How are the ESX hosts being physically connected?
All ESX in one Building. ESX connected to HP 3500zl(Core1 switch) and 3400yl(Core2 switch)
I have ESX 3.5 in this Datacenter. Maybe thats a problem?
I try to backup vm only on esx4 host.
VDR can protected VMs residing on ESX 4 hosts only. But it should not care if there are ESX 3.5 hosts that you are NOT protecting.
So, I find problem. I use @ in datastore name