Tagged: Backup

Backup Audiocodes Mediant VE on Azure

In this post I describe how you can backup your Audiocodes Mediant VE on Microsoft Azure. Let’s start with some basics before configuring your SBC backup on Azure.

Save config

First of all, if you deploy your Audiocodes Session Border Controller (SBC) for Teams Direct Routing or any other SBC I’d recommend to save the configuration. For instance, on Audiocodes Mediant SBCs you can easily save the configuration file (config.ini) and/or packages.

Screenshot: Saving Audiocodes Mediant Configuration File
Screenshot: Saving Audiocodes Mediant Configuration File and/or Package

Take a (“on-system”) snapshot

Another option is to directly save a snapshot on the Audiocodes SBC which enables you to quickly revert to this “restore point”.

Screenshot: System Snapshot (Setup\Administration\Maintenance)
Screenshot: Create a system snapshot directly on the Mediant
Screenshot: Create a system snapshot directly on the Mediant

Enable Azure Backup for virtual SBC

Hereinafter, I’ll show an example on how you can enable and configure your Audiocodes Mediant VE getting backed up on Azure.

Screenshot: Backup configuration on Azure
Screenshot: Configure backup (Resource group\VM\Backup)
Screenshot: Configure backup policy which fits your requirements

Here you can configure retention, how long which type of backup should be kept.

Screenshot: Configuring backup data retention
Screenshot: (optional) create a separate backup resource group
Screenshot (optional) create a separate backup resource group
Screenshot: check your backup policy settings
Screenshot: Wait for validation to complete successful

After the validation is ok, your done.
You could trigger an ad hoc backup now, to check if it works.

Screenshot: Trigger backup now
Screenshot: Here you can monitor the backup status and progress
Screenshot: Backup process running

If configured you should also restore the system once, to ensure that you know that it works and how to restore a VM.

Conclusion, opinion and summary

To backup your virtual SBC on Azure is a good thing in my opinion. Especially if you maybe want to revert the SBC after a firmware upgrade to an earlier release or just quickly bring back another configuration if you’ve missed to download the config.ini or config package before you made this one big change on the system.

Additional resources

Microsoft Teams Backup and Restore?

In this post I’d like to describe on a high level what you can do regarding backup (and restore) Microsoft Teams chats and files (January 2019, this might be subject to change).

Do you need backups of Teams (data) stored within a global hyperscaler cloud infrastructure? Shouldn’t it be resilient and highly available based on the SLAs …? Well, there is no one-size-fits-all-answer. It depends on your requirements and needs. However, in my opinion, it’s not a bad idea to have a (working) backup in place in case data was deleted or became inaccessible, anyhow.

Where are my Teams conversations and files located?

Your chats and conversations are basically stored on Azure. However, there are also copies stored in your Exchange Online user mailbox or an Office 365 group’s mailbox for compliance purposes. The copies within a mailbox are not directly visible because it’s saved in a hidden folder Conversation History\Team Chat.

“Personal Chat” Data

If you exchange files it will be stored in your OneDrive For Business\Microsoft Teams Chat Files.

Teams Data

If you share files in a Teams Channel it will be stored in its associated SharePoint Online Document Library Folder of the Teams channel.

By default deleted files on SharePoint online are available for 93 day to be restored if no other configuration was set or quotas are applied and exceeded.

What backup and restore limitations do I have (after a “soft-delete” period)? (January 2019)

If a Team was deleted and you notice this or get requested to restore a Team after the “soft-delete” period of 30 days (default) the content is permanently deleted and cannot be restored, see link at the bottom “Restore a deleted Office 365 Group”.

You cannot restore a Team 1:1 after its 30 days “soft-delete” period.

Chat even if you have the data cannot be restored or at least I did not find a way to accomplish this easily. I was thinking about importing chats based on scripts in a newly re-created Team and it’s channels but it seemed to be a way to cumbersome to quickly test it with some lines of ps script code.

What backup options are there?

Option 1: Archive Teams

Archiving is not backup. However if you archived instead of deleting it, you can restore it easily via the Teams Admin Center or via the Teams Client, see link at the bottom “Archive or restore a team”.

Option 2:  Office 365 Security and compliance center (eDiscovery cases, retention policies)

You can maintain copies of chats  by using eDiscovery cases/litigation/inplace hold/retention policies. You can set this up to store the copies hidden in the mailbox. Either for a certain periode of time or indefinitely.

You can configure retention policies to retain files longer and to be stored in the preservation hold library. However, you might search and access the retained chat/files but not within Teams as it were before the “permanent” delete.

Option 3: Thirdparty solution/s?

Most of the thirdparty backup solutions are offering options to backup Exchange Online, SharePoint Online and OneDrive For Business data. Some providers also mention capabilities to restore Office 365 groups but it needs clarification if they have working restore procedures to recover a deleted Teams after the default “soft-delete” period of 30 days. If you consider to leverage a thirdparty solution you should take this into account for your Microsoft Teams evaluation and proof of concept phase.

Conclusion and summary

If a Team get’s (soft) deleted you can restore it within 30 days by default.

Beyond 30 days, there no default or extend restore procedure to get the deleted Team to 100 % recovered as it was before.

Thirdparty solutions might provide an exception to a certain extent and add value based to extensible restore capabilities which should be thoroughly examined during an evaluation or proof of concept phase.

In case you have certain security and compliance requirements you should evaluate features provided by the Office 365 security and compliance center, Teams Lifecycle Management options based on the Graph API (https://3k09.wordpress.com/2018/11/20/whats-new-in-managing-microsoft-teams-11-2018/) as well as third party backup solutions.

Further Resources