My job at Veeam is the first time in my IT career working in a software company, and I’ve learned a ton of things about software development. Not as a developer myself, since I don’t have any code writing skill (I wouldn’t call my low scripting capabilities “coding”), but partecipating to internal discussions about development has been so far an interesting experience. One of the most fascinating things I’ve learned is UX (User Experience) development, in particular around the User Interface.
A nice and easy way to receive email notifications into Slack.
The upcoming Veeam Availability Suite v9, among many new and exciting features, will bring more enhancements for Enterprise environments. Learn more about Guest Interaction Proxy, Mount Server, Standalone Console, and all the enhancements coming for tapes.
Looking at the latest announcements and the history of the behemoth of public cloud services, probably yes. And a leading one.
If you want to learn how Veeam Cloud Connect uses encryption to protect and secure communications over an unsecure channel like the Internet, this video I recorded is for you.
Last year, together with the release of the new Veeam Cloud Connect, I wrote and published its Reference Architecture. The paper had a great success with 1500 people downloading it. Because of the new additions in Veeam Backup & Replication v8 Update 2, it was time to upgrade the document.
The upcoming Veeam Availability Suite v9 has tons of enhancements and new features, but improvements around primary and backup storage will surely be one of the biggest parts of our next release.
We already announced a new addition in our list of supported storage arrays for our storage snapshots integration (EMC VNX/VNXe), but this isn’t the only storage news—on the contrary, there are plenty of them, and I’ll cover some of them in this post.
As I’m following closely the growth and evolution of this new technology for vSphere environments, I’ve found an article on the blogosphere and some additional comments on Twitter that made me re-think a bit about the real value of VVOLS. Is the real value of VVOLs the VM granularity, or it’s more the policy-based management?