Hi All,

I'm just getting familiar with SRM but not sure about what the journal is or does and the requirements.  We use Tintri storage and trying to decommission old EMC VNXs, so my question is do I need a traditional SAN to keep the SRM journal on?  Where does this even get configured in SRM?  We've just upgraded vsphere, esxi and SRM to 6.5.

Thanks,

Hi all,

I know that I can retrieve events when the last time is replication started and when finished but I would like to get info about configured RPO time per virtual machine. This can be seen on a slider in the SRM web console, but unable to find any PowerShell code which will retrieve this information. Any idea how to get configured RPO?

Hi All：

When install SRM version 8.2.0 and SRA(DELLEMC SC Storage) on Server 2019 host on both SRM site,

The SRM Web UI always appears ''failed to sync data on replica devices.SRA command 'syncOnce'failed.Unable to create a temporary file''

error message, we found that the "C:\Windows\Temp\vmware-SYSTEM"folders in the system will be automatically deleted , current workaround solution

must manual restart SRM service again and again , has anyone encountered a similar error?

Hello All,

We have a multiple clusters in our vCenter and we have same configurations at our DR site. Since we have configured SRM on both sides what is the best practice of creating placeholder Data-stores. It should be one per cluster or shared across all the clusters?

Thanks.

Masi.

I have a new vSphere 6.7u1 environment with the vCenter 6.7 appliances setup with embedded PSCs link, per the recommendations for a SSO environment with multiple vCenters. I then installed SRM 8.1.1 in Windows 2016 (firewall disabled). After running the setup of SRM and connect it to the vCenter PSC and vCenter, SRM is up and running but the client plugin for SRM is not installed in the Web Console of vCenter. I have checked the package directory on the appliance on the srm package directory was not created in /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity. It looks like the plugin was not pushed. Is this a known issue? is there a way to manually install the client plugin? Any clues?

Hi, following a failover from primary to secondary site there will be a requirement to failback.

The question i have is regards to 're-protect' - when clicking reprotect as well as creating placeholder VMs does it also replicate the entire VM from scratch OR only the changes whilst hosted at the secondary site.

In this situation Array Based storage is used and vSphere Replciation with SRM

thanks

I am moving my NSX-V over to NSX-T.   I have two sites, Site-A with a DVS and Site B with NVDS. When I move my VMs from Site-A to Site-B, IP customization works without issue. I then re-protect my workload and move the VMs from Site-B to Site-A.  The VMs get connected to the DVS on the correct portgroup but the recovery site will not process the ip customization.  When I go through the DR.LOG I have an error "Cannot resolve from recovery site a protected site Opaque Network by device backing info."

I have opened a ticket with VMware. Hopefully someone else had the issue can point me at a resolution before I hear back from VMware.  

Site Recovery manager : Version 8.2.0, Build 14761905

vCenter Version : 6.7 U3F

ESXi version: VMware ESXi, 6.5.0, 15256549

NSX-T : 2.5.1

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03696] [SRM@6876 sub=LocalSite.LocalVcServer.PCM tid=task-43820.VirtualMachineReconfigure] Starting destruction of filter 'sessionId[5293b]520b7acf-802d-74dd-5aea-11bd89792110'

2020-04-28T15:36:29.584-04:00 info vmware-dr[03696] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6:f61d:3c12] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg] DeployPackageJob succeeded for VM: 6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] 6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg succeeded for Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Retrieving network cards from VM Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Retrieved network cards from VM Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 warning vmware-dr[03688] [SRM@6876 sub=Replication.VmRecoveryInterface ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Protected site resolved device info is not found for NIC with key '4000'. Attempt best effort guess of the original protected site Network MoRef by the device backing info object.

2020-04-28T15:36:29.584-04:00 warning vmware-dr[03688] [SRM@6876 sub=Replication.VmRecoveryInterface ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Cannot resolve from recovery site a protected site Opaque Network by device backing info.

2020-04-28T15:36:29.584-04:00 error vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6]  Protected Network for VirtualEthernetCard :00:50:56:A4:5C:E6 is NULL, skipping this device

2020-04-28T15:36:29.584-04:00 info vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Skipping IP mapping based customization for VM Test250 [vm-2041]

2020-04-28T15:36:29.599-04:00 info vmware-dr[03844] [SRM@6876 sub=HostDomain ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Task 'Task-8773' has completed, tasks in queue 'TaskQueue-8768': 0

2020-04-28T15:36:29.599-04:00 verbose vmware-dr[03844] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.failoverOrchJob] IP customization succeeded for VM Test250 [vm-2041]

2020-04-28T15:36:29.599-04:00 verbose vmware-dr[03696] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.failoverOrchJob] VM Test250 [vm-2041]powerOnTimeout: 300,powerOnDelay: 0

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.masterPowerOn-protected-vm-122932] Initializing power on sequence for VM Test250 [vm-2041], powerOn: 1, # of pre/post callouts: 0/0, VM tools timeout (secs): 300, power on delay (secs): 0

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=PlaceholderVmManager ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Looking up the VM handler for '[dr.replication.ProtectedVm:0202eca5-a511-49e7-a185-d44bd62e352b:protected-vm-122932]' to get it's placeholder VM info.

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=PlaceholderVmManager ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Getting the PlaceholderVmInfo for placeholder VM '[vim.VirtualMachine:b36a38d5-940d-4e29-a584-e0a45def8825:vm-2041]' of '[dr.replication.ProtectedVm:0202eca5-a511-49e7-a185-d44bd62e352b:protected-vm-122932]'.

