Hi All,

I need some help on an approach for a new DR POD that we're standing up.

I currently have 2 sites Prod and DR that are using SRM 5.8.1. Satellite offices in the Prod VC fail into DR using Mirrorview.

I'm setting up a new DR POD (NW,SAN,Servers) to be shipped to a hosted DC and have created a new VMWare infrastructure to support it.

I now have to setup a parallel install to be used temporarily until the POD can be stood up at the hosted site. SAN has changed the replication mechanism to RecoverPoint under vSRM.

I'd ideally like to synch as much data as possible locallybefore shipment and stage the config

Has anyone done this before and have any guidance on the installation approach for theis new instance of SRM

Many Thanks any help would be appreciated,

DGN

Hi,

vCenter VCSA with external PSC (also appliance) 6.0.0 (build 4541948)

SRM 6.1.1 (build 4535903)

The same versions on both (protected and recovery) sites.

Recovery site uses VCSA with embedded PSC.

Additionally VMCA on PSC on protected site is configured as SubCA.

Site pairing task fails with status "Cannot complete login due to an incorrect user name or password" after 5 minutes from start. In vmware-dr... log I can see such messages:

...

2017-01-17T09:00:11.280+01:00 [03904 warning 'HmsProxy'] Dr::Providers::Hbr::HmsProxy::HmsServerMonitor::CheckRemotePair: Unable to find the remote site

2017-01-17T09:00:11.280+01:00 [03904 verbose 'HmsProxy'] Dr::Providers::Hbr::HmsProxy::HmsProxyImpl::SetRemoteInfoFailed: Unable to get remote HMS server info, error=

--> (dr.fault.RemoteSiteNotFound) {

-->    faultCause = (vmodl.MethodFault) null,

-->    msg = ""

--> }

...

2017-01-17T09:00:11.561+01:00 [04172 info 'LocalAuthzServer.PermissionSync' connID=sso-admin-7f6f] Received permission update for user 'VSPHERE.LOCAL\SRM-remote-dceaa31a-b2d2-4d84-a82d-1aa38db5d361' from SRM server.

2017-01-17T09:00:11.561+01:00 [03120 verbose 'AuthzStorageProvider'] [AuthzStorageProvider::WaitForUpdate] Got global permission update: current version: 4, new version 5

2017-01-17T09:00:11.561+01:00 [03904 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f] [PCM] Using token '4' for pending filter creation

2017-01-17T09:00:11.576+01:00 [04900 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f opID=15b10f9e] [PCM] Filter creation succeeded for filter token '4'

2017-01-17T09:00:11.576+01:00 [04900 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f opID=15b10f9e] [PCM] Recording new filter 'sessionId[52096]52793155-ce58-ccc2-a8d0-b554508aa053' for token '4' and connection version '1'

2017-01-17T09:00:11.576+01:00 [02900 info 'LocalAuthzServer.PermissionSync' connID=sso-admin-7f6f] Received permission update for user 'VSPHERE.LOCAL\SRM-remote-dceaa31a-b2d2-4d84-a82d-1aa38db5d361' from VC server.

2017-01-17T09:00:11.576+01:00 [04476 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f] [PCM] Destroying filter with filter token '4'

2017-01-17T09:00:11.576+01:00 [04476 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f] [PCM] Starting filter destruction of filter 'sessionId[52096]52793155-ce58-ccc2-a8d0-b554508aa053'

2017-01-17T09:00:11.576+01:00 [04476 info 'DrSiteUserManager' connID=sso-admin-7f6f] The task to assign default privileges for solution user 'SRM-remote-dceaa31a-b2d2-4d84-a82d-1aa38db5d361' for site 'dceaa31a-b2d2-4d84-a82d-1aa38db5d361' finished successfully.

2017-01-17T09:00:11.576+01:00 [03120 verbose 'AuthzStorageProvider'] [AuthzStorageProvider::GetGlobalPermissionUpdate] Get a new permission: DrServiceInstance:0:VSPHERE.LOCAL\SRM-remote-f4f96693-4630-482d-9252-0e41c5a2b5e3

2017-01-17T09:00:11.576+01:00 [02900 verbose 'LocalVcServer-PCM' connID=sso-admin-7f6f] [PCM] Destruction of filter 'sessionId[52096]52793155-ce58-ccc2-a8d0-b554508aa053' succeeded

