All Posts

Hello, Trying to run the dr-ip-reporter command on an SRM appliance.  When I type the command the system returns "-bash: dr-ip-reporter: command not found".  If I attempt to run as sudo and enter th... See more...
Hello, Trying to run the dr-ip-reporter command on an SRM appliance.  When I type the command the system returns "-bash: dr-ip-reporter: command not found".  If I attempt to run as sudo and enter the admin password says the password is incorrect. Sadly Linux is just one more skill I have not mastered. What am I doing wrong? 
Thanks for the awesome response! I found it easier to get the pairingid like this: $pairingId = $pairings.List.pairingId.Guid   instead of: $pairingId = $srmConnection.ConnectedPairing.Pairing... See more...
Thanks for the awesome response! I found it easier to get the pairingid like this: $pairingId = $pairings.List.pairingId.Guid   instead of: $pairingId = $srmConnection.ConnectedPairing.PairingId After running the sample code you posted, I got a proper response.  $response = Invoke-RestMethod $recoveryStepsUrl -Method 'GET' -Headers $global:headers -SkipCertificateCheck PS /Users/username/Documents/VMwareAPI> $response list ---- {@{plan_callout_position_spec=; vm_callout_position_spec=; title=Synchronize storage; step_number=1.; child_count=6; depth=0; finish_time=; start_time=; expanded=False; id=4254; progress=0; status=INACTIVE; warnings=; errors=; referred_… I do hope they fix the issue with the PowerCLI cmdlets though.  This is a nice workaround. 
You can use the public VR REST API to create the script you are looking for. Check the API docs: https://developer.vmware.com/apis/vsphere-replication-api/latest/pairings/pairing_id/replications/... See more...
You can use the public VR REST API to create the script you are looking for. Check the API docs: https://developer.vmware.com/apis/vsphere-replication-api/latest/pairings/pairing_id/replications/get/
Hey, The Id is the correct field you should use when need to call object-related APIs (like recovery plans, protection groups, etc). Here I suspect there is some issue with the PowerCLI cmdlets and... See more...
Hey, The Id is the correct field you should use when need to call object-related APIs (like recovery plans, protection groups, etc). Here I suspect there is some issue with the PowerCLI cmdlets and the REST API itself. Until the problem is fixed, you can use PowerShell to communicate with this exact API endpoint. Here is a snippet: // Authenticate to the local site $srmConnection = Connect-SrmSdkServer -Server $srmLocalHostName `  -User $localVcUsername `  -Password $localVcPassword `  -RemoteUser $remoteVcUsername `  -RemotePassword $remoteVcPassword $pairings = Invoke-SrmGetPairings $pairingId = $srmConnection.ConnectedPairing.PairingId // Find the desired plan $plans = Invoke-SrmGetAllRecoveryPlans -pairingId $pairingId $plan = $plans.list | Where-Object { $_.Name -eq "PlanName1" } $planId = $plan.Id // Get the current API session $sessionId = $srmConnection.SessionId // And use it to construct request headers $global:headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]" $global:headers.Add("x-dr-session", $sessionId) $global:headers.Add("Content-Type", "application/json") // The view mode $viewMode = "test" // Construct the recovery steps URL $recoveryStepsUrl = $srmConnection.ServerUri.AbsoluteUri + "api/rest/srm/v2/pairings/${pairingId}/recovery-management/plans/${planId}/recovery-steps/${viewMode}" // Make the call $response = Invoke-RestMethod $recoveryStepsUrl -Method 'GET' -Headers $global:headers // $response will contain all recovery steps Some API examples using PowerShell and PowerCLI: https://github.com/vmware-samples/site-recovery-manager-rest-api-examples/tree/main/power-shell Hope this helps,  Zdravko Ivanov
I ran into a similar issue. Anyone within this community have any advice or insight? 
Dear VMware community I am currently exploring the VMware.Sdk.srm module to interact with the SRM REST API for a project involving disaster recovery and business continuity. While navigating this pr... See more...
Dear VMware community I am currently exploring the VMware.Sdk.srm module to interact with the SRM REST API for a project involving disaster recovery and business continuity. While navigating this process, I have encountered a question regarding the retrieval of the 'PlanId' value and the overall usage of this parameter in my scripting efforts. To provide context, I have outlined the steps I have taken so far: 1. I initiate my script by obtaining the pairing ID with the command: ```powershell $pairings = Invoke-SrmGetPairings ``` 2. Following this, I compile a list of recovery plans associated with the obtained pairing ID: ```powershell $plans = Invoke-SrmGetAllRecoveryPlans -pairingId $pairings.List.pairingid.guid ``` 3. From the list of recovery plans, I extract relevant information from a plan named 'PlanName1' using the following line of code: ```powershell $planid = $plans.list | Where-Object { $_.Name -eq "PlanName1" } ``` 4. My intention is to use the 'PlanId' I've gathered in the previous step to retrieve recovery steps for this particular plan. However, when executing the following command, I encounter an error: ```powershell Invoke-SrmGetRecoverySteps -PairingId $pairings.List.pairingid.guid -PlanId $planid.Id -ViewMode test The error looks like this: Invoke-SrmGetRecoverySteps: Error converting value {null} to type 'System.Int64'. Path 'list[0].start_time', line 1, position 213. ``` To clarify my query further, when I inspect the `$planid` variable, it provides the following details: ```powershell Status : READYSTATE Id : DrRecoveryRecoveryPlan:9fzzzzz-23zz-48zz-b2zz-bzzzzzzzzzz:4zzzzzzzz-7zzz-4zzz-9fzz-b7zzzzzzzzz ProtectedSiteName : vcenter1 RecoverySiteName : vcenter2 ProtectedVcGuid : 80zzzzz-95zz-4zzz-9zzzz-f4zzzzzzzz RecoveryVcGuid : 89zzzzz-69zz-4bzz-97zz-5zzzzzzzz Name : RecoveryPlan1 Description : Location : DrFolder:DrRecoveryRootFolder:442zzzzz-77zz-46zz-9fzz-bzzzzzzzz LocationName : Recovery Plans Progress : 0 IsRunning : False ``` In summary, I would greatly appreciate your assistance in clarifying whether the 'Id' property within the `$planid` variable contains the 'PlanId' I should be using in the `Invoke-SrmGetRecoverySteps` command.
Problem solved after I was installed everything from beginning with SRM and vSphere replication 8.6.
Hello to everyone, I have a problem with vSphere replication between two sites. On the primary site, vCentre was upgraded to version 7.03 and hosts were upgraded to the same version. On the DR site,... See more...
Hello to everyone, I have a problem with vSphere replication between two sites. On the primary site, vCentre was upgraded to version 7.03 and hosts were upgraded to the same version. On the DR site, vCentre was also upgraded to version 7, but the hosts remained on version 6.7 due to hardware incompatibility. After I add a new replication machine according to the DR site, I get the following error: A replication error occurred at the vSphere Replication Server for replication 'mymachine'. Details: 'Error for (diskId: "RDID-462aa3d2-cbc3-47a1-aa6a-324d5e5721f2"), (hostIP: "192.168.123.123"), (flags: on-disk-open, retriable): Fault: (vmodl.fault.InvalidRequest) { faultCause = (vmodl.MethodFault) null, faultMessage = <unset> msg = "Received SOAP response fault from [<SSL(<io_obj p:0x00007f5cc0004048, h:22, <TCP '192.168.123.124 : 34334'>, <TCP '192.168.123.123 : 80'>>), /sdk>]: fileManagement Unexpected element tag "mask" seen while parsing call information for method NfcFileManagement at line 10, column 0 while parsing SOAP body at line 9, column 0 while parsing SOAP envelope at line 2, column 0 while parsing HTTP request for method fileManagement on object of type vim.NfcService at line 1, column 0" }; Set error flag: retriable; Failed to get NFC system management ticket.; Can't get NFC ticket to establish session (target=); establish nfc connection on host-29; Tried operation 4 times, giving up.; Probing disk capacity.; While getting host capabilities for disk. (native snapshot hint = false); Failed to open disk, couldn't get disk type/capabilities; Set error flag: on-disk-open; Tried operation 4 times, giving up.; Failed to open replica (/vmfs/volumes/52d6e65e-8e968e30-a79d-40f2e92a7e02/mymachine/mymachine.vmdk); Failed to open activeDisk (GroupID=GID-9f254aac-357f-4fd4-ae27-2a5a5212835a) (DiskID=RDID-462aa3d2-cbc3-47a1-aa6a-324d5e5721f2); Can't create replica state (GroupID=GID-9f254aac-357f-4fd4-ae27-2a5a5212835a) (DiskID=RDID-462aa3d2-cbc3-47a1-aa6a-324d5e5721f2); Cannot activate group. Loading disks from database (GroupID=GID-9f254aac-357f-4fd4-ae27-2a5a5212835a) ; Connecting to group GID-9f254aac-357f-4fd4-ae27-2a5a5212835a'. 192.168.123.123 - this is IP address of my esxi host on dr site version esxi 6.7 192.168.123.124 - this is IP address of my vSphere replication server 8.7 on DR site I have enough space on storage. What could be the problem?    
we have very similar issue, SRM broken for entire organisation.  We downgraded SRM to our last version from a backup (8.5)  and got the same initiator errors.   "Failed to promote replica devices. F... See more...
we have very similar issue, SRM broken for entire organisation.  We downgraded SRM to our last version from a backup (8.5)  and got the same initiator errors.   "Failed to promote replica devices. Failed to promote replica consistency group '*****'. Skipping failover operation for device group '******' as initiators were missing for one or more hosts."   Whats weird is initial failover worked fine, run a failback and thats when we got above error.   Thats how its been since. Have a case running with vmware now who just seem to blame storage from SRM logs, but no changes have happened storage side to cause this.
Good night I have the following scenario to replicate some VMs: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + SRM 8.5 and VR 8.... See more...
Good night I have the following scenario to replicate some VMs: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + SRM 8.5 and VR 8.5. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. We have the scenario where we want to replicate some critical VMs that are in Site 1. This Site would be temporary. We have the SRM and vsphere Replication instances connected from Site 1 to Site 2. However, when we want to connect the SRM instances from Site 2 to Site 3, it does not allow it, it gives us an error indicating that the previous sites are already connected. Basically the plan consists of replicating some VMs from Site 1 to Site 2 and then to Site 3, where Site 3 would be our recovery site. Since Site 1 would be left out due to obsolescence issues. We want to validate if this idea is feasible, we would display: Site 1 (Temporary Production): vCenter 6.5 + SRM 8.4 and VR 8.4. Site 2 (Definitive Production): vCenter 7.0 + Two instances SRM 8.5 and VR 8.5. (Here you would have Two SRM instances and two vsphere Replication instances connected to a single vcenter instance.) Between Site 1 and Site 2 it will make the connection of sites between them. Here you would use the first instance of SRM and vsphere Replication belonging to Site 2. Between site 2 and Site 3 it would make a new site connection between them, here what it would do is make the second SRM instance and vsphere Replication point to Site 3. Site 3 (Recovery Site): vCenter 7.0 + SRM 8.5 and VR 8.5. Any comment or suggestion is very helpful. Thank you.
Hello everyone, Good day! I'm facing an issue now. My VM is currently in state of incomplete recovery and now the VM is down both PRD and DRC same goes with the datastore.
You can try the following steps. Check the logs: The first step is to look at the SRM logs for more information about the error. Logs often provide valuable clues as to what might be causing the p... See more...
You can try the following steps. Check the logs: The first step is to look at the SRM logs for more information about the error. Logs often provide valuable clues as to what might be causing the problem. Look for specific error messages that might indicate why the failback failed. Configuration Validation: Make sure that all required settings are correctly configured on the SRM. This includes connection details, networking, storage mapping, and so on. A repeated configuration can lead to failback issues. Connectivity test: Verify that there is proper connectivity between the primary and secondary sites. This includes checking network connectivity, firewall and DNS. Available resources: Make sure that the necessary resources, such as storage and compute resources, are available at the target site to accommodate the virtual machines you are trying to failback. Attempt to failback in smaller steps: If you are trying to failback multiple virtual machines, try to failback in smaller steps. This can help isolate specific issues. Updates and Patches: Make sure you are using the latest version of SRM and that all patches are applied. Known issues are sometimes fixed in updates. Technical Support: If you are unable to resolve the issue on your own, please do not hesitate to contact VMware technical support. They are experienced in dealing with a variety of issues and can provide personalized assistance. Backup: Before taking any more drastic action, back up your critical data. This is important to avoid losing data if something goes wrong during the troubleshooting process.
hello everyone, I would like someone to help me with a problem in SRM I am doing recovery tests for some VMS but when I move this machine from site A to Site B, everything works normally, after perf... See more...
hello everyone, I would like someone to help me with a problem in SRM I am doing recovery tests for some VMS but when I move this machine from site A to Site B, everything works normally, after performing the reprotection and wanting to return to site A, I am presented with the following error "no hosts with hardware version "11" and datastores "NAME_DATASTORE" are available that are powered on and not in maintenance mode"  Can someone help me with this problem and how to solve it? It happens to me with all the vms and backup groups, it always stays at step #13   Thank you very much in advance for everyone's help    
What was the error? I have this too...
Hello, I exported a list of outgoing replication vm list from gui export option that have column like  vm namr,status,RPO,Target,Replication Server,protection group.   Wanted to schedule this expo... See more...
Hello, I exported a list of outgoing replication vm list from gui export option that have column like  vm namr,status,RPO,Target,Replication Server,protection group.   Wanted to schedule this export from multiple vcenter so looking for script. Tried googling but unable to get right script.   Please help.   Thanks  
  • o
OK I've made progress... I unregistered my new appliances while the old ones were on. Turned those off. Re-registered the appliances and it's connect. I have one last problem...   Operation Failed ... See more...
OK I've made progress... I unregistered my new appliances while the old ones were on. Turned those off. Re-registered the appliances and it's connect. I have one last problem...   Operation Failed vSphere Replication Management Server could not establish connection to remote vSphere Replication Management Server at 'remoteVSRA:8043'.   I'm reading KB about it saying I need to get into the DB and clean it, but it's referencing MSSQL so I think that's an older one. I've unregistered everything so the new IP shouldn't matter I wouldn't think. Going to keep chasing it, but I've gotten over the biggest hurdle.  Edit: I rebooted the VSRA and it's looking better. Doing a test replication now to see what happens. Fingers crossed! 
I can't, they're all stuck. Delete is grayed out for VMs, protection groups and plans unfortunately. I'm thinking that since I installed 8.5.0 over top of 8.4 or whatever I had before it kept the dat... See more...
I can't, they're all stuck. Delete is grayed out for VMs, protection groups and plans unfortunately. I'm thinking that since I installed 8.5.0 over top of 8.4 or whatever I had before it kept the database in vCenter. 
Hi, do you have a timeframe on this fix? Thanks
i think you should remove any plans you have first. then remove any protection group. and then break the site pair to do a clean removal.