Recovery plans

Similar Questions

• PowerCLI 5.5 R2 and SRM - how to check the status of a Recovery Plan?

  I need to write a script that will examine the current status (apparently called a "RunMode") of a Recovery Plan, is the appropriate status (1 = Test, 3 = cleaning), then get a list of all virtual machines in a suitable specific folder and they will light up (wait 15 seconds between move them on to the next). There are reasons why the Recovery Plan cannot be responsible to do, so why do I need to write a script (the reasons have nothing to do with PowerCLI). And I have problems with the first part, determination of status.

  I have this (I won pretty well most of this pure and simple of the blog of Ken Werneburg. Thank you, Ken!) :

  $DR_vCenter = "xxxxxx".

  $SRM = connect-SrmServer-Server $DR_vCenter

  $SRM_API = $SRM. ExtensionData

  $PlanMoRef = $SRM_API. . Moref Recovery.ListPlans () [2]

  (My plan is #2, others their test plans. I checked this by looking at the name of each plan. And all the good things I want is in this 'moref,"apparently...)

  $HistoryMoRef = $SRM_API. Recovery.GetHistory ($PlanMoRef)

  (it's the history of the races of this plan. Here it is the story of the last race)

  $HistoryMoRef.GetRecoveryResult (1)

  
  

  Key: 68835

  Plan: VMware.VimAutomation.Srm.Views.SrmRecoveryPlan

  Name: Recovery_Plan_PHA

  Description:

  StartTime: 15/07/2014 11:03:15

  StopTime: 15/07/2014 11:09:29

  ExecutionTimeInSeconds: 374

  TotalPausedTimeInSeconds: 0

  ResultState: success

  RunMode: CleanupTest

  WarningCount: 0

  ErrorCount: 0

  SO: I understand how to get the history of the plan that I want, and it's more progress. The problem I have is that if the RunMode is a specific value (either "Test" or "Failover", then I need to launch other actions (power of virtual machines.) And I can't seem to do. «$HistoryMoRef.GetRecoveryResult (1).» RunMode"is empty return. I don't know how it is that the value of "CleanupTest".

  How can I query the RunMode, to see if it is a value which I am interested in?

  $HistoryMoRef.GetRecoveryResult (1) | GM

  
  

  TypeName: VMware.VimAutomation.Srm.Views.SrmRecoveryResult

  
  

  Name MemberType definition

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

  Equals method Boolean Equals (System.Object, obj)

  GetHashCode method int GetHashCode()

  Type of the method GetType GetType()

  String the ToString ToString() method

  Description property System.String Description {get; set ;}}

  ErrorCount property System.Int32 ErrorCount {get; set ;}}

  ExecutionTimeInSeconds property System.Int64 ExecutionTimeInSeconds {get; set ;}}

  Key key of System.Int32 property {get; set ;}}

  Property System.String name {get; set ;}}

  Plan of property VMware.VimAutomation.Srm.Views.SrmRecoveryPlan {get; set ;}}

  ResultState property VMware.VimAutomation.Srm.Views.SrmRecoveryResultResultState ResultState {get; set ;}}

  RunMode property VMware.VimAutomation.Srm.Views.SrmRecoveryPlanRecoveryMode RunMode {get; set ;}}

  StartTime property System.DateTime StartTime {get; set ;}}

  StopTime property System.DateTime StopTime {get; set ;}}

  TotalPausedTimeInSeconds property System.Int64 TotalPausedTimeInSeconds {get; set ;}}

  WarningCount property System.Int32 WarningCount {get; set ;}}

  Thank you

  Well, I managed to reproduce the problem and to understand what might happen.

  First the error "you can not call a method on an expression evaluated to null." seems to be linked to the "Write-Output"PG ="$pg" line. When I remove the error to go away (I'm not a person of PowerShell so don't know why this is the case).

  The second error (not not being filled seems to be linked to how they make the connection virtual computers SRM.) Specifically, you will need to establish the connection of VC and then do SRM login without specifying the SRM server, let that be determined by searching the SRM recorded with the VC you are connected to.

  The following code worked in my environment when it is connected to the protected so site full of hope that it will work for you as well:

  SE connect-VIServer-Server $protectedSiteVC - user $user-password $pass

  Connect-SrmServer-user $user-password $pass

  Write-Host "implementation details on Protection groups.

  Get-ProtectionGroup | {ForEach-Object

  $pg = $_

  Get-ProtectedVM - ProtectionGroup $pg} | {ForEach-Object

  #Write - Output 'do for each virtual computer.

  $output = "" | Select VmName, PgName

  $_. Vm.UpdateViewData)

  $output. VmName = $_. Vm.Name

  $output. PgName = $pg. GetInfo(). Name

  $output

  } | Format-Table @{Label = 'Name of the virtual computer'; Expression = {$_.} VmName}}, @{Label = 'Protection Group name'; Expression = {$_.} PgName}

  }

