Better Together: RecoverPoint for Virtual Machines and Fidelity & Guaranty Life

As data growth increases, so does the need for companies to separate themselves from their competition. Fidelity & Guaranty Life “competes with firms offering similar products, so we need to differentiate by processing customer applications faster and running our business 24×7” according to Jeff Sabid, Director of IT Infrastructure. A power outage knocked IT systems offline for hours, and as a result F&GL was unable to process customer orders. This outage was detrimental to business, ultimately costing F&GL tens of thousands of dollars.

After replacing the Commvault System that caused this multiple hour outage, F&GL implemented a Dell EMC Data Protection software solution that would substantially increase efficient availability for business critical applications and workloads. This industry-leading solution provided an unparalleled impact. It not only positively impacted the business, but it also eliminated many of the complexities and time-consuming administration tasks.

F&GL uses Dell EMC RecoverPoint for Virtual Machines and Data Protection software to protect 200 VMs between data centers in Virginia and Texas. “With RecoverPoint for Virtual Machines, we’ve reduced our outage window from hours to minutes. That assures we can keep making money and serving customers during an outage or DR test” says Sabin. The concept of DR has shifted—they are now able to move virtual workloads between data centers with just a few clicks. Not only is the solution easy to use, it also requires minimal training. As a result, it frees up time and resources for the Data Protection IT team, allowing further focus on strategic projects that increase sales. With Dell EMC’s RecoverPoint for Virtual Machines, F&GL was able to save money, make money, and mitigate risks.

Dell EMC’s Data Protection solutions coupled with the Future-Proof Loyalty Program is what truly makes customers comfortable choosing Dell EMC. “Dell EMC’s Future-Proof Loyalty Program goes well beyond what most technology companies provide. Dell EMC has been listening to their customers” says Sabin. Satisfaction guaranteed for 3 years across storage, data protection and HCI appliance customers.

For Fidelity & Guaranteed Life, the peace of mind is invaluable.

Related:

Easy, Economical Cloud DR to AWS with RecoverPoint for Virtual Machines

The most recent RecoverPoint for Virtual Machines v5.2.1 release, adds the capability to protect VMs directly to AWS S3 object storage, using proprietary snap-based replication, with RPO that can be measured in minutes. This blog recaps the capabilities that Cloud DR 18.4 unlocks for Recover Point for Virtual Machines. RecoverPoint for Virtual Machines works with Cloud DR to protect your VMs by replicating them to the AWS cloud. Replicated data is compressed, encrypted, and stored as incremental snapshots on Amazon S3 object storage. You can set parameters around the snap-replication policies for reliable and repeatable Disaster … READ MORE

Related:

RecoverPoint for Virtual Machines – Unable to create copy VM

Article Number: 503056 Article Version: 3 Article Type: Break Fix



RecoverPoint for Virtual Machines

When Protecting a new VM we were unable to create copy VM and CG remains in Disabled state.

Error viewed on Target Vcenter when trying to deploy OVF template shown as below:

“This operation is not allowed in the current state of the datastore”

error screenshot:


Symptoms found in logs:

DR_RPA/files/home/kos/connectors/logs/connectors.log

2017-08-08 22:23:41,272 [pool-4-thread-1] (CreateNewVMAction.java:227) ERROR – Failed creating new vm: AMRNDHL1038.copy, error msg: The operation is not allowed in the current state of the datastore. (com.vmware.vim25.InvalidDatastoreState)

2017-08-08 22:23:41,281 [pool-4-thread-1] (BaseAction.java:34) ERROR – CreateNewVMAction Failed.

2017-08-08 22:23:41,283 [pool-4-thread-1] (BaseCommand.java:59) ERROR – Command failed: CreateNewVMCommand(ID:2015901748783485597) took: 2161

2017-08-08 22:23:42,236 [pool-5-thread-1] (CommandState.java:80) ERROR – Command Exception:

