Hi all,
I´d like to discuss the following with you, I´m pretty new with SRM but I understand the basics. Please hear my story:
I have a twin data center, both sites have a vSphere environment with ESXi hosts and VirtCenter server running W2K8R2. I installed the SVC SRA and SRM recently and wanted to run a little test failover. Unfortunally this has failed, for a unknown reason.
What happens?
Well first it is going to prepare the storage and attach disks for the protection group, after this the power on of the test VM fails. I never get further than this.
looking at the log files I see these thing happen (I took out lots of parts by the way):
[2011-02-10 14:09:23.415 03100 warning 'SecondarySanProvider'] Timed out (30 sec) waiting for change on 'datastore' for 'vim.HostSystem:host-44'
[2011-02-10 14:09:23.416 03100 verbose 'SecondarySanProvider'] Received no new datastore updates for host 'host-44' after waiting for 30 seconds
[2011-02-10 14:09:23.416 02056 trivia 'SecondarySanProvider'] 'Rescan 1 hosts' took 37.025 seconds
[2011-02-10 14:09:23.776 02056 warning 'SecondarySanProvider'] Shadow datastore for datastore 'sanfs://vmfs_uuid:4d37e0e1-be371768-cb2e-e61f135e9b97/' not found
[2011-02-10 14:09:23.792 02056 trivia 'SecondarySanProvider'] 'Prepare VM 'shadow-vm-2493' for test' took 0.002 seconds
[2011-02-10 14:09:23.792 02056 warning 'SecondarySanProvider'] Failed to prepare shadow vm for recovery: (dr.san.fault.RecoveredDatastoreNotFound) {
[#1] dynamicType = <unset>,
[#1] faultCause = (vmodl.MethodFault) null,
[#1] datastore = (dr.vimext.SanProviderDatastoreLocator) {
[#1] dynamicType = <unset>,
[#1] primaryUrl = "sanfs://vmfs_uuid:4d37e0e1-be371768-cb2e-e61f135e9b97/",
[#1] },
[#1] reason = (vmodl.MethodFault) null,
[#1] msg = "",
[#1] }
As you can see it can´t find its shadow LUN (the shadow copy). Does anyone know why it takes so long for the host to see it´s failover datastore?
the SRA config is set to `Pre-Configured environment` and is using R3 failover with ShadowCopy, after a while the recoverd LUN is showing on the host but then the test has already failed.
So what am I doing wrong here? Anyone have seen this before?
Regards,
Peter.
