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
Why and how are organizations protecting Microsoft 365 data? And by whom?
Get link
Facebook
X
Pinterest
Email
Other Apps
Welcome to another installment in our ongoing series about the Cloud Protection Trends Report for 2023, which surveyed 1,700 “as a Service” administrators, including those responsible for managing and protecting Microsoft 365 data. Veeam contracts with independent research firms to ask questions on an assortment of topics, including the reasons and methods IT leaders have for protecting Microsoft 365 data:
This research revealed a few key truths, all of which have implications for the myriad of organizations that rely on Microsoft 365 systems and data every day:
The vast majority of M365 organizations understand two important things: One, the Recycle Bin is not a replacement for backup, and two, neither are the extended hold features within the premium tiers of Microsoft 365.
While application owners have historically underestimated the importance of longer-term backups, Microsoft 365 Admins “get it.” Survey results show remediating from ransomware and ensuring regulatory compliance are primary drivers why Microsoft 365 data needs to be backed up.
There is a healthy mix of those using third-party backup solutions from their data centers (or cloud-hosted infrastructure) as well as those using Backup as a Service (BaaS) to protect Microsoft 365 data. The users’ goal is to ensure separate controls/credentials as another step in preparing against ransomware.
With that in mind, Veeam Backup for Microsoft 365 is built to be agnostic and flexible in deployment to give control back to the data owner. This oversight allows administrators to provide sufficient data separation and control planes between production data and backups to mitigate the risks of data loss or compliance violations. In addition to data siloing, Veeam Backup for Microsoft 365 offers data recovery options that go far beyond just the export of raw data — offering application-specific restore and recovery, both to and in the native application formats.
This blog is especially timely as we get ready to unveil the next generation of Veeam Backup for Microsoft 365. We’ll be discussing the roles and methods for backing up Microsoft 365 with Veeam’s lead technologist for 365 strategies, Karinne Bessette (@RinBytes) on next week’s livestream on Feb. 28 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