glauk
Contributor
Contributor

SRM test error cannot power VM

Hello

<![endif]><![if gte mso 9]>

<!--

/* Font Definitions */

@font-face

{font-family:"Cambria Math";

panose-1:2 4 5 3 5 4 6 3 2 4;

mso-font-charset:1;

mso-generic-font-family:roman;

mso-font-format:other;

mso-font-pitch:variable;

mso-font-signature:0 0 0 0 0 0;}

@font-face

{font-family:Calibri;

panose-1:2 15 5 2 2 2 4 3 2 4;

mso-font-charset:0;

mso-generic-font-family:swiss;

mso-font-pitch:variable;

mso-font-signature:-520092929 1073786111 9 0 415 0;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

{mso-style-unhide:no;

mso-style-qformat:yes;

mso-style-parent:"";

margin:0cm;

margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:11.0pt;

font-family:"Calibri","sans-serif";

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

mso-fareast-language:EN-US;}

p

{mso-style-noshow:yes;

mso-style-priority:99;

mso-margin-top-alt:auto;

margin-right:0cm;

mso-margin-bottom-alt:auto;

margin-left:0cm;

mso-pagination:widow-orphan;

font-size:12.0pt;

font-family:"Times New Roman","serif";

mso-fareast-font-family:"Times New Roman";}

span.EmailStyle15

{mso-style-type:personal;

mso-style-noshow:yes;

mso-style-unhide:no;

mso-ansi-font-size:11.0pt;

mso-bidi-font-size:11.0pt;

font-family:"Calibri","sans-serif";

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

color:windowtext;}

.MsoChpDefault

{mso-style-type:export-only;

mso-default-props:yes;

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

mso-fareast-language:EN-US;}

@page Section1

div.Section1

-->

I have issue with test SRM while it goes all ok but when come to power VM in

normal mode does not power VM , the rest of them is OK.

we have run recovery twice the SRM it went ok but I don’t know why is

this in test does not run VM.

someone sad that it may be the isolated network but I know that it

create bubbled network automatically.

the system is designed that has 14 ESX servers IBM blade boot from EMC

clarion and the recovery site the same.

G

0 Kudos
12 Replies
glauk
Contributor
Contributor

i just want to ad the sreen imag!file:///C:/Users/LIFEVE~1/AppData/Local/Temp/moz-screenshot-2.png!e of the error

!file:///C:/Users/LIFEVE~1/AppData/Local/Temp/moz-screenshot-3.png!

0 Kudos
TimOudin
Hot Shot
Hot Shot

1) Does the virtual machine show as being protected when looking at your protection group?

2) What does that full status message read?

Tim Oudin

Tim Oudin
0 Kudos
glauk
Contributor
Contributor

hello Tim

thanks for your reply and the answer is that the mashine is protected and show all in blue with no error .

<![endif]><![if gte mso 9]>

<!--

/* Font Definitions */

@font-face

{font-family:"Cambria Math";

panose-1:2 4 5 3 5 4 6 3 2 4;

mso-font-charset:1;

mso-generic-font-family:roman;

mso-font-format:other;

mso-font-pitch:variable;

mso-font-signature:0 0 0 0 0 0;}

@font-face

{font-family:Calibri;

panose-1:2 15 5 2 2 2 4 3 2 4;

mso-font-charset:0;

mso-generic-font-family:swiss;

mso-font-pitch:variable;

mso-font-signature:-520092929 1073786111 9 0 415 0;}

/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal

{mso-style-unhide:no;

mso-style-qformat:yes;

mso-style-parent:"";

margin:0cm;

margin-bottom:.0001pt;

mso-pagination:widow-orphan;

font-size:11.0pt;

font-family:"Calibri","sans-serif";

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

mso-fareast-language:EN-US;}

span.EmailStyle15

{mso-style-type:personal;

mso-style-noshow:yes;

mso-style-unhide:no;

mso-ansi-font-size:11.0pt;

mso-bidi-font-size:11.0pt;

font-family:"Calibri","sans-serif";

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

color:windowtext;}

.MsoChpDefault

