>> Want to know all the details about how Azure Backup
and restore works for SQL Server on Azure Virtual Machines?
Learn all about it this week on Data Exposed.
[MUSIC].
>> Hi, I'm Anna Hoffman and welcome
to this episode of Data Exposed.
Today I have two special guests joining us.
One we have Logan joining us again.
Logan thanks so much for coming back on the show and we
also have Kartik joining us today.
Can we start with a little bit of intros, Logan,
maybe if you can remind folks who might not have
seen you before what you do.
>> Thank you for having us
again and it's great to be back on Data Exposed.
My name is Logan Carrington and I'm a member of
the Azure Relational Database Marketing team folks and
Product Marketing for SQL Server on Azure Virtual Machines.
>> Awesome. Cool. It's great to have you back.
Kartik, what about you?
Tell us a little bit about yourself.
>> Thanks Anna for having me,
my name is Kartik and I'm a Senior Program Manager
from Azure Business Continuity and Disaster Recovery team,
I deal with specifically in database,
backups and disaster recovery.
Excited to be here at Data Exposed.
>> Awesome, cool. It's great to have you on the show and
you're the great person to talk to us about
Azure Backup and restore to
SQL Server or for SQL Server on Azure Virtual Machines.
We hear a lot about customers lifting and shifting from on-prem to
VMs and a big reason is business continuity and HADR.
As customers think about this,
I want to understand what are some things that people are
expecting of their backup solution
and then how are some ways that we can help?
>> Backup solution must know how to do a couple things,
however, first, a backup solution must connect the database.
From there, a customer can expect SQL commands to
trigger backups where BI OnDemand or it's going to periodically,
then verifying with a source of truth and even integrating with
underlying storage snapshots for even very large databases.
>> Got it, makes sense. After they
backup the data or generate the backup,
what does a customer or what does the service do next?
>> Great question, Anna. After generating the backup data,
as I just previously mentioned,
a customer should expect to have
backup storage management offered.
In this process, you start with transferring and retrieving
data to and from Azure.
This includes backup data like management in Azure,
dependency checks for deletion,
handling high availability which you just mentioned,
otherwise known as AJ configurations,
Terry options or cost management and redundancy for backup data.
>> Cool. Makes sense. Definitely have
a lot of this expectations for all good reasons.
But switching a little bit of gears,
a lot of stuff has been happening
or fears around things like ransomware.
Another big part of backups is often like trying to
understand is my customer data protected,
especially when it comes to SQL Server on
Azure VMs against ransomware?
>> Yeah, in the era of the virtual world,
honestly just connecting the database and
managing the backup data is just not enough, Anna.
The backup solution should also offer
customer security, especially against ransomware.
Also in terms of governance, the
customer's probably asking themselves,
how do I make sure my important servers are protected?
Management at scale when it comes to how to
build business continuity and disaster recovery,
otherwise known as BCDR
because those have hundreds of SQL servers.
This is actually where Azure Backup for SQL comes into play.
In a talk more about it,
I'll actually handed over to Kartik. Kartik over to you.
>> Thanks Logan. As you mentioned,
apart from the basic requirements of
the cool workload, backup and restore,
these new requirements in terms of security,
governance and management at
scale forms key criteria for a customer to select
a backup solution and here is where Azure Backup comes in.
VR in Azure,
integrated business disaster recovery solution
that offer native work-load integration,
scalable storage, and building management at scale.
Here on the screen I would like to show
an overview of the solution.
As you can see on the screen at the bottom layer,
Azure Backup offers a diverse and mission
critical workload support natively.
As you mentioned, the backup data goes into Azure Backup storage.
In here what we can call as modern Erica,
the backups are stored securely offsite in
Azure Backup storage but
make it also offers you resiliency as well.
In resilience stories there,
multiple access to use
we had built up in terms of restore performance
and cost optimization and
especially I want to talk about the built-in security.
We do have a comprehensive out-of-the-box package solution
in terms of security,
authorized access for your RBAC,
encrypting your data using customer managed keys,
a soft delete for protection against
accidental deletion scenarios and
then multi-user authentication and
immutability for protection against ransomware is one of
our core offer links in terms of built-in security.
At the top, you can see about management at
scale and this is especially helpful
for enterprise customers who have hundreds of machines.
Azure Backup center,
it is a single unified management experience
you can fit a single pane of glass to
view all your backups and they also
leverage as you need to other Azure native services.
For example, you can use Azure Policy to make sure,
you know the backup is status complaint.
Make sure your keys are protected or you
can use Azure Resource Graph to export metadata.
You can monitor your hundreds of backups and restores,
leveraging Azure Monitor-based experience.
You can automate using not just portal,
but not only auto machine clients like PowerShell,
CLI, SDK Terraform, etc.
All of this from one single place, just a backup center.
This is what Azure Backup has to offer in
terms of not just need to upload integration,
resiliency, access and cost management,
built-in security and management at scale.
Now these are values that automatically accrue to every server.
Let's move to the other slide
where I'm going to explain a little bit
about what do we offer specifically for SQL cells.
Here you can see in the screen that Azure Backup for SQL
is natively integrated with the SQL various streams.
The data is streamed directly from within
the VM to what we call as the recovery services vault.
A vault is nothing but a place to store your backups..
It's completely zero infrastructure,
you don't need any additional backup server.
We do have support for
the HA configurations that Logan mentioned earlier,
especially AlwaysOn AG,
they give 15-minute RPO,
especially we support long-term retention.
If you want to store data for 10 years,
it is possible and we even give
archive support to make sure that it is optimized on cost as well.
We do offer point-in-time recovery,
central management and hey,
if you are adding a new database, a service,
just use data protection and
the whole experience is very simplified.
The onboarding experience is pretty simple,
just login into Azure portal,
discover the SQL databases and configure backup.
This is how if an enterprise is looking to backup
their anti SQL st. Just to
add here on the screen that the backup data is extreme,
but we're also adding the snapshot support.
With this, what I can say is it doesn't matter where
the database is, small, medium, large.
Production landscape that uses AlwaysOn or doesn't,
Azure backup for SQL becomes
one single backup and recovery solution.
Simply just simple, secure, cost-efficient,
and also offers on-demand services that I mentioned above.
It will just let you know the starting point,
this is my Azure put to to screen.
I can just click "Backup Center" in the services you can
see that the backup center is present.
I click and this is
the single landing page where
you start your journey with Azure Backup.
You can see that it has collected
all the backup information across multiple subscriptions,
multiple tenants, multiple regions, all in a single place.
Please, you just start,
just click press Backup, you can select, hey,
I want to protect my SQL databases in Azure VMs select the vault,
the vault is again a place to store your backups,
select a vault,
and then continue, that's it,
It is as simple as picking few buttons.
A customer may not learn about
complexity SQL commands and syntaxes,
they do not have to worry about
the recovery chain, they do it for you.
They also make sure that the dependency chain is intact,
we don't delete any files inadvertently,
all of this comes natively inbuilt with Azure backup for SQL.
>> Oh awesome,
this is really cool, Kartik,
and what I love is just how easy it is and also how you set
the unit scale and how you've
all this visibility into some of
the different things that are here.
What else is here?
>> Yes. There are a backup simply can't
see that there are multiple sections.
There's a manage section there you can view your entire,
on the landing page you can see that
immediately it shows you how to operate.
Monitor all the jobs in the last 24 hours,
just click them and go over to that.
Please if you hit us an overview of what you already protected,
synchronize we can see that the aggregate of
all the sequence was protected and here we're also
integrating with Azure Monitor-based electing system.
This is a landing page,
you have options to configure, backup, restore,
create policies and volts,
on the left-hand side you can see we've a host of
other central management experience that we just talked about.
Monitoring and reporting,
monitor your backup estate using the jobs,
use Azure, monitor,
click and configure alerts and then get electrically notified,
use metrics where to get,
there are few short variations.
We have also analysis reports.
You want to go back to
backup data to analyze what this might cost.
You have data in using lot electrics space,
which is again an inbuilt service of Azure Backup.
Then in the backup compliance section,
you can see that you can authorize your policies.
This is just to make sure that
the entire Azure Backup data is protected.
You can use policy to
determine the important resources should always be backed up.
Just to give a second, the screen is loading and then this place,
I would say Azure Backup center becomes
single landing page for you to configure backups,
operate them, monitor them,
analyze them, govern them all from one single place.
>> Awesome, cool. This is great to see.
I know sometimes the demos
sometimes don't work when we share our screens and stuff,
but it's great to see
all the different things that are available here.
As we think about closing the show,
are there any tips or
tricks that you have for folks as they get started with this?
>> I have a documentation link ak.ms/azurebackupforSQLinAzureVM.
That should be fantastic place to start because we
have the architecture discussions troubleshooting guidance.
Because if backup and recovery
support when it's everything recorded there,
there should be a really good starting point
and just user solution is generally available.
Please just use it and give us feedback.
>> Awesome. Cool. Thanks Kartik,
thanks Logan so much for coming on Data Exposed.
For our viewers, if you want to learn more,
we'll put links in the description for you to learn
more about everything that was talked about on the show today.
If you like this episode, go ahead, give it a like,
leave us a comment and let us know what you think
and we hope to see you next time on Data Exposed.
[MUSIC]