alteradmin
Contributor
Contributor

Filtering out non-replicated guests

Jump to solution

Hello we are using SRM 5.5 with Recoverpoint as the Protection SRA.

You used to be able to filter out guests on the Recoverpoint side that were not going to be part of the protection group.

I dont see that option anymore and was told it was removed. How does one filter out non-replicated vm's or even vm's wejust dont want to protect in

SRM now? It is blowing out our license usage not and I cannot create the protection group.

Thanks!

0 Kudos
1 Solution

Accepted Solutions
cjscol
Expert
Expert

When you create the protection group it should only allow you to select replicated datastores. Therefore the protection group should not include VMs that are not replicated.

If you have VMs that you do not want to protect with SRM then they should not be on replicated datastores with VMs that you do want to protect.

However, if you do have some VMs on a datastore included in a protection group that you do not want to protect you can select the Protection Group within SRM, and then from the Virtual Machines tab right click on the VM you do not want to protect and select Remove Protection. I am not sure if this will take up a license or not.

Calvin Scoltock VCP 2.5, 3.5, 4, 5 & 6 VCAP5-DCD VCAP5-DCA http://pelicanohintsandtips.wordpress.com/blog LinkedIn: https://www.linkedin.com/in/cscoltock

View solution in original post

0 Kudos
4 Replies
cjscol
Expert
Expert

When you create the protection group it should only allow you to select replicated datastores. Therefore the protection group should not include VMs that are not replicated.

If you have VMs that you do not want to protect with SRM then they should not be on replicated datastores with VMs that you do want to protect.

However, if you do have some VMs on a datastore included in a protection group that you do not want to protect you can select the Protection Group within SRM, and then from the Virtual Machines tab right click on the VM you do not want to protect and select Remove Protection. I am not sure if this will take up a license or not.

Calvin Scoltock VCP 2.5, 3.5, 4, 5 & 6 VCAP5-DCD VCAP5-DCA http://pelicanohintsandtips.wordpress.com/blog LinkedIn: https://www.linkedin.com/in/cscoltock

View solution in original post

0 Kudos
vbrowncoat
VMware Employee
VMware Employee

To second and add to what cjscol said, what defines a protection group in SRM is a replicated LUN or consistency group (group of LUNs replicated together). If you add a LUN or consistency group to an SRM protection group, all of the VMs on that LUN or consistency group have to be protected by SRM, and all of the disks for all of those VMs need to be located on that LUN or consistency group.

When using array based replication (like RecoverPoint) it isn't possible to protect some VMs on a LUN and not others. This has never been an option with SRM. If you want VM level granularity you would need to use vSphere replication, or place 1 VM per LUN.

0 Kudos
alteradmin
Contributor
Contributor

Thanks guys I have resolved it by moving the guests to luns that where not replicated but this absolutely was an option in recoverpoint prior to 4.0.

You could set filters in the Vcenter section of recoverpoint that hid machines on any Lun you didnt want SRM to see.

0 Kudos
vbrowncoat
VMware Employee
VMware Employee

Interesting, it's good they removed it, that would have caused you trouble in SRM & vSphere by failing over a LUN with VMs that weren't protected.

0 Kudos