{mso-style-type:export-only;

mso-default-props:yes;

mso-ascii-font-family:Calibri;

mso-ascii-theme-font:minor-latin;

mso-fareast-font-family:Calibri;

mso-fareast-theme-font:minor-latin;

mso-hansi-font-family:Calibri;

mso-hansi-theme-font:minor-latin;

mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font:minor-bidi;

mso-fareast-language:EN-US;}

@page Section1

div.Section1

-->

the errorr mesage is:

error: unable to recover virtual machine 'name of server'.

protection for the VM need to be repaired

0 Kudos
TimOudin
Hot Shot
Hot Shot

With that error message the virtual machine should show with an error in the protection group. I would, from the protection group, remove protection. If, after that, the shadow vm exists on the remote site, delete that from disk as well. Then configure protection on the virtual machine.

Good luck!

Tim Oudin

Tim Oudin
0 Kudos
glauk
Contributor
Contributor

If I remove protection group the shadow VM does not show in the remote site. we now that the config is fine only test does not work but when you RUN the recovery it finish with suces. I think i am mising something that stop power-in VM.

0 Kudos
Dynamax
Enthusiast
Enthusiast

could you provide the SRM log file?

Its default location is below unless you changed it on install

C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\Logs

0 Kudos
glauk
Contributor
Contributor

the requestet log file is in atachment

0 Kudos
TimOudin
Hot Shot
Hot Shot

You're having storage issues. I believe I see at least two datastores disappearing during your test, possibly this vm is on both. Go back and analyze the LUN mapping in MirrorView and you're snapshot configuration, then get EMC on the phone.

Here I see discovery of at least one of the LUN that I believe this VM resides

Received update for vim.Datastore:datastore-1237:
name = "info",
op = "assign",
val = (vim.host.VmfsDatastoreInfo) {
dynamicType = &lt;unset&gt;,
name = "snap-0307ec41-OS_LUN_64_EXMS4-A",
url = "sanfs://vmfs_uuid:4bc32265-80d65abb-a810-001a64902d22/",
freeSpace = 18446548992,
maxFileSize = 274877906944,
drsUnfairnessThreshold = &lt;unset&gt;,
timestamp = "2010-04-12T13:38:45.834738Z",
vmfs = (vim.host.VmfsVolume) {
dynamicType = &lt;unset&gt;,
type = "VMFS",
name = "snap-0307ec41-OS_LUN_64_EXMS4-A",
capacity = 117843165184,
blockSizeMb = 1,
maxBlocks = 262144,
majorVersion = 3,
version = "3.33",
uuid = "4bc32265-80d65abb-a810-001a64902d22",
extent = (vim.host.ScsiDisk.Partition) ,
vmfsUpgradable = false,
forceMountedInfo = (vim.host.ForceMountedInfo) null,
},
},
}

Now, identification of the VM

Noticed new virtual machine 'vm-1243' on datastore 'datastore-1237'

Datastore mapping

Adding datastore 'snap-0307ec41-OS_LUN_64_EXMS4-A' with MoId 'datastore-1237' and VMFS volume UUID '4bc32265-80d65abb-a810-001a64902d22' spanning 1 LUNs

Failure of the VM and datastore