• Site Recovery Manager - Import/Export of recovery Plans

  Hello world

  I have a few questions about SRM:

  1. what SRM version supports the export of stimulus packages to the formats xml, doc and html? Y at - it a Composite indicator advanced to do the same thing?

  2. is it possible to import script of stimulus plans?

  3. when the recovery plans reside? SRM DB or vCenter?

  4. is it possible to generate scripts an automatic failover on the disaster without administrator intervention? As in without clicking any button?

  5. is there any limitation to the distance between the site of production and recovery site, for synchronous and asynchronous?

  6. the SRM 5.5 is compatible with vSphere (5.1.2)?

  Thank you very much for your answers

  Kind regards

  Ritu

  Export of "No recovery plan" is available even in SRM 5.1 but it cannot be imported back so that it is not repeated import/export plan that you expect. I expect the same year. Export of the stages of recovery plan is good for the documentation of DR but not for PR backup and restore.

  To be honest I don't have a hands-on experience with 5.5 but I don't see anything about importing in the documentation so I expect same behavior as in 5.1.

  Just my $0.2

• Types of SRM recovery plans

  Hi, I use vSphere 5 and have an obligation to SRM of Set - up for a handful of virtual machines (about 10). I think to implement a unique restoration plan, the Group of protection... etc.

  Can anyone in detail why 1 > stimulus package will be useful? that is the test cases in different scenrios or DR.

  I guess a single RP can fit for all purposes, but have heard that it is not advisable and want more details of the types of recovery plans.

  Thank you

  Hello

  For a small enviromnent like what you describe, I don't think more than a PR is necessary.

  As Chris said, nn more often by RPs application is created.

  Much less common, but the RP may be based on certain parts of the infrastructure (by Bay RP, RP for specific server room).

  P.S. good point about real DR / Migration scheduled, but it is more difficult to manage, because you need to make any changes twice to keep both RPS in sync. In addition, you will need to test both of them to make sure that everything works as expected.

  Michael.

• After execution of the recovery plan, the Test is greyed out

  I missed successfully test on 2 virtual machines running the recovery as part of our POC plan.  I have powered down VMS protected and recovery, initiated a resynchronization on the volume of SnapMirror and intend to continue to use the same recovery plan for additional tests.  However, the Test option for the recovery plan is dimmed (Run option is still available).  What I need to remove the stimulus plan and recreate a whenever I run a Run and not a Test?  It is a chore because I need to re-add the customizations (messages, orders), update priorities and so on.  I use SRM v4.1.1.

  Hello

  You need to re - create groups of Protection that is pushed. Stimulus plans do not need to be re-created, but you will need to reconfigure to include recreated protection groups. All customizations related to virtual machines (priorities, orders, customizations) must be configured again.

  It was a case in the 4.x versions, don't think that changed in 5.0.

  Michael.