2017-08-08 22:23:42,523 [pool-6-thread-1] (CommandState.java:80) ERROR – Command Exception:

2017-08-08 22:24:17,283 [pool-4-thread-2] (CreateNewVMAction.java:227) ERROR – Failed creating new vm: AMRNDHL1038.copy,

When trying to deploy the copy VM on DR Vcenter it fails due to Datastore state checks.

Protecting new VM and trying to deploy new copy VM at Target side vCenter.

Free some space on the Target Datastore will allow the deployment of new VMs at target vCenter.

Related:

RecoverPoint: ScaleIO Initialization not moving, host crash or stuck on highload

Article Number: 503004 Article Version: 3 Article Type: Break Fix



RecoverPoint,RecoverPoint CL,RecoverPoint EX,ScaleIO Product Family,ScaleIO Software

IOs to offsets greater than 1T are causing a short init on the CG. Host crash/stuck on high load.

Symptoms found in the logs:

ScaleIO host logs:

sdw1 kernel: attempt to access beyond end of device

sdw1 kernel: sdr: rw=33, want=2147483736, limit=1967000000


OR

sdw4 kernel: NMI watchdog: BUG: soft lockup – CPU#40 stuck for 22s! [splDataPathExec:97896]

localhost kernel: INFO: task dd:3540 blocked for more than 120 seconds.

Splitter logs:

sdw1 kernel: 4967/4967: RPS:#0 – spl_kbox_end_io : offset = 2147483704, len = 16384, MajorMinor(65, 16), error status = -5

sdw1 kernel: 1351/1351: RPS:#1 – CommandIoSplit_KboxEndIo: Immediate MOH is true. Moving to Tracking. vol guid=0xe102395df73e4b67

RPA (Storage):

st_handle_write_atio: huge write !!! len=1048576 max_chunk_len=524288 (in bytes), ox_id=0x16, cd_remote_entity_id=0x6bca7c6343a4ccca, vlun=0x2c2d8

Splitter type(s): ScaleIO Splitter

Affected versions: 5.0.1, 5.0.1.1, 5.0.1.2

Splitter has no limitation on number of inflight IOs. Splitter’s RPA IO timeout flow is wrongly handled. Historically RPA supports IOs to addresses up to 1T.

Workaround:

None

Resolution:

Dell EMC engineering is currently investigating this issue. A permanent fix is still in progress. Contact the Dell EMC Customer Support Center or your service representative for assistance and reference this solution ID.

Related:

Re: RecoverPoint for vm on different site but same Vcenter

Hi there,

Just to reiterate, as Rich stated, they can deploy a single vRPA cluster which would allow them to do local replication and RPVM doesn’t have any issue with replicating to RPVM clusters within the same vCenter (and ESX cluster).

That said, If they need a DR solution, it would be recommended to configure 2 RPVM clusters w/ remote replication. Finally, it would be recommended to protect vCenter with vCenter HA as vCenter is a management SPOF and if production site failure causes vCenter failure then management of the secondary site would be impacted, unless vCenter HA, which RPVM fully supports, is deployed.

Regards,

Idan Kentor

RecoverPoint Corporate Systems Engineering

@IdanKentor

Related:

Re: Does ViPR controller support the last version of VMware Site Recovery Manager 8.1

Hi JYD,

Sorry it took so long to answer your question, but this DECN page is for Vipr Controller, and while you might think that Vipr SRA and Vipr SRM would be supported by the same teams, they are actually supported by different teams!

Vipr SRA is supported by the EHC team, so I reached out to them and got the following info.

This is the short answer to your question:

  1. VMware vSphere supports SRM 8.1, but EHC does not.
  2. Vipr SRA is only used in EHC environments…
  3. So Vipr SRA is not currently supported with VMWare SRM 8.1…but an RPQ can be submitted for both EHC and Vipr SRA

This is the full info I got from the EHC team:



Please take a look at the EHC ESSM here:

https://elabnavigator.emc.com/vault/pdf/EHC_4.1.2_SSM_01.pdf?key=1543338304483

The latest supported SRM version is 6.5.1 build 6014840, though vSphere supports it EHC does not, also if 6.5.1 is to be used then the following is also true:

Dell EMC ViPR SRA 5.0.5.163 5.0.5.174 Vulnerability fixes / component support (requires RP 5.0 & ViPR 3.6.2.x). IMPORTANT see note a/b) below

Footnotes: a) For SRM DR – Recoverpoint 5.0 support requires ViPR 3.6.2 and the updated SRA 5.0.5.174 to use with vSphere 6.0/SRM 6.1.2 please file an RPQ to evaluate support criteria. If not using SRM DR ViPR 3.6.2 can be used with any other configuration or EHC update release.

Footnotes: b) All components are supported under either vSphere 6.5 or vSphere 6.0 with the exception of SRM DR (Site Recovery Manager based Disaster Recovery) – the EHC Update 3/Update 4 modules are not compatible with vSphere 6.0 & SRM 6.1.2 due to API changes made to support vSphere 6.5/SRM 6.5.1 – if you wish to use EHC Update 3/Update 4 code you MUST UPGRADE to vSphere 6.5/SRM 6.5.1 (See revision 6 above).

Please take a look at the ESSM, this is the official support document for EHC if anything falls outside of this then an approved RPQ will be required for support, please also remember that the ViPr SRA version needs to also be within supported scope as well.. VMware vSphere supports SRM 8.1, EHC does not.. hope this helps.. The ESSM is a customer consumable document and provided for this purpose. I have also attached a copy to this email string as well.



I hope this helps answer your question!

Jay F

Related:

Re: RecoverPoint for VMs Alerts

Yes, do this first and as per your original request then configure your alerts/events.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer – RecoverPoint & VPLEX (EMEA)

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: 44 (0) 7730 781169<tel:44%20(0)%207730%20781169>

E-mail: richard.forshaw@emc.com<mailto:richard.forshaw@emc.com>

Twitter: @rw4shaw

Related:

Re: RecoverPoint Licenses

Hi there,

Yes, you’ll need an EX or CL license as SE is limited to 2 clusters and one array per cluster.

Also, if the installation type is SE (when there are VNX arrays), then conversion using Deployment Manager to RP classic would be required before the license is changed.

Hope that helps,

Idan Kentor

Sr. Principal Product Technology Engineer – RecoverPoint and RecoverPoint for VMs

@IdanKentor

idan.kentor@emc.com

Related:

Re: Can not undo writes when enable access during recover production(RP4VM)

Hi,

Enable Direct Image Access is disabled intentionally in Test a Copy and Recover Production as well as failover as these recovery operations cannot be performed while there’s direct image access. Direct IA cannot be executed only through the Test a Copy Wizard. Same for Undo Writes, although might be perceived as a legitimate operation for all recovery operations, it’s a known issue. As a workaround, undo writes through Test a Copy and then use the current image when proceeding to any of the other wizards.

Regards,

Idan Kentor

RecoverPoint Corporate Systems Engineering

@IdanKentor

Related:

Re: No IP connection between RPA and VNX/CLARiiON array

Hi All,

After changing the login credentials on a VNX array, the RecoverPoint started complaining about the IP connection between the RPA and the VNX array.

RPA 4.1.0

VNX Block-05.32.000.5.221 File-7.1.80.7

I found an article in the support site (Knowledge Base Article: 000470762), which says I need to detach all RPAs from the cluster make changes to the globalsystemconfig.XML file and then reattach the RPAs back.

I have few questions:

What are the risks involved in doing so?

Also will I loose the journals and therefore the bookmarks.

How long resync time I am looking at? The entire data is about 50TB and the link is 400Mb/s between the two sites.

Thanks.

Bobby

Related:

  • No Related Posts