Shadow virtual machine: 'vim.VirtualMachine:vm-1243' has become inaccessible!
RecordOp ASSIGN: needsRepair, shadow-vm-21140
Received update for vim.Datacenter:datacenter-2:
(vmodl.query.PropertyCollector.Change) [
(vmodl.query.PropertyCollector.Change) {
dynamicType = &lt;unset&gt;,
name = "datastore",
op = "remove",
val = &lt;unset&gt;,
},
(vmodl.query.PropertyCollector.Change) {
dynamicType = &lt;unset&gt;,
name = "datastore
ShadowUpdateCallback
Noticed removal of datastore 'datastore' from datacenter 'datacenter-2'
Noticed removal of datastore 'datastore' from datacenter 'datacenter-2'
Result set
to (dr.secondary.ReplicationManager.SingleVmFailure) [
(dr.secondary.ReplicationManager.SingleVmFailure) {
dynamicType = &lt;unset&gt;,
vm = 'dr.secondary.ShadowVm:shadow-vm-21140',
fault = (dr.secondary.fault.ShadowVmNeedsRepair) {
dynamicType = &lt;unset&gt;,
faultCause = (vmodl.MethodFault) null,
vmName = "EXMS4-A",
shadowVm = 'dr.secondary.ShadowVm:shadow-vm-21140',
msg = "",
},
}
]

Object being watched was destroyed: vm-1243 fault:
(vmodl.fault.ManagedObjectNotFound) {
dynamicType = &lt;unset&gt;,
faultCause = (vmodl.MethodFault) null,
obj = 'vim.VirtualMachine:vm-1243',
msg = "",
}
Received update for vim.Datacenter:datacenter-2:
(vmodl.query.PropertyCollector.Change) [
(vmodl.query.PropertyCollector.Change) {
dynamicType = &lt;unset&gt;,
name = "datastore
Error set to (vmodl.fault.ManagedObjectNotFound) {
dynamicType = &lt;unset&gt;,
faultCause = (vmodl.MethodFault) null,
obj = 'vim.Datastore:datastore-1237',
msg = "The object has already been deleted or has not been completely created",
}
RecordOp ASSIGN: info.completeTime, ShadowVm.RepairShadow-877
State set to error
RecordOp ASSIGN: info.state, ShadowVm.RepairShadow-877
Shadow virtual machine: vim.VirtualMachine:vm-1243 has been destroyed!
NeedsRepair is already set to 'true' for ShadowVm 'dr.secondary.ShadowVm:shadow-vm-21140'. Ignoring...
Object 'vim.VirtualMachine:vm-1243' could not be found in MultiPropertyGetter::Get
Cannot find Shadow VM 'vm-1243' on the VC. The VM seems to be deleted.

Tim Oudin

Tim Oudin
0 Kudos
glauk
Contributor
Contributor

hello Tim

thanks for the answer. where do you se that there is a mirorview issue. the name of VM is exms4 and i dont se that is snapshoot is not working well.

0 Kudos
TimOudin
Hot Shot
Hot Shot

You say the name of the VM is "exms4"? Your first screen shot shows a VM named "EXMS4-A" and I see only this one virtual machine in these logs.

My comment on MirrorView was likely wrong, I should had said SnapVIew. Do you have adequate space allocated to the Reserved LUN Pool? If this is the issue you would be able to confirm through the Navisphere Event Monitor.

The things that would lead me to look at storage first are entries like the disappearance of the:

2010-04-12 15:38:46.937 05368 verbose 'SanConfigManager' Adding datastore 'snap-0307ec41-OS_LUN_64_EXMS4-A' with MoId 'datastore-1237' and VMFS volume UUID '4bc32265-80d65abb-a810-001a64902d22' spanning 1 LUNs

2010-04-12 15:43:49.062 04228 verbose 'SanConfigManager' Noticed removal of datastore 'datastore' from datacenter 'datacenter-2'

2010-04-12 15:57:29.984 05368 info 'MainVcPM' Object being watched was destroyed: vm-1243

2010-04-12 15:57:30.171 04932 verbose 'ShadowVm.RepairShadow-Task' Error set to (vmodl.fault.ManagedObjectNotFound) {

11 dynamicType = ,

11 faultCause = (vmodl.MethodFault) null,

11 obj = 'vim.Datastore:datastore-1237',

11 msg = "The object has already been deleted or has not been completely created",

11 }

Tim Oudin

Tim Oudin
0 Kudos
glauk
Contributor
Contributor

Hello Tim

ok what should i do with Snapview . everything is OK with that, any advice

second that i want to clear that i have problems with issolated network that i dont know how to do. do you know how should i create that network.

0 Kudos
glauk
Contributor
Contributor

<![endif]><![if gte mso 9]>

Hello

The problem was solved. I saw in protected site need to have the same

configuration of snapview as recovery site. Also in recovery site I find that

placeholder of configurable files was marked with read question marks and I

change to different lun something else that was presented to blade server.

from that I don’t know the reason why the protected site need the snapview

the same as in recovery site.

glaukx

.

0 Kudos