We are excited to announce the release of Kasten K10 version 6.0, the latest and most advanced version of our industry-leading platform that provides enterprise-grade Kubernetes data protection and application mobility. This release helps customers scale their cloud native data protection efficiently. Kubernetes deployments are growing at an unprecedented rate. Gartner predicts that by 2027, more than 90% of global organizations will be running containerized applications in production. However, today’s market conditions are scarred with financial uncertainty and a shortage of cloud native skills. Therefore, you must ensure operational efficiencies are in place to unleash the full potential of your cloud native environments while protecting your data. Additionally, security remains an imperative as organizations focus on keeping their businesses running. With this release, we also continue to innovate in this growing ecosystem, so that you can take advantage of the best-of-breed inn...
Get link
Facebook
X
Pinterest
Email
Other Apps
What is driving hybrid-cloud (IaaS & PaaS) adoption strategies?
Get link
Facebook
X
Pinterest
Email
Other Apps
Welcome to another installment in our ongoing series focusing on the Cloud Protection Trends Report for 2023, which surveyed 1,700 “as a Service” administrators, including those responsible for Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) for file services and/or databases. Veeam contracts with independent research firms to ask questions on an assortment of topics – including the adoption trends for both IaaS and PaaS scenarios:
This research revealed a few key truths, all of which have implications for data protection strategies in a multi- and hybrid-cloud world:
The data center is not going away, but the percentage of workloads running as physical or virtual machines will continue to dilute as organizations’ “cloud-first” strategies continue to bring new workloads to hyperscale clouds at faster rates.
Not only are there drivers TO the cloud, but also from one cloud to another, as well as from cloud hosts back to the data center.
For many organizations, the journey to production clouds may start with a “lift and shift” of servers from the data center to a host (or a new server image), but eventually organizations will continue that journey of foundational services like file shares and databases from IaaS instances into natively delivered cloud file shares and cloud-hosted databases.
Veeam has long been able to protect data within server instances running on public cloud (IaaS) platforms, including Amazon Web Services (AWS), Microsoft Azure and Google Cloud by way of Veeam Agents. And while there are reasons to do so, just like utilizing agents within virtual machines within the data center, Veeam pioneered “the better way” of protecting VMs from the hypervisor layer. In the same philosophy, the better way to protect IaaS server instances is through the hyperscale cloud’s underpinnings, which Veeam has been doing for over three years. The Veeam solution utilizes each cloud platforms’ native snapshots, storage and security services, and APIs. This approach also enables IT administrators to protect databases and file systems on dedicated PaaS services like Amazon RDS, Amazon EFS, Azure SQL, Azure Files and more, as well as those hosted on IaaS.
We’ll be discussing these ideas and more on our livestream on Nov. 15 and throughout this blog series:
For those of us who have been in the business of backing up data for a while, we’re used to making copies of data on different types of media. I won’t date myself by mentioning reel-to-reel tapes, but the journey started with tape and then backing up data to block/file-based disk storage came along. More recently, a new kid on the block has become a popular destination for backed up data, object storage. Veeam started to use object storage as a target when we released Veeam Backup & Replication 9.5 Update 4 in January 2019 by introducing our use of AWS S3 compliant object storage via the Capacity Tier. A year later, we launched Veeam Backup & Replication v10 which featured support for object locking to provide data immutability for object storage. Immutability provides protection from ransomware attacks by locking the objects which prevents them from being modified or deleted by malicious software or humans. Today, Veeam Backup & Replication is protecting hundreds of petab...
Before Veeam Backup & Replication v11, the product used SQL Server to create and store its configuration database. It has always been possible to use SQL Server Express to store a Veeam Backup & Replication, however, this version of SQL Server had some critical limitations. In the 2022 version of SQL Server Express, the most relevant limitations were: Use of one socket or four cores Use of only 1.4GB per instance 10GB limit for databases In an environment of 500 machines or fewer, these limitations may not have an impact, but if you have a large backup environment, you had to migrate to one of the paid SQL Server versions to avoid these limitations. You can check the limits for each version of SQL Server 2022 by clicking this link . For V12 and with scalability, performance and licensing cost in mind, Veeam introduced the possibility of using PostgreSQL as a configuration database. PostgreSQL is a relational database management system that’s been used for over 35 years...
update notice: The information in this blog post has been updated on April 1st, 2022. Since Veeam Backup & Replication version 10, it’s possible to back up NAS shares with the SMB (CIFS) and NFS protocol. One of the challenges with backing up large file shares is doing so in a consistent state. This blog post shows how to create a consistent backup of an SMB share hosted on a NetApp ONTAP based storage. NetApp storage snapshot, Microsoft VSS snapshot or Storage Integration? Veeam offers three ways to back up a NetApp ONTAP SMB share in a consistent state. With NetApp storage integration From a NetApp storage snapshot (without integration) With Microsoft remote VSS snapshot Using the storage integration is the easiest way to get the latest state with very few configuration steps. Using an alternative snapshot path allows complex scenarios like backing up from a SnapMirror/SnapVault location but it involves scripting or a schedule on NetApp to create and delete t...
Comments
Post a Comment