2017-01-17T09:00:11.639+01:00 [04296 info 'Default'] W32Util_CreateOrReplaceAdminOnlyFile: deleting pre-existing file .\dceaa31a-b2d2-4d84-a82d-1aa38db5d361.p12.

[#1] -->

2017-01-17T09:00:11.639+01:00 [04296 info 'DrSiteUserManager'] Temporary certificate/key pair for solution user 'SRM-remote-0b265a6d-4e3e-43b0-aed9-35f6a9619816' at domain 'vsphere.local', LS++ site 'default-first-site', VC '0093BB51-B459-48E3-A010-36FB267D01B3' and SRM with id 'dceaa31a-b2d2-4d84-a82d-1aa38db5d361' promoted to permanent successfully.

2017-01-17T09:00:11.639+01:00 [03120 verbose 'UserDirectory'] [GetUserInfo] User not found: 'VSPHERE.LOCAL\SRM-remote-f4f96693-4630-482d-9252-0e41c5a2b5e3' isGroup=false

2017-01-17T09:00:11.639+01:00 [03120 warning 'AuthzStorageProvider'] [AuthzStorageProvider::SyncClientCache] ignore the exception for adding global permission for user class Vmacore::Authorize::AuthUserNotFoundException(User VSPHERE.LOCAL\SRM-remote-f4f96693-4630-482d-9252-0e41c5a2b5e3): VSPHERE.LOCAL\SRM-remote-f4f96693-4630-482d-9252-0e41c5a2b5e3

2017-01-17T09:00:11.639+01:00 [02884 verbose 'TaskQueue'] Created FIFO Task Queue.

2017-01-17T09:00:11.639+01:00 [02884 info 'DrTask'] Starting task 'dr.site.SiteManager.pairSrm1'

2017-01-17T09:00:11.639+01:00 [02884 verbose 'PropertyProvider'] RecordOp ASSIGN: info.progress, dr.site.SiteManager.pairSrm1. Applied change to temp map.

2017-01-17T09:00:11.639+01:00 [02736 verbose 'DrTask'] Starting VC task 'com.vmware.vcDr.dr.site.SiteManager.pairSrm'

2017-01-17T09:00:11.639+01:00 [02884 verbose 'DrSiteSiteManager'] Building a connection spec for the local services.

2017-01-17T09:00:11.654+01:00 [02884 info 'RemoteLkpServer' connID=c037] Starting persistent connection monitoring

2017-01-17T09:00:11.654+01:00 [02884 verbose 'RemoteLkpServer' connID=c037] The newly started persistent connection is still waiting to connect

2017-01-17T09:00:11.654+01:00 [02884 verbose 'RemoteLkpServer' connID=c037] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2017-01-17T09:00:11.654+01:00 [04476 verbose 'StubFactory' connID=c037] Event broadcasted

2017-01-17T09:00:11.670+01:00 [04792 verbose 'DrTask'] Created VC task 'com.vmware.vcDr.dr.site.SiteManager.pairSrm:task-8054'

2017-01-17T09:00:11.701+01:00 [03088 verbose 'RemoteLkpServer' connID=c037] Connect succeeded, new connection id="lkp-anonymous"

2017-01-17T09:00:11.701+01:00 [02212 verbose 'StubFactory' connID=c037 ctxID=7cca22] Event broadcasted

2017-01-17T09:00:11.701+01:00 [05060 verbose 'StubFactory' connID=c037] Event broadcasted

2017-01-17T09:00:11.701+01:00 [02212 verbose 'ServerSingletonCache' connID=c037 ctxID=7cca22] Event broadcasted

2017-01-17T09:00:11.701+01:00 [04792 info 'RemoteSsoServer' connID=sso-admin-b822 ctxID=7cca22] Dr::SsoPersistentConnection::SsoPersistentConnection: Created an SSO persistent connection.

2017-01-17T09:00:11.701+01:00 [04792 info 'RemoteVcServer' connID=vc-admin-acb2 ctxID=7cca22] Created VC persistent connection for an admin session.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'RemoteVcServer-PCM' connID=c037 ctxID=7cca22] [PCM] Initialized without an active connection

