Quantcast
Channel: VMware Communities : All Content - Site Recovery Manager
Viewing all 2572 articles
Browse latest View live
↧

VMware SRM 6.1 and IBM Storwize SRA 3.1 Issues

November 16, 2015, 2:21 pm
$
0
0

hello ,

 

We have sites,  all critical   VM's protected with VMware Srm + IBM SVC. During the  setup phase we did the fail-over and fail-back tests and everything works smooth.

 

Recently we had a storage  outage  and we lost the all the LUNs in primary location, then we have tried to recover the VM's  in secondary location using  SRM . unforunatly its not working with below error.

 

"The error is "Error failed to promote replicate devices. SRA command 'failover' failed. Invalid Array ID. Refer to IBM SAN Volume Controller troubleshooting Failed to promote replica devices. SRA command 'failover failed' Invalid Array ID. Refer to IBM SAN Volume Controller troubleshooting"


Sadly we have manually mount the LUN's to ESXi servers and started the VMs manually.


Does anyone seen the error  ?



The next step  was we have  built the SRM test environment  and did the following  tests..

 

1.  failover and failback tests  - the result  was success..

2.  deleting the LUN in primary location and recovering the VM from DR location . Unfortunately its failed with same as above SRA error.

.

How do we simulate the real disaster scenario with  SRM ?


"Like  deleting  the primary location VM lun and recover the VM from secondary site with SRM" is that right test case ?


Regards,

Surya







.

↧
Search

SRM with array based replication - how to achieve better than crash consistency?

November 20, 2015, 8:29 am
$
0
0

So I believe that when using SRM with vSphere replication, that when VMs are replicated, VMware tools first does a VSS quiesce on the VM. We can see this here:

 

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

 

But what about when using array based replication instead of vSphere replication?

 

Would it be the SRA that touches VMwtools on each VM, causing it to trigger a VSS quiesce? Or - is this not done?

 

If it is not done - how do we assure that the servers and applications are proplerly quiesced before they are replicated? Is there a way to do a "pre-replicate" power-cli or something, to ensure that (for example) SQL running on a VM is properly quiesced? We want full application consistency, not just crash consistency ...

↧
↧

SRM Test Recovery plan issue

November 18, 2015, 2:43 am
$
0
0

Hello,

we have two sites with ESXi hosts 5.5 and vCenter 6 and SRM 6 installed and configured on both the sites. we are using IBM Storwize v7000 storage on both the sites. I have configured SRM with array based replication. Everything looks fine but when i run the recovery plane in test recovery mode, it generates error on stem 4;

--------------

Failed to create snapshots of replica devices.

 

Cause:

Failed to create snapshot of replica consistency group Test.

 

Cause:

SRA command 'testFailoverStart' failed for consistency group 'Test'.

 

Cause:

The replication might have been terminated as a result of a previous failover operation.

Refer to IBM SAN Volume Controller troubleshooting

 

------------

Attached is the snapshot also. Please any one advise how to resolve this issue.

thanks in advance..

↧

Can SRM test failovers be performed if WAN connection is taken offline between sites?

December 20, 2013, 11:05 am
$
0
0

I am trying to figure out the options for testing SRM.    I know that I can perform a test failover (to test bubble network) when the WAN is up and both SRM instances can talk to eachother.  What if I wanted to disconnect the WAN and execute a test failover?  Will SRM let me do a test failover if the protected site is offline?   The thinking is that if the disconnecting of the WAN is a requirement for SRM testing,  that  I would still like to do a test failover as a real failover would be a mess to cleanup when it is a test.

 

Thanks,

-MattG

↧

Plan Recovery Issue

November 23, 2015, 5:20 am
$
0
0

Hello,

 

With reference to my previous post ;

https://communities.vmware.com/message/2556721#2556721

the Test Recovery went successfully but Plan Recovery generating some issues. The Recovery plan is successfully running but when I am rescanning my SRA, it shows status "Failover in progress" instead "synced or completed" and after some time it shows Unknown status as per the snapshot. Please see the attached snapshot and advise;