• SRM 4.1 - steps in Test of Recovery Plan and DR Mode

  Hi all

  Whilst running the SRM Recovery Plan, I need to start two different handwritings (doing different things), depending on whether the plan is executed in testing, or fashion DR.

  Is it possible according to the operator to input (like "choice Y/N - is this a test?"), or do I have to build two separate Recovery Plans, one for testing, the other for the actual failover?

  Kind regards
  Radek

  If you add a step in order to stimulus package to run a batch file, for example

  c:\windows\system32\cmd.exe /c c:\srm_scripts\myscript.bat

  And then in the batch file, make sure the variable % VMware_RecoveryMode %.  If it is set to the recovery, it is running in recovery mode, if it is set to be tested is in testmode for example to run a script PowerCLI different depending on whether it is running a true recovery DR or a trial, but what follows in the batch file, where myrecoveryscript.ps1 is the script of PowerCLI is running in recovery mode and mytestscript.ps1 is PowerCLI script to run in test mode :

  If % VMware_RecoveryMode % == "recovery" powershell - PSconsolefile "C:\Program Files (x 86) \VMware\Infrastructure\vSphere"-command "c:\srm_scripts\myrecoveryscript.ps1".

  If % VMware_RecoveryMode % == 'test' powershell - PSconsolefile "C:\Program Files (x 86) \VMware\Infrastructure\vSphere"-command "c:\srm_scripts\mytestscript.ps1".

• recovery plan. Mount LUNs for VM

  Hi all

  I'm new to SRM, help me please,

  I have DS4800 and mirror lun with the VMFS and mirror lun with data (sql2008).

  In my recovery plan, I need map LUNs with SQL data and run SQL VM. How can I do this?

  THX!

  Hello

  I did some tests today. Works perfectly.

  I tried physical and virtual RDMs and SRM has done all the work.

  In addition, Windows (2003/2008) acknowledged and turned up the same drive letter.

  Good luck

  Michael.

• Recovery plan test failed - a file is not found error

  Hi all

  Finally, I got my SRM environment installed a few days ago and made a small test with 2 VMS successfully recovery plan. Today, we run a new trial with 18 virtual machines of low priority and everything went smoothly until after 15 minutes, the process failed with the error "file not found" turn on/off the virtual machines on the remote site.

  Basically, we have 1 EMC Clariion each site with mirrorview which have been configured after EMC VMware Site Recovery Manager with EMC CLARiiON CX3 and MirrorViewS implementation and MRS. 1.0 Guide. We have detected that the snashot created recovery Clarrion is placed to the right of the active state after the beginning of the trial, but after 15 minutes later he returned to Inactive.

  Other research showed me that the error that gives me the recovery plan test is correct given that the snapshot is no longer active and all files in the virtual machines (VMX and VMDK) that the SRM tries to light are on the snapshot.

  Any of you have seen something like that?

  

  Thanks in advance.

  Saludos/looks

  Nicolas Solop

  Buenos Aires, Argentina

  -

  ---

  Mi empresa

  En mi perfil LinkedIn

  Grupo de Virtualizacion en Español of Linkedin

  -

  ---

  Hello

  Our best practices for configuring CLARiiON SnapView, which copies itself on the first point of entry in the catch instant times the volume of production is to distribute between 20-30% of the production LUN for the RLP LUNS box

  Regarding your volume of 300 GB of LUN LUN Pool reserved (and you might need more than one - that is to say if you have a consistent snapshot that includes multiple LUNS it will add ot the space required)-you should provide at least a 30 GB, otherwise a 60 GB LUNS in your region Reserved LUN Pool

  I would try to increase the RLP LUNS for this kind of size and try again

  Concerning

  Alex Tanner