2017-01-17T09:00:11.701+01:00 [04792 verbose 'TaskQueue' connID=c037 ctxID=7cca22] Created FIFO Task Queue.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'VmDomain' connID=c037 ctxID=7cca22] Created a VmDomainImpl instance.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'TaskQueue' connID=c037 ctxID=7cca22] Created FIFO Task Queue.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'HostDomain' connID=c037 ctxID=7cca22] Initialized Task Queue Service.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'HostDomain' connID=c037 ctxID=7cca22] Initialized Task Queue Service.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'HostDomain' connID=c037 ctxID=7cca22] Initialized Task Queue Service.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'HostDomain' connID=c037 ctxID=7cca22] Created Host Domain.

2017-01-17T09:00:11.701+01:00 [04792 info 'RemoteAuthzServer' connID=authz-admin-43be ctxID=7cca22] Dr::AuthzPersistentConnection::AuthzPersistentConnection: Created an AuthZ persistent connection.

2017-01-17T09:00:11.701+01:00 [04792 info 'RemoteDrServer' connID=dr-admin-9301 ctxID=7cca22] Created DR persistent connection for solution user.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'RemoteDrServer-PCM' connID=c037 ctxID=7cca22] [PCM] Initialized without an active connection

2017-01-17T09:00:11.701+01:00 [04792 verbose 'TaskQueue' connID=c037 ctxID=7cca22] Created FIFO Task Queue.

2017-01-17T09:00:11.701+01:00 [04792 verbose 'PropertyProvider' connID=c037 ctxID=7cca22] RecordOp ASSIGN: info.progress, dr.site.SiteManager.pairSrm1. Applied change to temp map.

2017-01-17T09:00:11.763+01:00 [02212 verbose 'PropertyProvider' connID=c037] RecordOp ASSIGN: info.progress, dr.site.SiteManager.pairSrm1. Applied change to temp map.

2017-01-17T09:00:11.779+01:00 [04748 verbose 'PropertyProvider' connID=c037] RecordOp ASSIGN: info.progress, dr.site.SiteManager.pairSrm1. Applied change to temp map.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'SamlTokenFactory' connID=c037] Setting the connection reset functor.

2017-01-17T09:00:11.810+01:00 [02212 info 'RemoteSsoServer' connID=sso-admin-b822] Resetting the PersistentConnection

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteSsoServer' connID=sso-admin-b822] Installing new stub adapter factory into the PersistentConnection.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteSsoServer' connID=sso-admin-b822] Invoking StartInternalLocked

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteSsoServer' connID=sso-admin-b822] Starting connection monitoring.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteSsoServer' connID=sso-admin-b822] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2017-01-17T09:00:11.810+01:00 [02212 info 'RemoteVcServer' connID=vc-admin-acb2] Resetting the PersistentConnection

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteVcServer' connID=vc-admin-acb2] Installing new stub adapter factory into the PersistentConnection.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteVcServer' connID=vc-admin-acb2] Invoking StartInternalLocked

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteVcServer' connID=vc-admin-acb2] Starting connection monitoring.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteVcServer' connID=vc-admin-acb2] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2017-01-17T09:00:11.810+01:00 [02212 info 'RemoteAuthzServer' connID=authz-admin-43be] Resetting the PersistentConnection

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteAuthzServer' connID=authz-admin-43be] Installing new stub adapter factory into the PersistentConnection.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteAuthzServer' connID=authz-admin-43be] Invoking StartInternalLocked

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteAuthzServer' connID=authz-admin-43be] Starting connection monitoring.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteAuthzServer' connID=authz-admin-43be] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2017-01-17T09:00:11.810+01:00 [02212 info 'RemoteDrServer' connID=dr-admin-9301] Resetting the PersistentConnection

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteDrServer' connID=dr-admin-9301] Installing new stub adapter factory into the PersistentConnection.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteDrServer' connID=dr-admin-9301] Invoking StartInternalLocked

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteDrServer' connID=dr-admin-9301] Starting connection monitoring.

2017-01-17T09:00:11.810+01:00 [02212 verbose 'RemoteDrServer' connID=dr-admin-9301] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2017-01-17T09:00:11.810+01:00 [02212 verbose 'PropertyProvider' connID=c037] RecordOp ASSIGN: info.progress, dr.site.SiteManager.pairSrm1. Applied change to temp map.

2017-01-17T09:00:11.810+01:00 [02884 verbose 'RemoteSsoServer.ConnHandler' connID=sso-admin-b822] Connecting to SSO server.

