Azure Backup support for SQL Server 2019 and Restore as files

As SQL Server 2019 continues to push the boundaries of availability, performance, and data intelligence, a centrally managed, enterprise-scale backup solution is imperative to ensure the protection of all that data. This is especially true if you are running the SQL Server in the cloud to leverage the benefits of dynamic scale and don't want to continue using the legacy backup methods that are tedious, infrastructure-heavy, and difficult to scale.

We are excited to share native backup for SQL Server 2019 running in Azure Virtual Machine. This is a key addition to the general availability of Azure Backup for SQL Server Virtual Machine, announced earlier this year.  Azure Backup is a zero-infrastructure solution that protects standalone SQL Server and SQL AlwaysOn configurations in Azure Virtual Machine without the need to deploy and manage any backup infrastructure. While it offers long-term retention and central monitoring capabilities to help IT admins govern and meet their compliance requirements, it lets SQL Admin continue to exercise the power of self-service backup and restore for operational recoveries.

In addition to this, we are also sharing Azure Backup general availability for:

 SQL Server 2008 and 2008 R2 migrating to Azure as SQL Server running in virtual machines.
SQL Server running on Windows 2019

Restore as files:

Adding to the list of enhancements is the key capability of Restore as Files, now restore anywhere by recovering the backed-up data as .bak files. Move these backup files across subscriptions, regions, or even to on-premises SQL Servers and trigger database restore wherever you want. Besides aiding cross-subscription and cross-region restore scenarios, this feature helps users stay compliant by giving them greater control over storing and recovering backup data to any destination of their choice.

 

Getting started:

Under the Restore operation, you will see a newly introduced option of Restore as files. Specify the destination server (this server should be SQL Server Virtual Machine registered to the vault) and path on that server. The service will dump all the .bak files specific to the recovery point you have chosen to this path. Typically, a network share path or path of a mounted Azure File share when specified as the destination enables easier access to these files by other machines in the same network or with the same Azure File share mounted on them.

Once the restore operation is completed, you can move these files to any machine across subscriptions or locations and restore them as a database using SQL Server Management Studio. Learn more.

Additional resources

Watch the getting started video.
Want more details about this feature? Review the Azure Backup for SQL Server documentation.
Get the Azure Backup pricing details for this feature.

Quelle: Azure

Change feed support now available in preview for Azure Blob Storage

Change feed support for Microsoft Azure Blob storage is now available in preview. Change feed provides a guaranteed, ordered, durable, read-only log of all the creation, modification, and deletion change events that occur to the blobs in your storage account. This log is stored as append blobs within your storage account, therefore you can manage the data retention and access control based on your requirements.

Change feed is the ideal solution for bulk handling of large volumes of blob changes in your storage account, as opposed to periodically listing and manually comparing for changes. It enables cost-efficient recording and processing by providing programmatic access such that event-driven applications can simply consume the change feed log and process change events from the last checkpoint.

Some scenarios that would benefit from consuming a blob change feed include:

Bulk processing a group of newly uploaded files for virus scanning, resizing, or backups.
Storing, auditing, and analyzing changes to your objects over any period of time for data management or compliance.
Combining data uploaded by various IoT sensors into a single collection for data transformation and insights.
Additional data movement by synchronizing with a cache, search engine, or data warehouse.

How to get started

To enroll in preview, you will need to submit a request to register this feature to your subscription. After your request is approved (within a few days), any existing or new GPv2 or blob storage accounts in West US 2 and West Central US can then enable the change feed feature.

To submit a request, run the following PowerShell or Microsoft Azure CLI commands:

Register by using PowerShell

Register-AzProviderFeature -FeatureName Changefeed -ProviderNamespace Microsoft.Storage

Register-AzResourceProvider -ProviderNamespace Microsoft.Storage

 

Register by using Azure CLI

az feature register –namespace Microsoft.Storage –name Changefeed

az provider register –namespace 'Microsoft.Storage'

Once you’re registered and approved for the change feed preview, you can then turn it on for your storage accounts and start consuming the log. For more information, please see change feed support in Azure Blob Storage and process change feed in Azure Blob Storage. As with most previews, this feature should not be used for production workloads until it reaches general availability.

Cost

Change feed pricing is currently in preview and subject to change for general availability. Customers are charged for the blob change events captured by change feed as well as the data storage costs of the change feed log. See block blob pricing to learn more about pricing.

Build it, use it, and tell us about it

We will continue to improve our feature capabilities and would like to hear your feedback regarding change feed or other features through email at AzureStorageFeedback@microsoft.com. As a reminder, we love hearing all of your ideas and suggestions about Azure Storage, which you can post at Azure Storage feedback forum.
Quelle: Azure