Month: September 2021

If you think about backup in Azure – probably you think about Recovery Services vaults. But there is currently a new possibility named Backup vaults. Of the box, you can configure backups every 4 hours. Currently, it supports: VM Managed Disk Backups (Snapshot) Azure Blobs Azure PostgreSQL Databases You can create ad-hock backups using portal or PowerShell. If you using PowerShell and see an error like: Backup-AzDataProtectionBackupInstanceAdhoc : Input provided for the call is invalid Probably you are using wrong parameter for -BackupRuleOptionRuleName it should be: -BackupRuleOptionRuleName “BackupDaily” Or -BackupRuleOptionRuleName “Daily” Note “Default” like mentioned in Documentation. Here is a code that can be implemented in the Azure function to do backup every 1h. param($Timer) Install-Module -Name Az.ResourceGraph -Force Import-Module -Name Az.DataProtection Import-Module -Name Az.ResourceGraph Get-InstalledModule $VaultBackupRG=”xxxx” $VaultBackupName=”xxxx” $AzureFunctionAppID = “xxxx” $AzureFunctionAppPwd = “xxxx” $TennantId = “xxxx” $SubscrybtionDev=”xxxx” $User = $AzureFunctionAppID $Pass = ConvertTo-SecureString -String $AzureFunctionAppPwd -AsPlainText -Force $Credential = New-Object System.Management.Automation.PSCredential $User,$Pass # Get the current universal time in the default string format. Write-Host “Logging to Azure….” Connect-AzAccount -Credential $Credential -TenantId $TennantId -ServicePrincipal Set-AzContext -Subscription $SubscrybtionDev Write-Host “Logged In and Starting Processing….” $AllInstances = Get-AzDataProtectionBackupInstance -ResourceGroupName $VaultBackupRG -VaultName $VaultBackupName Backup-AzDataProtectionBackupInstanceAdhoc -BackupInstanceName $AllInstances[0].Name -ResourceGroupName $VaultBackupRG -VaultName $VaultBackupName -BackupRuleOptionRuleName “BackupDaily” $job … Azure Backup vaults – New era of snapshot backups – backup every 1hRead more

Azure Managed Application is not widely used, just to create it we must use ARM templates. Sometimes it is a must when you want to deploy a solution via Azure Marketplace. Managed Application is simply a set of Azure Resources that usually can not be managed/modify by the person who deploys it but by the creator. So it is a very useful way to distribute an application across your organization or via mentioned Azure Marketplace. You can start with this simple code: #mf@fast-sms.net $Subscribtion=”ed4838b9-2782-4ada-xxxx” $tenant=”50ea0418-683d-4007-87fb-xxxx” az login –tenant $tenant az account set -s $Subscribtion az group create –name ManagedApp –location eastus az storage account create –name mfmanagedapp –resource-group ManagedApp –location eastus –sku Standard_LRS –kind StorageV2 az storage container create –account-name mfmanagedapp –name appcontaineroracle –public-access blob az storage blob upload –account-name mfmanagedapp –container-name appcontaineroracle –name “app.zip” –file “app.zip” $groupid=$(az ad group show –group group_in_azure_ad –query objectId –output tsv) $ownerid=$(az role definition list –name user_in_azure_ad –query [].name –output tsv) az group create –name appDefinitionGroup –location westcentralus $blob=$(az storage blob url –account-name mfmanagedapp –container-name appcontaineroracle –name app.zip –output tsv) $blob $groupid $ownerid az managedapp definition create –name “ManagedStorageMF” –location “westcentralus” –resource-group appDefinitionGroup –lock-level ReadOnly –display-name “Managed Storage Account MF” –description “Managed Azure Storage … Azure Managed ApplicationRead more

It is not well-known information that after creating AWS EKS Cluster the person (user) who created the cluster must give rights to other persons to use kubectl. If the person is not available you will not be able to login to Kubernetes Cluster. We can try to create the same user again and try to move permission to another user.   So it the important to move the permission to the next person, just after creating the EKS cluster: eksctl create iamidentitymapping –cluster clustername –arn arn:aws:iam::XXXXXX:user/destination_user_name –group system:masters –username destination_user_name   The eksctl is a parser for kubectl. Or the best option can always use the DevOps process for creating not only EKS but all resources. When EKS was created using role you can try one of four scenarios: https://stackoverflow.com/questions/50791303/kubectl-error-you-must-be-logged-in-to-the-server-unauthorized-when-accessing