2017-01-17T09:00:11.810+01:00 [04748 warning 'RemoteVcServer' connID=vc-admin-acb2] Failed to connect: std::exception 'class Vmacore::NotInitializedException' "Not initialized: VcConnectionHandler SSO"

2017-01-17T09:00:11.810+01:00 [03088 warning 'RemoteDrServer' connID=dr-admin-9301] Failed to connect: std::exception 'class Vmacore::NotInitializedException' "Not initialized: DrConnectionHandler SSO"

2017-01-17T09:00:11.810+01:00 [04476 warning 'RemoteAuthzServer' connID=authz-admin-43be] Failed to connect: std::exception 'class Vmacore::NotInitializedException' "Not initialized: AuthzConnectionHandler SSO"

2017-01-17T09:00:11.904+01:00 [04508 verbose 'SamlTokenFactory' connID=sso-admin-b822 ctxID=37acec3e] Setting signing certificates and broadcasting.

2017-01-17T09:00:11.904+01:00 [03088 trivia 'SsoClient'] opId=52411ecc-97b0-960a-cee6-885b11fbfab3 START operation SecurityTokenServiceImpl::AcquireTokenByCertificate

2017-01-17T09:00:11.904+01:00 [03088 trivia 'SsoClient'] Requested token with spec `TokenSpec [tokenLifetimeSec=28800, delegable=false, delegateTo=<unset>, renewable=false, confirmationType=0,audienceRestriction=, advice=[]'

2017-01-17T09:00:11.982+01:00 [03088 trivia 'SsoClient'] opId=52411ecc-97b0-960a-cee6-885b11fbfab3 END operation SecurityTokenServiceImpl::AcquireTokenByCertificate

2017-01-17T09:00:11.982+01:00 [03088 error 'RemoteSsoServer.ConnHandler'] `anonymous-namespace'::ConnectHandler::GetTokenComplete: Unable to retrieve token from SSO; no token. Exception:

--> Authentication failed: Invalid credentials

...

2017-01-17T09:05:11.829+01:00 [02736 error 'DrSiteSiteManager' connID=c037] Connection check to service of type com.vmware.cis.cs.identity failed:

--> std::exception 'class SsoClient::InvalidCredentialsException' "Authentication failed: Invalid credentials"

2017-01-17T09:05:11.829+01:00 [02736 error 'DrSiteSiteManager' connID=c037] Connection check to service of type com.vmware.cis.vcenterserver failed:

--> std::exception 'class Dr::TimeoutException' "Operation timed out after '300.000000' seconds"

2017-01-17T09:05:11.829+01:00 [02736 error 'DrSiteSiteManager' connID=c037] Connection check to service of type com.vmware.cis.cs.authorization failed:

--> std::exception 'class Dr::TimeoutException' "Operation timed out after '300.000000' seconds"

2017-01-17T09:05:11.829+01:00 [02736 error 'DrSiteSiteManager' connID=c037] Connection check to service of type com.vmware.dr.vcDr failed:

--> std::exception 'class Dr::TimeoutException' "Operation timed out after '300.000000' seconds"

2017-01-17T09:05:11.829+01:00 [02736 info 'RemoteLkpServer' connID=c037] Shutting down connection

Problem sent to VMware support. VMware recommendation is to reinstall vCenter/PSC on both sites.

No DNS resolution, static entries in hosts files on vCenter, PSC and SRM.

User account used for site pairing is member of SSO Administrators group on recovery site.

We bought an additional 75 pack license for SRM Std 6.1.1.  Gave us 2 packs of 75 licenses.  combined those into 1 key and added to vcenter and removed the others.  when trying to protect more than 75 vms, get an error that we are out of licenses.  have been working with vmware support to no avail.  have rebuilt everything in the environment and connected to existing vcenter db.  my guess is there is some entry in the db that is "stuck".  i've tried diffferent sized keys by splitting it up but no luck.

ideas?  any way to just use 2 different keys without combining into 1?

Dear All,

I have Main Production Site with IBM Flex blade servers (Intel Xeon Processor E5-2650 v2 8C 2.6GHz 20MB Cache 1866MHZ 95W Processor - all 16 blades are with same type of processor) and have Disaster Recovery Site with different type of Hardware (15 physical servers) with the below detail;

1. Dell PowerEdge m520 (Intel(R) Xeon(R) CPU E5-2470  @ 2.30GHz ) -  3 servers