Appreciated in advance.

↧
↧

No VRM Server registered with vCenter Server for site "Live"

November 26, 2015, 8:18 am
$
0
0

I have SRM 6.1 and vSphere replication 6.1 installed on both sites.

The VSRs are connected to vCenter server.

I'm getting this error: Unable to create protection group. No VRM Server registered with vCenter Server for site "Live"

Screenshot attached, does anyone know what's going on here?

Capture.jpg

↧

Site Recovery Manager - mid size (less than 500 VMs) data centre migration

November 30, 2015, 12:01 am
$
0
0

We are trying to evaluate SRM as AS-IS DC migration product for a mid-size DC migration. Expectation is whatever VMs (less than 500) are present in the source DC all will be moved to a new DC (distance within 200 Kms), kind of AS-IS migration.

 

Our initial approach was -

1. Perform application due diligence including infra, network & security

2. Find out application dependencies (as per it's interfaces) - accordingly create move group ---- this way we may be in a position to create 10 bundle which can be migrated 1 by 1 and then data migration needs to be taken care. Minimum data migrate first (replication link). Once smoke testing is done we will move rest of the data by using incremental approach. Then migrate next group and test etc.

 

Question -

By using SRM can we migrate entire VMs (less than 500) - app + data in a single go? in that case app dependencies is required? Also pre-migration as well as post migration testing is required? Kindly help.

 

 

Thanks

↧

Array Based Replication Status

November 29, 2015, 12:29 am
$
0
0

Hello,

 

i am using SRM6.1 with vcenter 6 and ESXi host 5.5 u2. I ran the Recovery Plan and it shows Recovery Complete (Snapshot_RP1) but in Array Based Replication when I scan SRA, it shows the status "Failover in progress" (Snapshot_RP2). My question is, the status also should not be changed from failover in progress to Complete or Synced OR it will remain "Failover in progress" until I run the Plan in Reprotect mode??

And 2nd question is; what exact the configuration I have to do on storage and SRM side for Reprotection process (Failback to original site)??

 

Moreover, When I run Recovery Plan, it creates a new Datastore with the name "snap-xxxxxx-ce" on Recovery site while the datastore name is "ce" in protected site. Now please advise what has to do next to run the Reprotection successfully (Snapshot_Qassim Rep LUN) OR only I need to switch-over to existing consistency group from Recovery site to Protection site??

 

Please advise..

↧
Search

Filtering out non-replicated guests

December 1, 2015, 7:10 am
$
0
0

Hello we are using SRM 5.5 with Recoverpoint as the Protection SRA.

You used to be able to filter out guests on the Recoverpoint side that were not going to be part of the protection group.

I dont see that option anymore and was told it was removed. How does one filter out non-replicated vm's or even vm's wejust dont want to protect in

SRM now? It is blowing out our license usage not and I cannot create the protection group.

Thanks!

↧
↧

SRM 6.1 with VR replication only?

December 3, 2015, 5:33 am
$
0
0

Hello,

 

I haven't worked with SRM for a little while and thought I would throw it together in my lab in order to see the changes.  I had done this previously using VR replication, but from what I see it appears that SRM 6.1 requires SRA's.  Is that the case?

 

 

Sorry I have to ask this here, I've searched the release notes and the answer is not clear.

 

Thanks.

↧

SRM Test Recovery Plan attempting to mount NFS datastore with wrong server IP

December 3, 2015, 8:54 am
$
0
0

testing SRM with EMC VNXe SRA in lab environment and have one replicated NFS datastore. When testing the recovery plan, datastore is snapshoted and promoted with r/w hosts permissions. However, when it attempts to mount the NFS datastore it is using the wrong storage server IP address in which the export path technically does not exist and fails. Not sure if this is an issue with SRM or the SRA.

 

Highlighted in red from the logs show that the remote NFS server 10.100.100.30 (src SPB) is mapped to 10.20.12.100 (dst SPA). Not sure where a mapping like this exists other than replication which is configured from 10.100.100.30 (src SPB)  to 10.20.12.101 (dst SPB)

 

 

from the vmware-dr-#.log

<Response xmlns="http://www.vmware.com/srm/sra/v2">

-->     <ReplicatedDevices>

-->         <StoragePorts>

-->             <StoragePort type="NFS" id="10.20.12.100"/>

-->             <StoragePort type="NFS" id="10.20.12.101"/>

-->         </StoragePorts>

-->         <TargetDevices>

-->             <TargetDevice state="read-only" key="125_APM00112004849_0000_469_APM00132612165_0000">

-->                 <Name>Dst-NFSB_Datastore1.00</Name>

-->             </TargetDevice>

-->         </TargetDevices>

-->     </ReplicatedDevices>

--> </Response>

 

2015-11-30T11:58:12.255-05:00 [06004 verbose 'StorageProvider' opID=7766543d:4d0e] Recovering NFS datastore 'NFSB_Datastore1' with URL 'ds:///vmfs/volumes/aa6bae62-3f81fc2e/'

2015-11-30T11:58:12.255-05:00 [06004 verbose 'StorageProvider' opID=7766543d:4d0e] NFS volume '/app_10_sg_9_root' is not mounted yet

2015-11-30T11:58:12.284-05:00 [06004 verbose 'Storage' opID=7766543d:4d0e] Mapped IP address of the remote NFS server: '10.100.100.30' -> '10.20.12.100'

2015-11-30T11:58:12.286-05:00 [06004 verbose 'StorageProvider' opID=7766543d:4d0e] Datastore name 'NFSB_Datastore1' is already taken. Will use 'NFSB_Datastore1 (2)'.

2015-11-30T11:58:12.286-05:00 [06004 verbose 'StorageProvider' opID=7766543d:4d0e] Recovering NFS datastore 'NFSB_Datastore1 (2)' with URL 'ds:///vmfs/volumes/aa6bae62-3f81fc2e/' by mounting '/app_10_sg_9_root' from '10.20.12.100' on 3 hosts ['vim.HostSystem:host-188', 'vim.HostSystem:host-192', 'vim.HostSystem:host-401']

2015-11-30T11:58:12.313-05:00 [06004 verbose 'HostDomain' opID=7766543d:4d0e] Enabling garbage collection of task queues

2015-11-30T11:58:12.335-05:00 [05044 verbose 'QsProvider'] Created entry iterator [class Dr::QueryService::ObjectEntryIterator:000000000BBF3960] from generation 2867. Max generation 2868

2015-11-30T11:58:12.354-05:00 [05044 verbose 'QsProvider'] All data up to generation '2868' is sent to IS

2015-11-30T11:58:12.884-05:00 [06008 error 'StorageProvider' opID=7766543d:4d0e] Failed to mount NFS volume '10.20.12.100:/app_10_sg_9_root' on host 'host-188': (vim.fault.PlatformConfigFault) {

 

 

 

SRA Log

 

2015-11-30 11:58:11,590 [com.emc.vnxe.platform.VnxeArray]: Filtering storage ports:

2015-11-30 11:58:11,590 [com.emc.vnxe.platform.VnxeArray]: Using storage port: 10.20.12.100

2015-11-30 11:58:11,590 [com.emc.vnxe.platform.VnxeArray]: Using storage port: 10.20.12.101

2015-11-30 11:58:11,590 [com.emc.vnxe.platform.VnxeArray]: Ignoring mgmt port: 10.20.4.17

 

 

2015-11-30 11:58:11,949 [com.emc.sra.SraController]:

 

 

**** Response ****

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<Response xmlns="http://www.vmware.com/srm/sra/v2">

    <TestFailoverStartResults>

        <TargetDevices>

            <TargetDevice key="125_APM00112004849_0000_469_APM00132612165_0000">

                <Snapshot id="app_10_sg_9">

                    <Identity>

                        <NfsName>/app_10_sg_9_root</NfsName>

                    </Identity>

                    <RecoveryPoint id="rp-app_10_SRM-TEST-FAILOVER">

                        <Name>Latest</Name>

                        <Time>2015-11-30T17:08:08.000-05:00</Time>

                    </RecoveryPoint>

                </Snapshot>

            </TargetDevice>

        </TargetDevices>

        <StoragePorts>

            <StoragePort type="NFS" id="10.20.12.100"/>

            <StoragePort type="NFS" id="10.20.12.101"/>

        </StoragePorts>

    </TestFailoverStartResults>

</Response>

↧

SRM pairing failed

December 6, 2015, 6:52 pm
$
0
0

Hi,

 

I'm experiencing issue when I'm trying to pair SRM. I'm using SRM 6.0 version. I also tried to telnet port 9086 on both SRM servers and it is not block.SitePair Error SRM.PNG

 

Thanks and appreciate your help.

↧

SRM AND VMView

March 23, 2011, 4:10 am
$
0
0

Hi,

 

We currently protect our main VM farm using SRM and are looking to extend this to cover to our farm of linked clone View desktops. I've search quite a lot for documentation on how to do this but have not came across much yet. I was wondering if anyone has tried implementing this and if so could give some advice/guidance.

 

I did find this website which involves creating scripts. http://virtualgeek.typepad.com/virtual_geek/2009/10/howto-use-site-recovery-manager-and-linked-clones-together.html

 

Our environment:

vSphere      4.1

View          4.6

Storage     Primary - EMC CX4, DR - EMC CX3

 

Any advice would be greatly appreciated.

 

Thomas

↧
↧

SRM & VMware View with Persistent Disk

December 7, 2015, 3:15 am
$
0
0

Hi All,

 

We want to achieve fail over of our VMware Desktop pool to DR site i.e. "Persistent Linked Clone Desktops with Persistent Disks. As per the below VMware white paper the scenario they have mentioned for Persistent Disks is for a situation when the DR IP Address will get change(Refer to Page-13).

 

http://www.vmware.com/files/pdf/techpaper/vmware-view-vcenter-site-recovery-manager-disaster-recovery.pdf

 

However we will keep the same IP addresses at the DR Site therefore we do not require to Provision the new VM's again at the DR site.


Now the quesiton is if we dont want to re-provision VM's at the DR site do we need to Deattach/Attach disk as mentioned on the Page-14 of the above guide?

 

Regards,

Khurram Shahzad

↧

Unable to modify/repair/uninstall srm service 6.1

December 7, 2015, 10:13 am
$
0
0

Hello,

 

I made a mistake during the initial installation of SRM on two servers.  I was able to successfully uninstall and reinstall it on one server by uninstalling SRM, then uninstalling the embedded database.  On the second server I made the mistake of uninstalling the embedded database PRIOR to uninstalling the SRM service.

 

Now modifying/repairing/uninstalling the SRM 6.1 service all fail.

 

Uninstall:

(I have tried it with Delete Site Recovery Manager data ticked on and off)

Uninstall1.jpg

 

 

Uninstall_err.jpg

Uninstall_err2.jpg

 

Repair:

 

repair1.jpg

 

Modify:

 

 

 

 

 

I am able to make it a bit further when I modify, I enter my admin credentials, virtual center name, however I get stuck here since the backend database has already been removed:

 

modify.jpg

 

So basically, I can see no way forward and no way back.  I could just deploy a new VM and install SRM on it from scratch, however I am concerned that if I try to link it to my vCenter it won't work because there is already an SRM server linked to it.

 

How do I remove this safely and gracefully?  Barring a graceful uninstall, how can I force it?

 

Thanks.

↧
Search

Consuming SRM WSDL using SoapUI

December 8, 2015, 11:12 am
$
0
0

Hi there, I'm consuming SRM wsdl using SoapUI. I want to unprotect some vms using UnprotectVms call but when I call this api, I got 'Object has deleted or has not completely created' in response. Attaching the request and response output of SoapUI. Could you please help me to make this call successful.

 

I'm defining type from srm_60_api documentation in request and the vmId which I got from ProtectionListProtectedVms api call. When I looked into SRM server log I saw following message.

2015-12-08T10:44:45.461-08:00 [05008 error 'authorize.EntityResolver'] Failed to resolve drextapi.ProtectionGroup:SrmProtectionGroup type

Does this mean request wsdl request is in wrong format? Please let me know the way to create correct request if it is.

↧

Unable to set up Protect Groups - Error: "Unable to create Protection Group. No VRM Server registered with VCenter for site xyz"

December 8, 2015, 7:59 am
$
0
0

I am trying to set up Protection Group type of "Individual VM's" and I receive this error.  We are using Vcenter 6.0, SRM 6.1, and VR Appliance 6.1.  The sites are paired, the VR service is running, everything appears fine.  I have repeatedly checked NTP and the times on the vcenter server, the ESX hosts and the VM's and all seem to be right.  I have included the logs for analysis.  My current date 12/8/2015 and the time that I attempted the creation of the Protection Group was at 10:36AM so that one can look at that time in the logs.  Thanks for the assistance.  Note, I am using a trial license of SRM now that will expire on 12/27/2015 until I get my order through my procurement system.

↧
↧

VM will not powerup after SRM

December 10, 2015, 12:49 am
$
0
0

I recently performed an SRM failover and 1 of the 6 VM's in question wouldn't power up after.

On inspection of the .vmx file, I saw that it seemed to lose a mapping of one of it's hard disks. Thankfully I had a copy of the original .vmx so it was relatively easy to identify the correct Disk mapping.

I'm wondering why this may have happened ?

 

The first few Hard Disks were mapped as follows and were all ok after the SRM,

scsi1.virtualDev = "pvscsi"

scsi1.present = "TRUE"

scsi1:0.deviceType = "scsi-hardDisk"

scsi1:0.fileName = "myservername02_1.vmdk"

scsi1:0.present = "TRUE"

scsi1:1.deviceType = "scsi-hardDisk"

scsi1:1.fileName = "myservername02_2.vmdk"

scsi1:1.present = "TRUE"

scsi1:2.deviceType = "scsi-hardDisk"

scsi1:2.fileName = "myservername02_3.vmdk"

scsi1:2.present = "TRUE"

 

The last Disk should have been mapped as follows after the SRM

scsi2.virtualDev = "pvscsi"

scsi2.present = "TRUE"

scsi2:0.deviceType = "scsi-hardDisk"

scsi2:0.fileName = "/vmfs/volumes/VMFS_SharedStorage_3154_BPM_LOG1_3696/myservername02/myservername02.vmdk"

scsi2:0.present = "TRUE"

 

instead it was mapped as

scsi2:0.fileName = "/vmfs/volumes/565fc9d6-4eb63031-9ce1-0025b506011e/myservername02/myservername02.vmdk"


Does anyone know why this may have happened and more importantly, what could be done to prevent it from happening again ?

Unfortunately, a different Team looks after Storage so I'm not able to directly answer any Storage related questions you may have


thanks


↧

How to delete a srm protection group using wsdl?

December 9, 2015, 9:08 pm
$
0
0

I'm looking for the way to delete srm protection group using wsdl, please help me to find it out. I'm using SoapUI to execute SRM wsdl and I have MOB id of protection group.

Let me know if any way to delete protection group using its MOB id in SRM 6.0.

↧

SRM and Recoverpoint protected LUNS/Datastores

December 11, 2015, 5:35 am
$
0
0

Hi all,

 

I have recently put in charge of a vBlock and my manager wants SRM installed and configured, I'm fine with SRM, have installed and configured it on other sites.

 

What I was hoping someone could help me with is the storage back end stuff.

 

I know SRM needs to replicated from the protected site to the recovery site, so what I am unclear on how the LUNS should be setup initially, then journalled and added to an RP consistency group.

 

Has anyone done this on a VNX storage array, any help, guidance, suggestions would be massively appreciated.

 

Thanks

↧
Viewing all 2572 articles
Browse latest View live
Search