• Citing a Recovery Plan without breaking replication

  Hi people,

  Small question just to make sure that I'm heading in the right direction. We have implemented the SRM and the customer wants to test it. They want to avoid having to reconfigure the replication and SRM failback. I was wondering, if we used a Recovery Plan tweaked in Test mode to connect VMs DR Live network down there after the tension Production virtual machines, would be that us allow you to test the recovery plan? They are happy to be scrapped all changes to the virtual machines while they are running in DR that day there (weekend). In theory this would allow us to complete the Test of Recovery Plan, to destroy DR VMs and can back up virtual machines in Production?

  Would this work?

  Thank you

  Mike

  Yep, I get from you. You cannot change the 'bubble test' to be one of VLAN real on the recovering site.

  Like many, I understand, test tip is just there to protect you against accidental conflict of IP/hostname... It is not mandatory and can be changed...

  Of course if you do - you will need to make some efforts to stop conflicts you may have...

  I think you should be able to hard without the routine of failback test - but you have to manual handle side storage... which makes recovery volumes, secondary to the site once again - and ensure replication of the protégés of recovery is restored again. A hard run does not affect your protected site, except turn off the protected site of VMS in order according to the recovery plan.

  I have to say I never tried this - someone from VMware can back me up here?

  Concerning

  Mike Landry

  RTFM education

  http://www.RTFM-ed.co.UK

  Author of the book of MRS: http://www.lulu.com/content/4343147

• Create the Recovery Plan

  Hello

  I install SRM for the first time. It is with the 1.0 1.0.1 update 1 Patch 3 (build 154949) is installed. I have the software installed and configured. The reproduction of painting works and SRA can communicate with the hardware. My VMs are on the LUN replcated. I have implemented the Protection Group and you can see the dummy VMs on the remote site of the network and the correct resource pool. Everything is good so far...

  Of course, the next step is to implement a Recovery Plan. When I run the wizard, I stop at step 2, there is no group of Protection listed for me to choose. What I'm negliecting to do! I don't see the error messages, which leads me to believe that miss me a step somewhere I followed the Administrator's guide.

  TIA,

  Julian.

  Even if you create a protection group using the vCenter and SRM server on the side of your protection, you create a recovery plan in the vCenter Server where it will be executed.  If you need to connect to the Server vCenter site recovery to create a recovery plan for your production VMs - looks like you might be connected to the protection Server vCenter Server-side.

  When you try to create a plan for relief on your protection server side, SRM believes you want to retrieve the virtual machines that run normally on the remote site.

  -Jon

• Run Recovery Plan - turn off virtual machines to the protected Site?

  Hello

  Pretty silly question here...  I read that when you run the Recovery Plan SRM will equip all virtual machines protected on the protected site.  Is this the case?

  Thank you

  Dave

  Exactly.  In this case, workloads on the recovering site absolutely remains lit throughout the entire test or recovery.

• Issue of SRM Test Recovery plan

  Hello

  We have two sites with hosts 5.5 ESXi and vCenter 6 and 6 SRM installed and configured on both sites. We use IBM midsize v7000 storage on both sites. I configured SRM with array based replication. Everything seems fine, but when I run the plan of recovery in recovery of test mode, it generates the error on the stem 4;

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

  Cannot create snapshots of the replica devices.

  Cause:

  Failed to create the snapshot of the consistency group replicates Test.

  Cause:

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

  Cause:

  Replication may have ended because of a previous failover operation.

  Refer to IBM SAN Volume Controller troubleshooting

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

  Home is also the snapshot. Please, no matter what advise how to solve this problem.

  Thanks in advance...

  Try to delete the file THAT SRA-STATUS located in C:\Program VMware vCenter Site Recovery Manager\storage\sra\IBMSVC and then refresh/rescan your picture frames.