2. Dell PowerEdge m520 (Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz  ) - 3 servers

3. Dell PowerEdge m520 (Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz) - 5 servers

4. Dell PowerEdge m600 (Intel(R) Xeon(R) CPU E5410 @ 2.33Hz) - 1 server

5. Dell PowerEdge m610 (Intel(R) Xeon(R) CPU x5560 @2.80Hz) - 3 servers

I want to install and configure VMWare vSphere 6.5 with SRM 6.5. Is it possible or no? Kindly guide.

Thanks in advance.

Hello,

I am using VMWare SRM API (VMware vCenter Site Recovery Manager 5.0) to query information about various objects including Protection Groups, Datastores, VMs, Recovery Plans etc.

There are ways to get more information for ProtectionGroups and RecoveryPlans via GetInfo() and  RecoveryPlanGetInfo() respectively. But how do I get this extended information (atleast the name) for other objects such as Datastores, VMs, etc.

Thanks,

Hemanth

Hello All

We had to re-ip our recovery site and now our protected site and recovery site can not talk.  Is there a way to log into the database on the protected site and change the IP address of the recovery site?

Or how do I force the SRM relationship to be broken so I can uninstall everything and reinstall from scratch?

thanks

ed !

Hi Team,

I am installing SRM for the first time and have few clarifications

1. In an environment with federated vCenter Single Sign-On domains, do not install Site Recovery Manager under more than one Platform Services Controller at the same time. What exactly does federated vCenter Single Sign-On domains means?
2. If I use the “vCenter Server with an embedded Platform Services Controller” at both sites. Can I use the  hostname of the vCenter server to Enter the address of the Platform Services Controller during the installation of  Site Recovery Manager Server
3. If I use the “vCenter Server with an embedded Platform Services Controller”  Is vCenter Server instance name same as its host name ?
4. Can I install the Site Recovery Manager enterprise in evaluation mode and configure SRM remote site? or License key is mandatory for  configuration? In SRM Document its mentioned “Site Recovery Manager Server requires a license key to operate. Install a Site Recovery Manager license key as soon as possible after you install Site Recovery Manager

Appreciate your answers

regards

Izhan

Boa noite Srs.

Estou tentando desmarcar um datastorage em um grupo de proteção, sempre que desmarco um os outros são desmarcados.

Hi all,

I have an environment with two sites A and B.  B is used almost exclusively for DR using SRM (other than a handful of service VMs).

This environment began life as vSphere 5.0 with one vCenter Server at each site, running both SRM and UM all on the same VM.  It is relatively small in terms of Host and VMs so this has worked well.

Late 2016 I upgraded to 5.5 and then on to 6.0 and obviously SRM was upgraded at the same time.  Again all working well apart from one small gripe I have and having read some of the new features from 6.5 etc I am now thinking about changing the deployment a little to work a bit better and be a little more streamlined.

Namely, site A and B have never been joined in link-mode so they need to be managed separately and of course, although the SRM nodes need to communicate they didn't necessarily need the vCenter Servers linked.

I would like to use the new 6.5 wizard to migrate vCenter and UM from the Windows Server to the appliance and based on the size of my environments everything embedded would be fine.  I don't think the Platform Module would need to be offloaded to its own appliance for example.

Finally my question.  What would be the best practice deployment and how best to migrate to this deployment?  i.e. Should I migrate to a single appliance at each site and configure enhanced linked mode?  If so, what are the steps for linking?  This I believe would result in a single appliance at each site for vCenter and UM using the embedded DB but we would be left with the Windows Server running SRM only.  I have found no evidence of SRM being available as an appliance or embedded into the vCenter/UM appliance so I'm assuming this has to be kept separate?

Kind regards all,

Ed Hazelden

Hi,

I checked the SRM API document https://www.vmware.com/support/developer/srm-api/srm_58_api.pdf

But I didn't find the API to create Recovery Plan on the SRM. Does any body know how to create it through API? Thanks a lot!

I have a few questions on setting up SRM to run a custom PowerCLI script during DR execution. Well more of a sanity check.

We have SRM configured between the Prod and DR site. In DR we use the hardware for testing so it is not sitting idle. What this means is there are copies of key systems running in the DR site isolated from the production network for doing testing with. They all are prefixed with SC_ in the name so they are easily identified.

