In addition to the previous comment which is important, I also recommend being very careful upgrading VM hardware, or deploying new VMs. Our standard recommendation is to upgrade the recovery sit...
See more...
In addition to the previous comment which is important, I also recommend being very careful upgrading VM hardware, or deploying new VMs. Our standard recommendation is to upgrade the recovery site first, this is because when you upgrade the protected site, you could end up in a place where you have a VM that can run at the protected site (VM hardware supported on vSphere 6.5) but not at the recovery site (VM hardware supported on 6.5 can't run on 6.0 hosts). The VMs will still replicate, they just won't be able to be started at the recovery site until the hosts are upgraded.
The new version of VR, 8.3, which was announced earlier this month, supports exporting all datagrids in the UI (see: What's New in SRM and vSphere Replication 8.3 | VMware SAN )
What journal are you referring to? I'm not aware of a journal related to SRM. SRM doesn't require a traditional SAN, it can be used with vSphere Replication only.
The capability to migrate tags with failover is being worked on. In the meantime, the script that you would want to create would be something that took the tags from the protected VMs and applied...
See more...
The capability to migrate tags with failover is being worked on. In the meantime, the script that you would want to create would be something that took the tags from the protected VMs and applied them to the recovery site placeholder VMs. When the recovery plan is failed over the recovered VMs would have the tags.
SRM and VR don't use tags by default. You could use PowerCLI to add tags to a VM that is located on particular storage. If you use vRealize Orchestrator along with the SRM & VR plug-ins you could...
See more...
SRM and VR don't use tags by default. You could use PowerCLI to add tags to a VM that is located on particular storage. If you use vRealize Orchestrator along with the SRM & VR plug-ins you could tag VMs as part of the protection workflow.
vSphere Replication doesn't currently support multi-VM consistency groups. You could use array-based replication to accomplish this. Often, in a tiered application stack, the changes only occu...
See more...
vSphere Replication doesn't currently support multi-VM consistency groups. You could use array-based replication to accomplish this. Often, in a tiered application stack, the changes only occur on the DB so the APP server doesn't need to be replicated at the exact same time. It might be worth testing and seeing what your application requires or how it functions if you aren't replicating them both at the same time.
1. By "recovery objects/pointers" do you mean as a seed for replication? If so, then yes, you can use clones as seeds for DR. 2. See above. The UUID needs to match for VR to use it as a seed
Support is wrong about those steps helping speed things up. The time would be exactly the same (plus the additional time to do those added on steps) as that is exactly the same process that VR go...
See more...
Support is wrong about those steps helping speed things up. The time would be exactly the same (plus the additional time to do those added on steps) as that is exactly the same process that VR goes through when you run a reprotect (it uses the previous source VM as a seed and calculates the checksum difference between the source and target). When you run a reprotect (or when you use a seed) the disks are not copied over the WAN, only changes/differences are. The checksum time is as long as it is not because VR doesn't use CBT (it uses a light-weight delta mechanism to track changes which is better suited to it's purpose than CBT), rather it is because VR doesn't currently have a way of recognizing that it is reprotecting (using something that should be almost exactly the same) vs. using a seed (something that could have some things the same and potentially a lot different). That is something we're working on though.
I would look for a solution that just backs up/protects Oracle VMs and use it alongside SRM. If that tool has an API SRM can trigger that recovery as part of a recovery plan. Or you could mig...
See more...
I would look for a solution that just backs up/protects Oracle VMs and use it alongside SRM. If that tool has an API SRM can trigger that recovery as part of a recovery plan. Or you could migrate off Oracle
This is what the SRM recovery plan test functionality does (with the addition that the SRM test doesn't impact replication or RPO). The thing to confirm is that your array vendor/SRA provider sup...
See more...
This is what the SRM recovery plan test functionality does (with the addition that the SRM test doesn't impact replication or RPO). The thing to confirm is that your array vendor/SRA provider supports running recovery plan tests with the connection between SRM servers disconnected. See these posts for additional detail: Recovery Testing and SRM pt 2 - Alternatives - Virtual Blocks
It sounds like you have a many to one mapping which can't work. Something like this Site A Site B RP 1 > RP A RP 2 > RP A In this situation, there is no way to re...
See more...
It sounds like you have a many to one mapping which can't work. Something like this Site A Site B RP 1 > RP A RP 2 > RP A In this situation, there is no way to reverse the second mapping because you would end up having A mapped to 2 things (RP 1 & 2) and SRM wouldn't know what VMs to put where. Does that make sense?
SRM requires a vCenter at each site so to use it with stretched storage requires an SRA that supports this configuration (look at the SRA compatibility guide and filter for "stretched storage"). ...
See more...
SRM requires a vCenter at each site so to use it with stretched storage requires an SRA that supports this configuration (look at the SRA compatibility guide and filter for "stretched storage"). Since SRM requires a vCenter at each site it doesn't need VC HA.
SRM supports protecting up to 5000 VMs per site. There are two different licensing levels with SRM, Standard and Enterprise. Standard supports up to 75 VMs per site, Enterprise supports the f...
See more...
SRM supports protecting up to 5000 VMs per site. There are two different licensing levels with SRM, Standard and Enterprise. Standard supports up to 75 VMs per site, Enterprise supports the full scale.