We are evaluating Azure ASR for cloud Backup and Site Recovery.
Started a month ago with Backup services to backup files, folders and SQL servers and everything worked fine, MABS is installed in server A.
We have also added a physical server to Site recovery, installing the Azure site recovery on the same server A. Since then, every dashboard referring to Backup information has not been updated though its clear that GRS Storage is used for backups.
Tried to uninstall/re-install MABS without any success, any ideas? there are no errors in the MABS MMC console.
It is not recommended to install backup (MABS) and site recovery on the same machine since both Services are using similar tasks there will be lot of conflicts.
Related
I have used Azure backup service to backup single laptop/desktop over the WAN. However what if I have 100 laptop to be backed-up.
Have someone used Azure backup service to protect multiple laptop and desktops?
there are a couple of components that come with Azure backup, each of them has a specific use case as below:
1- Azure Backup (MARS) agent
Back up files and folders on physical or virtual Windows OS (VMs can be on-premises or in Azure)
No separate backup server required.
2- System Center DPM
Application-aware snapshots (VSS)
Full flexibility for when to take backups
Recovery granularity (all)
Can use Recovery Services vault
Linux support on Hyper-V and VMware VMs
Back up and restore VMware VMs using DPM 2012 R2
3- Azure Backup Server
App aware snapshots (VSS)
Full flexibility for when to take backups
Recovery granularity (all)
Can use Recovery Services vault
Linux support on Hyper-V and VMware VMs
Back up and restore VMware VMs
Does not require a System Center license
4-Azure IaaS VM Backup
Native backups for Windows/Linux
No specific agent installation required
Fabric-level backup with no backup infrastructure needed
For full info regarding Which Azure Backup components should I use?: checkout the following link: https://learn.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup
as suggested by #Vikranth S, MARS would be your best option for the use case you've described.
-Adam
There are two azure backup products which can be used to backup on-premises workloads.
Using Microsoft Azure Recovery services agent (MARS)
2.Using Microsoft Azure Backup server (MABS)
With MARS agent you can protect Files & Folders and System State of only Windows clients and server operating system, but you have to manually register each and every server with recovery services vault.
With MABs you can protect entire (Windows and Linux) Machines, if you register one server with recovery services vault, you can protect all other Machines are in same network by using that server. With MABS you can only protect Server operating system starting from Win 2008 R2. Please let me know if you have any other queries
I have 2 web applications in azure on a Standard App Service Plan (S1 Standard).
After I finish a scheduled backup configuration, it returns to the backup blade and show the following message:
"Backup and Restore feature requires your App Service plan to be Standard or higher. Click here to upgrade your App Service plan and access this feature."
Also all the backup options are grey out.
But I have a standard service plan already...
Is there other requirement that I'm missing?
Sometimes if I keep refreshing I can access the backup configuration again, but when I try to configure the backup it never finishes loading the backup options (Storage account/Schedule/Database).
Is there a problem with the backup system?
I just created a Azure Web App in South Central US location and tested its backup feature. It worked fine on my side.
Is there other requirement that I'm missing?
No, what you did is right. The issue maybe a temporary problem of Azure backup service or caused by the cache of your browser. Please clear the cache or history of your browser and try your steps again.
The last couple of days Azure Backup has been failing jobs with error 100023.
The encryption passphrase stored for this computer is not correctly configured. The encryption passphrase can be configured from the Windows Azure Backup Agent MMC snap-in. In the Action pane, click Properties and then click the Encryption
settings tab. Type the passphrase used for encryption of backups in the space provided.
I haven't changed the encryption password or location lately, so this is a bit unexpected.
At first I tought It may be an outage with Azure Backup itself but it's been a couple of days and still I'm getting the same issue.
I have since accessed the Backup Vault panel on manage.windowsazure.com and allowed re-registration for the affected server. However during the re-registration process I'm getting the same error.
Any ideas?
Download and update to the latest Azure Backup Agent (MARSAgentInstaller.exe) from the management portal at https://manage.windowsazure.com/
After doing so, try again.
This article can be used as a reference: https://azure.microsoft.com/en-us/documentation/articles/backup-configure-vault/#download-install-and-register-the-azure-backup-agent
The download page should look something like this (Windows Server agent highlighted in red):
Install the new agent from the Azure Site.
Delete the backup Jobs
De-register the server from the Azure Site
Uninstall Agent from the server
Download new registration certificate
Install Agent and point it to the new certificate.
Create a backup job and test it.
I have an application in centos VM running in amazon EC2 and now I need to migrate it to windows azure.
Is there a way to copy a snapshot to azure??
I wish to answer it step by step, but I found a link that is more than good & have almost details required to migrate an existing instance from Amazon EC2 to Windows Azure with video. The link is Guided Hands-on Lab: Migrate VMs to Windows Azure from Amazon AWS [ 20 Key Cloud Scenarios with Windows Azure Infrastructure Services ]
I hope it will help.
Well this is only possible if you are running Windows Server on your EC2 instance by following this link:
https://convective.wordpress.com/2014/07/04/migrating-a-vm-from-ec2-to-azure-at-300-mbps/
If you're running linux, currently there's no simple tool that does it, but you can go to your Azure account and follow these steps:
1- Mimic your architecture of servers on your Azure account by keeping eyes on number of VMs, Network, Storages, and other services if found.
2- Make the correct setup on those servers (configure your web server, db server, etc..)
3- Zip all of your data files found on EC2 (/var/www/Web_Folder) and use mysqldump to backup your database as well.
4- Create a windows server VM on Azure that you can connect to Remotely (Profit from the cloud internet speed) and use filezilla to download your zipped files from EC2 and then upload them back to newly created VMs on Azure. Upload your db backup file there as well.
5- Create a new database on your Azure VMs with the same old name, give user access, exit mysql and then restore your db backup file that you uploaded using: mysql -u root -p DB_Name
Just an update, Now you can accomplish this task using Azure Site Recovery this is a super easy task. In site recovery once you do failover all the virtual machines will automatically gets created which means with minimal or no downtime the migration can be performed https://azure.microsoft.com/en-in/documentation/articles/site-recovery-migrate-aws-to-azure/
I configured Windows Azure Backup on my VM hosted on Azure. I did manage to create and upload a certificate following this tutorial and this tutorial.
I downloaded the server agent to the VM and configured it, I then managed to perform a manual backup and it worked fine.
However I scheduled it to run every day at 3am using the wizard provided and it's not running. I check every day, and the last backup that is listed is the one I did manually. The dashboard in the Backup Server Agent shows it's scheduled, but it's not running.
I tried leaving the agent open overnight, and it didn't help.
Any insight on the situation will be helpful.
Thanks,
After checking my VM's event log, I figured out that the backup wasn't running as expected due to limited space in the HD. After I cleared some space it started running as expected.