Hi All,

I am facing an issue while running azure backup on one windows VM. The VM is created from Azure marketplace windows 2016.

There are three VMs in the same RG and on two VMs the backup is running fine however on one VM I am getting the following error "VM agent is unable to communicate with the Azure Backup Service".

I have followed the given document on the azure portal website and everything seems to be OK. Are there any logs which can lead me to the right direction ?

Initial Azure backup (Windows desktop PC on peer to peer network in small business) is taking a VERY long time.

Total file volume is about 200Gb, and about 160,000 files.

Backing up from Windows 10 Pro computer. (No server present).

Computer is new. Clean install of Win 10 Pro. Folders/Files then transfer from another computer.

Using Azure Backup for the first time.

Agent configured to run at 9.30pm each night.

Initial backup triggered 9.30pm on Sunday 21 July.

It is now 9.30am on Wednesday 24 July, i.e. 60 hours later.

(Backups on Monday and Tuesday night failed because the earlier one was still in progress).

If I double click on the Job in the "Microsoft Azure Backup" view in Microsoft Management Console I'm told "Data transfer is in progress. It might take longer .. etc". And, after running for 60hours continuously, the Data Transferred column says only "8.43Gb"!

The computer has been used only lightly for other tasks for about 1-2hr during that 60hr period.

Internet activity from other devices on the peer-to-peer network has been light and totalling only 2-4 hours.

A few weeks ago I downloaded 4+Gb Win 10 Pro installer (to another computer using the same internet connection) and this completed in several hours.

In the Azure Backup documentation that I read prior to setting up Azure Backup, it said to consider offline backup if there were several Tb to backup - but I had only 200Gb (0.2Tb) so I thought it would be fine.

I'm in Perth in Western Australia. Internet connection is broadband, but we are not on the nbn yet.

Backup is to the Melbourne data centre.

Windows Defender and Malwarebytes are installed and running.

How long is it going to take because it's severely interfering with my work?

I'm debating whether to cancel and then use offline backup - but that involves trusting disk transport and I'm loath to do that unless necessary.

What should I do please?

Scheduled backups won't take place on my Win2k8r2 and Win2k12 servers.  They only seem to be working on my Win2k16 servers, and Win7 / Win10 clients (all on-premises). I set my scheduled backup items in the Backup Agent windows application, everything looks fine, application status states correct next backup time, the time comes and goes, and the status simply changes to waiting for the next schedule backup time. No errors, the Task Scheduler history states task and action has completed successfully but no completed job is listed. Manually running the backup works fine.  This is for an on-premise VM with the Backup Agent installed on the Win2k8r2 guest.

  -- Mike

Hi, I have an issue with the Azure backup not running on schedule. I have followed the tips here https://t.co/mXWTe99keg but this hasn't resolved it.

I am using MARS version 2.0.9052.0 and I can run the backup manually successfully.

The scheduled task is running:



The execution policy has been set to Unrestricted:

I have tried running the command from the argument in the task scheduler directly in powershell I received these errors:

I've tried stopping and recreating the schedule to no avail.

Dear Community,

Announcing a recent change in behavior to the Azure Backup service. This change impacts the waybacked-up items are deleted from the vault. 

If you encounter the error below while attempting a deletion, perform one of the following to resolve (depending on your scenario).

1. Stop protecting a VM  - for Cloud scenarios (e.g. IaaS VM backup, AFS)

 2. Delete backup items from management console - for On-premises scenarios (e.g. MARS, MABS, DPM-to-Azure)

Hi team

We're looking to harness azure backup for azure file shares (currently public preview), however I'm struggling to find the costs associated for it. We have about 75TB of data in various azure file shares. 

Is there a cost calculator out there / a rough estimate I can pass onto my customer please?

Thanks!

Hello,

We have a Windows server with Azure backup. It is configured to back up once a week.

When I log into Azure, and goto: Home > "ResourceName" > Backup Infrastructure > Protected Servers (Azure Backup Agent) > "Server Name" > Backup policy,

It shows Backup Frequency as follows:

This has been mentioned a few times, like in https://social.technet.microsoft.com/Forums/en-US/f8de03b6-b97b-4c7b-940f-7a8c72303427/critical-alert-backup-failure-this-operation-cannot-be-performed-now-because-a-backup-or-restore?forum=windowsazureonlinebackup

On some VM's (spread across different companies, OS and internet connections) we get "This operation cannot be performed now because a backup or restore operation is currently in progress.", this is either an intermittent error or on some VMs it happens on every MARS Agent scheduled backup job. We're only backing up files and folders.

When this happens, it looks like the MARS Agent is spawning two jobs instead of just one at the scheduled time. There are no other backups running at this time.

I've tried re-creating the schedule (i.e following the wizard again) but that doesn't help. I've re-installed the MARS Agent and ensured it's on the latest version at the time of writing this 2.0.9167.0

