Received this error "Java 7 must be installed before installing EMC recoverpoint storage adapter" when installing EMC RP SRA 2.2.

Steps:

1) Installed Java 7.  Error still.

2) uninstalled java 6 and 7, reboot, reinstall 7 from java site.  Error still.

3) right click on RP SRA and install as admin.  Error still

4) Found SRA logfile in localsettings\temp\2\MSI673b8.log.  log file said it Looked for "HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment"  then a few lines later thew the error

5) checked registry... no HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment

6) installed jre-7u40-windows-x64.exe from IE

7) still no HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment

8) uninstalled java 7 and rebooted

9) right click on jre-7u40-windows-x64.exe and run as administrator.  Checked registry and had HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment this time

10) right click on RP SRA and install as admin.

8-10 is probably all that is needed.

Opened a ticket with EMC before I found the log file.  Still have not heard back but will let them know also.

Hopefully this helps

Cheers,

JBMORE

Hi,

I'm looking to deploy SRM for the first time.

In site A (3 hosts), I have a vSphere Essentials Plus licence kit that was purchased a while back, and I know that the vCenter Server 'Essentials' in that kit is compatible with SRM.

One of the 3 hosts in Site A is using one out the three vSphere Essentials Plus licences from the beforementioned kit.

The two other hosts are actually licenced with keys from separate licencing purchases (1x Enterprise, 1 Essentials Plus OEM)

I have 2 two hosts in site B, licenced with the remaining two Essentials Plus keys from my Essentials Plus kit.

I believe that for SRM to work, all I need now is a second vCenter Server instance for site B.

Can I just purchase a vSphere Essentials kit (it's cheap), and use the vCenter Server Essentials included in that kit?

I'm hoping to add my two hosts in site B to a new DR cluster that I create over on that site, using my new vCenter Server instance from the Essentials kit

Thanks for your help

Dear All,

We are having a XenDesktop 7.1 farm running on vsphere 5.1 U1 infrastructure. Setup has two desktop delivery controllers, two storefront servers, 1 netscaler. We have many dedicated desktops and Xenapp servers all booting from PXE and PVS.

We are planning to failover this entire setup to a DR site with vmware SRM. What are the considerations I should make in planning..

Thanks..

Hi guys,

We are in the process of implementing SRM for our DR.  We have our VM's being replicated to another location, and then SRM is changing the IP's on them.

We have a lot of web boxes that have two or three IP's assigned to them and both HTTP and HTTPs site bindings to these IP's for different web pages.

When we fail over, what is the best practice to change the site bindings?  I have two ideas that we have come up with:

1.  Add duplicate site binding for the secondary IP address into production.  These in theory should just sit unused until SRM activates the VM and switches to the new IP addresses.  I however can not find any articles backing this up.

2.  Use scripts to change the Site Bindings to the new ip's.  I got this working using appcmd to first delete the old site bindings and then add the new ones, however, when it adds the HTTPS binding it does not have a method that allows me to add the SSL cert.

Does anyone have experience with this or a best practice?

Much appreciated.

Hi all,

I have a problem with SRM. Initially, I have 2 vCenters, in Linked mode, with default SRM installation (1:1). After a long time, now, one of this two sites won't start the service. The SRM service starts and after a minute, stops.

In the log I see a lot of these:

015-01-20T13:30:53.532+01:00 [10772 verbose 'QsServerSingletonCache' connID=e09c] Dr::QsServerSingletonCache::SetContext: Setting context and broadcasting

2015-01-20T13:30:53.534+01:00 [03592 warning 'QsClient' connID=e09c] Got bad response. Code: 400, Message: Bad Request

2015-01-20T13:30:53.534+01:00 [03592 warning 'Default' connID=e09c] Closing Response processing in unexpected state: 3

2015-01-20T13:30:53.535+01:00 [03592 error 'LocalQS' connID=e09c] Exception while pinging QS server

--> std::exception 'class QsClient::ValidationException' "Bad Request"

2015-01-20T13:30:53.535+01:00 [03592 warning 'LocalQS' connID=e09c] Ping failed: std::exception 'class QsClient::ValidationException' "Bad Request"

2015-01-20T13:30:53.535+01:00 [03592 info 'QsServerSingletonCache' connID=e09c] Dr::QsServerSingletonCache::SetContext: Lost connection, resetting connection context

2015-01-20T13:30:53.535+01:00 [03592 verbose 'LocalQS' connID=e09c] Attempting to connect

2015-01-20T13:30:53.541+01:00 [10372 info 'Default' opID=6b661b6d] CoreDump: Writing minidump

2015-01-20T13:30:53.587+01:00 [10800 info 'Default'] CoreDump: Writing minidump

2015-01-20T13:30:54.568+01:00 [10772 verbose 'LocalQS' connID=e09c] Connect succeeded, new session id=""

2015-01-20T13:30:54.569+01:00 [10772 verbose 'LocalQS' connID=e09c] Posting event to VC: (dr.eventEx.LocalQsConnectionUpEvent) {

-->    dynamicType = <unset>,

--> }

Any idea? I have tried the dejoin and rejoin of the 2 vCenters, but nothing changes.

thank you very much,

Matrix

Hi all,

We have dual dc setup same setup both side

HP 3PAR - 7200

VSphere 5.5

SRM 5.5 (win2012)

3par SRA

Now 3par is configured all looking fine , replication also no errors seen , but when setup the protection groups the same is listed twice.

When selecting the datastore the vms inside are only listed once , so OK

Should i be worried  about this?

Thanks

Hi all,

Environment :

Windows Server 2012 r2 (SRM server for both production and dr site)

vCenter virtual appliance 5.5 (both production and dr site)

Site Recovery Manager 5.5 (Success installed on dr site but failed in production site)

MSSQL 2008 r2 express (installed on the same servers of SRM)

I have success to install the SRM on DR site but failed in production, and below are the SRM installation logs from production site, it seems the SRM cannot get the VC version from the SQL statement and the ODBC source already tested and success. The SRM installation will rollback when almost done. Any advices for this? Thanks

Section for VMware vCenter Site Recovery Manager, pid=2016, version=5.5.0, build=1315893, option=Release

2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Logging uses fast path: false

2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Handling bora/lib logs with VmaCore facilities

2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Initialized channel manager

2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Current working directory: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin

2015-01-22T10:38:45.160+08:00 [02168 verbose 'Default'] Setting COM threading model to MTA

2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] ThreadPool windowsStackImmediateCommit = true