2020-04-28T15:36:29.615-04:00 info vmware-dr[03816] [SRM@6876 sub=HostDomain opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Starting task 'Task-8776', queue 'TaskQueue-8768' at: Dr::HostDomainImpl::EnqueueBootVmOrShutdownVmTask(3336)

Hi Community

I have a problem with a Vm replication on Site Recovery

I try quit,delete or reconfigure on my Site Recovery and I can´t, When I try reconfigure the replication show the following message

"Reverse replication configuration is not available. If you have forced the reverse replication to stop, you must also force the reverse replication to stop because it can no longer be used."

Or when I try Quit the Replication Show the Following

Thanks!!!!!!

Hello everyone,

i have end to setup the infrastructure with SRM and VReplicator. We have in sync different VMs without issues.

In the coming weeks our customer will want to do a real DR test with failover and failback (to do within the day).

We have tested the  SRM process with a single test VM and everythin worked well (planned migration, reprotection, 2nd planned and reprotection).

The only problem detected is the long time to do checksum for the reprotection. For the test VM it took 10-12 minutes; in this case it's no much time but for the real DR, we have 10 TB of data to move from Primary to DR Site; if the checksum time is directly proportional to the size of the data, to complete checksum we need some days and this mean that the production will stay on the DR site for some days.

To avoid this risk and issue, we have in mind to use SRM with the Test DR function.  Obviously we will have some manual activities to do but, when the test will be finished, we can clean the environment avoiding reprotect phase. Our idea is:

• power off on Primary Site
• run SRM Test DR
• change routing from Primary to DR site
• test access to DR test environement
• test environment form customer
• when the test will declared finsih cleanup Test DR
• change routing on Primary SIte
• power on Production VMs

What do you think about it? Is it feaseable? Have you some suggestion?

Thanks

Vincent

We use workbench 3.6 to run SRA certification

the first item: SetupNFSTests

Workbench show ERROR as follow:

Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'drTestClientManager' defined in URL [jar:file:/opt/vmware/VTAF/sra82-cert/VTAF/Test/SRM/SRA/srm82/lib/srmqa-main-main-SNAPSHOT.jar!/com/vmware/srm/core/test/base/DrTestClientManager.class]:
Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate[com.vmware.srm.core.test.base.DrTestClientManager]: Constructor threw exception; nested exception is java.lang.RuntimeException: com.vmware.srm.main.core.test.TestException: Error initializing CIS connection

Checking the limits on the webpage I need to understand the limit "Total number of replicated datastores (using array-based replication)=255 " since it's a low number. Is it per cluster? I think is more related to the number to the amount of datastores per virtual machine.

We have 2 infrastructures with vsphere 6.7 and SRM 8.1 and 8.2. We run SRM tests over 25 cluster, more than 500vm and 390 datastores replicated without issues or limit.
I need to understand how this limit operate in detail, since I cannot find information about this on the web.

Anybody have more information or knowledge about it?

Thanks in advance

Hi, we have two separate storage arrays configured in a cluster. I'd like to know can SRM accommodate this? Can we have a placeholder datastore for one array and a second placeholder datastore for another array in the same cluster?

Thanks in advance and regards

Steve

I dont see any way of pulling the devices tab details or information on the consistency groups directly from SRM powershell module. Is this even possible? im using version 8+ and EMC RP4VM.

Versions used

vSphere 6.7 U3e

SRM 8.2 appliance based

vSphere Replication appliance 8.2@

Issue - Reprotect task in SRM fails with errors below:

Recovery StepResultStep StartedStep CompletedExecution Time1. Restore protected site hosts from standbySuccess2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:26 (UTC 0)00:00:002. Configure storage to reverse directionError

             - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1. Protection Group XYZ

             - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1.1. Configure VR replicationError

             - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1.1.1. XYZError

             - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:03

Findings: The issue is seen when the vSAN health service (vmware-vsan-health) stops running at one site on the VCSA. A quick putty session to both VC and running the command control-service --status --all should show you if this service is running or in a stopped state. Then on the VC where it is in a stopped state run the command to start service-control --start -vmware-vsan-health.

Once the service is running, check the status of the vSphere replication and re-try the Reprotect task in SRM and it should start working.

Not sure if this related to the known issue with the vmware-vsan-health service on the VCSA 6.7U3e.

Cheers,

Onil Varghese

Hi,

we recently migrate from Windows SRM to appliance and since then we were not able to connect via powercli.

I know that the default port is now 443 and you have to specified that in the connection string but still no luck.

Here is my connection string :

Connect-SrmServer -SrmServerAddress 10.60.10.10 -port 443 -Credential $credential

Connect-SrmServer : Unable to connect to the remote server

At line:1 char:1

+ Connect-SrmServer -SrmServerAddress 10.60.10.10 -port 443 -Credentia ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Connect-SrmServer], VimException

    + FullyQualifiedErrorId : VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.VimException.VimException,VMware.VimAutomation.Srm.Commands.Commands.ConnectSr

   mServer

