Testing Replica (B&R 6.0 and later)

[foggy]

Hi Bernard,

1. Please see above for the replica testing procedure.
2. In case of re-IP, you'd need to adjust your DR network by modyfing DNS entries during a failover, so you can reach the servers with their new addresses.

[kevin_cambs_uk]

Afternoon, very simple question

We replicate a few VM's to our DR site.

We occasionally start these up just to ensure they work, but we never use them in live, as they are for DR, so they start up, we log in and just give a quick sense check then shut them down. What happens in terms of any writes to these machines , or is this not the best way to do this?

Thanks Folks

Kevin

[foggy]

Hi Kevin, all the changes performed while replica VM was up are discarded during the next job run.

[kevin_cambs_uk]

That great mate, much appreciated. Sorry for the double post I was not sure where the first one went!

[That guy]

I was wondering if I made changes to the OS of a replica (installing a program or update) would the next replication change all of that? Or would I have to roll back to a previous snapshot restore point to erase those changes?

Thanks

[DGrinev]

Hi,

No worries, all changes you made to replica VM will be discarded during the next job run.
Please review this thread for additional information. Thanks!

[sze]

I have a replication job.
Replica VM was powered on manually, and wrote to.
Can I continue with the existing replication job after shutting down replica VM manually?

[foggy]

Yes, the changes occurred while the replica VM has been on will be discarded.

[sze]

Ok. Good to know the replica can be used later. Thank you so much for helping!

post10941.html?hilit=replica%20testing#p10941
I read from this forum that
Testing replica with Veeam is really easy:
- Disable the Veeam replication job temporarily
- Use VMware Infrastructure Client to create snapshot on replica (so that VMDKs do not change during the testing, and you can continue replicating)
- Use VMware Infrastructure Client to edit replica VM configuration and change VLAN from production to test network
- Power on replica VM with VMware Infrastructure Client, and see if it can boot up properly
- Shutdown replica VM
- Use VMware Infrastructure Client to discard replica snapshot (to revert replica to original state, as before the testing)
- Enable the Veeam replication job back

Are these steps still valid & I can use these to test?

or

I just
- Disable the Veeam replication job temporarily
- manual power up the replica VM
- Use VMware Infrastructure Client to edit replica VM configuration and change VLAN from production to test network
- Power on replica VM with VMware Infrastructure Client, and see if it can boot up properly. Do all testing.
- Shutdown replica VM
- Enable the Veeam replication job back

Thanks again for your help & quick response.

[foggy]

The one referred to above is a bit old - you do not need to create a snapshot, since each replica restore point is already a snapshot. This is covered in the sticky FAQ, btw:

Q: I want to test replica failover. Can I simply power on any replica restore point with vSphere Client?
A: Yes you can, but we recommend to use “failover” / “undo failover” or SureReplica. Because each restore point is a snapshot, its content will remain intact, because all disk changes inflicted by the running VM will go into the new snapshot file that host automatically creates to protect the selected snapshot's state (standard VMware snapshot tree functionality). For the same reason, Veeam replication job will not be affected either.

[sze]

Hi foggy,

Thanks for your help!