2015-01-22T10:38:45.160+08:00 [02168 info 'ThreadPool'] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 401, 2, 200, 2147483647

2015-01-22T10:38:45.160+08:00 [02168 info 'ThreadPool'] Thread enlisted

2015-01-22T10:38:45.176+08:00 [01836 info 'ThreadPool'] Thread enlisted

2015-01-22T10:38:45.191+08:00 [02476 info 'ThreadPool'] Thread enlisted

2015-01-22T10:38:45.191+08:00 [01956 info 'ThreadPool'] Thread enlisted

2015-01-22T10:38:45.191+08:00 [00620 info 'ThreadPool'] Thread enlisted

2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute - SQL execution failed: SELECT * FROM VPX_VERSION

2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute -    Bind parameters:

2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute - ODBC Error: "ODBC error: (42S02) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'VPX_VERSION'." is returned when executing SQL statement "SELECT * FROM VPX_VERSION"

2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Backtrace:

--> backtrace[00] rip 00007fff4b5aa04a

--> backtrace[01] rip 00007fff4b46f51f

--> backtrace[02] rip 00007fff4b4706be

--> backtrace[03] rip 0000000000187140

--> backtrace[04] rip 000000000018733c

--> backtrace[05] rip 0000000140005d6d

--> backtrace[06] rip 0000000140007a3c

--> backtrace[07] rip 0000000140008019

--> backtrace[08] rip 000000014000f322

--> backtrace[09] rip 00007fff608113d2

--> backtrace[10] rip 00007fff60f903c4

-->

2015-01-22T10:38:45.238+08:00 [02168 error 'Vdb'] VdbStatement::Execute(): Failed: "ODBC error: (42S02) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'VPX_VERSION'." is returned when executing SQL statement "SELECT * FROM VPX_VERSION"

2015-01-22T10:38:45.254+08:00 [00620 info 'ThreadPool'] Thread delisted

2015-01-22T10:38:45.254+08:00 [01956 info 'ThreadPool'] Thread delisted

2015-01-22T10:38:45.254+08:00 [02476 info 'ThreadPool'] Thread delisted