if i do a netstat right after the command i have this

C:\Users\Administrator>netstat -an | findstr "10.60.10.10"

  TCP    10.60.192.205:50191    10.60.10.10:443       ESTABLISHED

  TCP    10.60.192.205:50192    10.60.10.10:443       ESTABLISHED

Which tell that the communication is ok.

I also try this but no luck to find any solutions

PS C:\Users\Administrator> $exception = $error[0].Exception

$exception | select *

ErrorId           : ConnectServer_UnhandledException

ErrorCategory     : NotSpecified

TargetObject      :

RecommendedAction :

SessionId         :

ConnectionId      :

Severity          : Error

Message           : Unable to connect to the remote server

Data              : {}

InnerException    : System.NullReferenceException: Object reference not set to an instance of an object.

                       at VMware.VimAutomation.Srm.Impl.V1.SrmServerImpl.ConstructSrmServer(String srmServerId, SrmClient srmClient, String loggedInUser)

                       at VMware.VimAutomation.Srm.Impl.V1.SrmServiceImpl.ConnectSrm(SrmClientConnectAction connectAction, String hostName, Nullable`1

                    portOverride, String protocol, String username, CookieContainer cookieContainer, IServerCertificateValidationHandler

                    certificateValidationHandler)

                       at VMware.VimAutomation.Srm.Commands.Commands.ConnectSrmServer.<>c__DisplayClass57_0.<ProcessManualParamset>b__1(IServerCertificateVal

                    idationHandler certificateValidationHandler)

                       at VMware.VimAutomation.Srm.Commands.Commands.ConnectSrmServer.<>c__DisplayClass64_0.<ConnectCertificateValidationHandled>b__0()

TargetSite        : Void ConnectCertificateValidationHandled(System.Func`2[VMware.VimAutomation.Common.Interop.V1.Certificate.IServerCertificateValidationHan

                    dler,VMware.VimAutomation.Srm.Interop.V1.SrmServerInterop[]])

StackTrace        :    at VMware.VimAutomation.Srm.Commands.Commands.ConnectSrmServer.ConnectCertificateValidationHandled(Func`2 connectAction)

                       at VMware.VimAutomation.Sdk.Util10Ps.BaseCmdlet.ErrorCallbackCmdletBase.ProcessRecord()

                       at System.Management.Automation.CommandProcessor.ProcessRecord()

HelpLink          :

Source            : VMware.VimAutomation.Srm.Commands

HResult           : -2146232832

Also if i specified wrong credential i have the expected error message

Connect-SrmServer : Cannot complete login due to an incorrect user name or password.

anyone can help ?

Thanks

Can some one share me working script for SRM reporting where i can export

protection group, vm name, any error and last sync date and sync size.  is this correct what am trying. we do have 15 datacenter, i know that will take some time. So that is not an issue.

Hello Folks!!

We have replicated our Windows/Linux boxes with SRM/vSphere replication appliances. We are having another set of virtual Apps like Fortimanager/FortiAnalyzer virtual appliances. Can we replicate those with vRA/SRM?

Please let me know.

Thanks!

Hi All,

Need one help, I am trying to modify existing srm odbc dsn and want to point to the new dsn.

When running srm installer in "modify"  mode in database page all the options are greyed put except to type password.

How can we change it.

Hi,

What my understanding for the Failover  operation (Planned and Unplanned)  from VMware SRM is actually bringing up the VM to other  site. As the same is handled  at VMware SRM UI level individually with two different option.

--

Planned failover attempts to refresh  and sync the last pending delta  to Replicated site and performs operation.

Unplanned Failover is actually to recover VM at Target site from available replicated data.

--

As per SDK documentation, it details only one method to perform but there is no detail for separate option to perform Planned/unplanned Failover operation.

Method:

void start(RecoveryPlan.RecoveryMode mode, @version5 @optional RecoveryOptions options)

Please advise how to handle these individual actions from VMware SRM API.