Hello,
I have two vcenter 4.x with full configuration SRM
We want to migrate ESXi from Site A into a new Vcenter 5.x and use a metrocluster architecture at the end.
I want to disabled/suspend or uninstall the SRM on Site A (Source site) because i don't know if SRM apply recovery when we decomissioned ESXi from Vcenter 4 to Vcenter 5
Tha two old vcenter 4 would not be used after mirgration.
Thanks,
We're going to be running a business continuity test soon and my predecessor has configured SRM so that VMs are grouped into their logical groups. Which makes sense. But what if I only want to recover one VM from a group of 5? I see I can change the power state of individual VMs but unless it's hidden away I'm not seeing anywhere I can choose which ones to recover individually.
In this case would it be better if I created individual protection groups per VM?
We're using VSC to quiesce VMs and back them up, then initiate a SnapMirror replication. SRM only sees the most recent snapshot, which is the SnapMirror's and not the VSC snapshot. So when we test, VMs are spun up and filesystems have to be checked because the quiesced VM is not what is being used.
How can I get SRM to use the most recent VSC (smvi_datastore1_timestamp-here) snapshot?
Thanks
Hi,
In the SRM recovery Steps, I use powershell scripts to control a NetApp NAS, which is accessed by my protected virtual machines for an application (VM Datastores resides on the SAN).
The recovery works fine, for both virtual machines and theirs NAS resources.
I want to automatize the re-protection of the NAS and include it in the SRM process. My script is ready, but I can't see how to add it in the reprotection steps.
Do you know if it is possible to do that ?
For information, we run on vCenter 5.0, and SRM 5.0.2.
Thanks !
Hi,
I want to ask if you have ever seen a design looked like a Site Recovery over an IAAS infrastructure. Do you think that it may be possible or not?
Regards,
Andry Tiana ANDRIANALY
Hello,
I am running two vCenters, one is hosting the Primary (Protected site) and the other is my dedicated DR site. I am using VR replication on all my VMs in the primary site. When I open up Site Recovery and click on vSphere replication all my VMs appear to have replicated successfully as can be seen in the screenshot.
When I attempt to protect the VMs using a protection group I am getting the error below, which seems to indicate that replication is not working properly, however as you can see from the screenshot below replication doesn't appear to be a problem. I've also verified that the VM files appear in the target datastore in the DR site.
I am running vCenter 5.1 on both sites, and SRM 5.1 with VR replication.
Any ideas where I can start troubleshooting?
Hi Sir
I am working in client place for SRM implementation.
Here i have a VMware vSphere , Vmware vCenter server and SRM setup in two different location for production environment.
My Setup is like this:-
Recovery site:-
2 EXSi 5.1.0-Update1 host .
vCenter server 5.1.0-update1 on Windows server 2012 in first virtual machine.
SRM 5.1.1 on Windows server 2012 in second Virtual machine
vSphere replication appliance deployed at recovery site.
Protection site
1 ESXI 5.1.0-update1 host
vCenter server 5.1.0-update1 on Windows server 2012 in first virtual machine
SRM 5.1.1 on windows server 2012 in 2nd Virtual machine
vSphere replication appliance deployed at protection site.
3 virtual machine for development use.
Note: - 1. I have done all the required setting for SRM and replication is successful, but after adding virtual machine in protection group when i running test and recovery plan getting error in the time test and recovery time. Could anyone please suggest me where i am doing wrong?
please check the atached screenshot
please help me for this
thanks
deep
Just spent days troubleshooting vSphere Replication in the lab. Installation of the VRMS and VRS servers went without issue. Configuring replication on a VM completed without error. But when I would view the replication status, it always said "Not Active" and never replicated. When I hit "Synchronize Now" it would pop up the following error:
Call "HmsGroup.OnlineSync" for object "GID" on Server "" failed. An unknown error has occurred.
Investigating the vmkernel logs on the ESXi host with the source VM I found this:
2012-07-12T21:30:06.452Z cpu1:2049)WARNING: Hbr: 3855: Failed to establish connection to [10.11.49.44]:31031(groupID=GID-dc6e77d9-f516-408b-9d11-8ea3b315e253): VR: The set of disks on the server doesn't match up
Finally called support and they eventually found a relevant bug report.
Apparently if you use NetApp's mbralign tool to align your disks it can cause a miss-match between the protected and recovery sides for the disks and this error results. You also seem to have to have more than one disk attached to the VM for this to happen.
The fix is to edit the vmdk settings and add 5 MB to the disk size. You don't have to re-partition to actually use the 5MB, you just have to grow the disk by 5 MB. Then magically replication starts working.
That was a weird one that I find nothing on anywhere, so thought I would share. I'm sure VMware will put out a KB at some point.
There is a conversation going on in another thread
(http://communities.vmware.com/message/2227065#2227065)
- but it is an old thread and started off with different versions of everything.
I'm going to start a new thread based on current versions.
I cannot get the SRA to work with SRM 5.1
When I run a "test" failover for a simple recovery plan - I get this error:
"Error - Failed to create snapshots of replica devices. Failed to create snapshot of replica consistency group test1rep. SRA command 'testFailoverStart' failed for consistency group 'test1rep'. Volume cannot be created, please check test mdiskgroup cofiguration Refer to IBM SAN Volume Controller troubleshooting"
I'm running:
IBM v7000 Version 6.4.1.2 (build 75.0.1211301000)
vCenter 5.1
SRM 5.1.0-941848 on Windows 2008 R2 64 bit (2vCPU 8GB RAM)
SRM advanced settings
I have set the Advanced Settings option:
storage.Commandtimeout to 1800 (def 300)
storageProvider.hostRescanRepeatCnt to 3 (def 1)
storageProvider.hostRescanTimeoutSec 1800 (def 300)
SRA v2.1.0.121224 (also tried 2.1.0.121108)
non-preconfigured environment
Pre-Configured Env. not set
Test MDisk Group ID set
SpaceEfficient Mode = False
Is anyone having success with the IBM V7000 SRA (any version) with SRM 5.1?
Thanks
Hi all
I am currently creating a protection group for SRM.
I have created a test cluster at our protected site which has 2 hosts, 1 datastore and a folder called Protected
I have then created a test cluster at our recover site which has 2 hosts, 1 datastore and folder called Recoverd
I have 3 test servers in the protected site and in the datastore and protected folder.
As far as I can see I have configured the folder mappings correctly, the recourses, placeholder datastores and network mappings on both sites.
When I create my protected group it comes back with the error againist each VM saying "Placeholder VM creation error: Unable to access file [SRM BAS Reocver Datastore01]"
Then on the vCentre at recovery site it says "unable to access file [SRM BAS Recover datastore01]
I have attached screenshots of the errors.
Can provide what extra information required.
Any help would be great.
Thanks!
Austin.
Hi,
I know from reading the documentation I need to appropriate SRA, which I have. The issues I am seeing is I can not find what particular NavCLI I need to download.. Do I need to download and install on the ESXi hosts? or somewhere else?
Where do I download it from, I was given a navcli to install on the ESXi nodes but it is in RPM format, can that be installed on a ESXi node?
Has anyone installed SRM5.0 on a VNX5300?
If so guidance would be appreciative.
thanks
SRM datastore extend : we are planning to extend the protected datastore on SRM 5 as it is 2 way replication , i want to know do we need to pause the replication and extend the datastore or how. please share
I have just discovered that you can only add steps to a recovery plan either in the recovery or test steps. The Add Step option is greyed out for both the reprotect and cleanup steps.
I want SRM to run powershell scripts to readd the NFS export back on our NetApp SAN and readd the datastores back onto the hosts of the protected site. This, logically, has to be done during the reprotect phase and not as part of the recovery phase especially if it is after an unplanned failover where the original protected site is not available at the recovery stage.
Does anyone know why this is or how you can get around it?
I'm attempting to test a recover plan. There is an issue with one of the vms on the datastore. It has a drive attached from a non replicated volume.
When I run the plan it logs the error below for all active steps after "Suspend Non-critical VMs at Recovery Site".
Error - Virtual machines "VM name" that
are not protected by this protection group use datastores "Volume Name"
that are in this protection group.
I understand that I can't protect that particular vm. The question is whether it will prevent other vms from being recovered or is something else going on?
Hello,
Is it possible to test SRM recovery plan with vSphere replication (like Array based replication) ?
If yes, How it works ?
The vsphere replication is automatically stopped, and after the VMs replicas are invertoried and the VMs started or something else ?
Thanks for your answers
Regards
Philippe
Does the Managed Object Reference for objects migrated via SRM remain the same from vCenter Server to vCenter Server instance?
If the MOR changes, how is SRM maintaining which object relates to which object between sites?
Does vSphere or SRM have the concept of GUIDs (as opposed to UUIDs)?
I have site recovery manager installed, everything is working just fine though 2 virtual machines at the main site show
the (butterfly) sign which should appear on vms at the DR site not on vms at the main site.
only those two vms show this sign, I checked of the plan for those two vms need to (Reprotected) but they were with (Recovery) sign only, which means they already reprotected.
is there any explanation for this ?!
Thanks for Advanced.
I am about to install SRM 5.02 in our environment. We have two sites one Production and one for DR.
We would like to have the ability to fail back after a disaster (Reprotect?).
It appears to do this I will need to go to Vcenter linked mode.
While I'm not adverse to going to linked mode I want to upgrade to Vcenter 5.1 before doing so.
So the question is can I install SRM 5.02 in unidirectional mode now and convert to bidirectional mode at a later date after the Vcenter servers are converted to linked mode?
Hi,
I'm new to vmware, so I'll ask maybe a basic question.
My company wants to move from physical to virtual system. We are over 20 servers with different roles (DC, Exchange, SQL, File Servers...), and we want to virtualize in the HQ, and in the same time create a DR site in another place. I would be very grateful if someone can help me to build a list of hardware, and software we need to achieve this:
1. In the HQ, we would like to have 2 Storages mirroring with each other, and 3 servers connected there to run VM machines so in case one craches, system doesn't need to start working in DR site. Is it possible, and if yes what we would need to buy (SAN license, special vmware license)
2. In the DR site to install 2 servers, and only one storage, and replicate with mirroring storages in HQ. Is this possible, and again ,what licenses we need (for storage, and wmware side).
Thank you in advance for your reply, and I hope I'm not asking to much.
Hi,
I have deployed vmware srm 5 based on array.
It could automatically run the recovery plan when it detects a drop in storage or servers? or it must be done manually when we detect the fall?
thanks!