2015-01-22T10:38:45.269+08:00 [01836 info 'ThreadPool'] Thread delisted

We are setting up srm for the first time and ran into a problem. We have a dc running at the recovery site online and on a 10.110.12 network.  This dc replicates to the remainder of the dc at the customer sites. All the vms that are included in the srm test will start with a 10.110.10 ip address in the primary site and failover. I have the recovery plan setup to change this ip to match the dc at the recovery location which would be 10.110.12 ip space.  All the primary vms will failover and poibt to the recovery dc as there dns in the srm config. 

When running a test for the first time yesterday, everything worked for the most part in the plan and the vms failed over but.....

Then the customer reported dns issues. We found out that the recovery vms came up online talked to the dc in the Dr location and then went out and replicated to the other dcs in the organization. Resulting in changing the ips to the new recovery side everywhere in dns. Changed from 10.110.10 then to the new ones that came online 10.110.12.

Srm was cleaned up and then the customer manually corrected the ips back to the correct ips. Major issues...

My question is who has done this srm testing with a live dc at the recovery location before? Does anyone have a workaround to PREVENT the replication?

-Turn off the recovery side dc before the test?

-Remove the dns entry in all of the vms failing over in the test?

Please let me know your thoughts.

thanks

J

I have a problem, my remote site does not have the same IP scheme as we do in the protected site.  So during the recovery plan I have a manual step where I ask my network admins to change the DNS record to point to the proper ip for the remote site.  In order to make sure IPs don't get used I have devised a plan that the server dns will actually be "servername-protected", and a cname "servername" will point to the "servername-protected" dns entry.  When we want to failover we repoint the cname to the dns entry for "servername-remote". 

This way everyone can always point to the cname entry "servername", but this is manual.  Anyone have a good scripted way to do this....also we are using infoblox for ip address management.  Thanks in advance

I wanted to expand a virtual disk attached to a guest and needed to remove replication before doing this.  When I removed the replication I got an error and not my replication for that VM are in an inconsistent state.  When I removed the replication I got two tasks.  The first, "Unconfigure virtual machine..." completed okay.  The second, "Disable replication of virtual..." failed with the error "A general system error occurred: The system returned an error. Communication with the virtual machine might have been interrupted."

The VM now seems to be in an inconsistent replication state.  The replicated VM still exists on the target machine but does not show up on the list of VM's being replicated.  Attempts to increase the disk size of the VM on the source host result in the error, "vSphere Replication does not support changing the length of a replicated disk" which makes me think that something didn't get unconfigured when the original error occurred.  To further confirm my suspicion, when I attempt to configure replication for the VM I get all the way to "Finish" and then get the error "Configuring Virtual Machine for Replication... failed.  The vSphere Replication configuration of the virtual machine has an issue: Replication is already enabled."

I did run a vim-vmd hbrsvc/vmreplica.getState from the console on the source host and got the following:

This was not how I planned my Friday, has anyone seen anything like this?

Thanks for any assistance

Raymond

Another group in my company is interested in sharing my SRM recovery site. I'm investigating ways to minimize the access SRM needs in addition to the user roles.

THe documentation seems to indicate that the account needed to connect the two sites needs admin access (Which I'm trying to avvoid).

DOed anyone have any experience with implementing a minimum permission set for shared recovery sites?

Good Day,

If we migrate VMs using SRM to a second DC will the MAC address for each VM change?

Thank you,

p.s any links to KB articles is appreciate it as well.

This might be really stooooopid but...

I have registered for the Eval, on the license and downloads tab, all I see is the replication adapters for download?

If I go to manually download SRM from the main Downloads section, it is grayed out saying I am not allowed to and I need to register...which I already have!?

What am I missing? lol

Cheers,

Bilal

Hi All,

I have made a SRM Lab, which following configuration

• Protected Site:
  • DC (2012 R2) - Primary DC
  • VC01 (2012 R2) - First vCenter (with Linked Mode)
  • SQL01 (2012 R2 / SQL 2012 Express) - Store SRM01 Database
  • SRM01 (2012 R2 / Version 5.8)
  • CMC (2012 R2 / HP StoreVirtual CMC 11.5) - Deploy VSA01
  • VSA01 - Deployed from CMC
• Recovery Site
  • ADC (2012 R2) - Additional DC
  • VC02 (2012 R2) - Second vCenter (with Linked Mode)
  • SQL02 (2012 R2 / SQL 2012 Express) - Store SRM02 Database
  • SRM02 (2012 R2 / Version 5.8)
  • VSA02 - Deployed from CMC

This lab was configured on Array Replication with HP VSA.

After finishes configuration, I started to test recovery plan, it's work fine

Then i try to test Recovery mode, still fine. Then i do reportect, still fine. at this time, protected site is recovery site & recovery site is protected site

So that i have to do a failback to switch everything to original state (before recovery), now i got the problem like html file that i attached.

Did i miss anything in my configuration? i have tried to edit StorageProvider from some recommends on VMware community with no luck

The host 9 & 11 still see the device, but only 9 can mount the VSA datastore, 11 cannot

Hello,

Is it possible to use SRM with SDRS?  We actually use SRM 5 (we plan to upgrade to 5.8 in a near futur).  We would like to implement SDRS on our protected site and I was asking myself how SRM could work with SDRS.

We use a NetApp SAN with SRA.

Thank you.

Hi gurus

  When I tried to break pair with my DR site I get the following error

"SRM server 'VCENTER server' cannot do a pair operation. The reason is: Cannot break a connection while protection groups, array pairs, or folders exist."

I have checked all my tab and they are empty, I have nothing on ,Mapping,folder,

can someone help please??

Thanks a bunch

Error - Timed out waiting for Customization scripts to complete in 600 seconds. IP settings may have been partially applied.

When we ran Test DR in VMware SRM, few VM did not automatically picked up IP address despite of having all configuration(i;e VMtool, ESXi build version, time out value) same with other VMs.

We found that Disabling LMHOSTS Lookup fixed the issue. (Network Properties>>IPv4 >>Advance>>>WINS>>>Unchecked LMHOSTS Lookup).

My Query is: Can anyone suggest the reason why it did not took IP while LMHOSTS lookup was enabled on VMs?

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!

In my lab I have the following configuration and can not get any vSphere Replication options to be available within SRM.  Only array based replication is an option.  I've looked and looked for a solution and have tried everything I could think of to get the options to show up and I've had no luck so far.

vcenter1 - 5.5 U2 windows install

esxi1 - 5.5

SRM1 - SRM 5.8.0.1 (install file 5.8.0-2336305)

vR1 - vSphere Replication 5.8.0.1

vcenter2 - 5.5 U2 windows install

esxi2 - 5.5

SRM2 - SRM 5.8.0.1 (install file 5.8.0-2336305)

vR2 - vSphere Replication 5.8.0.1

I started off my lab tests by deploying the lefthand VSA with SRM.  I'm now moving onto using SRM with vSphere replication.  The steps I've taken since the lefthand testing:

Removed Lefthand VSA appliances

Uninstalled SRM and selected to remove the database contents also

Confirmed SRM does not show up in the Web Client any more

Installed vSphere Replication at both sites and configured replication for 1 VM - Replication is complete

Installed SRM on the same servers as before and setup pairing

Walking thought the SRM setup theres no mention and no option of vSphere Replication.  Theres also no mention of any SRM integration when in the vSphere Replication interface.  Now, I remember deploying the same setup in 5.1 which gave the options to deploy vR within SRM but that was then.  Now, from what the documentation says, you're supposed to first deploy vR, set that up, then deploy SRM.  SRM will then detect vR during the install, and I guess in theory, display those options. I've checked permissions and everything looks right.  My lab account is the account I'm using to register and install everything.  SRM pairs fine, vR replications, they just don't know they can work together.  I even reinstalled SRM a second time and confirmed the install files were correct on the interop matrix and everything looks good.  SRM just acts like theres nothing but array replication options.  I'm thinking theres a special version of SRM or vSphere Replication thats required to get the two to work together, but I can't find any documentation on it. 

Please help.  Thanks!

Joe

Hi Everyone,

When i logged into my web client today and try to add a new server to the protection group i was unable to do so, the option was greyed out and i received the error message saying session already logged in.

When i click on manage under my protected site and try to go to any of the binding tabs is shows unable to retrieve mappings,session already logged in. I have restarted the services on both SRM servers and still unable to start a recovery or edit the protection group.

The only thing i haven't tried to do is restart the vCenter for both sites. I have logged off and logged back on and still says session already logged in. Please advise if there is a another way to kill the session.

Regards

Kaylin