- This topic has 9 replies, 8 voices, and was last updated April 5, 2018 by Carlos C.
Thoughts on moving Zerto to all appliance based?
As I wait in my silo based organization for Windows VM’s to be deployed so I can install Zerto mgt VM’s, I think maybe it would be a good thing to either move to an appliance based OVA/OVF for Zerto. This gives Zerto more control over configuration and less onus on the customer to deploy and manage more windows VM’s with patching and anti-virus etc. Certainly makes for faster deployments and perhaps fewer support calls.Harry SDecember 20, 2016 06:17:53 PM
Thanks for your feedback. This is certainly up for consideration as we continue to build on the offering. We do understand the majority of time deploying ZVM is actually in installing and configuring Windows! 🙂
Would you prefer only an appliance over a Windows-based installation, or do you think both offerings should still be available?
Do you have an opinion on an included internal database within an appliance? With the option to connect to an external DB if desired?
Please keep the feedback coming! Also, there is a “Feature Request” option within the ZVM interface as well. Just go to the menu in the top-right corner, select “Submit Support Ticket,” and under “Type of ticket” select “Feature Request.”
HarryFollow me: www.twitter.com/HarrySiiiJeffrey SJanuary 12, 2017 09:23:42 PM
+1 for me on making Zerto 100% virtual appliance based. I think you can look at the vCenter Appliance development over the past years. It’s pretty much where you want it to be regarding configuration management, database usage/scalability etc. External database is often not a requirement for my customers. They are more interested in good configuration backup/restore functionality and a stable management platform which is not impacted by windows OS. Even further reduced deploy times are an advantage as well off course. Also, i came across a few VMware environments which were almost 100% *NIX based. In those cases, faces go in unhappy-mode when told that windows is needed for a solution.Nick HJanuary 17, 2017 09:33:02 PM
I have to agree with Jeffrey. The ZVM as a OVA/OVF appliance would be great. The VMware vCenter VCSA is a good example of how moving from a Windows server/Application installation to a Linux appliance can be successful. We have moved to the vCenter Appliance exclusively and have been very happy. Along with not eating a windows licenses for every customer and every site we have, it would also simplify deployments. In a dream world, the ZVM, ZCM, ZSSP, and Z-VRA would all be appliances. I know some of them are already. For me, I can say that if a virtual appliance was available, I would move to it exclusively.
Embedded vPostgress seems to be the go-to database for things like this. However, other options are definitely available depending on the type of DB.Colin MMarch 13, 2018 04:49:52 PM
Hi, is there any traction to this? A ZVM Appliance would provide customers with a far more efficient setup.
I suggest that we all open feature requests with Zerto. They treat them like a support case that they want to close ASAP but that may get some traction.
I just added a new feature request for this called
“Produce a virtualized appliance (OVA/OVF) for ZVM’s as alternative to Windows based ZVM”
Upvote please 🙂
I’ll throw my name in the hat for the appliance. It would streamline deployment and who doesn’t want to reduce their Windows license footprint?Mike CMarch 20, 2018 06:06:40 PM
Here’s another vote for an appliance with a built in database. Fewer moving parts, fewer patches (and easier when they do come out), and better uptime.Carlos CApril 5, 2018 03:04:03 AM
I was thinking the same thing as well
it would let us to implement even faster and also avoid windows licenses I do in fact have a couple of customer who did not know about a new Windows for ZVM was needed so they used an existing Windows with a couple of roles… of course I said to them that’s now supported but let’s install it and a user still using a Windows 2008 R2 VM as ZVM