What does seem to help, is changing the schedule altogether, i.e the one common thing I noticed is a lot of the jobs run at 0100, if we change this to 0130 we don't seem to encounter further errors. The event logs don't really show anything else running/happening at 0100 that would account for this tho.

I'm unclear on if this will change our retention as the schedule wizard then says to keep the restore points at the new time slot rather than the old - I cannot afford to lose all of the previous restore points on some of these VM's.

Can anyone advise on the best way to resolve this? If I change the scheduled time to 0130 (which automatically changes the retention policy to that time also) will I lose all my previous retention/restore points?  If I change it to 0130 and then immediately back to 0100 again will I lose the previous retention/restore point? Or is anyone aware of a different fix altogether?

Any help is very much appreciated.

good day

we have a storage account with a file share configured. i need to protect this storageaccount with azure backup. i have found different information about the support of storageaccount with vnet/firewall enabled.

"The support to Backup File shares in accounts with VNET is now available in preview in WCUS and AE" -> docs.microsoft.com as answer for a user question

"Azure Backup now supports storage accounts secured with Azure Storage Firewalls and Virtual Networks" -> azure.microsoft.com

"You can't protect Azure file shares in storage accounts that have Virtual Networks or Firewall enabled." -> docs.microsoft.com

at the moment, we have firewall/vnet enabled on the storageaccount. azure backup does not find a storage account to protect, even when i have the option "Allow trusted MS Services to access this storage account" enabled.

If i disable firewall / vnet i'm able to configure the azure backup job for this storageaccount. so it seems, at the moment it is not supported.... even if some documents say it should work

->> What is the official statement about azure backup for storage accounts with enabled firewall/vnet. When can we expect it to work in europe region?

Thanks

Been using MABS for quite some time now and it's great however I noticed lack of a function (or misconfiguration)

In my short-term goals I have retention set to 5 days meaning and Syncronization frequency has been set to every 15 minutes.

When I perform a restore of the database within last 5 days I can choose specific time that I want to restore it from (with 15 minute intervals) which is great however if I go older than that I only get single full backup.

My understanding is that the log backups are being saved in Cloud and that only full backups are available there.

Is there a way to keep those 15 minute transaction logs in cloud and be able to restore not just the full backup but also a more specific point in time restore when it comes to restoring from cloud?

Does any one knows how much years consider a Steady State in the calculator? I see that amount of data increase according with the churn rate Low.

Example 

Hello

Could you please advise how much space I need for Azure Snapshots or what is the common practice. For example if I would like to make Premium subscription and add 1000GB limit to my Azure File shares, how much should I add for Snapshot limit? 

Best Regards

Anti

Hi,

UBUNTU 16.04
We've a linux azure VM wherein the backup failed "Could not communicate with the VM agent for snapshot status - Snapshot VM sub task timed out". Manual backup failed with the same error.

We checked - Agent (Ready state) & 2.2.32 version. We tried restarting the agent but it fails with connection timed out as an error. The same happened while trying to update the agent as it was not able to stop the running walinuxagent.service & the process got stuck so we abandoned it.

systemctl restart walinuxagent.service - doesn't work
systemctl stop walinuxagent.service - doesn't work

Please let us know how to resolve this issue & initiate the backup again 
Following the \var\logs\waagent.log 

2019/07/01 06:25:04.525782 ERROR ExtHandler Event: name=Microsoft.Azure.RecoveryServices.SiteRecovery.Linux, op=Download, message=[ExtensionError] Non-zero exit code: 1, A2aVmExtension/handler.py disable
[stdout]
2019/07/01 06:25:02.516906 INFO ExtHandler Move process 28936 into cgroup for extension Microsoft.Azure.RecoveryServices.SiteRecovery.Linux


[stderr]
Traceback (most recent call last):
  File "/var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9117/A2aVmExtension/handler.py", line 32, in <module>
    from A2aVmExtension.CmdHandlers.install_and_configure \
  File "/var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9117/A2aVmExtension/CmdHandlers/install_and_configure.py", line 39, in <module>
    from main.ExtensionLib.utilities import get_cmd_output
ImportError: No module named main.ExtensionLib.utilities
, duration=0
2019/07/01 06:25:04.539348 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Target handler state: enabled
2019/07/01 06:25:04.540780 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] [Enable] current handler state is: notinstalled
2019/07/01 06:25:04.541169 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Using existing extension package: /var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery__LinuxUBUNTU1604__1.0.0.9118.zip
2019/07/01 06:25:04.541328 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Unzipping extension package: /var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery__LinuxUBUNTU1604__1.0.0.9118.zip
2019/07/01 06:25:04.793542 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Initialize extension directory
2019/07/01 06:25:04.795868 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Update settings file: 0.settings
2019/07/01 06:25:04.797549 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9117] Disable extension [A2aVmExtension/handler.py disable]
2019/07/01 06:25:04.801784 INFO ExtHandler Move process 29005 into cgroup for extension Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604
2019/07/01 06:25:06.809827 ERROR ExtHandler Event: name=Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604, op=Download, message=[ExtensionError] Non-zero exit code: 1, A2aVmExtension/handler.py disable
[stdout]
2019/07/01 06:25:04.801784 INFO ExtHandler Move process 29005 into cgroup for extension Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604


