Backup local onprem to Azure

Hello,

it seems that the backup process is blocked by a firewall.

The firewall can be local on the servers, or globally the firewall network.

Right.  I read that the 130001 might be a firewall issue, but it is not.  The firewalls on the servers are off and there is nothing blocking inside\out traffic.  I have also confirmed that I can reach every URL required for the Azure backup to work.

Ok, it seems that you can access the needed URL from your account when the session is open.

But, are you sure that the computer, under its system context, has the same Internet access?

Do you have a proxy or something like that? Does it need authentication?

No proxy.  No authentication.  It's pretty wide open for testing.  That being said, I'm still curious about the "needs" to make this work.  For example, do I just install the agent on the server and then use the MABS to schedule the backup or so I install the agent on the server and put MABS on a different server and manage it from there?

From what I read, once my backup vault is created and I've downloaded the key, I should just be able to schedule the backup, but that's when I run into the 130001 error.  There only a couple of suggested fixes for that and I've eliminated both, or made sure those two are not my issue.

Phillip, I use Veeam on other sites and yes, it's pretty sweet.  Sadly, this client is all Hyper-V and I need to know this stuff, so I'm going to bang it out.  I feel sure it's something I missed, so I'll keep plugging away at it.  I appreciate your recommendation though.

:)  I appreciate the sage advice; however, I prefer to use the tools available versus buying something else that's easier because I won't invest the time to learn what I have.  Make sense?

Rest assured, we have backups and we have backups of the backups off-site.  No computers were harmed while testing.  I just want to get past the 130001 error and have a nice onprem environment backed up to the cloud.

 Each host runs several VMs and I want to backup the VMs to the Azure cloud.

I believe you should be able to just use the MARS backup for Windows servers https://learn.microsoft.com/en-us/azure/backup/tutorial-backup-windows-server-to-azure instead of MABS server as you noted above. 

From what I read, once my backup vault is created and I've downloaded the key, I should just be able to schedule the backup, but that's when I run into the 130001 error. 

So when do you exactly get the error from link above? When you "4. Register" the vault under "Install and register the agent" OR when you "Schedule backup"  under "Configure backup and retention" Here are few other things to check: 
1. anti virus https://learn.microsoft.com/en-us/azure/backup/backup-azure-manage-mars#configuring-antivirus-for-the-mars-agent 

2. "If the vault-file is located on a network share the wizard will fail. So a pretty simple fix, move the vault-file to a local storage and try again."

3. worst case you can go into Azure and delete the server out of the Recovery Vault assuming you (obviously) didn't backed up anything yet. Then rerun the installer again and it should register.

4. Verify Internet Access and allow FQDN's as mentioned here https://docs.azure.cn/en-us/backup/install-mars-agent?view=azs-2102#verify-internet-access

Thank you Icohan.  I am reading and following the first article you reference there.  

I get the 130001 Error after downloading the vault creds and trying to register the server.

What I DID just learn is that I am ALSO using the local windows backup to backup the server to an offsite location on the other side of our VPN.  I am wondering if the existance of the local backup, and it's schedule, might be preventing me from doing the backup to azure. 

I'm testing that now.

I don't think the local backup to offsite is causing the failed Azure vault MARS agent registration but for sure you don't want that one running at the same time and I would just try to make sure the "Location for the installation and cache folder." is on a local drive and permissions set to "everyone" FULL on it just to eliminate that constraint. 

You are right Icohan.  I removed the off-site backup from the local BU schedule and it made no difference.  I just tested to make sure the server could reach the URLs MS suggests and that's good.  Nothing in event viewer either.  SO irritating.  

Wow...that must be frustrating indeed...What about "Location for the installation and cache folder." and AV? I assume the folder is on local disk right and AV restrictions taken care of...not much else I can think of ATM...

No Av on the servers and all good on the installation and cache.  I mean the servers are new installs, like six months old and the MARS install is new.  I'm going to try a reboot tonight and see what happens.