I am getting error with Nimble SRA on SRM 6.0 which  works with old SRM releases e.g SRM 5.5/5.1/5.0 etc.

Its looks like the package Try/Tiny.pm has been removed from Perl lib.

Here is the error message :

Internal error: Can't locate Try/Tiny.pm in @INC (@INC contains: C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/modules

C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage

C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/DateTime

C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Params-Validate C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Params-Classify C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Module-Runtime C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Module-Implementation C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/DateTime-TimeZone C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/DateTime-Locale C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty C:/Program Files/VMware/VMware vCenter Site Recovery Manager/external/perl/site/lib C:/Program Files/VMware/VMware vCenter Site Recovery Manager/external/perl/lib .) at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Module-Implementation/Module/Implementation.pm line 10, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Module-Implementation/Module/Implementation.pm line 10, <DATA> line 584.

Compilation failed in require at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Params-Validate/Params/Validate.pm line 11, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/thirdparty/Params-Validate/Params/Validate.pm line 11, <DATA> line 584.

Compilation failed in require at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/NimbleStorage/WS/ApiLibrary.pm line 17, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/NimbleStorage/WS/ApiLibrary.pm line 17, <DATA> line 584.

Compilation failed in require at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/RESTv1/NsSDK.pm line 20, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/RESTv1/NsSDK.pm line 20, <DATA> line 584.

Compilation failed in require at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/RESTv1/NsSraServiceRESTAPI.pm line 19, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/RESTv1/NsSraServiceRESTAPI.pm line 19, <DATA> line 584.

Compilation failed in require at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/HandleProtocolRequest.pm line 24, <DATA> line 584.

BEGIN failed--compilation aborted at C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/Nimble Storage/HandleProtocolRequest.pm line 24, <DATA> line 584.

Compilation failed in require at C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\Nimble Storage\command.pl line 45, <DATA> line 584.

BEGIN failed--compilation aborted at C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\Nimble Storage\command.pl line 45, <DATA> line 584

Hi, guys!

I'm trying to add an ArrayManager to SRM 6.0 and I'm getting the error:

"SRA command 'discoverArrays' failed.

Cause:

Failed opening session for user to site mgmt IP.

Please see server logs for further details."

My environment is:

Protected Site

            RecoverPoint MGMT: x.x.x.22

            RPA1: x.x.x.23

            RPA2: x.x.x.24

            RPA3: x.x.x.25

Recovery Site

                RecoverPoint MGMT: x.x.x.1

              RPA1: x.x.x.2

                RPA2: x.x.x.3

                RPA3: x.x.x.4

- At Recovery Site I can add the ArrayManager based on any recover Point IP address (listed above)

- At Protected Site I can add the ArrayManager pointing only for x.x.x.25 (RPA3), for the 3 others receive that error.

- If I add both arrays (based on x.x.x.25 IP address) I can enable the ArrayPair, but I can't create any ProtectionGroup, because the arrayPair is grayed.

I already tried  configure SRA HTTPs, using c:\Program Files\VMware\VMware vCenter Site Recovery Manager\external\perl\bin\perl.exe” command.pl –useHttps true , and it does not work.

Products Version:

EMC RecoverPoint 4.1

SRM 6.0

vCenter 6.0

SRA 2.2.0.3

tks

Hi All--

I was applying a set of host profiles today and it was flagging an invalid setting "VMFS.UnresolbedVolumeLiveCheck" - after a bit of troubleshooting I noticed on handful of hosts this setting is set to true and the other portion is set to false.  The only common denominator of the hosts that had this setting set to false was they were manipulated by SRM at any given time during testing and failover testing. 

My question, is there any harm in leaving this set to disabled, and also can one confirm that SRM is making this change during a recovery plan test?  Also any documentation on what is doing under the hood would be greatly appreciated if it exists.  Thanks very much in advance.

We are running vCenter and vsphere 6 and SRM 6. We are trying to add a vm to vsphere replication, but it fails with

Unable to configure replication for virtual machine 'vm1' because group 'vm1' cannot be created. Another virtual machine 'vm1' that has the same instance UUID '5032d989-816a-8330-4eac-8782df227fd0' already exists on protection site 'vcenter

I have verified that the vm uuid does not match the one in the error message. I also verified the vm does not exist in vSphere replication or SRM in the primary or the recovey site. Any help would be great.

