Skip to main content

Automated Backup - Windows Azure Web Sites

We have a new feature available for Windows Azure Web Sites – we can create backups automatically of our site and database that can be used later on.
To be able to use this feature, you will need to change the web site mode from free to standard. Only for standard web sites this feature is available. When you are in the standard mode you have multiple instance sizes and you can scale your site automatically.
From the cost perspective you should know that there are no additional cost to it (automatically backup feature). You only pay the space used by the backup on the storage. This is a nice think, we have another nice service that is free.
When we activate the automated backup feature we will need to specify the storage account where we want to make the backup and what is the frequency. In this moment we can specify only in days the frequency, but I don’t see this a real problem. In normal cases, you don’t want to make a backup every 5 minutes. Beside this, you can specify the time when the backup is made. In general we prefer to make the backup during the night, but based on your client location, night can mean 03:00 UTC or 14:00 UTC.
A nice feature available is the ability to include not only the site but the database that is used by your site. In general, the most important information can be found in the database. This is the place where data is changing very offer and you don’t want to lose it.
Any database that is linked to your site can be backup. What is nice is that you can create a backup for not only SQL but also for MySQL.
Once you configure all this, the last thing that you need to do is to hit “Save” button. And wait, we have something more. You can trigger the backup manually. To use manual backup feature you don’t need to activate the automated backup, you only need to configure what is backup and where.
The most complicated step is the restoring (or not). From the same tab we can navigate to the restore action that give us the ability to restore the web site and database from our storage account or from a file that is on another storage account.
I would recommend this feature especially for the database backup and how easily you can restore your web site. Please be aware, don’t use this feature if you write in the web site directory pictures or data uploaded by the clients. In this case you should store the data directly to Windows Azure Storage Blobs.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP