Yes you do.
Regards
Ritesh
Yes you do.
Regards
Ritesh
Hi
Yeah, I think so.
I ended up creating RP1 - RP5 under the SRM resource pool in the recovery environment, and created the mappings as 1 to 1, which worked a treat.
Thanks
Sorry to drag up an old thread, but it's not been answered, so...
I've just experienced a similar thing.
Running a DR test over the weekend, a planned migration of a set of VM's took place. Sites connected by 2 x 10GB links. Two of the VM's within the Protection Groups that formed part of the Recovery Plan were on the larger side - one for example was around 4TB's, and the other just under that.
Fail over (planned migration) is not too bad in fairness; took around 35 minutes from Saite A to B. Reprotection took around 4 hours. Fail back (again, planned migration) took around an hour and half.
However, I initiated reprotect at 14:55, and at 20:09 the Protection Groups finally displayed an "OK" status. However, vSphere Replication was still working through Initial Sync.
We're using vSphere Replication version 6.1.2.
Based on this, if we tried to do a full DR test via planned migration, we'd never fit the activities into the agreed testing window.
I have a ticket logged for VMware Support to assist.
Hi
Would need a little advice after upgraded SRM 6.5.1 to 8.1.1
as I want to use powercli to automatically add the new datastores to storage replicated protectiongroups I face one issue with it.
I can't find the new protectiongroup object (VMware.VimAutomation.Srm.Views.SrmProtectionGroup) method introduced in 8.1 API - "addDatastores"
I wonder if I have to also upgrade the API somehow as under srmapi connection the api version shows 7.0 or does it come somehow from the BenMeadowcroft module what I'm using?
PS > $srmapi.Content
ApiVersion : 7.0
SrmApi : SrmApi-SrmRecoveryApi1
Protection : SrmProtection-SrmProtection
Recovery : SrmRecovery-SrmRecovery
InventoryMapping : SrmInventoryMapping-SrmInventoryMapping
About : VMware.Vim.AboutInfo
Storage : SrmStorage-SrmStorage
PS> $protectiongroup | gm
TypeName: VMware.VimAutomation.Srm.Views.SrmProtectionGroup
Name MemberType Definition
---- ---------- ----------
AssociateVms Method void AssociateVms(VMware.Vim.ManagedObjectReference[] vms)
CheckConfigured Method bool CheckConfigured()
Equals Method bool Equals(System.Object obj)
GetHashCode Method int GetHashCode()
GetInfo Method VMware.VimAutomation.Srm.Views.SrmProtectionGroupInfo GetInfo()
GetParentFolder Method VMware.VimAutomation.Srm.Views.SrmProtectionGroupFolder GetParentFolder()
GetPeer Method VMware.VimAutomation.Srm.Views.SrmProtectionGroupPeer GetPeer()
GetProtectionState Method VMware.VimAutomation.Srm.Views.SrmProtectionGroupProtectionState GetProtectionState()
GetType Method type GetType()
ListAssociatedVms Method System.Collections.Generic.List[VMware.Vim.VirtualMachine] ListAssociatedVms()
ListProtectedDatastores Method System.Collections.Generic.List[VMware.Vim.Datastore] ListProtectedDatastores()
ListProtectedVms Method System.Collections.Generic.List[VMware.VimAutomation.Srm.Views.SrmProtectionGroupProtectedVm] ListProtectedVms()
ListRecoveryPlans Method System.Collections.Generic.List[VMware.VimAutomation.Srm.Views.SrmRecoveryPlan] ListRecoveryPlans()
ProtectionGroupGetOperationalLocation Method string ProtectionGroupGetOperationalLocation()
ProtectVms Method VMware.VimAutomation.Srm.Views.SrmProtectionTask ProtectVms(VMware.VimAutomation.Srm.Views.SrmProtectionGroupVmProtectionSpec[] vms)
QueryVmProtection Method System.Collections.Generic.List[VMware.VimAutomation.Srm.Views.SrmProtectionGroupVmProtectionInfo] QueryVmProtection(VMware.Vim.ManagedObjectReference[] vms)
ToString Method string ToString()
UnassociateVms Method void UnassociateVms(VMware.Vim.ManagedObjectReference[] vms)
UnprotectVms Method VMware.VimAutomation.Srm.Views.SrmProtectionTask UnprotectVms(VMware.Vim.ManagedObjectReference[] vms)
MoRef Property VMware.Vim.ManagedObjectReference MoRef {get;set;}
Is there a way to run a powershell script during the SRM cleanup process? SRM v6.5
Here's the situation
We have two production domain controllers at our DR site that are up and running all the time. These are for VPN authentication and DNS for the infrastructure. During a DR test, we shut these down and use clones of these DCs for the test. This way, anything we do during the DR test isn't going to impact the production DCs. When the DR test is done, we delete the clones and power the production DCs back on.
I have a script that does the DC shutdown, clone, and power on of the clones. This script is at the beginning of the recovery plan. It works great.
I'd like to script the deletion of the clones and the power on of the production DCs but, I don't know where to stick it. Ideally, the cleanup process is where it should go. I thought about putting a pause at the end of the recovery plan and then the deletion script but, if somebody accidentally answers the prompt, it could bring up the production DCs on the same network as other older restored DCs.
Any help anyone could provide would be ... uh .... helpful.
Sorted. Forgot about this. Seems the older version of Enterprise manager was the cause as it conflicts with the newer version of the SRA and SRM.
Updated to storage manager appliance and all seems to be working happily now
In case this helps anyone in the future, given the versions we were using, the performance is expected.
The re-protect activity initiates what looks like an "initial sync" in vSphere Replication, but it is in fact initiating checksum activities. The time taken largely depends on the size of the VMDK files being checked. The bulk of the checksum time is taken up by hashing, as vSphere Replication does not have a Change Block Tracking mechanism.
If more speed is required, array based replication should be considered. There unfortunately isn't a way around it.
I worked our testing out, and our checksum activity worked through around 1.2TB per hour (per re-protect direction).
There is an unsupported work around to the time of re-protect though, which was given to me by VMware Support, with the caveat that it "should technically work, but is unsupported. If you cannot wait for SRM and VR to complete their work through their processes automatically, you might consider the following steps - note that this is unsupported by VMware though and I accept no liability for these steps:
Dear Team,
Any guess for this query mentioned below?
When I am logged in to VMware SRM, > Recovery Group > Related Objects > Virtual Machine
"Status Modified By" tab is showing blank for only few Virtual Machines. Whereas it showing RG name in other VMs. I have attached screenshot.
SRM Version - 6.5
SRM Server Build - 8946135
Can anyone please suggest.
I am having issues running the SRM environment variables such as :
VMware_RecoveryMode and VMware_VC_Host.
I want to know how to apply these to scripts like in a if and else statements.
So if i pass the variable via echo and run it in a step in a recovery plan it works so the script is called testrun :
echo %VMware_RecoveryMode% >> D:\scripts\MES\logs\logfile.log
and so when i add a step in the recovery step to the location of this script like :
C:\Windows\System32\cmd.exe /c d:\scripts\MES\Testrun.bat
It runs fine when i run a test as it outputs test in the log fils.
But now when i run this variable in a script with the if and else statements when doing a test recovery it does not work. So an example of the script is :
If "%VMware_RecoveryMode%==test"
echo %VMware_RecoveryMode% >> D:\scripts\MES\logs\logfile.log
This fails in a recovery plan. I have tried various combinations of if syntax with quotation marks, brackets, and then commands, but it keeps failing.
Has anyone used these variables in scripts and made it to work, can anyone send a sample of a working script.
Thanks
Hi, Is there anyone saw this error message while running the recovery pla ? I am using SRM with vSphere replication and while Test recovery.
- Tired with same network both site
- Tired with Isolated network (auto created)
I am able to resolve it.
VMware.VimAutomation.Srm Updated.. Thank You Google!
After installing SRM, I can't seem to locate the database in SQL and I am certain I selected my odbc connection. Is it possible to find the database location through the registry?
Hi,
you can find the DSN that you use during the installation in the registry. You should look into HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware vCenter Site Recovery Manager, InstallDsn contains the DSN used during the install. After that open the ODBC Data Source Administrator(System DSN) and look for the DSN that is from the InstallDsn registry key.
Hope this helps,
Daniel G.
I have same issues when installation SRM 8.1. after trial and error, im tried during the installation process I prefer to use a domain login rather than local to start up service srm. Then success
Hope it help
Hi,
It is old topic but I have the same case now for some customer.
your plan seems to be ok when vCenter is connected to the same domain like before migration (i think name of connected vCenter is in database)
what in case we have to change domain for two components vCenter and SRM?
First we change domain for vCenter (do you hae action plan for it?)
is it possible to edit connected vCenter in SRM?
Yes, it means the placeholder at the remote site for the VM being protected at the source site is missing. Why is it missing? Dunno. What have you done to cause this?
well before running the test i found those vmswhich are part of protection are recovered and showing in DR .
there was no option to clean recovery as it was greyed out so it means they were recovered manually by someone .as it shows in events,
so i thought of removing it from inventory to start test again .
can yu suggest how i can get it back in placeholder datastore .
one option i am thinking to cretae protection group again and then recovery plan .this way it will create vms in placeholder datastore .
can yu suggest something on it.
Support is wrong about those steps helping speed things up. The time would be exactly the same (plus the additional time to do those added on steps) as that is exactly the same process that VR goes through when you run a reprotect (it uses the previous source VM as a seed and calculates the checksum difference between the source and target). When you run a reprotect (or when you use a seed) the disks are not copied over the WAN, only changes/differences are.
The checksum time is as long as it is not because VR doesn't use CBT (it uses a light-weight delta mechanism to track changes which is better suited to it's purpose than CBT), rather it is because VR doesn't currently have a way of recognizing that it is reprotecting (using something that should be almost exactly the same) vs. using a seed (something that could have some things the same and potentially a lot different). That is something we're working on though.