Ed

Hi,

We've got an issue with a SRM Recovery Plan we have just created where during a Test it will not proceed past the first step of Sychronizing the Storage. It fails every time with a message "Failed to sync data on replica consistency group '15725743990x72092424a3e5e3a' Failed to create snapshot".

I've tried everything i can think of including destroying the consistency group and all the actual TDEV's involved. All the recovery plans and protection groups in SRM were removed as well. And i basically started from scratch comparing it to another existing group and SRM Protection group/Recovery Plan and it still fails with this error.

I've done tests with Recover Point when this particular consistency group is not under SRM control and replication seems to work fine. The datastores in the Protected site automatically mount and i can browse them when i enable image access. So i am happy that the basics of RecoverPoint are working and think this is something within the SRM/SRA configuration. But since i am learning SRM as i go i am not 100% confident of that fact.

Don't know if it makes any difference but normally the LUN's in the protected site are visible to the ESX if i look under Configuration->Storage->Devices on any of the hosts, but they are not mounted. If i test image access in RecoverPoint when the consistency group is not under SRM control it automatically mount the LUN's which i assume is the same way SRM would work? Or would you expect that the LUN's in the protected site are mounted as datastores all the time?

I've logged a call with EMC but if anyone has any thoughts/ideas on what could be causing this i would welcome them.

Thanks

Hi

We have two vSphere 5.5 datacenters. Both have a vCenter 5.5 instance with SSO in multisite. Main reason for multisite SSO  is to be able to use linked mode.

When using Site Recovery Manager 5.8 in a  multisite SSO deployment there is an issue. Execution of a recovery plan is not possible when the SSO instance at the protected site is unavailable!

Basically this makes SRM unuseable! We want to be able to use SRM when the protected site is unavailable.

One of the options to solve this is re-installing vCenter / SSO  in standalone mode.

Anyone has experience in converting SSO from multisite to standalone?

Is it possible to just reinstall vCenter /SSO  in the recovery site in standalone mode, and keep vCenter and SSO in the protected site as multisite?

An alternative is to upgrade to vCenter Server 6.0. I understand the PSC does not have the issue of being dependant on the SSO instance in the protected side.

thanks for your help!

Dear all, is it possible to SRM protection of a Production DC to two Recovery Site? for example, Site DC is Data-center Site which need to be protected by SRM.

NDC is Near data-center and DR is Disaster Recovery site.

When DC is down, NDC SRM is the first protected site SRM. If both DC and NDC is down. DR is the last SRM protected site.

If not, is it possible for DC and NDC can be protected by SRM on one single site to DR by SRM?

Please any suggestion will very much helpful.

Thank you.

Hi

Currently we have SRM setup and configure and it works when we do the test.

Our management would like to see it work, were they are able to log on to the servers and work.

My question is our network is mapped to 3 network adapters 1 for Management 1 for the servers and 1 for Vmotion.

If I moved the 1 for servers to a separate switch not connected to any network and plug a laptop running a copy of our domain controller can I do a test failover while the live site is running and connect via the laptop to the DR servers and test. I have done this on a small lab and it worked but I would like to confirm this before we test it the servers is running our ERP system and I don't want to mess up anything.

Hi,

I have a single vCenter 5.5 server covering my Prod and DR sites and looking to deploy SRM 5.8. I know that I could just deploy additional vCenter server and have my DR hosts being managed by the additional vCenter but what about Linked Mode and having both "under one roof" type of setup? Linked mode scenario is possible but are there any pitfalls I need to be aware of? Is Linked Mode what people are going for when it comes to SRM and multiple sites?

What I would like to ideally avoid is to have two separate instances of vCenter managing 50% of my estate each.

Would appreciate any input/feedback so fire away if you can help.

cheers,

Adrian

Hello,

I have a single platform services controller called psc.itdemoguy.ca and two vCenters called vcprod1.itdemoguy.ca and drvc1.itdemoguy.ca.  I have a single SSO domain called itdemoguy.local.  Both vCenters have been added as target sites for each other, VR appliances have been deployed and configured, and I have some VMs being replicated across the sites.

I am getting the attached error attempting to install SRM immediately after entering the information for my platform services controller.  I suspect that this error is due to the fact that I have two vCenters connecting to a single Platform Services controller, however I believe this configuration is a supported practice.

