How to remove Azure backup

Here I’m goin to show the steps to remove or disable the azure backup which is configured with Azure Virtual machine

You can go into  More and select Stop backup.

Then in next window it will ask to select whether you want to keep the backup data or remove option.

Here If you select to keep the backup data. then the storage consume charges will apply and you will be charge for that in the month end. Because of that make sure to delete the backups if you don’t want them.

Or else you  can say that under more Delete backup data.Then type the Serve name and hit enter.

It will delete the backup and now you will able to configure that with a different retention policy.

How to enable azure backup for Virtual Machine

Here I’m going to test the Microsoft Azure Backup for VM. Basically its a next next process and easy to configure.

If you want to use Azure backup for on-premise infrastructure below are the list of servers which is support by Azure backup,

 

Once you created a VM in Azure You can see the Backup configuration tab. If you created a backup job, then clicking on that will show you the status of the backup and the policy which used to setup the backup job.

If this is the first time you are creating a backup, then you can create a new vault and create a backup policy.

But If you have your own Vault created then you can assign this backup in to same vault which you have created created at an earlier date.

Here you can create the backup frequency and the retention period. assign them and click ok and then click Enable Backup to start the Job,

Then the backup status will say that Initial backup pending till the fist backup finish the job.

Hope this help you to get an idea about the Azure VM backup.

Here I have attached the pricing detail about the Azure backup and if you want more information you can refer Microsoft Pricing calculator. https://azure.microsoft.com/en-us/pricing/details/backup/

How to install PowerShell ARM

In your Azure portal, you will create Storage account, VMs, Search Services, Web apps, Virtual Network and DNS, Database servers, Third-party applications. If you want to manage and deploy them as a group, then ARM is the key point.

By using an ARM you can create, update, delete all the resource group in a single operation.

Here I have listed down the main terms that ARM used. (Copy-paste from MSTF Docs.)

• Resource - A manageable item that is available through Azure. Some common resources are a virtual machine, storage account, web app, database, and virtual network, but there are many more.
• Resource group - A container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to allocate resources to resource groups based on what makes the most sense for your organization. See Resource groups.
• Resource provider - A service that supplies the resources you can deploy and manage through Resource Manager. Each resource provider offers operations for working with the resources that are deployed. Some common resource providers are Microsoft.Compute, which supplies the virtual machine resource, Microsoft.Storage, which supplies the storage account resource, and Microsoft.Web, which supplies resources related to web apps. See Resource providers.
• Resource Manager template - A JavaScript Object Notation (JSON) file that defines one or more resources to deploy to a resource group. It also defines the dependencies between the deployed resources. The template can be used to deploy the resources consistently and repeatedly. See Template deployment.
• declarative syntax - Syntax that lets you state "Here is what I intend to create" without having to write the sequence of programming commands to create it. The Resource Manager template is an example of declarative syntax. In the file, you define the properties for the infrastructure to deploy to Azure.

If you are using an ARM , there are some benefits. specially you can save your time on doing same thing again and again in Azure portal,

I'll now show the steps that we need to follow to install ARM in your PowerShell. 

To use the cmdlets, you need to install and configure Azure PowerShell to connect it to your account.

Step 1: Install

Following are the two methods by which you can install Azure PowerShell. You can install it either from the PowerShell Gallery or from  the WebPI.

• Installing Azure PowerShell from the PowerShell Gallery

To use PowerShell Gallery. You need the PowerShellGet module to use the PowerShell Gallery. This is available here: PowerShellGallery.com

Install the latest Azure PowerShell from the PowerShell Gallery using an elevated Windows PowerShell or PowerShell Integrated Scripting Environment (ISE) prompt using the following commands:

+ Install the Azure Resource Manager modules from the PowerShell Gallery

  Install-Module AzureRM

+ Install the Azure Service Management module from the PowerShell Gallery

  Install-Module Azure

More about these commands

• Install-Module AzureRM installs a rollup module for the Azure Resource Manager cmdlets. The AzureRM module depends on a particular version range for each Azure Resource Manager module. The included version range assures that no breaking module changes can be included when installing AzureRM modules with the same major version. When you install the AzureRM module, any Azure Resource Manager module that has not previously been installed will be downloaded and installed from the PowerShell Gallery.

• Install-Module Azure installs the Azure module. This module is the Service Management module from Azure PowerShell 0.9.x. This should have no major changes and be interchangeable for the previous version of the Azure module.

Then you can test the Azure connectivity  by typing below command, 

PS C:\Windows\system32> Login-AzureRmAccount

If you can get the below mentioned windows means, You are good to go with it.

[Solved] The requested session access is denied

 

This is a known error message for IT Administrators. But I'll highlight the options that are available to mitigate this issue.

You will face this issue when you try to connect into, 

Azure virtual Server 

Windows 2012 Server 

Windows 2008/20008 R2 Server 

First, you need to check whether your enter you Admin credentials on the same RDP window is working. This would be working.

Then run the MTSC without Admin (mstsc /admin) and give your user credentials.

If that is an Azure VPC, without clicking the Connect tab on the VM control page, you can copy the Virtual machine IP address or the FQDN and use the normal RDP connection to connect.

In Azure, you can find the VPC details under Essentials tab.

Hope this will help.