To run a DR test we need to power down these systems before we bring up the actual recovered systems. We tried to use the Step to suspend VMs in the recovery site but that doesnt power them down, it suspends them. Last test we ran was the first time we tried to use that step. It took over an hour to 'suspend' the boxes. I did a little research and found some code to power down the VMs using PowerCLI. The script works fine when I just run it logged in as me. I have not had a chance to test it using SRM.

From what I have read I need to do the following to set this up:

1. Install PowerCLI on the SRM Servers. I actually installed PowerCLI on the 2 SRM servers and the 2 VC servers.
2. Put the script on the SRM Servers (mine is in C:\Scripts and is called SC_PowerDown.ps1)
3. Add a step to SRM to call the script using the below syntax.

     c:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe  C:\Scripts\SC_PowerDown.ps1

This step is inserted as Step 3 in the plan right before the now un-configured 'Suspend' step.

SC_PowerDown.ps1 conatins the following code:

."C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1"

connect-viserver DR-VC-Server

$vmservers=Get-VM -Name SC_* | Where-Object {$_.powerstate -eq ‘PoweredOn’}

$vmservers | select Name | export-csv c:\Scripts\DR-PWR-Off_Servers.csv -NoTypeInformation

$vmservers | Shutdown-VMGuest -Confirm:$false

My main questions are:

1. Does this look like it is configured correctly?
2. Do I need the first two lines of code to load 'Initalize-PowerCLIEnvironment.ps1' and 'connect-viserver' or does SRM assume that and does it automatically?
3. I have a script to power the SC_ Systems back on when the test is complete and wanted to insert it into the 'Clean up' steps but I can't edit that. How can I get that in there or do I need to run the power on script by hand once the cleanup process in SRM is complete?

Thank you for any assistance!

Mike...

Hi all,

I have been working on VMWare SRM for the past 1-2 months and I wanted to automate the entire SRM workflow.

I could not find any API/commandlets to create a new recovery plan. There is a mention of one of it in the SRM API guide. However, there are no examples and hence I am clueless.

Could any of you please help me in this regard?

Regards,

Praveen

I'm currently using SRM.  Other than vCloud Air, what cloud based solutions allow you to bring up your SRM protected VMs in their infrastructure in the event of a DR event?

Thanks!

I am adding an SRA from a new storage vendor so that I will have two SRAs for SRM.

Can I add datastores from the new storage vendor to the same protection group as datastores from the existing storage vendor?

Will recovery plans need to be updated for the new array's datastores to be replicated?

Thanks!

Hi Guy,

Can VMware SRM integrated with EMC RecoverPoint replication for storage arrays provide zero RPO? it can work well with EMC RecoverPoint replication for storage arrays that can provide real time replication?

any recommend between using SRM integrated with EMC RecoverPoint replication for storage arrays and EMC RecoverPoint for VM?

Thank you in advanced for all of your comment. all of your advice are valuable.

Vivath

Is it possible to have SRM 2 protection groups on the same VMware datastore?

Hi,

Any clue why the SRM trial download is not available anymore? Regards.

Can I have an SRM protection group that spans multiple datastores? 

I have a number of VMs with different relationships and startup order needs.  What dictates whether I need to put them in different protection groups, or put them in the same protection group but just modify the startup order within the protection group?

Hi all,

I have a client that wishes to upgrade their vSphere platform from 5.5 to 6.5 via a side-by-side migration.  To ensure as little production downtime as possible, ESXi 5.5 hosts will be disconnected from vCenter 5.5 and re-connected to the new vCenter 6.5 environment.  To accomplish this, all SAN LUNs, networks etc will be shared across all ESXi 5.5 and 6.5 hosts.

Part of this project will require the migration and upgrade of SRM to 6.5, however as the new vCenter 6.5 will be a new instance and not an upgrade I am not sure how the SRM migration should proceed.

The current SRM configuration is a fairly simple Prod/DR arrangement:

- Protected Site (Production)

- Recovery Site (DR)

- EMC FC storage

- Array replication and EMC SRDF's used.

The client wants to create a new SRM 6.5 instance in the new vCenter environment but I have concerns around having any kind of storage coexistence between the production SRM and new 6.5 SRM instances.  Is there any way to safely share LUNs/Datastores in a way that facilitates an easy SRM transition or will I be forced to uninstall/disable the original SRM environment before the new SRM 6.5 can be configured?

Cheers