Any suggestions as to what I could try?

Thanks.

Hey Guys,

We're using SRM with Hitachi SRA, we have several protection groups with recovery plans associated with them.

Now when I test one my Recovery Plans, I'm getting the following warning:

The host that is presented in the warning is not related to the protection group in any way. We have a protection group for each cluster, and the host in warning is from another cluster.
I've check if this host have virtual machine files on the datastores i'm recovering, but it doesn't. Why SRM cares that the this particular server can't see the datastores. Expect that warning the recovery test work relatively smooth.

Any Idea?

Dan.

Hey again,

Another SRM question. While testing a recovery plan i'm getting the following error:

Error - No hosts with hardware version '9' and datastore(s) snap-xxxxxx which are powered on and not in maintenance mode are available

I'm getting it on a template! all host in the recovery site are hardware version 9 and the snapshot are being exposed on the recovery site as it should.
Other virtual machines that reside on the same datastore are being recovered properly

Any Ideas?

Dan.

Hi

I have stopped replication for a VM on vSphere 5.5 environment, when i try to configure the replication again, i get this error below:

I have followed the following VMWare KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2065033

when I try to access VRMS 5.8.1.0 MOB URL: https://IP_address_of_primnary_VRM_server:8043/mob/?moid=GID ??? ... with my parameters i get nothing

Please Advise

regards.

Hi everyone,

I'm having issues with this SRA version 2.1! The installation went just fine on both sites. Pairing and mapping is functional between two VCenters.

I have VCenter 5.1, SRM 5.1 running together on a W2K8 R2 on both sites.

After the SRA installation, i tried to "Add Array Manager" on VSphere Client SRM GUI, and i got the error: "Unable to find any array script (SRA) files. You must install SRAs before adding an array manager"

If i try to "Rescan SRAs" i have this error message: "Failed to load SRA from 'E:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/array-type-recoverpoint'. SRA command 'queryInfo' didn't return a response"

Tried to restart/reinstall several times, but it didn't work!

I have exactly the same symptoms on both SRM servers!

Did anyone face this problem?

Thank you

We're install UCS (Flexpod) systems to replace the existing Dell/NetApp solution we have. I'm looking around and have not been able to find a document that indicates if I'll be able to fail-over my current non-UCS (no VM-FEX) VMs into the new UCS stack that we're going to be running VM-FEX on. Both sides using iSCSI...not even sure that matters.

New UCS

UCSM 2.2(1)

C-Series UCS Servers

vCenter 6

ESXi 6

SRM 6

Existing Stacks

Dell R910s

EqualLogic 10Gb CNAs

Nexus 5020s

NetApp 3270

Hi,

I am hoping someone can help as I am struggling to run a Test Recovery in SRM4 with NetApp, there seems to be very little online and in the community which relates to the errors I am getting so I am hoping someone may have come across this before and offer some advice.

At exactly 5:00 mins (300 seconds) into trying to recover a VM I receive the error "A general system error occurred: Unexpected optional not set: vim.VirtualMachine:vm-6874.config"

Below is a extract from the report and further below a copy from the log which I think points to the error, I appreciate any help.

So far I have deleted the protection group\recovery group and recreated, and extended any timeout settings I can see in the Advanced settings.

1. Shutdown Protected Virtual Machines at Protected Site "Site Recovery for GH-WH"  

    1.1. Shutdown Low Priority Protected Virtual Machines  

    1.2. Shutdown Normal Priority Protected Virtual Machines  

        1.2.1. Shutdown Protected Site VM "Test_VM"  

            1.2.1.1. Shutdown Guest OS for Remote VM "Test_VM"  

            1.2.1.2. Wait for Guest OS Shutdown  

            1.2.1.3. Power off VM "Test_VM"  

    1.3. Shutdown High Priority Protected Virtual Machines  

2. Prepare Storage Success 00:46:27

    2.1. Attach Disks for Protection Group "Test" Success 00:46:26

3. Suspend Non-critical Virtual Machines Success 00:00:00

4. Recover High Priority Virtual Machines Success 00:00:00

5. Recover Normal Priority Virtual Machines Error: A general system error occurred: Unexpected optional not set: vim.VirtualMachine:vm-6874.config 00:00:00

    5.1. Recover VM "Test_VM" Error: A general system error occurred: Unexpected optional not set: vim.VirtualMachine:vm-6874.config 00:00:00

