Skip to main content

vSphere Replication vs Array-based Replication

As many request come in on the comparison between vSphere Replication vs Array-based Replication, I've decided to write this blog based on vSphere Replication 5.5 and Array-based Replication.

FeatureSRM vSphere ReplicationStorage array-based replication
Replication ComponentHypervisor-levelStorage-level
Storage at recovery siteDoes not need to match active site, support on local disk as well.Must be the same array type as the active site
Supported storage typesAny Storage that is supported by vSphere 5.5ISCSI, Fibre Channel and NFS, as long as supported by VMware. Check Compatibility here
Integration with Site Recovery Manager (SRM)YesYes, as long as supported by VMware. Check Compatibility here.
CostLow. vSphere Replication is included in vSphere hypervisor and work with any storage, including local disk.High. It is normally sold as an option on top of SAN box. Additional to that, you must purchase the similar box, at least the same firmware that support the replication between two SAN box. 
Use casesSmaller infrastructures, remote offices of large companies and/or business-critical applicationsLarge and/or business-critical environments
Recovery point objective (RPO) times15-minute to 24-hour RPOsZero-minute (synchronous replication) to 24-hour RPOs
Reprotect and failback with SRMYes. Yes, but limited on the supported model. 
Total number of protected virtual machines5001500, with ESXi 5.5 and SRM 5.5.
Protection groups250250. If vSphere Replication and array-based replication are used together, the limit remains 250.
SnapshotsYes, with up to 24 Point-in-time recovery.Yes, with specific limitations detailed in VMware's SRM 5.1documentation
Linked clonesNot supportedSupported as long as nodes in the snapshot tree are replicated
Raw device mapping (RDM) VMsVirtual mode RDM onlyVirtual and physical RDM formats
Application-consistent recoverySupported for Windows environments with VSSThe storage vendor ensures application-consistent replication
Works with VMware Fault ToleranceNoYes
SRM IntegrationYesYes
Respective hardware vendor SRM equivalent, such as HP Insight Recovery (MR), etc...NoYes
Area ProtectionVM onlyProtect data as long as it's located in SAN
Bandwidth RequirementLowerHigher
Initial SeedingSupported seeding to external mediaOnly work between SAN box. If it failed and required full sync, it will need to replicate everything over the WAN, unless SAN box is relocated to the production SAN network.
Non-disruptive DR TestingYes, provided by SRMYes, provided by SRM only
User friendlyYes, and work with any hardware vendorHarder to implement, and only work with specific hardware vendor
Shared DRYes, N:1 No.

Comments

Popular posts from this blog

VMware VRNI 3.5 NTP is working but not healthy

We have experienced this problem where some of the major services not started. You will not be able to connect to the vRNI via web -> https://<ip_address_of_vrni_platform>>. This probably caused by NTP insync. You need to manually start these services. Login with Consoleuser / and default password if not changed before via venter web console. Run services restart and wait for couple minutes (it took me 5-6 mins). Types of Users  User name  Password  Admin UI  admin@local Set this password in the Activate License window during installation. SSH User  support ark1nc0113ct0r CLI User  consoleuser ark1nc0ns0l3 Note It is recommended that the users change the default passwords immediately after the deployment.  Procedure 1 Navigate to  https://<vRealize Network Insight Platform IP address> .  2 Log in to the product UI with the corresponding user name and password. Troubleshoot NTP - https://kb.vmware.com

vSphere Replication - checking the replication status

Enable SSH on ESXi host (you can do this using vCenter) Download putty or any SSH client and log in with root access vim-cmd vmsvc/getallvms ~ # vim-cmd hbrsvc Commands available under hbrsvc/: vmreplica.abort vmreplica.pause vmreplica.create vmreplica.queryReplicationState vmreplica.disable vmreplica.reconfig vmreplica.diskDisable vmreplica.resume vmreplica.diskEnable vmreplica.startOfflineInstance vmreplica.enable vmreplica.stopOfflineInstance vmreplica.getConfig vmreplica.sync vmreplica.getState  See more at: http://www.virtuallyghetto.com/2011/07/hbr-host-based-replication-cli-for-srm.html#sthash.mpqbyGmw.dpuf http://www.virtuallyghetto.com/2011/07/hbr-host-based-replication-cli-for-srm.html

Editing hosts file in iPhone/iPAD

You can now edit the hosts file with a jailbroken iPhone/iPad. Download the hosts file using tool like FileZilla. Default location is /etc/hosts. Download Notepad++ and edit the file. I've edit the file and convert it to ANSI under the Encoding menu. Once completed, upload the file back to the default location.  Try to ping the DNS... It should works!