Veeam Blog

At VeeamON 2019, during the Technical Main Stage keynote, I joined members of the Product Strategy Team to do a number of live demos showing current and future products and features. While the first half focused on what had been released in 2019 so far, the second half focused on what is coming. One of those was the highly anticipated Copy Mode feature being added to the Cloud Tier in v10 of Veeam Backup & Replication.

In 2017, Veeam PN was released as part of Veeam Recovery to Microsoft Azure. The Veeam PN use case went beyond the extending of Azure networks for workload recoverability and was quickly adopted by IT enthusiasts for use of remote connectivity to home labs and the connectivity of remote networks that could be spread out across cloud and on-premises platforms. Our development roadmap for Veeam PN had been locked in, however, we found that customers wanted more.

With the release of Veeam Availability Console v3 we have taken huge strides in delivering to VCSP partners a console that acts as the central place to manage all aspects of their backup offerings. Not only does it build on the previous releases, but also looks to place VAC as a critical component of any Veeam-powered service provider offering.

With the release of Update 4, we added support for Veeam Cloud Connect to replicate directly into vCloud Director virtual data centers, allowing both our cloud and service provider partners, and tenants alike, to take advantage of the enhancements VMware has built into the platform.

Data growth continues to accelerate at almost exponential speed and with that comes pain points of organizations trying to manage that growth. More data means more robust applications to handle larger data sets, which also means more infrastructure to handle applications and the data itself. While the cost and management of on-premises storage has come down as hardware and disk technologies improve, organizations still face significant overhead when maintaining their own hardware infrastructure.

The nomination window for the 2019 Veeam Innovation Awards for Partners is closing in a few days, so we’re taking a minute to highlight some of the VIA 2018 winners announced earlier this year with a few VCSPs.

Having been hands-on in service provider land for the entirety of my career prior to joining Veeam, I understand the pain points that come with offering backup and recovery services. I’ve spent countless hours working on getting the best combination of hardware and software for those services. I also know firsthand the challenges that storage platforms pose for architecture, engineering and operations teams who design, implement and manage these platforms.

With the release of vSphere 6.5, VMware introduced a supported version of the HTML5 vSphere Client that was bundled as part of the vCenter Server Appliance. Built upon VMware’s Clarity UI Framework, the move to the new HTML5 client had begun. The 6.5 release had partial functionality compared to the Flash-based Web Client, however, with the release of vSphere 6.7 in April, the HTML5 vSphere Client was brought up to feature parity and is now the preferred way to configure and manage vSphere environments.

In this blog post, I’ll be covering a very real-world solution with Veeam PN where it will be used to easily connect geographically disparate cloud hosting zones, enabling you to achieve High Availability for applications and provide cross cloud application and services access. This is probably the most exciting of the three use cases I will cover in this blog series on Veeam PN, and with multi-cloud adoption in full swing, this is a very timely and useful capability.

On January 2018, Veeam publicly announced the release of Veeam PN (powered network) version 1, a lightweight SDN appliance that was released completely FREE to use. And while Veeam PN was released as part of a greater solution focused on extending network Availability for Microsoft Azure, Veeam PN can also be deployed as a standalone tool via a downloadable OVA. Veeam PN has some key standalone use cases we’ll explore in this blog series.