Log

[2015-11-06 09:06:32.998 08516 verbose 'SanConfigManager'] Noticed removal of virtual machine 'vm["vm-6862"]' from datastore 'datastore-3502'

[2015-11-06 09:06:33.034 12908 verbose 'RegistrationHelper'] VM unregistered successfully

[2015-11-06 09:06:33.034 12908 verbose 'SecondaryReplication'] Registering virtual machine from '[snap-178fde61-Test_Test] Test_VM/Test_VM.vmx' on host 'vim.HostSystem:host-3528' for ShadowVm 'shadow-vm-2753207'

[2015-11-06 09:06:33.245 08516 trivia 'SanConfigManager'] Ignoring update on 'vm-6864' for property 'config.ftInfo.role' of update type 'indirectRemove'

[2015-11-06 09:06:33.245 08516 warning 'SanConfigManager'] Failed to parse change name 'config.hardware.device'

[2015-11-06 09:06:35.388 12908 verbose 'RegistrationHelper'] VM Test_VM registered successfully as 'vm-6864'

[2015-11-06 09:06:35.394 12908 verbose 'SecondaryReplication'] Saving ShadowVm to DB object

[2015-11-06 09:06:35.423 12908 verbose 'PropertyProvider'] RecordOp ASSIGN: vm, shadow-vm-2753207

[2015-11-06 09:06:35.424 12908 verbose 'SecondaryReplication'] Registered new virtual machine 'vm-6864' for ShadowVm 'shadow-vm-2753207'

[2015-11-06 09:06:35.440 09104 error 'SecondaryReplication'] Shadow virtual machine: 'vim.VirtualMachine:vm-6864' has become inaccessible!

[2015-11-06 09:06:35.440 09104 verbose 'PropertyProvider'] RecordOp ASSIGN: needsRepair, shadow-vm-2753207

Hello

Is it possible for a per VM recovery from SRM without disrupting the other VMs in the Protection Group?

Planned method: edit recovery plan and select Do Not Power On for the other VMs in the Group (or put the other VMs into Suspend non-critical VMs at Recovery Site step)

Click Run.

What happens to the protected VMs which I'm not interested in recovering?  Do they get disrupted or carry on regardless?

Although this isn't the EMC forum, does anyone know when we can expect a supported EMC VNX SRA for SRM 6.1?

The VMware website only lists SRA's for EMC VPLEX and RecoverPoint.

Our customer has datastores which have both virtual machines which need to be protected by SRM and vm's which do not require SRM protection.

Is there a way to protect those VM's without the need to storage migrate the non-SRM VM's to other datastores?

When performing a test failover this is the error I get

Error - Virtual machines "<VM names>" that are not protected by this protection group use datastores "<datastore>" that are in this protection group.

I expect this is by design but maybe there is a workaroud. Performing many storage migations and placing high IO/ high priority VM's on a limited number of datastores is not what I am looking forward too.

Gentlemen 

What can SRM customers to ensure that a SQL VM running on (and replicated by) 3^rd party storage is application-consistent? Does the HP SRA have code that can invoke quiescing within the VM? Or is there some sort of scripted way, within the context of SRM, that a DB quiesce in the VM can be triggered in tandem with or just as a LUN replication occurs?

I know that HP is responsible for the SRA – but in these situations we get sometimes caught between the vendors. Looking for some “how have others protected mission critical SQL resources using 3PAR and SRM” experience.

Said another way:

We are looking for assistance with a DR implementation for a specific SQL application. The app is on VMs running on 3PAR storage. We have purchased all the required “3PAR application suite licenses” and then also have VMware SRM.

We are most concerned that LUNs replicated from production to DR site (LUNs will be datastores hosting the SQL VMs I presume) will be fully SQL-consistent (i.e. better than crash-consistent), when replicated.

We have some experience with 3PAR replications – but to my knowledge have not yet worked with the application suites.

Question – can anyone describe what role (if any) the 3PAR application suites may have in properly quiescing SQL running on a VM that is on a 3PAR LUN? I for one am not sure it can be done this way – seems that we may need to use RDMs (or vVOls if they are SRM compatible) to properly quiesce the DB. Is there an HP storage agent that can run on a SQL VM to coordinate with the array when snapshots of the underlying LUN are executed?