• How to migrate the production to the server in recovery planning disaster?

  We use planning 11.1.1.3 Oracle repository. Currently our name of the DR Planning Application is different from the production name and Windows of the DR server names are different from Production. Otherwise, any other configuration even.
  
  How to migrate production planning to the recovery server disaster? We stopped planning on DR server. Then we exported repository Oracle of production planning and it imported in DR Planning. We restarted Dr. DR planning planning seems to work very well, but I'm afraid to click on "Refresh planning" DR Planning - it can update the Production Server. So, how can I be sure that DR and Production planning are disconnected?
  Is there something we need to do? This method seems to be faster than the migration with LCM.
  
  Published by: Essbase Fan on October 18, 2010 10:11

  You must go about it the right way, if you migrate all planning an application, I agree that it is a safer and faster way.
  The essbase connection information is stored in the planning system database/schema, so as long as you have not migrated that then you should be good to refresh.
  To put your mind at rest, connect to the planning application and change the source of data associated with the application and then you will see where the essbase server is that it's going to update.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Storms RS of recovery Plans and start

  Hi, I work on the stimulus package for a large number of servers. I am aware that the phase of assignment IP address can cause a storm to start on our environment (MRS. 5.5.1) and thus increase the overall reboot for servers recovered time.

  I can introduce a delay between groups of priority or protection groups in order to reduce the effect of storm boot?

  TIA, Derrick

  Are you really the problems in your recovery with SRM currently infrastructure?

  Assuming that you hit the questions then take a look at recommendations for environments on a large scale as a guide to how you can change various settings of recovery to increase the flow rate-> change the settings to run large environments Site Recovery Manager

  I would recommend you first reference to try to see where you hit the questions and then subsequently take a methodical approach to optimize configuration settings appropriate to your environment and of course to validate the effect of the change later.

• SRM with virtual disks not replicated RDM Recovery Plan.

  We try to do a test of SRM with a Virtual Machine that has disks Virutal RDM attached, however these volumes are not replicated with RecoverPoint, they exist already on the side of DR, so basically we're already reproducing machine virtual and it's virtual disks, but these 3 RDM are outside it.  The reason for this is because they have massive volumes that had previously been replicated using another product before virtualize us and there is no need to replicate this info again because the volumes are never going to change.

  
  Then...

  It is done within the SRM, when you look at tab groups protection, we see a warning "not configured VMs: 1" because SRM / RecoverPoint believe that this virtual machine has volumes that are not replicated.

  Is there any way to exclude this or saying SRM to ignore what we will manually add the RDM on the DR side ourselves?  Also on the side of DR, I don't see the VM under hosts and Clusters as I see the replication of other virtual machines, it is because MRS. think he isn't entirely reproduced?  Or is it a manual step where you need to create a virtual machine on the side of the DR and to disable this option in order to see it?  Also, we see what VM listed on the virtual computers tab for this group of special protection, but the other two VMs residing on the sam MON appear and I already tested successfully the two machines.

  Here are the settings in the file for the RDM .vmx

  scsi0:4.filename = "server_3.vmdk".
  scsi0:4.mode = "persistent".
  scsi0:4.ctkEnabled = "FALSE".
  scsi0:4.DeviceType = "scsi-disk" hard
  scsi0:4.present = 'TRUE '.
  scsi0:4.redo = «»

  scsi0:5.filename = "server_4.vmdk".
  scsi0:5.mode = "persistent".
  scsi0:5.ctkEnabled = "FALSE".
  scsi0:5.DeviceType = "scsi-disk" hard
  scsi0:5.present = 'TRUE '.
  scsi0:5.redo = «»
  scsi0:6.filename = "server_5.vmdk".
  scsi0:6.mode = "persistent".
  scsi0:6.ctkEnabled = "FALSE".
  scsi0:6.DeviceType = "scsi-disk" hard
  scsi0:6.present = 'TRUE '.
  scsi0:6.redo = «»

  Hello

  You do not see the DR VM (usually it's called shadow or the space reserved VM), because currently the VM is not protected by SRM. You can't manually create.

  What you can do is run the Wizard "To configure Protection" for your virtual machine. One of the steps, "storage options" or something like this, allows you to select specific disks and mark as detached, allowing you to protect the computer with disks not replicated virtual.

  Michael.