[stderr]
Traceback (most recent call last):
  File "/var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9117/A2aVmExtension/handler.py", line 32, in <module>
    from A2aVmExtension.CmdHandlers.install_and_configure \
  File "/var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9117/A2aVmExtension/CmdHandlers/install_and_configure.py", line 39, in <module>
    from main.ExtensionLib.utilities import get_cmd_output
ImportError: No module named main.ExtensionLib.utilities
, duration=0
2019/07/01 06:25:06.896216 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118] Remove extension handler directory: /var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.LinuxUBUNTU1604-1.0.0.9118
2019/07/01 06:25:06.916748 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9118] Remove extension handler directory: /var/lib/waagent/Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9118
2019/07/01 06:25:09.939578 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9118] Target handler state: enabled
2019/07/01 06:25:09.940387 INFO [Microsoft.Azure.RecoveryServices.SiteRecovery.Linux-1.0.0.9118] [Enable] current handler state is: notinstalled
"waagent.log" [readonly] 16542553L, 2311268155C                                                                                                      1,1           Top

Regards,
Gaurav N.

So here is the situation. We started using Recovery Services backing up our onprem servers via MARS. After we realized the default options for our vault were GRS we created a new vault with the LRS setting. Migrated all over our servers over to it. One server is out of commission and we are unable to unregister the MARS agent. It appears without doing this you cannot delete the vault because of the orphaned backup items inside the vault. Following the documentation here does not allow us to delete the backup item. https://docs.microsoft.com/en-us/azure/backup/backup-azure-delete-vault

When you go to the Backup Items and click on the server name and go to delete you enter in the server name and click confirm deletion and nothing happens. No delete, no error, nothing. 

I have also tried deleting this via powershell it seems I can't target any container.Get-AzureRmRecoveryServicesBackupContainer Does not let me pull any containers. 

<rant> Many guides/walkthroughs/documentation I have found is full of deprecated commands or screenshots that no longer look/function anything like the modern Azure. This is the primary problem with cloud/web platforms in my opinion same thing experienced with Sophos/SonicWALL firewalls. Many of the revisions change the interface/commands so much that you are constantly learning how to manage the hardware/services. Microsoft you have done so well with your Server OS's in the past few years and powershell is a strong utility. But Azure seems like a clustered mess everytime I use it for enterprise work it is more of a headache than it is worth... </rant>      

I have a VM running on a Windows 10 machine that has the client Hyper-V role installed on premises. I back up the drive containing the VM to Azure using the Windows 10 Azure Backup tool, so the VHDX file and the VM configuration info is in Azure. How do I make this VM into a running Azure VM if my on-premises machine becomes unavailable? 

Azure does not recognize the files as a VM since they are part of a backup (which is expected) so I assume I'd need to somehow get the VM information from the Recovery Services vault into a state where it can run as an Azure VM. How do I do that?

The Azure Backup tool for Windows 10 doesn't allow me to back up the VM to Azure in a way Azure will recognize as a VM (that option is for Windows Server only, I think). 

Thanks in advance for the help. 

Hello Team,

Getting Below Error in MARS

Azure Backup is unable to initialize internal data structures please contact support for solution 0X07ef7.

We have updated latest MARS agent, done AV Exclusion still getting same error.

APK

I am trying to use the MARS agent to backup files and folders to a Azure recovery services vault, it works fine on non encrypted drives but fails when the drive is encrypted. 

Does anyone know how to get around this?

Thanks in advance!

how to export Azure Database for MySQL server to blob from azure cli ? 

can i keep the backup for over 35 days in blob and still be able to restore it ? if so how to do ut from azure cli ?

i have tried via az sql db export command but i am confused about what is : storage-key-type, name and storage-key that it seems to be obligatory parameters in this command 

Hello,

We began using Azure Backup (MARS) back in January.  It's been mostly pretty good, but occasionally we will have inexplicable failures, most with the error:

0x80990A60 Unable to find changes in a file.

Reviewing the Event logs and MARS/Azure Backup logs, it appears as though what's happening is the scratch VHD file the agent is creating is corrupted for some reason.

I've seen other folks advising people to check that there is both at least 5% free disk space and 5-10% of total backup size available on the volume the scratch VHD is created on.  I can confirm in this case, we have plenty of space in both cases.

I've run chkdsk on the volume, no issues.

Has anyone else run into this / does anyone have any ideas?

Thanks,

Erik