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
Real-World Statistics on Downtime and Data Loss in 2022
Get link
Facebook
X
Pinterest
Email
Other Apps
As another installment from the Data Protection Trends 2022 report, we’re covering the topic of downtime and data loss. These results really give us a view on the current trends happening in the IT environment.
There isn’t much difference between high-priority and normal applications
Even though applications vary from each other in other ways, the survey respondents noted minimal difference between the expectations against downtime or data loss of ‘high-priority or critical’ applications versus ‘normal’ applications. In 2021, organizations reported a downtime tolerance of “an hour or less” for 56% of their high-priority applications and 49% of their normal applications. Similarly, the frequency of protecting their data (i.e. reducing data loss) was also at similar levels between their high-priority and normal applications.
It is notable that “Tolerable Data Loss” showed the same trends as “Tolerable Downtime” as described above:
Again, minimal difference between “high-priority” and “normal” data dependencies
All data is considered important, with both tolerances leaning increasingly to the left as service level agreements continue to tighten
Tolerable Data Loss, as shown by protection frequency
Downtime from outages and the most common causes
The 2022 report carefully examined the frequency and causes of outages. Globally, 40% or 2 out of 5 servers had at least one or more outages over the past 12 months.
What’s the cause of these outages? The most common outages are still caused by breakage of infrastructure or software, while the most impactful outages in both 2020 and 2021 were caused by cyberattacks and user errors. For more details, please check out this 4-minute video:
We hope these topics have been helpful. This post is the first part of a multi-part series, so please stay tuned to the Veeam blog:
Part 7: Real-World Statistics on Downtime and Data Loss in 2022
Please reach out to Dave (@BackupDave) or Jason(@JBuff) or email us at StrategicResearch@veeam.com to tell us how this research aligns with your organization’s data protection goals for 2022 — and don’t forget to download the full report.
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