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
Get ready for Veeam Backup for Microsoft 365 v6a
Get link
Facebook
X
Pinterest
Email
Other Apps
The next release of Veeam Backup for Microsoft 365 will bring a major change to the way we protect Microsoft Teams chats data. Starting from V6A we will back up Team chats by using the newly released Teams Export APIs. What does it mean for you and how to prepare for this new release?
The legacy approach to Teams backup is retiring
Technically, Teams chat backup has always been a challenge because there were no specific APIs to access and get messages. Since we introduced Teams support, we only could protect the chats by backing up the messages from the TeamsMessageData folder of the Exchange group mailbox. Microsoft used this hidden folder to archive messages sent within a team channel or between individual users or groups. In the last few months, Microsoft has started applying more restrictions for access to this folder which sometimes caused issues with Teams protection for our customers. These restrictions will be applied to everyone in a couple of months
The future – Teams Export APIs
A few months ago, Microsoft introduced a new set of Teams Export APIs designed to access team chats directly and get messages straight from the underlying Cosmos DB service that hosts the chats. By Oct. 1 of this year, Microsoft will completely deprecate any access to the TeamsMessageData folder and Teams Export APIs will remain the only way to go for working with Teams message data in the future.
The APIs are protected and to enable them in your Microsoft 365 tenant you need to be granted special access and permissions. And on top of that Microsoft charges their customers for using these APIs.
How this underlying change will affect your Teams backup
After you upgrade to the upcoming Veeam Backup for Microsoft 365 v6a, your Team chats will no longer be backed up by default. Note — this only applies to chats, the rest of Teams data, including metadata, channels, tabs, files and membership, will continue to be protected.
Why did we do this? Because we want to make sure that none of you get unexpected costs or errors and warning notifications in your jobs. As you will be able to read further, backing up chats will require preparations on your side and comes with additional costs that will need to be paid to Microsoft.
To make it clear and visible for you, in V6A, we’re adding processing options for Microsoft Teams —chats are now a separate option that you can enable or disable per team when configuring your backup jobs:
Additionally, if you’re up to continue protecting Team chats for any of your teams, you will need to reconfigure your organization and explicitly select the option to back up Team chats:
Team chats backup is supported only for organizations using the modern app-only authentication and is in the Default (Worldwide) region. So, on the next steps of the wizard, Veeam Backup for Microsoft 365 will verify if your organization meets the authentication and region requirements and if the provided app has the required permissions.
The cost
Charges for using Teams Export APIs apply per tenant per message and depend on the license model used. Veeam Backup for Microsoft 365 will support Model B, which means that protection of Teams message data will cost you $0.00075 per message. At the end of a month, the amount spent on using the APIs will be included in your invoice from Microsoft — Veeam itself does not apply any charges.
And I know that your next question would be “How can I estimate my costs?”. Currently, the best way would be to decide what team chats are critical for your business, check out the average usage statistics, and do some calculations manually. Microsoft Teams admin center provides you usage reports on the number of channel messages sent and replies to these messages that you can use as a basis for your calculations:
How to apply for access to the protected APIs
Microsoft provides a special form that you need to fill in to apply for access to Teams Export APIs:
The following list will help you to fill in the form quickly:
Publisher name
Veeam Software
Application name
Put the name of the app that you use to add your Microsoft 365 organization to the VB365 scope. You can find it in the Azure Active Directory admin center -> App registrations
Application ID(s) to enable permissions for (GUID, semicolon separated)
Put the application (client) ID of the app that you use to add your Microsoft 365 organization to the VB365 scope. You can find it in the Azure Active Directory admin center -> App registrations -> Overview of your app:
Which category best describes your application (select one)
Select “Backup/restore”
Why does your application need read access to all messages in the tenant? (If you don’t, you don’t need access to protected APIs)
To allow for backup/protection of Teams message data
Data retention (select one):
Select “It is obvious to any admin installing this app that it will make a copy of Microsoft Teams messages”
What are the tenant ID’s that this application needs to run in? (GUID, semicolon-separated. If you’re writing software for other organizations to use, include “all”).
Put the tenant ID of your Microsoft 365 organization that you protect with VB365. You can find it in the Azure Active Directory admin center -> Overview of your tenant:
The access is usually provided by Microsoft within a few days, but sometimes it may take up to two weeks or longer, so plan for applying in advance.
Tl;Dr check-list
In Veeam Backup for Microsoft 365 v6a, switches to the new Teams Export APIs for messages data protection
To continue protecting Teams channel chats, you need to:
Get ready for additional costs
Apply for access to APIs from Microsoft
Reconfigure your organization in Veeam Backup for Microsoft 365
Reconfigure your Teams backup jobs
If you have any questions on the upcoming changes, you’re welcome to post them on Veeam Forums.
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