Start a Conversation

Unsolved

This post is more than 5 years old

B

3182

June 23rd, 2016 08:00

RP4VM: Seeding with "Manually select an existing VM to use as the copy VM"

In RP4VM, when configuring protection, there is an option called "Manually select an existing VM to use as the copy VM".  I presume this allows a customer to "seed" the initial VMDKs at the DR Site ahead of time (via Sneaker Net or FedEx, or whatever method is best).  I tried this in my lab and it seems to trigger an "Init" operation, which seems like a full sync, which would defeat the purpose of an initial seeding.  Can someone confirm whether this is the expected behavior, or if there is a way to see exactly what is happening behind the scenes?  Or, is there a different preferred method to handle the initial seeding?

Thanks,

Bill

2 Intern

 • 

143 Posts

June 23rd, 2016 08:00

Thanks Rich.  Does EMC provide any documentation on the CLI procedure to perform initial seeding without doing a full Init?  We have a lot of customers with 15 TB+ of data, and don't want to perform the initial sync over the WAN, so I want to get a good idea as to the official seeding procedure.  Thanks,

Bill

2 Intern

 • 

1.1K Posts

June 23rd, 2016 08:00

Hi Bill,

The manual replica VM selection option is an alternative to the Automatic provisioning option. Yes you could seed the VMDKs and potentially avoid the init via a specific CLI based procedure. The start transfer option on the summary page of the protect VM flow (default is to transfer), initiates the init.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: +44 (0) 7730 781169

E-mail: richard.forshaw@emc.com

Twitter: @rw4shaw

EMC Europe Limited

Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.

2 Intern

 • 

1.1K Posts

June 23rd, 2016 10:00

There is nothing stated in the RP4VMs documentation mainly because the activity is a dangerous one, however the stepped procedure would be as follows:

- Protect the VM(s) as part of a new CG. Do not allow start transfer.

- From the CLI, use the clear_markers commands which forces RP to avoid the full init on the basis that the source and replica VM(s)/VMDK(s) are identical – clear_markers group=xxxxxx

- Start replication by starting the transfer from the RP4VMs plugin or via the CLI using start_transfer group=xxxxxx

- The CG will move to an Active state immediately but avoid a full init although you may see a short init.

- Use Test Copy to check the integrity of the replica VMs.

Let me know how you get on.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection and Availability Solutions

EMC Europe Limited

Mobile: +44 (0) 7730 781169

E-mail: richard.forshaw@emc.com

Twitter: @rw4shaw

EMC Europe Limited

Registered in England with Company No. 00990752 Registered office address: Level 1, Exchange House, Primrose Street, London C2A 2EG

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited.

18 Posts

April 8th, 2021 02:00

Hi,

I would re-open this post because we have a similar question but we have upgraded RP4VM to latest version (5.3.SP1.P1) and we can't create a CG without start it.

Is there a procedure to create a CG without initiating the transfer?

Thanks

18 Posts

April 8th, 2021 04:00

Hi 

maybe I have written a wrong question.

I have installed a new rp cluster (not upgrade) and I have the vm1 in both environment (prod and dr).

Obviously we haven't any journal and we have to create a new CG.

The VM1 in the dr's site is oldest than vm1 in production's site about 2 weeks.

Can I seed the vm1 from the production site? 

In the procedure mentioned in this post, I don't see a full sweep after the seeding...is it normal?

I'm little bit confused

Moderator

 • 

9.2K Posts

April 8th, 2021 10:00

Hi,

This should work, but it would be better to finish the setup of the CG. https://dell.to/3acbStV

675 Posts

April 11th, 2021 10:00

Hi @Mutis2019,

There's a full sweep when using pre-configured/existing replica VM as RPVM reads the prod and replica, compares them and replicates only the difference. It's certainly advantageous to pre-seed, especially in poor WAN conditions.

 

Hope that helps,

Idan 

No Events found!

Top